Recurring internal judgment
Teams approve, route, block, or escalate the same class of request repeatedly, but the current path depends on memory and ad hoc review.
Work with us: Workflow App Sprint
Put one high-friction workflow into usable pilot operation.
Bring one repeated approval, exception, or handoff. Krafthaus turns it into a hosted browser surface your team can run on five agreed cases, with a visible result, record, next owner, and handoff for each.
$2,500 total: $1,250 after written scope acceptance and $1,250 after the five acceptance cases pass. Custom connectors are separate unless the written scope includes one.
No account or production credentials are required for the base pilot. Submit a brief, receive a 24-hour fit/scope reply, and start the 10-business-day window after scope, deposit, and customer inputs are confirmed.
Briefs are stored privately for fit and scope review. Prefer email? Run free preflight
Who buys this
Software companies with one repeated workflow.
The buyer is usually a founder, ops lead, RevOps owner, customer-success lead, or AI product team that already knows the workflow is too manual, inconsistent, risky, or slow to keep living in Slack, spreadsheets, internal docs, or half-built admin screens.
Software wants to act
Agents, copilots, queues, or internal tools need a bounded action gate before they book, refund, quote, launch, cancel, or touch customer state.
Exceptions leak time or money
Pricing, onboarding, support, implementation, and approval workflows need a tighter path from evidence to owner to next action.
Sprint unit
Start with one workflow the 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.
What ships
A focused app packet, not a slide deck.
Your team can open the browser surface, enter the agreed metadata, and run the five acceptance cases.
Required fields, business rules or owner review, missing-input states, and the allowed result are explicit.
Each accepted case shows the result, reason or matched rule, record, next owner, and handoff artifact.
Five case results, delivered artifacts, and a clear note on what ongoing hosting, rules, users, or integrations would require.
Five representative cases
Each case names its inputs, expected result, reason, next owner, and required record or handoff.
Pass, defect, or scope change
A failed agreed case is a defect. A new rule, field, system, workflow, action, or materially different result is a scope change.
Half at scope, half at acceptance
The customer has three business days to review delivery. One correction period for failed agreed cases is included before the balance is due.
Sprint timeline
What the 10 business days look like.
The sprint is paced around one workflow owner and one app surface. Each checkpoint narrows ambiguity before anything becomes a production integration.
Confirm the trigger, owner, current path, failure mode, required inputs, and the handoff the team needs.
Draft the intake contract, bounded rulebook or adapter path, Decision Record fields, and review states.
Show the first focused app surface so the buyer can inspect the request, verdict, record, and next action.
Run the five agreed cases, attach the visible records and handoffs, and open the three-business-day acceptance review.
Send one repeated workflow
Start with the handoff that keeps slowing the team down.
Give Krafthaus the trigger, owner, current failure mode, and desired handoff. The form stores the brief privately, creates a workspace reference, and starts fit and scope review without requiring an account.
Starting point
- Reply
- Fit and scope within 24 hours
- Sprint
- 10 business days after scope, deposit, and inputs
- Price
- $1,250 at scope + $1,250 at acceptance
Workflow starters
Start from a workflow category.
Public category pages explain the pattern before personalization. Start there, then use the brief builder only when the company-specific workflow is real enough to review.
01 Revenue workflow
Quote Approval Gate
Pricing exceptions, discount requests, nonstandard terms, and approval routing before sales sends the quote.
Open category page 02 AI workflow AI Agent Action GateAction boundaries before an agent books, refunds, cancels, qualifies, routes, or uses a tool.
Open category page 03 Support workflow Support Routing GateTicket evidence, policy context, SLA risk, escalation path, and owner assignment before queue state changes.
Open category page 04 Customer workflow Onboarding Readiness GateGo-live readiness, missing inputs, implementation risk, and customer-success handoff.
Open category page 05 Review workflow Compliance Document Review GateCases, questionnaires, evidence packets, and review-ready handoffs before a regulated or sensitive workflow advances.
Open category page 06 Finance workflow Procurement Exception GateVendor, invoice, AP, mismatch, approval, and payment exceptions before spend or payment moves.
Open category pageTrust boundary
A usable pilot without pretending it is a deep integration.
The standard delivery mode starts with approved metadata and browser-based or manual intake. It proves the workflow on real representative cases before either side commits to production access or a connector.
Hosted and usable by the workflow owner
Contracts, customer records, full transcripts, and production credentials stay out unless both sides approve a separate implementation path.
- Manual metadata intake is supported. The customer can run the agreed cases without a custom connector.
- Rules and review stay bounded. The written scope names the allowed outputs and human owner route.
The five agreed cases pass.
- The hosted surface is open and usable by the named workflow owner.
- Each agreed case returns the accepted result or review route with a visible record and next owner.
- Delivered records and handoff artifacts are accessible or exportable without an implied production mutation.
Tight scope is the point.
- No platform migration or rebuild
- No production-system mutation or custom connector unless explicitly written into scope
- No additional workflows, unlimited revisions, or guaranteed business outcome
After Day 10
Thirty days of defect correction are included.
Ongoing hosting, support, new rules, more users, and connectors are scoped only after the pilot proves useful. Krafthaus keeps its reusable platform; the customer keeps its submitted data, business rules, materials, and exported records. Review the technical app contract.
Do not buy this if
You need a platform replacement, an untested production connector, or an open-ended consulting project.
The sprint is for a buyer who can name one repeated workflow, one owner, and five representative cases. If those are not available yet, use the free preflight or brief review first.