What I Do

Fixed-price reliability reviews, fixes & on-call cover

Focused engineering services built around one rule: a system should never fail the person relying on it in silence. The standard behind it, and where it came from, is on the Philosophy page.

Developer tooling, scientific software and architecture reviews are priced and scoped the same way, under Other ways to work with me.

Services

I'm the person you bring in when your system works most of the time, and nobody can tell you why it sometimes doesn't. Every engagement is scoped to a concrete outcome, not billed hours against a vague brief.

That mostly means small and medium businesses: a few people, software nobody on staff really owns, and no appetite for hourly billing. You get a fixed price agreed before any work starts, findings in plain language, and me directly, with no account manager and no hand-off.

Rather skip the technical words? Start with the plain-English version, with everyday problems and three examples.

🔧 First Fix · hands-on, one finding

One finding, one fixed price. This closes the top item from a review: with your sign-off, I build the guardrail that stops it and confirm it catches the input that caused the trouble before I hand it back. It usually follows a starter review, but you don't need to have had one.

Hands-on, but never in your live system: I work in a copy you control and hand it back for you, or whoever looks after your software, to put live.

£450 fixed · one finding, priced before any work starts
→ The thing that keeps breaking, stopped, without committing to a full engagement
Close my top finding →

🔍 Reliability Review · read-only

I read your configuration, pipelines, and validation in detail and report exactly where a wrong value or a missing guardrail will fail silently. You get prioritized findings plus the guardrail specs for your own engineers to implement.

Read-only: nothing in your system is touched or changed.

from £900 · minimum engagement; your fixed price is agreed before any work starts
→ Find the silent config failures, without anyone touching prod
Read the pack & scope it → See a sample report →

🚧 Validation & Guardrails · hands-on

Everything in the Reliability Review, plus the fix: I build the guardrails that close the gaps it finds. Schema-driven validation (JSON Schema, YAML, typing.Annotated) rejects invalid configuration and data with a clear, human-readable error before your system runs. I confirm the guardrails catch known-bad configurations before handover.

Hands-on, but never in your live system: I work in a repository, branch or environment you control, and hand over for your team to merge.

from £2,500 · minimum engagement; your fixed price is agreed before any work starts
→ Invalid states caught before deployment, not in production
Read the pack & scope it → See a sample report →

🧩 Running Odoo? · the same ladder, for your custom modules

from £200fixed

If your business runs on Odoo, the part most likely to fail quietly is usually the custom modules, built by a partner or freelancer and owned by nobody on staff. Every tier above covers them at the same fixed prices. I read the modules, I don't run them, and nothing in your Odoo database is touched or changed.

  • A rule that only holds in the form. Odoo skips form-level checks on imports, the API and scheduled actions, so bad data comes in through the side door and nobody sees it arrive.
  • Values that quietly go stale. A stored field worked out from other fields is only recalculated when the fields it lists change. Leave one off and the value goes stale whenever that one changes: no error, no failed test, just a report that slowly stops matching the data.
  • Settings every upgrade puts back. Data a module ships without protecting it is reset to the module's default on each upgrade, including the values your team tuned by hand.
  • Dates a day out. The Odoo server works in UTC and your business doesn't, so a date taken from the server's clock can land on the wrong day.
  • Upgrading to Odoo 19? From version 19, old-style database constraints are no longer created. Odoo notes it in one startup log line, and a rule like "no two customers with the same reference" simply stops existing on upgrade day. Finding them first is a Starter or Reliability Review in its own right.

How it is done: I scan the modules with Nexa, the Odoo checker I build and maintain, and read every finding myself before it reaches your report. The scan runs on my own machine and sends your code to no scanning service; anything AI-assisted is covered under How I work, below.

On the Odoo community's own open-source modules, of the findings I read by hand in September 2026, 83 were real problems, 6 were false alarms, and 7 needed more than one file to decide. Fixes are never made in your live system, always in a copy you control.

Scope an Odoo review →

See a sample Odoo report → A starter review of a fictional custom module, with Nexa's real scan results.

📞 Someone on Call · ongoing, for clients I have worked with

£200 to £450/month

