369 Lexington Avenue, 3rd Floor, New York City, NY 10017Mon-Fri 9:00-18:00 · [EMAIL]
Get a Quote

Process

Our Software Development Process

Four steps, written outputs at each one, and working software every two weeks.

  1. Discover

    Duration confirmed in discovery

    Stakeholder interviews, workflow mapping, integration inventory and a written scope with a phased estimate.

    • Prioritized backlog
    • Architecture outline
    • Clickable prototype
    • Phased estimate
  2. Design

    Duration confirmed in discovery

    Interface design tested with real users, technical design reviewed with your IT and security stakeholders.

    • Validated UI designs
    • Data model
    • Security plan
    • Release plan
  3. Build

    Duration confirmed in discovery

    Working software demonstrated at regular, agreed intervals, automated tests in continuous integration and a staging environment you can use.

    • Regular demos
    • Automated test suite
    • Weekly written update
    • Repository you own
  4. Launch and support

    Scope-dependent

    Staged rollout, monitoring, training and a support plan, followed by iteration based on how people actually use it.

    • Runbooks
    • Monitoring and alerts
    • Handover package
    • Support retainer

Why a defined software development process matters

The software development process is where most of the risk in a project lives. Code is rarely the reason projects fail; unclear decisions, late surprises and invisible progress are. A good process makes those problems visible early, while they are still cheap to fix.

Ours is deliberately simple: four steps, each ending in written outputs you keep. It scales from an eight-week internal tool to a multi-year platform programme without changing shape.

Step 1: Discover

Discovery replaces assumptions with facts. We interview the people who will use, pay for and support the software; we map the current workflow including its workarounds; and we inventory every system the new software must connect to. Technical spikes test the riskiest integrations before they are built into an estimate.

The result is a prioritized backlog, an architecture outline, a clickable prototype of the critical journeys and a phased estimate. It is a complete package: you can take it to another vendor if you choose.

Step 2: Design

Interface design is tested with real users before engineering starts in earnest, because changing a design file costs minutes and changing shipped code costs days. In parallel, we write the technical design: data model, security approach, hosting plan and release strategy, reviewed with your IT and security stakeholders.

Step 3: Build, the custom software development process in practice

Our custom software development process runs in two-week cycles. Each cycle begins with planning against the backlog and ends with a demo of working software in a staging environment you can use yourself. Automated tests run on every change, code is peer reviewed, and a short written update arrives every week covering progress, decisions needed and risks.

You have access to the repository, the board and the staging environment from day one. If something slips, you hear about it from us first, with options.

Step 4: Launch and support

Launches are staged: internal users first, then a pilot group, then everyone. Monitoring, alerting and backups are in place before go-live. We train your staff, hand over runbooks and remain on call through the first weeks.

After launch, most clients continue on a support retainer or a dedicated team. Software that is used changes, and the process simply continues at a sustainable pace.

Quality is part of every step

Testing is not a phase at the end. Acceptance criteria are written during discovery, automated tests grow with each feature and accessibility is checked continuously. Our software testing and QA practice is available independently for teams who need it.

Related: software testing services, how we price each step, and continuing with a dedicated team.

Process questions

How involved do we need to be?

Expect a few hours a week from a product owner on your side, plus short reviews every two weeks. Discovery needs more time from more people, concentrated in the first weeks.

Can we skip discovery?

For small, well-documented work, sometimes. For anything with integrations, compliance or unclear scope, discovery is what keeps the estimate honest.

What happens if priorities change mid-project?

We re-plan at the next sprint boundary, show the impact on time and budget, and you decide.

How do you measure progress?

Working software in a staging environment, a burn-up chart against the agreed scope and a weekly written update.

Tell us what you need to build.

A member of our New York team reviews every request and replies to arrange a scoping call.

Get a Quote