← Back

Services

Six kinds of work. Most jobs are two or three of them at once, because the interesting problems sit where they meet.

01

Building the software

The thing itself: an assistant that does a job, a system that sets prices, a tool your team opens every day.

I do all of it — where the data lives, the logic that makes decisions, the screens people click, and getting it running on your systems. At the end you have something working, with notes on how to keep it working. Not a demo that needs someone else to finish.

02

Working out what to build

Which ideas are worth building, in what order, and which ones to drop. Usually a short piece of work before anything gets made.

AI projects usually fail because the data underneath is a mess, not because the AI is bad. I look at what you already have, tell you what you can reach in the next few months, and what needs fixing first.

03

Connecting AI to your own systems

So your team can ask a question in plain language and get an answer from your own numbers.

I connect the AI tools your team already uses to your real systems and data. Set up so people only reach what they are allowed to, every question and answer is recorded, and nothing can change or delete anything live by accident.

04

Dashboards and reporting

Reports people actually trust, where a number means the same thing everywhere in the company.

The hard part comes before the chart: agreeing what a word like "revenue" means, deciding who owns that answer, and making every report read from that one definition instead of keeping its own copy.

05

Getting your data in order

Collecting data from the places it lives, cleaning it up, and keeping it current.

Built on one rule: every number is worked out in exactly one place, and everything else reads it from there. That rule is what stops a company ending up with three different answers to the same question.

06

Helping your team use AI well

Getting your developers genuinely faster with AI coding tools, instead of just having them installed.

How to set a project up so the tools help rather than get in the way, when to run several at once, what to check before trusting what comes back, and where they should not be used at all.

How engagements work

Project
A clear job, built and handed over
We agree in writing what it is and what it has to do. At the end it runs on your systems, with instructions for keeping it going — not just the code.
Retainer
I act as your AI and data team
A monthly arrangement: the list keeps moving, the tools stay working, and your team can ask me things as they come up. This is what most of my work turns into after the first project.

The first conversation is free, and specific. Bring the job that is slow, done by hand, or where nobody trusts the numbers, and I will tell you honestly whether software fixes it — including when it does not.

martin@enumstudio.com