Approach
How a small practice carries a hard problem.
Aspegio keeps every engagement small enough to move quickly and rigorous enough to defend. The engineers who scope your problem deliver the work: one or two senior engineers, occasionally three for larger programmes. There is no bench to keep busy.
That shape is deliberate. Hard, one-off problems are not served by a pyramid of juniors and a partner who visits monthly. They are served by senior hands, one question at a time.
The method
Frame, thread, iterate.
Three steps, in this order. The model beside them is built in the same order as you read.
-
01
Frame
Every engagement starts with a short, paid scoping window. We agree the problem, who will use the tool, the data reality, and one real case to carry from end to end. Scoping is allowed to end the project: if the data cannot carry the work, or a spreadsheet already answers the question, we say so and stop.
What you get
A written scoping note
-
02
Thread
We build the thinnest version that works from end to end, and we build it quickly: one real case in, one real answer out, as software your team can open. It is narrow and it is rough. It is also real, so the conversation moves from what a tool might do to what this one does.
What you get
A first working version, end to end
-
03
Iterate
Then it goes into your team’s hands, and we improve it in short rounds against their real work: plan, do, check, adjust. Each round widens what it covers. We show you where it is wrong, so you can trust where it is right. Handover is part of the work, not an afterthought: your team ends the engagement owning what we built.
What you get
A tool your team has shaped, and full ownership at handover
How it is built
Engineers direct, agents build.
Most of the code we deliver is written by AI coding agents, working to an engineer’s direction and under written rules. It is how one or two engineers carry a programme of tools. This is how it is kept honest.
- Direction
- An engineer scopes each piece of work, writes it down as a task, and answers for the result.
- Roles
- Each agent has a defined role and written rules. Long unattended runs have a budget and a time to stop.
- Review
- The agent that builds a change never approves it. A separate agent reviews it, adversarially.
- Sums
- Numbers are computed by code, not written by a language model, so they can be reproduced and checked.
- Evidence
- A tool is run against reference work from your own experts, and an engineer sees it running before it ships.
- Separation
- Each client’s code, rules and records are kept apart from every other client’s.
Principles
Six working principles.
- 01
One question at a time.
Engagements are scoped to a named decision, not a theme.
- 02
Senior hands, no bench.
The people in the room are the people doing the work.
- 03
Build for handover.
Source, documentation and capability transfer are deliverables, not extras.
- 04
Honest about uncertainty.
We tell you what the model cannot support.
- 05
Engineering practice, not theatre.
No giant discovery phase, no black box if a simple model will do.
- 06
The catalogue is not the limit.
If the right tool does not exist, we build it.
A small firm
Working with a small firm.
Capacity
We take on a handful of engagements at a time and staff them with one or two senior engineers, occasionally three. If we cannot give your problem senior attention, we do not take it on.
Continuity
Everything we build is handed over with source, documentation and training, so the practice survives our exit. You are never dependent on us to keep the work alive.
Confidentiality
Most of our work sits under client confidentiality, including programmes for Rolls-Royce, the FCDO and FLSmidth. We are comfortable under NDA by default.
What can stop the project
The scoping gate is real. Projects stop there when the data cannot support the model, when a simpler tool already answers the question, or when the decision has in truth already been made. You pay for the scoping window, not for momentum.
Practicalities
Working with us.
- First call
- A 30-minute first call. Always free.
- Response
- Replies come from an engineer, usually within a business day.
- Scoping
- If the work is right for us, a short written scoping note within the week.
- Length
- Advisory, 2 to 12 weeks. Build, 8 to 36 weeks. Training and capability, 4 to 24 weeks.
- Ownership
- Full ownership at handover: source, documentation, capability.
- Hosting
- In your environment, or run by us until yours is ready.
- Confidentiality
- NDA comfortable by default.
Talk to an engineer, not a sales filter.
A 30-minute call answers most of the questions this page cannot.
Write to an engineer harry@aspegio.comFirst call 30 minutes, always free.
Write to an engineer