1SOFTWARELimited · London W12

The method, in order.

We don’t publish client logos, awards or headline figures. What we can show you is how work is organised and what we check before calling something finished.

  1. Agree item one

    A short conversation and a written summary of the first release: who it is for, what they must be able to do, and what is deliberately left out.

  2. Shape it

    Flows and wireframes before polished visuals. Cheap to change, easy to discuss.

  3. Build in slices

    Working pieces you can try early, rather than one large reveal at the end.

  4. Check against criteria

    The list below, applied honestly. Where something falls short, we say so and agree what to do.

  5. Release and hand over

    Help with submission or launch, and notes so the next person can carry on.

Quality criteria we write down

These are checks, not guarantees. Each project agrees which apply.

Quality criteria and how each is checked
CriterionHow we check it
The main task can be completedWalk through it on a phone and a desktop, with a keyboard and with large text.
Text is readableContrast checked; layout holds at small widths without sideways scrolling.
Errors explain themselvesEach form and failure state says what happened and what to do next.
Nothing pretendsNo buttons without behaviour, no placeholder claims, no fake data left in.
Someone else can maintain itHandover notes cover hosting, accounts, and how to make common changes.
Personal data is handled with careOnly collected where needed, and described in plain language.
What if the first release turns out too big?

We cut it, together, before building further. The list is ordered so that this is a conversation about item order, not a renegotiation.

Do you sign off your own work?

You do. We check against the agreed criteria and show you the results; acceptance is your decision.

Can we skip stages?

If you already have designs or a clear spec, yes. We will review them first rather than repeat the work.