Knowledge fragments
Answers live across PDFs, release notes, old pages, and the founder’s head.
The support layer between your product and your users
Turn product knowledge into answers customers can trust.
FAQ Hub gives lean SaaS teams one controlled knowledge layer for help centres, in-app search, and grounded AI support.
Built, not conceptual
Pre-revenueNow proving activation, willingness to pay, and repeatable distribution.01 / 11
The problem
Support starts as a few questions. Then it takes over the week.
Self-service loses trust
Stale docs and unsupported AI answers train customers to open a ticket instead.
The team becomes the index
Founders and engineers repeat answers instead of improving the product.
“The chatbot is not the hard part. Deciding what it is allowed to say is.”
02 / 11
The product
One governed source. Three ways to get an answer.
Import what already exists, review it in a real CMS, and publish cited answers wherever users need help. When the evidence runs out, FAQ Hub stops and hands over the context.
CONTROL LAYERVerified support CMSHuman approval · product scope · source history
Embedded chat
Grounded answers inside the product.
Inline help
Searchable guidance without leaving the workflow.
Hosted portal
A branded destination for deeper support.
03 / 11
How it works
Messy material becomes a support system.
- 01 · InputBring scattered knowledgePDF · DOCX · WEB · MD
- 02 · StructureDraft and categoriseAI-assisted, not auto-published
- 03 · ControlReview and publishHuman approval
- 04 · DeliverChat, inline help, and portalCited, product-scoped answers
- 05 · EscalateHand unresolved questions to a personConversation context included
04 / 11
Why now
AI made answers cheap. Trust became the scarce input.
Customers expect an answer now
They increasingly start with search or AI before opening a ticket.
Every interface can become support
Help no longer needs to live in a separate portal or heavyweight helpdesk.
Governance is the missing layer
Teams still need control over sources, approvals, scope, citations, and escalation.
05 / 11
Market and expansion
Start with teams that feel support pain before they can justify support software sprawl.
The wedge is deliberately narrow. The product surface is not.
ExpansionMulti-product and enterprise support operations
NextGrowing SaaS support teams
BeachheadFounder-led SaaS
Bottom-up revenue potential at today’s Growth price
1,000 customers≈ $1.19m ARR
10,000 customers≈ $11.88m ARR
Illustrative arithmetic at $99/month, not a forecast or current pipeline.06 / 11
Business model
Predictable product pricing. No support-seat tax.
One product, up to 500 articles, and all core delivery surfaces.
Three products, higher usage, custom domains, and escalation webhooks.
Managed rollout, more products, higher limits, and tailored terms.
LandOne product and one painful support workflow.ExpandMore products, more knowledge, more support surfaces.
07 / 11
Why FAQ Hub can win
The control loop is the product.
A chat window is easy to copy. A dependable operating loop across content, retrieval, delivery, and escalation is not.
- 01Content operations first
Ingest, structure, approve, publish, and improve from one system.
- 02Product-scoped retrieval
Tenant boundaries and source selection are part of the architecture.
- 03Second-pass answer judgement
Unsupported answers fail closed instead of improvising.
- 04Distribution where users work
The same source powers chat, inline help, and a hosted portal.
- 05Human escape hatch
Unresolved conversations keep their context when they escalate.
08 / 11
Current stage
The technical risk is down. The commercial questions are next.
No invented ARR. No customer logos without permission. The product is ready for a controlled first cohort.
Content ingestion, review, search, grounded chat, citations, delivery surfaces, billing, and escalation.
More than 1,100 backend tests and production builds across the API, portal, and marketing surface.
Activation, first grounded answer, retained usage, conversion, and measurable ticket deflection.
09 / 11
The early-seed plan
Fund proof, not speculative feature volume.
Capital and investor access shorten the path from working product to repeatable demand.
Win the first reference cohort
Founder-led sales, hands-on onboarding, and weekly product interviews.
Proof: activation and paid conversionTurn onboarding into a system
Reduce time to first trusted answer and package the strongest use cases.
Proof: retained usage and referralsBuild focused acquisition loops
Free tools, founder communities, product-led trials, and selected channel partners.
Proof: efficient qualified pipelinePrincipal riskDistribution and repeatable willingness to pay, not whether the core system can be built.
10 / 11
Start a useful conversation
Help prove the next part of FAQ Hub.
We are speaking with early-seed investors, SaaS founders, support leaders, and channel partners who value disciplined validation over inflated claims.
FOUNDERDane
Solo technical founder with 12+ years building enterprise platforms, now applying those operating standards to support software for lean teams.
11 / 11