What we build, and what you receive.
There is no catalogue here. Every engagement is scoped to a specific decision and built by senior engineers. Most work combines simulation, custom software and applied AI. Whatever we build, you own: source, documentation and the means to run it without us.
30 minutes, always free
No catalogue.
We don’t configure software; we design and build it: from first principles when the problem deserves it, from proven primitives when it doesn’t.
Modelling & simulation.
- Mode
- Delivery
- Cadence
- 8 to 36 weeks
- Output
- Models, evidence
What we model
Factories, fleets, queues and teams rarely behave like the spreadsheet average. The cheapest place to discover that is inside a model: a small virtual world that can be tested, challenged and improved before money moves. We build discrete-event, agent-based and physics-based simulations of queues, assets, logistics, resources and uncertainty.
Typical questions
- Where does the design break under real movement: queues, bottlenecks, capacity?
- What does the transition cost, down to the unit economics?
- Which operational policy still holds when the inputs are uncertain?
What you receive
A working model with its documentation, the runs and evidence behind every claim it makes, and a handover so your team can run and extend it. You own all of it.
Software, tools & dashboards.
- Mode
- Delivery
- Cadence
- 8 to 36 weeks
- Stack
- Python, TypeScript, GL
- Handover
- Full ownership
What we build
Decision tools, not products. Custom software, decision-support dashboards, scenario explorers and internal applications that replace brittle spreadsheets: engineered to a brief and owned by the client. We build the thing, not a slide deck about the thing, and we make sure it is sustainable.
Typical questions
- Which spreadsheet has quietly become critical infrastructure?
- What would the planning cycle look like as a tool the team actually uses?
- Can the model we built become something operators run every week?
What you receive
Full ownership at handover: source, documentation, and a team that knows how to run it.
Applied AI systems.
- Mode
- Delivery
- Domain
- AI, data, engineering
What we build
Statistical and machine-learning models, and applied LLM tooling, built into real engineering workflows rather than trend decks. Where a simple model answers the question, we say so and build the simple model: no black box if a simple model will do.
Typical questions
- Where does AI genuinely change this workflow, and where is it theatre?
- Can the system’s output be checked by the people who rely on it?
- What does it take to run this inside our own environment?
What you receive
A scoped, working system, the evidence from its evaluation, and the documentation to hold it to account.
AI strategy & adoption.
- Mode
- Advisory
- Cadence
- 2 to 12 weeks
- Output
- Reports, briefings
- Audience
- Boards, CxO
What we advise on
Independent advice for boards, programmes and technical leaders on where AI changes the answer, and where it does not. Roadmaps, audits and decision-support architecture for leaders deciding what to build, what to buy, and what to leave alone.
What you receive
A 12-to-24-month roadmap sequenced by value, risk and team readiness, with build, buy or partner scenarios. Audit and assurance. Technical due diligence on investment theses. Briefings and senior sessions. A standing advisory retainer where useful.
Training & capability.
- Mode
- Embedded
- Cadence
- 4 to 24 weeks
- Format
- On-site, remote
- Audience
- Internal teams
What we deliver
Training, briefings and embedded coaching that lift teams from AI-curious to AI-productive: practical, and grounded in the engineering work they are actually doing. We deliberately avoid generic training. Sessions are multi-day and calibrated to a specific team, a specific problem and a specific dataset.
What you receive
Curricula and learning pathways. Embedded delivery alongside your engineers. Senior leadership briefings. Knowledge transfer designed so the practice survives our exit, and, where it helps, an internal community of practice.
Engagement terms.
What we don’t do.
- Resell off-the-shelf software.
- Run very large, multi-year transformation programmes.
- Staff a standing team of twenty. We work in small senior teams.
- Compete on being cheapest.
| Advisory | Build | Training & capability | |
|---|---|---|---|
| Mode | Advisory | Delivery | Embedded |
| Cadence | 2 to 12 weeks | 8 to 36 weeks | 4 to 24 weeks |
| Output | Reports, briefings | Software, models | Curricula, coaching |
- Team
- One or two senior engineers, occasionally three for larger programmes.
- Who you work with
- The engineers who scope the problem deliver it. The practice is led by Harry Munro, CEng MIMechE: CEO and Director of Aspegio Ltd and Chief Technology Officer of Aspegio (Bermuda) Ltd.
- Ownership
- Everything we build is handed over: source, documentation, full ownership.
The catalogue is not the limit.
If the right tool does not exist, we build it.
Write to an engineerharry@aspegio.comFirst call 30 minutes, always free.