Plans can change, but your budget doesn't have to.

We build your Shopify or Odoo system in short cycles, with you using it from the first one. You can reprioritise as you go without the budget creeping up, and by go-live your team already knows the system inside out.

How your project will run

1. Strategic review

Before we design anything, we want to know where you're heading. A single site and a group planning acquisitions need different systems underneath them. So let's get this straight from the start.

2. Analysis and blueprint

This is where every project really starts. We map how you actually work. Roughly first, then in real detail with your team in the room, argued out properly.

You finish with what we're building and why, the full list of work in priority order, the sequence we'd build it in and what it costs.

3. Four-week cycles

We work in four-week cycles. That means: two weeks where we build, two weeks you use what we built. Priorities get reviewed with you before every one, so the plan keeps matching what matters now.

4. ddCare

Go-live isn't the finish line. Our team stays with you to keep your system running and ready for what's next, for a fixed price.

Most of a new system's value shows up in the months after launch, and that's when we stay close.

How does the four-week cycle system work?

First, we define
Every cycle starts by agreeing what 'finished' means to you: the specific conditions you'll check it against. We write those with you before anything gets built, so everything is clear for everyone involved.

We build, you test
Then we build for two weeks, and you spend the next two weeks using it on your own work, with our project owner beside you to answer questions and catch what isn't right.

Fixed budget, your priorities
You decide what's worth building before every four-week cycle. The budget stays fixed and we reprioritise the work inside it with you. And by the time you go live, none of it is new: your team has been working in the real system for months.

Three things we commit to before we start

  • The budget is fixed, the scope flexible
    You commit to a budget. We keep prioritising the work inside it, with you, for as long as the project runs.

  • You test it yourself, from the first cycle
    Every four weeks you get a working version and two weeks to use it properly. What you find goes into the next cycle, not onto a list for later.

  • One team, from the first workshop to years after go-live
    From start to years later, you're still working with the same partner. We know your company through and through, all documentation within our reach. We only have to get to know you once.

Questions we get asked

How long will our project take?

That depends on scope, but you won't be guessing. The blueprint tells you how many cycles we expect, and we update that forecast after every single one. The first cycle usually delivers less than the ones after it, which is normal and already in the plan.

What if we change our minds halfway through?

Then we change the plan. That's the whole point of working this way. Priorities get reviewed before every cycle, so a change of mind is a normal conversation rather than a renegotiation.

What if we don't have time to test every cycle?

Then tell us now. The model depends on a few hours from the right people every four weeks, and it's the cheapest time you'll spend on the project. If nobody is genuinely available, we'd rather redesign the rhythm with you up front than build for months on assumptions.

Do we need to understand agile to work with you?

No. You need to know your own business and be able to make decisions. The method is our job.

Who decides what gets built first?

You do. We advise, sometimes strongly, and we'll tell you when we think you're prioritising the wrong thing. The call is yours.

What if a cycle doesn't deliver everything that was planned?

You'll hear about it during the cycle, not at the end of it. Unfinished work moves to the next one. We don't demo things that aren't done, because a demo of nearly-finished work is how projects end up looking healthier than they are.

Let's talk about how your project would run

Tell us what you're trying to change. We'll walk you through what your first weeks would look like, and what we'd need from you.