Skip to content
PeakX Routes
TREN
Get a Quote
Process

Six clear steps
from discovery to launch

At every step we state what we deliver, how long it takes and what we need from you. No surprises.

  1. Discovery and scope

    1 week

    Before we talk about the work, we talk about the problem. Who is the user, what are they trying to do, what can't they do today?

    In a one-week discovery round we map the goals, the technical constraints and the competition. You end up with a scope list, a risk list and a realistic schedule. The scope is locked in writing; anything that arrives later is quoted as a separate line item — which removes the risk of a surprise invoice.

    • Scope document
    • Risk list
    • Schedule and budget

  2. Design and flows

    2 – 3 weeks

    Before drawing screens we draw the flow. How many taps it takes a user to reach their goal matters more than picking a colour.

    Information architecture, a flow diagram, then high-fidelity screens. Colour, spacing and typography are defined as tokens, and those tokens go straight into the code. Dark and light themes are designed at the same time, not added later.

    • Flow diagram
    • Screen designs
    • Design tokens

  3. Architecture and infrastructure

    1 – 2 weeks

    Decisions about the data model, authorisation, scaling and backups are made before the first line of code.

    We write the data model, the endpoint contract and the permission matrix. Environments (development / staging / production) and the deployment pipeline are set up at this stage. Where secrets live, where logs are written and how a backup is restored are clear from the start.

    • Data model
    • API contract
    • Environment setup

  4. Development

    Depends on scope

    We work in two-week cycles. At the end of each one you have a working build.

    Every cycle ends with a demo and a working build on staging. Progress is discussed as delivered features, not percentages. Code review and the automated check pipeline are open from day one.

    • A demo every two weeks
    • A staging build
    • A changelog

  5. Testing and launch

    1 – 2 weeks

    Testing on real devices with real data. Then the store and server release.

    Screen tests, load tests and a real-device round. On mobile, store submission, permission texts and rating questionnaires; on web, performance and accessibility audits. A rollback plan is written before launch — the bad scenario deserves a plan too.

    • Test report
    • Store release
    • Rollback plan

  6. Maintenance and growth

    Ongoing

    Launch is a beginning, not an end. We measure, improve and plan the next release.

    Bug fixing, monitoring, performance work and a release schedule. We set the priorities for the next cycle together, using usage data. If a handover is requested, the source code, the documentation and the training are delivered in full.

    • Monthly maintenance summary
    • Monitoring dashboard
    • Release roadmap
Responsibilities

Who does what,
and when?

What usually delays a schedule is not the technology but unclear responsibilities. So we write them down up front.

From us

A written scope, a day-by-day schedule, a demo every two weeks, a weekly progress report and the complete source code.

From you

A single decision-maker, feedback within 3 business days after each demo, and product content delivered on time.

Together

Handling scope changes in writing and with a price; prioritising with usage data rather than opinion.

Book a Discovery Call

Shall we turn your idea
into a real product?

Let's write the scope together and give you a day-by-day schedule. The first call is free; we reply within one business day.

Get a QuoteSee Pricing

Written scope · Fixed price · You own the source code