Start a project
Process

A calm, clear process, from idea to launch and beyond.

No black boxes. You see progress every couple of weeks, decisions are written down, and the price is agreed before we build.

  1. 01Days, not months

    Discover

    We start by listening. In a few focused conversations we learn how your team works today, what slows it down, and what success would look like.

    • Workshops with the people who will use the system
    • Map of current workflows and data
    • The highest-value place to start
  2. 02Before any code

    Plan & quote

    We turn what we learned into a plan you can hold us to: scope, key screens, architecture and a fixed, itemised quote with a timeline.

    • Written scope and user flows
    • Clickable prototype for larger projects
    • Fixed quote, milestones and payment schedule
  3. 03Alongside planning

    Design

    Clean, accessible interfaces designed around real tasks. We test the flows with your team early, when changes are cheap.

    • Interface design and design system
    • Accessibility built in, not bolted on
    • Early feedback from real users
  4. 04Two-week cycles

    Build in sprints

    We build in short cycles and show you working software at the end of each one on a private staging site. You steer; we keep the quality bar high.

    • Demo at the end of every sprint
    • Automated tests and code review on every change
    • Shared board so you always know the status
  5. 05Planned, rehearsed

    Launch

    Go-live is a checklist, not a leap of faith. We migrate data, train your team, and watch the system closely in the first weeks.

    • Data migration and dry runs
    • Training and simple guides
    • Monitoring, alerts and a rollback plan
  6. 06For the long run

    Support & grow

    Software is never quite finished. We keep it secure and healthy, and keep improving it as your business changes.

    • Security updates and backups
    • Agreed response times
    • A roadmap of improvements
Ways to work together

Choose the engagement that fits.

Many clients start with a fixed-scope project, then move to a product team or a support plan.

Fixed-scope project

A clearly defined system or release, delivered for an agreed price and timeline. Best when you know what you need.

Ongoing product team

A dedicated slice of our team every month, working through a prioritised backlog. Best for evolving products.

Support plan

Maintenance, monitoring and small improvements for a predictable monthly fee. For systems we built or inherit.

Principles

How it feels to work with us.

Plain language

No jargon walls. You will always understand what we are doing and why.

Predictable rhythm

Weekly updates, regular demos, and decisions written down.

Quality by habit

Tests, reviews and security checks are part of every change.

Process questions

How involved do we need to be?
Most involvement happens at the start (discovery and planning) and at each demo. A single decision-maker with an hour or two a week is usually enough.
What if our needs change mid-project?
They usually do, and that is fine. We estimate each change, you decide whether to swap it in, add it, or leave it for later, and the plan is updated in writing.
Do you sign NDAs?
Yes. We are happy to sign a mutual NDA before you share anything sensitive.
Where is our system hosted?
Wherever suits you, usually in cloud accounts that you own. We set it up, document it and can manage it for you.
Start a project

Have a system in mind? Let’s talk it through.

Tell us what slows your team down or what you want to launch. We’ll reply with honest advice and a clear next step, with no obligation.

Start a project How we work