Workflow App Sprint Category
Custom quote approval workflow
Build one quote approval workflow around your discount policy, contract exceptions, and review owners. This Workflow App Sprint scopes a pilot for Sales Ops and RevOps; the linked Quote Approval Gate demo shows the starting pattern.
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.
Illustrative acceptance pack
Agree five cases before the workflow is installed.
Start with these quote approval examples, then replace the demo thresholds, review owners, and handoffs with five representative cases agreed with your team. Each case needs an expected result and a named next owner.
A 10% discount, 40% margin, standard terms, and completed legal and security review.
Expected result: APPROVE_QUOTE. Hand the checked record to sales for the agreed quote send.
A 30% discount with 35% margin; the other reviews are complete.
Expected result: ROUTE_REVIEW. Keep the send pending and route it to the named approval owner.
A 15% discount and 35% margin with a contract exception, even when legal review is complete.
Expected result: ROUTE_REVIEW. Put the exception and record in the approval owner's handoff.
A 10% discount leaves only 5% margin; the other reviews are complete.
Expected result: BLOCK_QUOTE. Stop the quote send and return the blocking reason to the owner.
A 12% discount and 32% margin with legal review still incomplete.
Expected result: ROUTE_REVIEW. Keep the send pending until the required review is resolved.
What acceptance checks: the expected verdict, reason code, Decision Record, named handoff, and verified canonical packet hash. Agree where the record is stored and who owns the next action. An approval result does not prove that a quote was sent.
The recorded demo rehearsal on passed these five cases. These are illustrative demo results, not customer outcomes or a fresh production health check. A pilot uses your agreed policy and cases.
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 surface the workflow owner can run on five accepted cases, with a visible result, record, next owner, and handoff.
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.
Confirm the bottleneck, then review five cases
If the workflow is real, use 15 minutes to confirm the owner, required inputs, five acceptance cases, and delivery boundary.
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.