Skip to content

How we work

From rough idea to release N.

Six steps, each ending in something you can see or use. After launch the loop starts again, with the same team.

01 / You bring

notes.docx✎ sketch of the booking screenorders.xlsxRe: Re: app idea

02 / We build

01Discover

Scope + estimate

02Design

Prototype

03Build

Sprint demos

04Test

QA + security

05Launch

Live app

06Grow

↺ Next release

03 / You get

1 yr+and still shipping
100%your code, your IP

The process

Six steps. One team.

Every step ends in something concrete — a scope, a prototype, a demo, a release — not a status update.

01 · Discover — We listen and write it down

It starts with a free 30-minute call to hear what you're building and why. From there your notes, sketches and spreadsheets become a written scope, with an estimate built around what you're actually asking for rather than a rate card.

Scope + estimate

02 · Design — You try it before we build

The scope becomes a clickable prototype before any production code exists, so you're reacting to something real instead of a document. Changes at this stage cost a conversation, not a rebuild.

Prototype

03 · Build — A demo every sprint

Engineers build against the agreed prototype in short sprints, and you see a working demo at the end of each one. Nothing about the product reaches you as a surprise months into the build.

Sprint demos

04 · Test — We break it so users can't

We run QA and a security pass against the scope we agreed, not against an ideal version of the product. Bugs get fixed before launch instead of landing in a backlog you inherit.

QA + security

05 · Launch — Live, handed over, yours

The app goes live on infrastructure you control, with the source code, credentials and documentation handed over at the same time. You own what we built — none of it stays locked to us.

Live app

06 · Grow — New features and support

Launch is a milestone, not the end of the relationship — we stay on for support and the next release. The loop starts again at Discover for whatever comes after, with the same team that shipped the first release.

↺ Next release

Questions

Straight answers.

If yours isn't here, email us and we'll answer it directly.

How long does a project take?

It depends on scope, so we don't quote a timeline before we've heard what you're building. A free 30-minute call gets you a written estimate for your project specifically, and you see a demo every sprint so you can watch progress instead of waiting for a delivery date.

How much does this cost?

There's no price list — cost follows scope, not a package tier. You get a written estimate after the same free call, before you commit to anything.

Do we own the code?

Yes. You get the source code, the infrastructure access and the documentation at handover, in full. Nothing we build for you stays locked to us.

What happens after launch?

We stay on. Launch starts the Grow step, not the end of the engagement — new features, fixes and the next release, with the same team that shipped the first one.

Can we start small?

Yes. The discovery call is free, and plenty of engagements start as a scoped prototype rather than a full build — we're comfortable starting from a rough version and growing it from there.

Talk to us

Ready to start something?

Send us the rough version. We reply within one business day.

Start a project →