What keeps a small business owner up at night is not knowing who to ask when something breaks at five o'clock on a Friday. Once we have done a piece of work together, this keeps me on call for you by the month. I already know your setup, so you are not paying someone to learn it from scratch in the middle of a bad week.

  • £200 a month: a monthly pass over your configuration and guardrails to confirm they still hold, a short note on anything that has drifted, and emergencies triaged the same working day, with anything under an hour just done.
  • £450 a month: all of the above, plus up to half a day of hands-on work each month on one task you name and we scope before I start, and I am reachable live during agreed hours when something is actually on fire.
  • That half day is a specific job agreed in advance (close this finding, add this check, fix this report), not an open afternoon of troubleshooting that finishes nothing.
  • A month you don't use isn't lost. Unused time rolls over and stays banked while your cover runs, and every monthly note shows the balance. If it grows into a block, we schedule it properly rather than squeezing it into an unplanned week. It stays yours either way.
  • Where you land in the band depends on how much cover you need, agreed before the month starts and reviewed whenever your setup changes. Quiet months move you down, not up.
  • Retainer clients come first when my week is full: your job is scheduled ahead of new inquiries.
  • Everything I already know about your setup stays loaded, including the findings from our earlier work.

What an emergency means here: I stop what I am doing and look at yours first, and you get a straight answer that day on whether it is a five-minute thing or a real job, even when the honest answer is that it isn't mine to fix. It is not a 24-hour rota: I am one engineer, and I won't sell a promise I cannot keep at three in the morning.

Day to day runs over email, so nothing gets lost. Anything bigger than the cover is quoted separately at a fixed price, and you can cancel on 14 days' notice.

Talk about on-call cover →
Other ways to work with me

The reliability ladder above is the core of what I do. These come up often enough to be worth naming, and are scoped the same way: a concrete outcome, agreed and priced before any work starts.

📐 Architecture Review

The failure modes, trust boundaries, and data flow that hold your system together live in people's heads, not on paper. I map how the pieces connect, what trusts what, and where data flows, then hand back a prioritized read of the design's weak points and what to rethink first.

Read-only: nothing in your system is touched or changed.

from £900 · minimum engagement; your fixed price is agreed before any work starts
→ See how your system really fits together, before a gap in the design bites
Discuss this →

🛠️ Developer Tooling & CLIs

Your team loses hours to fragile scripts, manual steps, and tools only one person really understands. I build internal tools, CLIs, and developer-experience improvements that turn that friction into something anyone can run without holding their breath.

Hands-on, but never in your live system: I work in a repository, branch or environment you control, and hand over for your team to merge.

from £2,500 · minimum engagement; your fixed price is agreed before any work starts
→ The scary manual step becomes one safe command
Discuss this →

🔬 Scientific Software

Your research pipeline gives a slightly different answer each run, and collaborators can't reproduce your results, which stalls papers and erodes trust in the data. I build Python tooling and configuration systems that make simulation and research pipelines reproducible: the same work that shipped in the official ESA Pyxel 2.14 release.

Hands-on, but never in your live system: I work in a repository, branch or environment you control, and hand over for your team to merge.

from £2,500 · minimum engagement; your fixed price is agreed before any work starts
→ Results you can defend and others can reproduce
Discuss this →

Read the paperwork before you talk to me

You should be able to see exactly what an engagement involves, what you receive, and how either of us can end it, without sending an email first. Everything below is ready to read or download right now.

Scope an engagement

How I work

My work is AI-assisted, and it is reviewed and tested as though no tool had been involved. What you are buying is a scoped outcome I stand behind.

Your code and data are handled under the confidentiality terms in the terms of business and the data privacy notice and DPA. The assisted tooling I use, Claude (Anthropic), operates under no-training and zero-retention terms: nothing you share is used to train a model, and no copy is kept once a request has been answered.

After an engagement ends I keep nothing of yours beyond the signed paperwork. If your code or data must never reach a third-party service, tell me before we scope the work and I will say straight away whether I can take it on those terms.

Cancel on 14 days' notice, or immediately if I have slipped up and not put it right. Fees and any deposit are agreed after we scope your project, and nothing is committed until we have both signed it off.

Trusted Partner

Justice Akason

Cybersecurity GRC Specialist, founder of CrenavoLab

I have partnered with Justice Akason and CrenavoLab for cybersecurity governance, risk and compliance (GRC) on projects and products that need it: understanding security obligations, strengthening controls, and preparing clear evidence for management, customers and assurance.

Justice and the CrenavoLab platform provide the cybersecurity perspective for Nimbus Vestige, my self-hosted forensic reconstruction platform for cloud and identity incidents. Through this partnership, my software engineering and reliability work sits alongside his governance and assurance expertise, to build more secure and resilient products.

Visit CrenavoLab →

Have a system that needs to be reliable?

Tell me what you're building or where things keep breaking.

💻 Start a conversation →