Skip to content
An industrial loft war room in soft focus: a whiteboard mapping an architecture and a prioritization grid
Kommon Field NotesBuild Week

We bring the engineers

Build Week

Five days to proof.

One tight team, your stakeholders and our builders, in a room for five days. We map the highest-value AI idea, then build it. You leave Friday with a working prototype, not a roadmap.

One prototype, in your hands

Most AI projects stall in the gap between the people who have the problem and the people who can build. Build Week closes that gap by putting them at one table for a week, with a single question: is this idea real? You answer it with something running, not a deck.

In this issue

  • The five-day programme
  • Why one week moves so fast
  • See it work before you fund it
  • What a Build Week looks like

The five-day timeline

Mon to Fri
MonWedFri

  1. Day 1 · 0 to 8h

    Map the ideas

    We sit with your leadership and stakeholders, surface the highest-value AI opportunities, and pick the one worth building this week.

  2. Days 2 to 4 · 8 to 32h

    Build, fast

    Our engineers build alongside your team. No tickets, no handoffs. Build, show, adjust, every day.

  3. Day 5 · 32 to 40h

    Demo and decide

    You get a working prototype and a clear read on whether the idea is real, decided with something in your hands.

Why one week moves so fast

Figures
  • one tableProblem ownerDecision makerOur engineers

    Fig. 1

    The right people, one table

    The people who own the problem, the people who can decide, and the people who build, together. Scope is set in the room, and calls get made on the spot, not next week.

  • BuildShowAdjustevery day

    Fig. 2

    Fast feedback loops

    Build, show, adjust, in hours, not sprints. The prototype gets sharper every day because the people it is for are watching it take shape.

  • certaintyMonguessingFriyou know

    Fig. 3

    The moment your team sees it work

    That moment moves a conversation further than a quarter of slides. It is the fastest path from problem to proof.

    • A wall of ideas: handwritten notes and sketches hung on strings

    Collaboration

    Fig. 4 · Brainstorming of ideas

    De-risk the bet

    See it work before you fund it.

    95% of enterprise AI pilots showed no measurable return, one MIT report found. A working prototype in a week tells you whether the idea is real before you commit a quarter to it.

    THE USUAL PATH?Months of decks and meetings. 95% of AI pilots showed no return, one MIT report found.BUILD WEEKworking prototype5 days

    Why a prototype

    If a picture is worth a thousand words, a prototype is worth a thousand meetings.
    IDEO
    1012141618202224FIG. 1
    Fig. 1 · The working prototype

    What a Build Week looks like

    Contact sheet
    Late-night build fuel01
    Mapping a build: eat, hack, sleep, repeat02
    Hand-drawn cups by the demo screen03

    A few slots each year

    Bring us one real problem.

    Tell us the problem you would put a week against, and we will tell you if it is a fit.

    questions

    Questions we get asked

    What is a Build Week?
    A Build Week is a five-day sprint where a small team of your stakeholders and our engineers goes from idea to a working AI prototype. It is like a design sprint, but you leave with something running, not a plan. The point is to de-risk an AI bet before you fund it.
    What do we need to bring?
    Your stakeholders and one real problem worth solving. We bring the engineers, the tools, and the way of working. Small and focused beats big and vague.
    Who from our side should be in the room?
    The people who own the problem and someone who can make decisions. Four or five is plenty. The tighter the team, the faster it moves.
    What do we own at the end?
    The prototype and everything we learn building it. It is yours. If it works, you have de-risked the next step instead of guessing at it.
    How is this different from a hackathon?
    Build Week is a small, focused team shipping one prototype in five days. A hackathon rallies your whole organization to build in a short burst. Both de-risk AI by showing you what is possible.