Book a 30-min call →
21 days · from $1,999 · fixed

Ship It Live · internal tools sprint

The spreadsheet your team runs on, as real software in 21 days.

The shared spreadsheet everyone is scared to touch, rebuilt as software with permissions, history and no accidental deletions.

4.93★ / 32 reviews 75+ shipped Kickoff in 24h

Quick answer

A custom internal tool or admin dashboard can be built and in use by your team in 21 days from a fixed $1,999. That covers accounts and roles, your records and workflows, search and filtering, exports, an audit trail and reporting. Replacing a full ERP is a programme, not a sprint.

The plan

Day one to day 21, written down.

You get this schedule before you commit, not after. If a phase slips, that is mine to absorb — the price and the date were agreed before anything started.

  1. 1

    Days 1–3

    Watch the current process

    Your spreadsheet, your workarounds, and the steps people do from memory. The undocumented steps are the ones that break rebuilds, so they get found first.

  2. 2

    Days 4–9

    Design

    The screens your team lives in, designed for speed rather than beauty — keyboard-friendly, dense where density helps, and honest about the messy states.

  3. 3

    Days 10–16

    Build

    Data model, permissions, workflow and reporting. Your real data goes in during the build so you are testing against reality, not sample rows.

  4. 4

    Days 17–19

    Run both in parallel

    Your team uses it alongside the spreadsheet for a few days. Every gap surfaces now, while there is still time to close it.

  5. 5

    Days 20–21

    Cut over

    Data migrated, team trained, spreadsheet retired. Access handed over so you can add users without me.

What from $1,999 gets you

Everything needed to launch — nothing padding the invoice.

Accounts, roles and permissions — who can see and change what
Your actual records and the workflow that moves them along
Tables that stay usable at ten thousand rows, with search and filters
Bulk actions, CSV import and export both ways
An audit trail: who changed what, when, and what it was before
Reporting and a dashboard for the numbers you check every morning
Integrations with the tools you already use, where they have an API
Source code, design files and 30 days of support at handover

Who books this

Built for

Operations teams running the business out of a spreadsheet nobody trusts

Companies paying per seat for a tool that fits two-thirds of their process

Founders whose ops load is growing faster than they can hire

The honest part

When 21 days is the wrong answer.

A fixed deadline only works when the scope genuinely fits inside it. These are the cases where I will tell you so rather than take the booking.

Replacing a full ERP or accounting system. Those carry compliance and integration weight that no three-week sprint should pretend to lift.

Integrating with legacy on-premise systems that have no API. Sometimes possible, never quick, and quoted only after I have seen what is actually there.

Processes nobody can describe. If two people disagree about how the work runs today, we fix that first — software will not settle it for you.

Questions

Before you book

If one fits, use it, and I will say so on the call. Custom wins when per-seat costs have outgrown a build, when your process needs logic those tools cannot express, or when you need the data somewhere you actually own.

21 days from now, this could be live.

A 30-minute call decides whether the scope fits. If it doesn't, I'll tell you what would.