Find the workflow boundary
We isolate one repeated workflow where ambiguity, manual routing, missing evidence, or inconsistent decisions costs time.
Workflow App Sprint
Turn one consequential workflow into a Krafthaus app.
One workflow. One app surface. One Decide-backed handoff. The sprint starts from an operational bottleneck and ships the surface that makes it usable.
Not generic consulting
The unit is one workflow your team already repeats.
Pricing exceptions, agent escalation, customer onboarding, support routing, quote approvals, vendor choice, implementation readiness, and rollout guardrails all have the same shape: messy inputs, policy or evidence, a recommended action, and a handoff.
Package the operating surface
The app gets the intake, interface, rulebook or adapter binding, and artifact your team can actually use.
Make the next action explicit
The output is proceed, block, defer, review, ask for missing input, open a ticket, anchor a hash, or hand to an owner.
Sprint deliverables
A focused app packet, not a slide deck.
Actors, trigger, current path, failure modes, and the boundary where a verdict or handoff matters.
Required fields, evidence standard, owner, missing-input states, and examples of acceptable requests.
Rulebook v1 draft, trusted-adapter spec, or direct-facts path, depending on how the workflow should evaluate. Executable customer rulebooks stay outside the production contract.
A usable app surface: review page, notary, packet builder, score, mini-tool, dashboard row, or handoff artifact.
Which Decide fields to store, where the record travels, and what downstream system or human receives next.
What to automate, measure, or turn into repeat runtime usage after the first workflow proves useful.
Workflow starters
Start from a workflow class.
The same Krafthaus/Decide spine can land in different operational surfaces. Start with the workflow class, then tailor the proposal to the company.
01 Pricing exceptions
Pricing exceptions
Discounts, usage edge cases, margin rules, and plan changes before pricing ships.
Start with this workflow 02 AI agent escalation AI agent escalationAction boundaries for booking, refunding, cancelling, qualifying, or routing to a human.
Start with this workflow 03 Onboarding readiness Onboarding readinessGo-live readiness, missing inputs, implementation risk, and customer-success handoff.
Start with this workflow 04 Quote approval Quote approvalEnterprise quote exceptions, approval thresholds, legal review, and sales ops ownership.
Start with this workflow 05 Support routing Support routingEvidence, confidence, SLA risk, policy context, queue routing, and owner assignment.
Start with this workflowFits the current ecosystem
Decision Memos are one existing app. The sprint creates the next one.
Existing
Decision memo workflow
One KPI call becomes a packet, recommendation, guardrails, rollback trigger, and written handoff.
Existing Solana execution gateA proposed action becomes a deterministic packet before wallet signing or onchain value movement.
Existing Policy MCP notariesAgent-facing refund, cancellation, return, and trial checks become citable policy calls.
New Krafthaus workflow bindingA proposed app surface calls Decide before bind_workflow_application and captures required Decision Record material.
Commercial wedge
Pick one workflow. Ship the first app surface.
The sprint is the delivery layer between a broad platform thesis and a real customer workflow. Start with the workflow, then let Decide power the parts that need a verdict, record, replay, or audit trail.