Process
one team (for example product support or CS ops) keeping one topic set current from draft to published article
Home / Blog / SaaS Knowledge Base: When a Starter Pilot Beats Another Wiki Nobody Reads
Pay vs ConsulteSaaS Knowledge Base: When a Starter Pilot Beats Another Wiki Nobody Reads
Pay vs Consulte for a SaaS knowledge base: when one team, one source system, and one success metric already exist, Starter ZG06 beats another unread wiki. If those three are missing, start with Consulte or Discovery $99 — no invented deflection or CSAT lifts.
Discovery $99 Consulting $499 Starter $2,500 Growth $8,000/mo Response within 24h
What this page is (and is not)
This is a fit guide for one named knowledge lane — one team publishing from one source system against one success metric they already watch. It is not a case study and it does not invent a deflection percentage, CSAT lift, savings figure, or certified outcome. Published commercial prices live on /plans/. The diagnostic is Discovery $99. Human-scoped work starts at /contact/.
Related reading: IT service desk automation Pay vs Consulte and Discovery $99 vs Starter $2,500. Adjacent hub: autonomous AI agents.
The unit of work
Systems
one source system — the help-center CMS, docs repo, or ITSM knowledge space that already holds the truth
Operating signal
one success metric you already have: stale-article age, “article missing” tags on a named queue, or time-to-publish a correction — not a fabricated deflection rate
Stop rule
Do not stand up a second wiki “for AI.” If the first wiki is unread because no owner exists, another tool will be unread too.
Pay vs Consulte
Pay (Starter $2,500 · ZG06)
One team, one source system, and one success metric are already named. “Done” is a live publish path plus a review queue for that lane — not a company-wide knowledge program.
Pay Starter ZG06 · menu on /plans/.
Consulte (/contact/)
Many products, legal review with no SLA, or support / product / IT do not share an owner. Consulte the SOW before you buy another empty wiki.
Start Consulte — SOW first, Pay later if the slice is clear.
If you cannot name the team, the source system, and the acceptor for “done,” do not Pay yet. Use Discovery $99 for a written map (Pay, Consulte, or stop). Deeper SKU comparison: Discovery $99 vs Starter $2,500. Adjacent desk work: ITIL service desk Pay vs Consulte.
When a Starter pilot beats another unread wiki
A Starter pilot is the honest next step when the graveyard pattern is already visible and bounded:
- One team will write and accept. Not “everyone should contribute.” A named editor and a named reviewer for one topic set.
- One source system is reachable. You are not migrating three help centers, a Confluence swamp, and Slack folklore in the same $2,500 slice.
- One success metric already exists. You can point at a report or a queue tag you already use. We will not invent a CSAT lift or a deflection percentage to justify the buy.
If those three are true, another strategy workshop will not make articles get read. A bounded Starter — publish path, review queue, stop rule — will. If any of the three is missing, Pay becomes a second wiki nobody reads. That is Consulte or Discovery first.
What Discovery $99 writes
- Owners and systems for this slice — not a company-wide knowledge transformation.
- A recommendation: Pay Starter, Consulte a SOW, Growth/retainer, or stop.
- The stop rule above, in writing, so kickoff cannot smuggle a second product line or a new CMS.
Discovery is not implementation. Implementation is Starter or a scoped SOW. Ongoing coverage is Growth after the model is clear. First-automation framing: Pay vs Consulte for AI automation.
Good after kickoff (no fake math)
- The process sentence still matches day 10 — same team, same source system, same topic set.
- Access landed or a named blocker with an owner (CMS, ITSM knowledge space, or repo).
- Definition of done is operational — a live publish + review path — not “we explored AI search.”
- Exception queue exists. Humans know which articles automation must not publish alone.
If access is still pending or success was redefined to “we launched a portal,” stop and re-scope. That is Consulte, not a silent expand of Pay.
FAQs
Can I skip Discovery and Pay Starter ZG06?
Yes — if one team, one source system, and one success metric you already measure are named, the CMS or knowledge space is reachable, and someone will accept “done.” If kickoff would still debate which wiki to replace, map first: Discovery $99.
Is Consulte a free consultation?
No. Consulte is a human-scoped conversation via /contact/ when the SKU is unclear. Discovery is the $99 written diagnostic. There is no free consultation SKU.
Do you publish deflection, CSAT, or ROI percentages for this work?
No. This guide uses fit patterns only. Use an operating signal you already measure. Board language without fake math starts from the Discovery map.
Where do Consulting $499 and Growth fit?
Consulting $499 sits between Discovery and Starter when you need RACI or roadmap without a pilot yet. Growth $8,000/mo is ongoing coverage after the model is clear. Ladder: /plans/.
Read next
- IT service desk automation Pay vs Consulte
- ITIL service desk Pay vs Consulte
- Discovery $99 vs Starter $2,500
- Pay vs Consulte for AI automation
- Autonomous AI agents
See also: IT service desk automation · ITIL service desk · Discovery vs Starter · Pay vs Consulte AI automation · Autonomous AI agents · Blog · Discovery $99 · Plans · Consulte