How a project runs, week by week.

1. Before

   01 / 06

   The first call

   Thirty minutes. You describe the product, the people who will use it and the deadline. I ask about your data, your team and what already exists.

   You get

   A written quote within two working days

2. Week 0

   02 / 06

   Data model and plan

   I model the data first: tables, relations, who can see what. Then a short plan with the screens and the order they ship in. Nothing is built until you sign it off.

   You get

   The data model, a plan and a price range

3. Week 1

   03 / 06

   First deploy

   A real screen on a real URL, behind a login, with CI and a preview for every pull request. From here, something ships every week.

   You get

   A link you can open on your phone

4. Weeks 2 to 6

   04 / 06

   Ship every week

   One feature at a time, finished before the next one starts: screens, empty and error states, tests. A real deploy every week, not a demo.

   You get

   A weekly deploy and a short written update

5. Throughout

   05 / 06

   Typed end to end

   Database, API and screens share one set of TypeScript types. When something changes, the build tells us before your users do.

   You get

   Shared types and a passing test suite

6. Last week

   06 / 06

   Handover

   Everything written down: docs in the repository, a recorded walkthrough and a call with whoever runs it next. Software management keeps it running after that.

   You get

   The docs, the recording and a support plan

// The length changes from project to project. The order does not.