Aspegio, home Write to an engineer

Services

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 full-stack software, applied AI and modelling.

Whatever we build, you own: source, documentation and the means to run it without us.

How we build

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.

Five capabilities

Built to the problem, owned by you.

01 / 05

Software, tools & dashboards

  • Delivery
  • 8 to 36 weeks
  • Python, TypeScript, WebGL
  • Full ownership at handover

Full-stack software, built to a brief. Complete working applications that replace brittle spreadsheets: the screens your team uses, the logic and calculations behind them, the data underneath, and the hosting. Owned by the client.

We build the thing, not a slide deck about the thing, and we make sure it is sustainable. We build for enterprises and for small companies: internal applications, decision-support dashboards and scenario explorers. Recent tools prepare proposals for engineered equipment, forecast sales, and carry engineering calculations out of spreadsheets into tested code.

Typical questions

  • Which spreadsheet has quietly become critical infrastructure?
  • Which steps of a proposal are reading and re-typing, and which are engineering judgement?
  • 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. Until your own IT is ready to host it, we can run it for you.

02 / 05

Applied AI systems

  • Delivery
  • AI, data and engineering

Statistical and machine-learning models, and applied LLM tooling, built into real engineering workflows rather than trend decks.

In the systems we build, a language model does the reading: enquiries, specifications, translations. The sums are done in code, so every figure can be reproduced and checked, and a person signs off before anything leaves. 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. Evaluation means running it against work your team has already done, and showing where it differs.

03 / 05

Modelling & simulation

  • Delivery
  • 8 to 36 weeks
  • Models and evidence

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.

04 / 05

AI strategy & adoption

  • Advisory
  • 2 to 12 weeks
  • Reports and briefings
  • Boards and CxOs

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.

Why ask engineers

We are not strategists who would not know how to ship the thing we are recommending. Every roadmap we produce we could, in principle, deliver ourselves.

05 / 05

Training & capability

  • Embedded
  • 4 to 24 weeks
  • On-site and remote
  • Internal teams

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 calibrated to a specific team, a specific problem and a specific dataset, using the AI tools your organisation already has. Your people do the building; we supply the method, written guides and review.

What you receive

  • Curricula and learning pathways.
  • Embedded delivery alongside your engineers.
  • Senior leadership briefings.
  • Knowledge transfer designed so the practice survives our exit.
  • Where it helps, an internal community of practice.

Three shapes of engagement

Engagement terms.

The three shapes of engagement: mode, length and output
AdvisoryBuildTraining & capability
ModeAdvisoryDeliveryEmbedded
Length2 to 12 weeks8 to 36 weeks4 to 24 weeks
OutputReports, briefingsSoftware, modelsCurricula, 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.
How it is built
By senior engineers directing AI coding agents, under written rules and independent review. How that works.
Ownership
Everything we build is handed over: source, documentation, full ownership.
Hosting
In your environment, or run by us until yours is ready.

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.

The catalogue is not the limit.

If the right tool does not exist, we build it.

Write to an engineer harry@aspegio.com

First call 30 minutes, always free.