Compare / Guru
Landing Platform vs Guru: team knowledge joined to the work
Guru is an enterprise knowledge platform. Landing gives your team an internal help centre on the same record as projects, clients, deals, HR and support, so the process sits beside the work it describes.
Landing suits you if
- You want internal know-how next to the projects and clients it is about
- You want one system for the team, not a knowledge layer over many
- You want a price you can work out yourself, today
Knowledge on top of a stack.
A knowledge layer helps people find answers. It does not reduce the number of places the work happens.
Another layer, not fewer tools
A knowledge platform sits on top of your project tool, your CRM, your HR app and your helpdesk. You still run all of them.
Priced in a consultation
There is no published price. What you pay is tailored in a sales conversation to your scale and complexity.
Process away from the work
The onboarding checklist lives in one tool and the new starter's record lives in another.
Landing Platform vs Guru, line by line.
An internal help centre, and the systems it describes, in one login.
| Feature | Landing Platform |  Guru |
|---|---|---|
| Internal knowledge | An internal help centre for the team, beside public and client-only ones, each in your brandCore | Its core product |
| Keeping articles current | Review dates per article, "was this helpful" on every page, and matching articles suggested beside the support formCore | Verification and stale-content flags |
| AI answers | A chat assistant that answers from your published articles and links the ones it usedGrowth | AI answers across your knowledge |
| AI agents | Claude and other assistants sign in with Landing and can only do what that person could doGrowth | Answers delivered to AI tools |
| Briefs and processes | Documents and processes on the project itselfCore | Stored as knowledge, apart from the work |
| Projects and boards | Kanban, lists, Gantt with dependencies and milestones, a portfolio view and templatesCore | Not part of the product |
| HR | Records, leave, shift rota and the org chartCore | Not part of the product |
| CRM and sales pipeline | Contacts, companies, deals and pipelinesCore | Not part of the product |
| Helpdesk and live chat | One inbox for email, live chat, Messenger and Instagram, with macros and assignment rulesCore | Not part of the product |
| Access | Access profiles that every screen and every query respectsGrowth | Permission-aware |
Plan tags show where a feature starts on Landing: Core, Growth or Scale. Guru details reflect its publicly available plans as of 2026; check current details on its own site.
What it costs, side by side.
Guru prices each customer in a sales conversation. Landing publishes its prices: full price only for the people who work in it every day, and less for everyone else.
Guru, as it lists it
How Guru is sold, as its pricing page describes it.
And still to buy separately: a project tool, a CRM, an HR app and a helpdesk.
a month on Landing, billed yearly, ex VAT
Includes an internal help centre, projects, timesheets, HR, CRM, email, the inbox, live chat and AI from a shared pool.
Work out your own priceExample team: four people who run operations, sales and marketing every day, twenty-six who read, log time and approve. Credits for AI come from a shared pool each Builder adds to.
Switching is our job, not yours.
We move you over one tool a month, against success criteria we agree with you up front. You don't pay until we prove each one is ready.
We map your stack
Show us how you use Guru and the tools around it. We agree what moves where, and what "ready" means for each tool, before you commit to anything.
We move Guru across
We move your cards and collections across as articles in an internal help centre as part of the switch, set up access so each team sees what it should, and check them with you before you switch off.
You sign it off
Billing starts only when we have shown it works against the criteria you set. Then we move the next tool, one a month.
But the team lives in Guru.
Here is what teams ask when they weigh up a knowledge tool against one system.
Can we keep internal knowledge private to the team?
Yes. Run an internal help centre alongside public and client-only ones. Access profiles decide who sees what, on every screen.
Can our AI tools reach it?
Claude and other assistants connect with "Sign in with Landing" and can only do what that person could do themselves. It is part of Growth.
How do we stop articles going stale?
Every article carries a review date and "was this helpful" feedback, so you can see what needs checking before someone trips over it.
What does it cost for a bigger team?
You can work it out on our pricing page now. Builders pay full price, Members from £4 a month, and clients and guests are free.
Onboarding a new starter?
Get the free client onboarding checklist and adapt it for your team.
“We were running PR, social scheduling and the rest of our marketing across half a dozen tools that never talked. Now we plan, schedule and measure from a single screen.”
Keep what the team knows beside what the team does.
Thirty minutes on your knowledge base and the tools it points at. We'll show you what moves and what it costs.