Workflow directory
Find the workflow your team already repeats.
Start with the operational boundary, not a generic platform pitch. Each pattern names the buyer, current failure mode, governed handoff, proof status, and commercial next step.
Discovery contract
Problem -> pattern -> proof -> Sprint
Proof-backed workflows have a substantive category page, executable app, manifest, and conversion path. Category-backed workflows have a concrete delivery boundary without pretending a live proof exists.
4 proof-backed
2 category-backed
Executable proof
Run the boundary before scoping your version.
These workflows have a live Krafthaus application, a pinned Application Manifest v1, and an explicit category-to-proof journey.
Live proof
Revenue Operations
Quote Approval
For: Founder, RevOps, Sales Ops, Finance, Legal
Before
Pricing, discount, and nonstandard terms move through Slack or founder memory before sales sends them.
Returns
Approve, review, or block a quote before sales sends it.
Live proof
AI Operations
AI Agent Action
For: Founder, AI Product, Product Operations, Risk Owner
Before
Autonomous software can change customer or operational state before confidence, consent, evidence, and reversibility are clear.
Returns
Allow, review, or block an AI agent action before execution.
Live proof
Customer Operations
Support Policy Action
For: Founder, Support Operations, Customer Operations, Support Product
Before
Support teams apply scattered policy notes and queue judgment before refunds, cancellations, returns, or trial actions change customer state.
Returns
Authorize, review, or block a cited policy-backed support action.
Compatibility path: Customer Operations Credit Gate
Live proof
Customer Success
Customer Onboarding Readiness
For: Founder, Customer Success, Implementation, Customer Operations
Before
Implementation moves accounts toward launch with blockers, evidence, training, security review, and owner state scattered across systems.
Returns
Mark customer go-live ready, route review, or block launch.
Commercial pattern
Concrete enough to scope. Not mislabeled as proof.
These categories define the buyer, intake, outcome, record, and handoff. They remain category-backed until an executable public app and manifest exist.
Pattern ready
Compliance Operations
Compliance Document Review
For: Founder, Operations, Compliance, Security, Legal Operations
Before
Cases and evidence packets advance before required evidence, reviewer ownership, deadline, and risk state are clear.
Returns
Mark review ready, request evidence, escalate, or block advancement.
Pattern ready
Finance Operations
Procurement Exceptions
For: Founder, Finance, Procurement, Operations
Before
Invoices, vendor choices, purchase requests, and mismatch reviews move through email, Slack, and spreadsheets without one exception record.
Returns
Approve, request evidence, route review, or block spend advancement.
Workflow App Sprint
Bring one consequential handoff.
Krafthaus turns it into one hosted workflow surface, five agreed acceptance cases, a visible record, and a named next owner in ten business days.