You'll know what you get, and when.

Six stages, scaled to the problem. Each one ends with something you can review, and during the build you get a demo every two weeks. We talk wherever your team already does: Slack, WhatsApp or email. The timelines below are for a full system. A well-built MVP takes a month or less, depending on complexity.

01First, we talkTypical duration: 30 minutes

Before we write a proposal, we make sure we understand what you need.

We get on a 30-minute call and ask how your business runs today and what you need. Then we write the proposal.

Deliverables

  • A 30-minute call
  • Questions about how your business runs today
  • What the first version needs to solve
02ProposalTypical duration: after the call

Before we start, you know what we'll build and what it costs.

After we talk, you get the scope and price in writing: what goes into the first version and, just as important, what doesn't. We never start without an approved quote. If part of the work can't be estimated without a closer look, we propose a short first phase, priced on its own. The proposal is free.

Deliverables

  • Prioritized scope for version one
  • What stays out
  • Price in writing, before we start
  • Identified technical risks
03DesignTypical duration: 2 to 3 weeks

You click through the screens before any code exists.

We design the key screens and walk through them with you before writing production code. In parallel we define the architecture, the data model and the integrations.

Deliverables

  • Clickable prototype of the main flows
  • Base design system
  • Architecture diagram and data model
  • Sprint plan
04BuildTypical duration: 6 to 16 weeks

Two-week sprints with a demo at the end of each one.

We work in your repository from day one. Every change goes through code review and a preview environment with its own URL, so you can try it before it reaches production.

Deliverables

  • Working demo every two weeks
  • Preview environment per change
  • Tests on the critical flows
  • Up-to-date technical docs
05LaunchTypical duration: 1 to 2 weeks

We go live with a rollback plan ready.

We migrate the data, set up monitoring and alerts, and stay with your team through the first days of real use. If something fails, we roll back to the previous version.

Deliverables

  • Verified data migration
  • Monitoring, logs and alerts
  • Team training
  • Rollback plan
06EvolutionTypical duration: ongoing

The people who built it maintain it.

After launch we look at how the system is used and prioritize improvements with you. We keep dependencies and security up to date so the system doesn't fall behind. If it goes down in production, we're on it as soon as you tell us, even if we're in the middle of other work. It's optional, billed monthly as a Maintenance plan.

Deliverables

  • Usage and error metrics
  • Quarterly roadmap
  • Security updates
  • Monthly hours for improvements
  • Outages handled as soon as you tell us

Frequently asked questions

What if one of you is unavailable?

We both know every project, and everything is documented. The code and access are in your name, so work keeps moving even if one of us is out.

What if you land a big project?

We only take on a few projects at a time so we can deliver on each one. If we don't have room for yours, we'll tell you and give you a start date we can keep.

How do you handle confidentiality?

The code and data stay in your name, and we keep credentials in a password manager.

How can we work together?

Three ways: a fixed-scope project, with a set scope, timeline and price; ongoing development, where we work as part of your team on monthly hours; or maintenance, for a system that's already live.

What if the system goes down in production?

With a Maintenance plan, we're on it as soon as you let us know, even if we're in the middle of other work.

What happens if we stop working together?

You keep the code, the access and the docs. It's all been in your name from the start, so another team can pick it up without needing us.

How long does an MVP take?

A well-built MVP takes a month or less, depending on complexity. The written proposal spells out the timeline.

Step one is telling us what you need.