Krafthaus Sign in

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.

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.

01Closed intake

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.

02Pinned Rulebook v1

All four live examples use direct_declarative_rulebook and reject customer executable rulebooks in production.

03Decision Record

Decide returns required binding material: runtime binding, rulebook contract, application verdict, input hash, and rulebook attestation.

04Execution handoff

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.

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.