Skip to content
Book a free 30-minute call with an engineer

How we work

Two-week sprints, a demo at the end of each one and a staging link you can click through any time. Here’s what that looks like week to week.

MVP roadmapSprint 4 of 6 · launch in 3 weeksLater2Next2Now2Done3Referral codesGrowthDark modeUIAdmin exportsBackendPush remindersMobileStripe checkoutPaymentsOnboarding flowDesignSign up & loginAuthBooking APIBackendStore listingReleasev1.0 live

The five stages

Five stages, two-week sprints and a demo at the end of every one.

  1. 01  Week 1

    Discover

    A couple of workshops with your team. We map the users, the must-haves and the risks, then send a written scope with a fixed estimate.

    MVP roadmapSprint 4 of 6 · launch in 3 weeksLater2Next2Now2Done3Referral codesGrowthDark modeUIAdmin exportsBackendPush remindersMobileStripe checkoutPaymentsOnboarding flowDesignSign up & loginAuthBooking APIBackendStore listingReleasev1.0 live
  2. 02  Weeks 2 to 4

    Design

    User flows, wireframes and the visual design in Figma. You click through a prototype, and we test it with a few real users before any code.

    Home · v2StaylineLisbon, 3 nights12 to 15 May · 2 guestsFree cancellation until FridayTotal€486Book nowColourTypeAaHeading 32Body 16 / 1.5Caption 12ComponentsPrimarySecondaryToggleTested with 6 users ✓
  3. 03  2-week sprints

    Build

    Code, tests and a staging site you can open any time. Every sprint ends with a demo, so you always see what changed.

    app.yourcompany.com/ordersNorthdeskOverviewOrdersCustomersInventoryReportsSettingsOrders142 this month · $48,210+ New orderOrderCustomerStatusTotal#1042Maple StudioNew$3,400#1038Harlow LtdPaid$1,240#1039BrightwayPending$860#1040Okafor & CoPaid$2,115#1041NordlineShipped$540Order #1042 created
  4. 04  Go-live

    Launch

    Security checks, load testing, App Store and Play Store submission, then a production release with monitoring switched on.

    ~/app — zsh$ git push origin mainEnumerating objects: 14, done.To github.com:acme/app.git 4f2a1c9..b81e0d3 main → mainCI triggered: pipeline #482Instances3 / 3 healthyCPU 64% · autoscale onPipeline #482main · b81e0d3BuildTestDeploy
  5. 05  After launch

    Improve

    We watch the analytics, fix what users trip over and keep shipping features. Most clients keep us on after launch.

    Uptime · last 30 days99.98%30 days agoTodayResponse time142 msp95 · all regions09:0015:00Incident resolved · 4 minCheckout API latencyRolled back · on-call: SamDeployed to productionv2.14.1Today 09:12Latest

How quality is built in

  1. 01

    Two-week sprints

    Planned together and demoed every other week. You see working software, not slide decks.

  2. 02

    Staging from day one

    A live staging environment lets your team click through every feature as it’s built.

  3. 03

    Automated testing

    Unit, integration and end-to-end tests run on every pull request to keep regressions out.

  4. 04

    Continuous delivery

    Every merge is built, tested and ready to deploy, so releases stop being events.

  5. 05

    Peer code review

    Every change is reviewed by a second senior engineer for quality, security and clarity.

  6. 06

    Clear communication

    A dedicated project lead, a shared Slack channel and a short written update every week.

Ways to work with us

Pick the one that fits your budget and how settled your plans are. You can switch later.

Good for MVPs

Fixed scope

We agree the scope, timeline and price before we start. Works best when you know what the first version needs to do.

  • Fixed budget and deadline
  • Paid by milestone
  • Written specification

Most common

Dedicated team

A product manager, designers, engineers and QA working on your roadmap as if they were in-house.

  • Full-time team on your product
  • Resize month to month
  • Shared Slack channel

For changing plans

Time and materials

You pay for the hours used. Useful for products that are still finding their shape or need ongoing work.

  • Change priorities any week
  • Weekly time reports
  • No long contract

Questions, answered

How do you estimate a project?

After a discovery call we break the product into features, estimate each one and add design, QA and project management. You get a written proposal with scope, timeline, cost and the assumptions behind them.

How involved do I need to be?

Around an hour a week: a sprint demo and quick feedback on designs and priorities. We handle the day-to-day and bring you decisions, not problems.

What if requirements change?

Change is normal. On dedicated-team and time-and-materials engagements we re-prioritize the backlog. On fixed-scope projects we estimate the change and agree on it before work starts.

What do I get at the end?

Full source code, infrastructure configuration, technical documentation, design files and admin access to every service, plus a handover session and an optional support plan.