Skip to content

How a project runs.

Four phases, each ending with something you can hold. And the cases where we advise against a project.

  1. 01

    Talk

    A call about what slows you down: who does what today, where it gets stuck, what it costs you. If we are not the right fit, we say so.

    You get: A straight answer on whether and how we would do it.

    First call
    • Who does what today
    • Where it gets stuck
    • What it costs you

    Our answer

    How we would do it

  2. 02

    Plan

    We map the process with the people who run it every day, and write down what gets built, what it costs and what stays out.

    You get: Scope and price in writing, before anything is built.

    Scope and price
    In writing

    What gets built

    PriceTake a part out or put it back: the price follows.

    Agreed before the build starts

  3. 03

    Build

    We start with one narrow path that works from start to finish in your environment, then widen it. Your team tests as we go, and you decide where a person has to confirm.

    You get: Working steps to try as they are built.

    Built in steps
    In your environment

    Choose where a person confirms

    First path, end to end
    Then wider

    Tested by your team

  4. 04

    Handover

    You get the source code, the documentation and every access. Care and hosting afterwards, if you want them.

    You get: Everything you need to run it without us.

    Handover
    Yours
    • Source code
    • Documentation
    • Every access

    Care and hosting afterwards

    If you want them

    Your team runs it

When we advise against it

Not every process should be automated. In these cases we say so.

  • Your software can already do it

    If a setting or a module does the job, we tell you. You don't need custom software for that.

  • The process is still changing

    Automating something that will look different in three months means paying twice.

  • Every case needs judgement

    Where each case needs a person's judgement, automation is the wrong tool.

  • There is no volume

    Ten cases a year don't pay for a system, even if saying so costs us the project.

Tell us what slows you down.

A few lines are enough: what you want to achieve, and by when. We answer within one business day.

Start a projectAsk a question