Financial data, sensitive information, and AI features people rely on — built to be correct, secure, and still working when something fails.

Notes on building things people can rely on.
I take ownership end to end: work out what matters, build it properly, make it reliable in production, and keep the team informed.
Fewer surprises, fewer half-finished features, and someone you can trust with the parts that touch money and data.
I also take on projects. You don't need a technical spec — tell me what you're trying to make happen and what's in the way.
You bring what you're trying to achieve. I help you get there: working out what matters, building what's needed, and making sure it keeps working.
Sometimes that's hands-on engineering, sometimes a product built from scratch, and sometimes working out what's worth building in the first place.
From a rough idea to something your users rely on, with one person owning it from the first conversation to launch.
Not a demo that impresses once. AI features that give the right answer on the hundredth question, at a cost that still makes sense as usage grows.
The release you hold your breath for, the page that times out, the data you're not sure is safe: found, fixed, and made dependable.
The spreadsheet someone updates by hand every Friday. The step where customers quietly drop off. Find where time, money, or customers are slipping away, and fix what's worth fixing.
Sometimes that's software. Sometimes it's automation, a better workflow, or a simpler process.
Three simple steps from problem to result. You always know what's happening and what comes next.
A 30-minute call. No technical spec needed, just what you're trying to achieve and what's in the way.
Clear scope, milestones, and price, so you know exactly what you're getting and when.
Shipped, working where your users actually are, and supported after launch.
Yes. You don't need to arrive with a technical specification. We start with what you're trying to accomplish, what your users or customers need, and what is currently getting in the way.
I translate that into the technical decisions required and explain the important trade-offs clearly.
There's no fixed list. I work on software products, technical systems, AI, data, infrastructure, integrations, operational problems, and other problems where my skills can create useful leverage.
If you're not sure whether I can help, tell me what you're dealing with.
No. You can start with the problem. We'll work out what needs to change and whether software or technology is actually the right way to address it.
Requirements usually change once reality enters the picture. I work in clear iterations so we can incorporate useful information without losing control of scope, quality, or direction.
Production software needs to be maintained. Builds include appropriate testing, error tracking, documentation, and a defined post-launch support period. Longer-term support can also be arranged where needed.
It depends on the problem, scope, and engagement. We first understand what needs to happen. From there, I can propose the appropriate structure, such as a fixed project, milestone-based engagement, ongoing work, or another arrangement that makes sense.
Often within a week or two of our first call, depending on scope and current commitments. Small, well-defined work can usually start sooner.
We agree milestones up front, and each one has to work before we move to the next. You see progress early and often, so problems surface while they're cheap to fix, and you're never locked into something that isn't working.
I'm Tobi Williams, a backend and AI engineer.
Most of my work sits where mistakes are expensive: money, sensitive data, and AI features people rely on.
I'm a Software Engineer at MileBack, a UK fintech, and I lead the platform at African Students’ Network. Before that I hardened a multi-tenant SaaS platform and shipped zero-to-one products with founding teams.
I enjoy problems that need more than code: understanding what matters, making good technical decisions under constraints, and building something that actually works. I'm also interested in what sits beyond engineering — businesses, markets, products.
Find something worth solving. Figure out what creates value. Build what is necessary.
Hiring an engineer, building a product, or dealing with a problem you haven't figured out yet — start with the problem.
Tell me what you're trying to make happen.