Pick a preset
Start from the workflow class closest to the company, or use the partner preset when the buyer is a consultancy introducing a client workflow.
Workflow App Sprint Brief Builder
Build a company-specific Workflow App Sprint brief.
Use this local builder to turn one observed workflow into a concrete artifact: problem-confirmation message, 10-business-day operational-pilot scope, five acceptance cases, payment gates, support, exclusions, and handoff. Nothing is submitted until you copy, share, or email it.
How to use it
Create one concrete next step.
This page is not a public customer draft board. It is a local brief builder for turning a workflow observation into copy you can send or bring into a workflow review.
Edit the workflow
Name the company, owner, current pain, business outcome, delivery mode, acceptance cases, and integration boundary before using the generated copy.
Copy the outbound pieces
Use the subject, Founder DM, follow-up, full brief, or share URL. Email or review it only when the workflow is specific enough.
Workflow presets
Start from a real workflow class.
These presets keep the thesis broad without drifting into generic consulting. Pick one, then edit the company, workflow, team, pain, and outcome.
Reusable sprint artifact
Fill one repeated workflow, then copy the brief.
Keep the claim narrow. The output should say what workflow changes, which team owns it, what ships, how five cases are accepted, what the customer supplies, when payment is due, and what is deliberately out of scope.
Generated artifact
Workflow App Sprint Brief
Not generic consulting
The brief should create one concrete next step.
Lead with the workflow, not the platform.
Name the observed bottleneck and the outcome. The product architecture is proof, not the opening sentence.
Own the app surface.
Intake, review UI, packet, notary, score, dashboard row, or handoff artifact lives in Krafthaus.
Keep runtime claims deterministic.
Use Decide for rulebook evaluation, trusted fact production, Decision Record fields, replay, and verification.
Ready to talk
Send the workflow when the brief is concrete.
The strongest email has one company, one owner, one current failure mode, and one desired handoff. Krafthaus can then scope whether this should be a sprint, a memo app run, or no project.