saascode
project & workflow operations·run 153 · Jun 2026

HandbookCite

A bounded internal knowledge assistant that cites approved handbook passages, displays organization-reviewed automation notices and records policy version, retrieval evidence and corrections without claiming legal compliance.

Genesis score6.21/10
Make HandbookCite real.0/500
500 more votes and HandbookCite is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
1Confirmed category substitutes
0Confirmed copying barrier
The case

Small teams want employees to find an approved procedure without searching folders or interrupting an operator. HandbookCite indexes a bounded, owner-approved corpus and returns answers with source version, exact passage and a visible automation notice. The supplied research confirms a saturated knowledge-assistant category and a competitor lacking the specific disclosure-log combination reviewed. That is a thin feature gap, not a moat. The input overstates legal scope: a banner and log do not make a bot disclosure-compliant, and the applicability of any rule to an internal employee interaction depends on enacted text, system role, context and qualified interpretation. Source citation does not make an answer current, complete or authorized for a real-world action. Policy publication, retrieval, generated answer, user acknowledgement, human escalation, exact operational approval, destination acknowledgement and outcome remain separate. HandbookCite can reduce search time and make answers easier to verify. It cannot replace training, employment or legal review, certify compliance or safely ship in a day without corpus, access and escalation controls.

Who pays — and why

A small or mid-sized organization with a maintained internal handbook, named policy owners and repeated employee procedure questions.

Market signalValidate by active employees, approved source collections, policy owners, monthly questions and escalation volumeInternal knowledge assistants and document-search services are observed market references, not fixed product pricing
What it unlocks
An approved-corpus contract defining document owners, versions, effective dates, audiences, supersession, access, retention and questions that require human review.
An answer evidence model separating user question, retrieved passage, source version, generated claim, uncertainty, citation, notice event, user feedback, owner correction and supersession.
A safe action boundary where answers can explain policy but any employment, finance, safety, security or customer-impacting action requires its separate authorized workflow.
How Genesis scored it
6.21across seven criteria
tension 6temporal 8blindspot 5buyer 8leverage 6convergence 5why-not 5
8
Temporal window

The supplied legal timeline creates interest but requires primary-source and contextual review.

8
Buyer persona

Organizations with maintained SOPs and recurring internal questions are identifiable buyers.

5
Why nobody did it

Recent disclosure focus creates a packaging opportunity, not a new technical barrier.

Why it scored well

A concrete SMB buyer, confirmed category demand and a bounded evidence-plus-notice workflow support a fast, narrow product.

What's holding it back

The category is saturated, legal applicability is contextual, the feature gap is easily copied and maintaining a trustworthy corpus creates ongoing work.

Signals detected3 sources crossed
SignalCompetitor research

SignalCompetitor research

SignalInput risk review

Direction briefhandbookcite-sop-answer-evidence.md
handbookcite-sop-answer-evidence.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.