Each app accepts only the facts needed before the workflow moves. It does not ask an LLM to make the business decision from an unbounded prompt.
Workflow App Examples
Workflow app examples
Krafthaus turns consequential software-company workflows into focused app surfaces. Four live apps prove the pattern across revenue, AI, customer success, and customer operations.
Live app surfaces
Four workflows. One delivery layer.
Each app has a public surface, a closed intake, a pinned Application Manifest v1, a direct_declarative_rulebook binding, a Decision Record, and an execution handoff before the customer workflow moves.
Enterprise quote approval before sales sends pricing, discount, or nonstandard terms. Governed action: send_enterprise_quote.
AI agent action boundary before customer-facing autonomous software acts. Governed action: execute_ai_agent_action.
Customer onboarding readiness before implementation moves to go-live. Governed action: launch_customer_go_live.
Cited refund, cancellation, return, or trial policy plus a separate authorization before support changes customer state.
Existing integrations can keep using the Customer Operations Credit Gate compatibility path for the original refund-credit boundary.
What repeats
The surface changes. The operating spine stays stable.
All four live examples use direct_declarative_rulebook and reject customer executable rulebooks in production.
Decide returns required binding material: runtime binding, rulebook contract, application verdict, input hash, and rulebook attestation.
Krafthaus turns the verdict into a next action: send, route, block, execute, or review.
More workflow categories
Start with the workflow your team already repeats.
Choose a category to see the intake, rulebook, record, and handoff before scoping a company-specific app.
Pricing exceptions, discounts, custom terms, legal review, and owner routing before a quote goes out.
Category AI agent actionConfidence, consent, approval, reversibility, risk, and human review before agent execution.
Category Support routingEvidence, policy context, SLA risk, queue routing, and owner assignment for support actions.
Category Onboarding readinessGo-live blockers, implementation status, launch readiness, and customer-success handoff.
Category Compliance document reviewReview-ready documents, evidence packets, owner routing, and case advancement.
Category Procurement exceptionsVendor, invoice, AP, mismatch, approval, and payment exception workflows.
One product layer
One delivery layer across consequential workflows.
Start with one repeated workflow. Krafthaus packages the intake, operating rules, record, and next-owner handoff; Decide handles deterministic verdicts, replay, and verification when the workflow needs them.