Plate H · The launch sequence

How we work: how a Cyberpath project runs, from scan to launch

no fog, no surprises

You always know what is happening and what comes next. Here is the whole path, in the order it happens.

01 · The idea

Plain steps, plainly shown

Most software projects go wrong in the dark. Nobody sees the work until the end, and by then it is too late to change it.

We work the other way round. You get a written plan and a fixed quote first. You try a prototype before we build. You see the real thing every week on a private link. And you get a handover you can read, so you are never stuck.

Start a mission
Two people at a desk talking through a flow diagram on a laptop, with a chalkboard of sketches behind them

How a project runs

four steps, no fog

  1. 01

    Scan

    We spend time with you and your team. We map how work moves today, where it stalls and what is worth fixing first, then write it down in plain English.

    You get A written plan and a fixed quote.

  2. 02

    Design

    We sketch the fix and turn it into something you can click. You try it, tell us what feels wrong and we change it before any real building starts.

    You get A clickable prototype you can try.

  3. 03

    Build

    We build in small steps and show you the work every week on a private preview link. You see progress, ask questions and change direction while it is cheap.

    You get Weekly demos on a private preview link.

  4. 04

    Launch

    We take it live, train your team and write down how it works. Then we agree what happens after launch, so you are never guessing who to call.

    You get Go-live, training, documentation and an aftercare plan.

02 · From you

What we need from you

  • A short note on what is slowing you down
  • A person who can answer questions and decide
  • Access to the tools and files involved, when we reach the build
  • About half an hour a week for the demo

03 · At the end

What you keep

  • A written plan and a fixed quote, before any work
  • Documentation that explains how it works, in plain English
  • Access to what we built, handed over with notes
  • A named person to write to after launch

Who owns what is agreed in writing before work starts.

Ways to work with us

Four ways to start, from one small fix to a long-term partner. Quoted in writing after a free scoping call.

  • W-01

    Sprint

    One problem, fixed fast.

    Suits
    A single pain point, such as an automation or a link between two tools.
    • A short scan of the problem
    • A fixed, written quote
    • One focused build with weekly demos
    • Handover notes
    Talk about a sprint
  • W-02

    Build

    A platform, app or game.

    Suits
    A bigger idea that needs designing and building properly.
    • A scan and a written plan
    • A clickable prototype
    • Weekly demos on a private preview link
    • Launch, training and documentation
    Talk about a build
  • W-03

    Unit setup

    One of the four Units, set up for you.

    Suits
    Teams that want to switch something on without a long build.
    • Your choice of FLOW, PULSE, ARCADE or SIGNAL
    • Set up around your tools and branding
    • A walk-through for your team
    • A clear price before we start
    Talk about a Unit
  • W-04

    Care

    Ongoing support and improvements.

    Suits
    Teams that have launched and want a steady hand to keep it healthy.
    • A named person to write to
    • Fixes and small improvements
    • Regular check-ins
    • A plain-English log of what changed
    Talk about care

Not sure which fits? Start with a sprint or a Unit setup. Both are small, both come with a written quote, and both can grow into a bigger build when you are ready.

No public prices: every project is different. We quote in writing.

Got a problem, a hunch or a blank page?

Tell us what's slowing you down.

Send a short note. We reply with a plan and a clear price before any code is written.

Email us