Craft Sprint

From problem to proof in two weeks.

Anyone can use AI now. What is still hard is understanding the real problem, designing the right solution and getting it approved. In a Craft Sprint we do all three with you, and prove the solution with a working prototype your decision makers can try, not just read about.

Book a Craft Sprint How it works

1–2wks

Fixed timebox from kick-off to decision demo

Working prototype, not a slide deck

1day

Fastest recent sprint, from first workshop to a working prototype

Fixed

Scope and fee agreed before we start

When a sprint helps

Sound familiar?

“We know something is wrong, but not what to build.”

“A proposal on paper will not get approved.”

“We are about to commit a large budget and want proof first.”

“Vendors pitch solutions before anyone agrees on the problem.”

How it works

Ten working days, three moments that matter

Frame the problem

Days 1–2

Workshops with business owners and users to agree the real problem, who it affects, what it costs and what success looks like.

Design the solution

Days 3–4

Process, data and architecture designed with you, and scoped to the one workflow worth proving first.

Prove it working

Days 5–10

A working build shown every day, ending in a live demo to decision makers with the solution design, an estimate and a roadmap.

What you get

Everything you need to get a yes

“Does it actually work for our people?”

Working prototype

A clickable, working application on sample or anonymised data. Not slides.

“What would it take to run this for real?”

Solution design

Architecture, data flow and process design: what it takes to run this for real.

“What will it cost, and in what order?”

Costed roadmap

A rough-order-of-magnitude estimate, phasing and risks for production and rollout.

“Can we say yes?”

One-page decision brief

A summary written for internal approval and budgeting, in English or Japanese.

Why it works

Working software in days, built on judgement, not guesswork.

We go from idea to working software in days. Speed alone isn't the point, though. The value is in asking the right questions, knowing how your industry and organisation work, and designing something that can survive production, security reviews and a regional rollout.

A working prototype changes the conversation. Stakeholders give concrete feedback, risks show up early, and the business case is built on something real. That makes internal approval much faster than with a proposal on paper.

Recent sprints

Working prototypes, in days

3 days

Quality gate management board

Japanese Industrial Manufacturer — Heat Processing Equipment Division

The problem: A quality process reform needed a consistent way to run Gate0, DR1 and DR2 gate decisions and to see where every project sat in the pipeline.
What we built: A Kanban-style board with gate decisions, criteria held as editable data, lead-time analytics and an optional AI pre-review that prepares suggestions for people to confirm.
Where it stands: Running in a live cloud environment, with a scripted 10-minute demo for division leadership.

Next.jsTypeScriptPrismaCloudflare WorkersCloudflare D1Claude API

5 days

Sales deal board

Japanese Industrial Manufacturer — Industrial Products Division

The problem: Deal information was spread across sales and technical reports, with no shared view of each opportunity or who should review it next.
What we built: A drag-and-drop deal pipeline with a detail view that brings sales notes, technical reports and comments together, built from a written build spec after a working-group session.
Where it stands: Version 0.1 captures the decisions from the first working-group session, ready for the next review.

ReactViteTypeScriptdnd-kitZustand

1 day

Price simulator

Japanese Industrial Manufacturer — Industrial Products Division

The problem: An internal pricing study needed a way to discuss deal-level pricing with both the supplier’s and the customer’s economics in view.
What we built: An interactive simulator that shows the effect of pricing assumptions on both sides of a deal, moved from a single-page concept to a maintainable web app.
Where it stands: Ready for the study team to run and extend on their own.

ReactViteTypeScript

Proof, close to home

This website was designed and built the same way: a short working session, then a working site the same day, refined live together.

Taira Promote
Built with the Craft Sprint approach

Questions

Why not just ask our team to use AI tools?

Anyone can generate code now. What matters is framing the right problem, understanding the business and designing something that can survive production, security and rollout. That is the part we bring.

Is the prototype production-ready?

No, and we are explicit about it. The prototype proves value and de-risks decisions. The roadmap spells out what production needs: security, integration, testing and operations.

What happens to our data?

We agree data handling up front. We default to sample or anonymised data, and we can build inside your own environment when required.

What does it cost?

A fixed fee for a fixed scope, agreed before we start. If you go ahead with the build, part of the sprint fee is credited towards it.

What happens after the sprint?

You decide. Most clients take the prototype into budget approval, then continue with us into build, regional rollout and managed services. Some build it themselves, and the design is theirs to keep.

After the sprint

The sprint is the first stage of our approach. When the prototype is approved, it moves into MVP, regional roll-out and managed run with the same team, so nothing is lost at handover.

Have a problem that needs proof?

Tell us the challenge in a few lines. We'll reply with a proposed sprint scope within a week.

Talk to us See our work