CACHALOTLAB

Protocol 21

Protocol 21: working software in 21 days, with the date guaranteed by contract.

Most software projects fail because the scope is never closed and the date moves every week. We do the opposite: we put in writing what we will build, fix the date and use artificial intelligence to work faster. If something has to change, what we build changes, never the date.

The 5 phases

What happens in each phase and what you get.

  1. Day 0

    Immersion

    A free diagnosis of the problem.

    You get: A diagnosis document, the problem measured, what counts as “done” and the access list. If the project does not fit in 21 days, we tell you here.

  2. Days 1-4

    Solution contract

    We put in writing what will be built.

    You get: A contract with scope and date.

  3. Days 5-14

    Build

    We build the core.

    You get: A first version working end to end.

  4. Days 15-18

    Production

    Real data, security, integrations and testing.

    You get: A system tested with real information.

  5. Days 19-21

    Handover

    We put it live and hand everything over.

    You get: Code, passwords, manuals and training.

Scope

What fits in 21 days and what does not.

Fits

One core system or module with its full flow, the key integrations, automations, an AI assistant, an online store or an app with the essentials.

Does not fit

Replacing a full accounting system, projects with dozens of integrations or systems that need prior certifications.

Large projects

They are split into 21-day cycles, each with a working delivery.

Small projects

Not everything needs 21 days: a simple website can be ready in 7.

Day 21

What you get when we finish.

  • Code in your account
  • Passwords in your name
  • Technical and user manuals
  • Recorded training
  • 14 days of bug fixes at no cost

Next step

Does your project fit in 21 days?

We review it with you in the free 30-minute diagnosis. If it does not fit, we tell you that too.