How to start

    Small, provable,
    in thirty days.

    If you've watched a data platform fail before, scepticism is the healthy response. So we don't ask for trust up front. We start with one question, make it provable, and only then talk about more.

    How you start

    One flow, four steps.

    Scan, conversation, thirty-day proof, next step. Every page below is a step in the same flow, so you never have to guess what comes next.

    1. 01About ninety seconds

      Take the foundation scan

      Six questions about your foundation. You get an honest read straight away, no email needed.

      Take the foundation scan

    2. 0230 minutes

      Book a starting call

      In half an hour we know whether there is a good starting point. If there isn't, we say so.

      Book a starting call

    3. 0330 days

      Prove it in thirty days

      One question, one agreed definition, a working result. Fixed price, then you decide again.

      Prove it in thirty days

    4. 04The growth path

      Decide the next step

      The thirty days are stage 1 of the growth path. See how the route continues and take the self-scan.

      Decide the next step

    Optional: where a pack for your sector fits, the thirty days start from it. See the packs

    The first thirty days

    Four weeks, one answer that holds.

    The proof loop is deliberately small. Not because we can't do more, but because trust has to be earned before it scales.

    Week 101

    Pick one question

    One question that has several answers today and that somebody genuinely needs. Small enough to prove, big enough to matter.

    Weeks 2 and 302

    Fix the meaning

    We agree the definition with the people who know it, put it in the brain and give it an owner.

    Week 403

    Let it prove itself

    Your team asks the question themselves. One answer, with source and owner. Then you decide whether this goes further.

    What the start gives you

    What's settled in the first month.

    01

    A bounded scope

    One topic, one owner, one agreed result. Not a programme.

    02

    Working within thirty days

    No six-month design phase. At the end of the month there is something you can use.

    03

    Fixed price, no open end

    You know up front what it costs and what you get back. Then you decide again.

    04

    You keep what we build

    The definitions and agreements are yours. Also if you want to continue without us.

    Good starting points

    Where others began.

    You don't need to know where to start. In the first conversation we pick the topic with the most friction and the shortest path together.

    01

    Power BI audit

    One concrete thirty-day starting point: we show where your existing reports contradict each other and which definition resolves it.

    02

    One contested definition

    Take the term finance and operations never agree on. That's usually the fastest win.

    03

    A question asked too often

    The question someone works out by hand every month. Getting it right once saves work structurally.

    After that

    Grow on earned trust.

    After the first month you set the pace. A second topic, a real data source, or nothing for a while. There's no multi-year commitment underneath and no reason to grow other than that it works.

    1. 1Sense
    2. 2Act
    3. 3Connect
    4. 4Steer
    5. 5Anticipate
    First call

    One question. Thirty days. Then you decide.

    In half an hour we'll know whether there's a good starting point. If there isn't, we'll say so.