We aim for speed and simplicity

What you are actually buying.

A single fixed fee against a written scope, four to eight weeks from start to handover, and a specific piece of working infrastructure at the end of it. We aim for the simplest thing that answers the question, because complexity is what makes a build somebody else cannot maintain. Below is what happens in between, in the order it happens.

Ask what yours would involve

Week 1

Finding out what is actually true

What happens: We map every system holding a record that matters, work out what can genuinely be extracted from each, and sit with the people who use them. Most of the useful information in this week comes from the workarounds people have built, because those mark precisely where the systems stopped serving the operation.
What you get: A source map, and a written list of the contradictions we have to resolve.

Week 2

Agreeing which number wins

What happens: Where two systems disagree, somebody has to decide which one the business will treat as authoritative, and that decision belongs to you rather than to us. We bring the options and the consequences of each; you make the call, and we write it down so it is not relitigated in six months.
What you get: Agreed definitions, join rules and a metric dictionary.

Weeks 3 to 6

The build

What happens: This is the part that produces the thing you are paying for, whether that is a joined data store, a reporting layer, an embedded automation or a planning model. We reconcile continuously against figures your team already accepts, because reporting that disagrees with the board pack is reporting nobody will use.
What you get: The working build, reconciled and in your environment.

Weeks 7 to 8

Handover, and then leaving

What happens: We document the build for the person who inherits it rather than for ourselves, walk your team through it while they drive rather than watch, and then stop. If a phase two is warranted we will say so, but it is quoted separately and there is no expectation that you take it.
What you get: Documentation, a runbook and a team that can operate it.

On tooling

We build on what you already run.

Where you already have a warehouse, we build inside it. Where you have nothing, we will stand up something deliberately unexciting and widely supported, so that the next person to touch it is not dependent on a choice we made for our own convenience. The same principle governs the automation work: the boring option is usually the fast one.

We are not a reseller and we take no commission from any vendor, which means we have no reason to recommend a platform you do not need.

On client examples

Why there are no logos on this site

We sign our clients’ confidentiality agreements rather than asking them to sign ours, and we will not name anyone without written permission. We would rather show you the method and let you judge it than publish anonymised stories you have no way of verifying. Ask us in a conversation and we will be specific.

Have that conversation