Nexaflex
Start a project

Process

How a build actually goes

Four stages, in order. Each one ends with something you can hold: a document, a set of screens, a deployment, a repository in your own account.

  1. Scope

    One to two weeks

    We read your systems, talk to the people who use them, and write down what the software has to do. If we find that a configured off-the-shelf tool solves it, we say so and you keep your money.

    You get

    • Written scope document
    • Fixed price or priced stages
    • A delivery date we hold
    • Named technical risks with mitigations

    We need from you

    • Two hours with the people who do the work today
    • Access to the systems it must talk to
  2. Design

    One to three weeks

    Interface design happens before the build, not during it. Every screen is designed in both themes and at phone width. You click through it and change your mind while changing your mind is still free.

    You get

    • Clickable prototype in both themes
    • Every state designed, not just the happy path
    • A component inventory the build follows

    We need from you

    • Feedback in one pass, in writing
    • Your logo files and any brand rules
  3. Build

    Four to sixteen weeks

    We deploy from day one. There is no reveal at the end because there is nothing you have not already seen running. Tests cover the paths where being wrong costs money.

    You get

    • Staging environment updated weekly
    • Weekly call with the engineer, not a manager
    • Automated tests on the money paths
    • Working software at every stage boundary

    We need from you

    • One decision-maker who can answer within a day
    • Test data that resembles the real thing
  4. Handover

    One week, then a month of support

    You own everything. Accounts are in your name from the start, so handover is a walkthrough rather than a migration. If you would rather we kept running it, that is a separate monthly arrangement you can end.

    You get

    • Repository and infrastructure in your accounts
    • Runbook for deploys, backups and incidents
    • A recorded walkthrough for your team
    • Thirty days of support included

    We need from you

    • Someone technical to receive it
    • A decision on who maintains it next

Typical timelines

Typical scope duration, build duration and pricing model by project size.
Project sizeScopeBuildPricing
Under £25k1 week4–6 weeksFixed price, held
£25k – £75k2 weeks8–12 weeksPriced stages
£75k – £150k2–3 weeks12–24 weeksPriced stages, monthly review