How We Run A Project

The steps

1. 01

   First contact

   You reach us through the site, by email or by phone. We answer the immediate questions, learn what you are setting out to achieve, and book a discovery session with the engineers who would do the work.

2. 02

   Confidentiality

   Before you share anything sensitive we put an NDA in place, ours or yours, whichever your legal team prefers. Most procurement processes require one, and having it in place early lets the first conversation go into real detail.

3. 03

   Discovery session

   A working session led by the engineers who would build the system. We come out of it with three things:

   • A map of the systems you already run and how work flows between them
   • The objectives the new system has to meet, written down and agreed
   • A clear view of technical and operational fit
4. 04

   Proposal

   You receive a written proposal covering:

   • Scope of work, stated as what the system will and will not do
   • The architecture and technical approach, with the reasoning behind it
   • Timeline broken into milestones you can hold us to
   • A cost breakdown showing where the investment goes
   • The recommended stack, and why it suits your team
   • Who is on the project team, and what support looks like after launch
5. 05

   Technical validation

   Where a proposal depends on something unproven, a payment integration, a third-party API, a data migration, we build a small proof of it before anyone signs. Proving it early keeps the timeline and the cost predictable.

6. 06

   Agreeing scope and cost

   We refine scope, timeline and budget together until the plan fits what your organization can approve. Where the budget shapes the scope, we set out what to build first and what to phase in later, so the sequence is agreed before work begins.

7. 07

   Contract

   The agreed proposal is rewritten to match what was settled and signed as a binding contract, so what you sign is exactly what was negotiated.

8. 08

   Milestone mapping

   Before any code is written we sequence the work into two-week increments with dates against each one, and agree which milestones trigger review and payment. You know from day one what should exist by when.

9. 09

   Kick-off and environments

   Design starts while the engineers stand up the system architecture and the environments. We use Docker for packaging, GitHub Actions for deployment and Pulumi for infrastructure as code, so the pipeline that will carry the project to production is in place before the first feature lands.

10. 10

    Two-week sprints

    We run two-week sprints, each ending with a demo of working software and a retrospective that decides what changes in the next one. Work is tracked in ClickUp against a prioritized backlog of user stories, which you can see at any time.

11. 11

    Reporting and governance

    Every increment reaches an environment you can click around in, so progress is something you can see and use. Alongside it you get a written update each sprint covering what shipped, what comes next, and any risks we are tracking.

12. 12

    Testing and QA

    Before handover the system goes through functional and usability testing, performance testing under realistic load, and security validation covering access control and data handling. You get a window to test it yourself and share what you find.

13. 13

    Handover

    At completion you receive everything needed to run the system without us:

    • The source code repository and access credentials
    • Deployment pipeline and infrastructure definitions
    • Technical documentation, user guides and API documentation
    • Design files and any brand assets we produced
    • A walkthrough session with the people who will operate it
14. 14

    Ongoing support

    After deployment we stay on for maintenance, improvements and scaling as your usage grows. Running our own product keeps us close to what a system needs in its third year, and we bring that experience to yours.