Workflow App Sprint Category
Quote Approval Gate
For sales ops, RevOps, and founders who need one governed path before nonstandard pricing or contract terms reach a customer.
The workflow
Where this breaks today.
Current failure mode
Discounts, payment terms, usage limits, SLAs, legal notes, and implementation promises move through Slack or founder memory before sales sends the terms.
Focused app surface
A quote intake, approval rulebook, Decision Record, and sales handoff that returns approve, block, or review before the quote moves.
Runtime or record layer
Binding mode: trusted_adapter_facts_then_declarative_rulebook. Customer executable rulebooks are outside the current production contract.
Example boundary
What the app decides or hands off.
Customer asks for enterprise pricing, custom discount, usage band, payment term, SLA, implementation commitment, urgency, owner, and risk notes.
Approve, block, or review required; route to RevOps, founder, finance, legal, or implementation before sales sends the terms.
One bad discount, custom term, unsupported API limit, or implementation promise can cost more than the sprint.
What ships
One useful workflow surface, not a broad project.
Trigger, current path, owner, failure modes, and the boundary where work should proceed, block, review, or route.
Required fields, evidence standard, missing-input states, and examples of acceptable requests.
Direct declarative Rulebook v1, trusted-adapter fact contract, or Decision Record-only path depending on the workflow.
A focused Krafthaus page, notary, packet builder, score, dashboard row, or handoff artifact the team can review.
What gets stored, where the record travels, and who or what receives the next action.
What to automate, measure, or turn into repeat runtime usage after the first workflow proves useful.
Trust boundary
Start with metadata and handoff shape.
Runs on deal metadata first. Contracts, customer files, and private deal rooms are not required for the first sprint.
One workflow
The sprint deliberately avoids broad AI transformation, platform rebuilds, or customer executable rulebooks.
Metadata first
The first sprint can use request metadata, policy fields, evidence status, owner, risk, and desired handoff before private-system integration.
15-minute review
The low-friction next step is to confirm the workflow owner, required inputs, Decide binding, and whether a Krafthaus surface is worth scoping.
Workflow App Sprint
Map your version of Quote Approval Gate.
Use this category as the public pattern. The company-specific artifact comes after the workflow is real enough to review.