Our process

How a project goes, from first call to launch

Every project goes through the same steps. How long each one takes depends on the project, but you'll always know which step we're on.

  1. 01

    Discovery

    We talk to you and, where we can, the people who'll use the software. The goal is to agree on what problem we're solving and what's out of scope, before anyone writes code.

    • Scope document
    • Rough timeline
    • Risks we can see
  2. 02

    Planning

    We choose the stack, sketch the data model and APIs, and break the work into milestones you can check against.

    • Architecture outline
    • Database schema
    • Milestone plan
  3. 03

    Design

    We design the main screens and flows in Figma and you click through them. It's much cheaper to change a design than to change code.

    • Figma designs
    • Clickable prototype
    • Shared components
  4. 04

    Development

    We build in short cycles and show you working software as we go, so there are no surprises at the end. Every change is reviewed by a second engineer.

    • Working builds
    • APIs
    • Regular demos
  5. 05

    Testing

    Automated tests for the important paths, manual testing on real browsers and devices, and a look at performance and security before launch.

    • Automated tests
    • Security check
    • Performance check
  6. 06

    Launch

    We set up hosting, the domain, SSL and a deployment pipeline, then launch and keep a close eye on things for the first few days.

    • Production hosting
    • Deployment pipeline
    • Domain and SSL
  7. 07

    Support

    After launch we can keep looking after it: monitoring, security updates, bug fixes, and new features as the product grows.

    • Monitoring
    • Security updates
    • New features
  8. Step zeroTell us what you needA short message is enough to start →