A laptop on a wooden desk showing a connected workflow diagram, beside a hand-drawn flowchart on paper, a pen and a blue mug.

HomeProcess

A calm, visible process from first message to launch.

Six steps, each with something concrete you can review. Timings depend on scope; we confirm them in the written plan before work starts.

Step by step

How a project runs.

Small or large, every engagement follows the same shape. Smaller projects simply move through the steps faster.

  1. Discover

    Understand

    We start by understanding how the work really happens: who does what, which tools are involved, where time is lost and what “better” would mean for you.

    We gather input from the people who will use the software through a short written questionnaire, review your current tools and data, and note what must not change.

    You receive

    • Process map of the current workflow
    • List of problems ranked by impact
    • Initial recommendations
  2. Define

    Plan

    We turn what we learned into a written plan you can review line by line.

    The scope separates must-haves from nice-to-haves, so the first release solves the most valuable problem quickly.

    You receive

    • Written scope and priorities
    • Phased plan and estimate
    • Acceptance criteria for each phase
  3. Design

    See it first

    You see and click through the screens before any production code is written.

    We design for the real devices and situations of your team, and test the flow with you until it feels obvious.

    You receive

    • Clickable prototype
    • Key screens for phone and desktop
    • Content and wording reviewed with you
  4. Build

    Short cycles

    We build in short cycles and show working software every one to two weeks.

    You get a private staging link to try each feature as it arrives. Feedback goes straight into the next cycle.

    You receive

    • Staging link and a short recorded walkthrough after each cycle
    • Progress notes after each cycle
    • Automated tests on critical paths
  5. Launch

    Go live

    We move your data, prepare your team with clear written guides and switch on the new system carefully.

    Launch is planned with a checklist and a rollback option. We stay close in the first weeks to fix anything that surfaces.

    You receive

    • Data migration and checks
    • Written training and admin guide
    • Launch checklist and support window
  6. Improve

    Keep improving

    Software improves with use. We keep it secure and current, and add what your team asks for.

    Through ongoing development or a care plan, you get regular releases and direct email access to us, since we built it. Monitoring, backups and the quarterly priority review are included only in the care & maintenance plan.

    You receive

    • Release notes
    • Monitoring and backups (care & maintenance plan only)
    • Quarterly priority review (care & maintenance plan only)

Working together

What you can expect from us.

  • One clear point of contact who knows your project in detail.
  • Plain-language updates after every cycle, with what is done, what is next and any decisions needed.
  • No surprises on cost: changes to scope are written down and agreed before work starts.
  • Honest advice, including when a simpler or cheaper option will do.

From your side

What helps a project go well.

  • A decision-maker available to review and approve each step by email.
  • Written answers from the people who do the work today, in a short questionnaire during discovery.
  • Examples of your current tools and data, such as spreadsheets, forms and exports.
  • Timely written feedback on the staging link and walkthrough, so each cycle builds on the last.
Hands typing on a laptop next to an iced coffee.

Next step

Ready for step one?

A free workflow review by email costs nothing and commits you to nothing. We will tell you honestly how we would approach it.