Sign in
The Krafthaus app collection
Approvals, agent actions, customer handoffs, and considered decisions. Explore by the job your team needs to do, then try an example or build a workflow around your own rules.
Explore the apps
Open a live app, try a sample request, and inspect what can proceed, what needs review, and who owns the next step. These are illustrative cases, not customer activity.
Check pricing, discounts, and nonstandard terms before sales sends the quote.
Check confidence, consent, and approval before an agent changes customer state.
Bring launch readiness, evidence, and open blockers into one go-live check.
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.
04 / Decision support
Some workflows need a considered recommendation, not permission to execute an action.
Compare options against a question, evidence and guardrails. A written recommendation gives the owner a clear basis for the next call; it does not authorize execution.
Start with the free readiness check. Paid memo runs use app-specific credits and depend on advisory-service availability.
What repeats
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.
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.
Every Krafthaus app closes the intake, binds the operating rules, preserves the record, and names the next owner before work moves. These live examples show that operating spine across revenue, AI, customer success, and customer operations.
intake -> rulebook -> record -> handoff
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. Actions include send_enterprise_quote, execute_ai_agent_action, and launch_customer_go_live.
More workflow categories
Choose a category to see the intake, rulebook, record, and handoff before scoping a company-specific app. Browse the complete workflow directory for proof status, buyers, failure modes, and outcomes.
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
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.
