Business logic
The systems that run the back office.
ERP
- inventory
- procurement
- purchasing
- order management
- multi-warehouse
- production planning
Work
Every client I work with has signed an NDA, so I don't publish names, screenshots or case studies. What I can show you is what I build, how I build it and how I protect what you tell me.
Delivered for clients in
Engineering capability
This is the range of systems I design, build and maintain. Each area is work I have delivered for real businesses.
The systems that run the back office.
ERP
Software that handles money, orders and trust.
Marketplaces
Physical-world processes, modelled in software.
Logistics
The foundations everything else stands on.
Identity and access (IAM)
Automation and intelligence, applied where it earns its place.
AI agents
Automation
The engineering around the code.
Web applications
Mobile
Architecture and technical audits
A few familiar patterns
No names, just the patterns.
Critical processes live in files that break, get duplicated and depend on one person.
Staff retype the same data across tools, and nobody trusts the numbers.
What worked at ten orders a day fails at a thousand.
Software that is slow, undocumented and impossible to change safely.
A product exists but nobody maintains, monitors or improves it.
Approvals, reports and data entry that should run themselves.
Teams need access control, trails and retention they can show.
A marketplace, platform or internal system that must be built properly the first time.
How I work
The same steps on every engagement, whatever the size.
01
A direct conversation about your operation, the problem, who uses the system and what success looks like. I ask a lot of questions and challenge assumptions where it helps you.
You get: a clear shared understanding, and an honest view on whether I'm the right fit.
02
Confidentiality is agreed before any sensitive detail is shared. Access to your systems is limited to what the work needs.
You get: a signed NDA and a short access plan.
03
I turn the problem into a written scope: what is built, what is not, in what order, with risks called out.
You get: a scope document, milestones and a fixed price or clear estimate.
04
Data model, system boundaries, integrations and security decisions are made on paper first, so the build doesn't wander.
You get: a plain-language architecture summary you can review.
05
Work ships in small, working pieces you can see and test, not a big reveal at the end.
You get: regular demos, a working preview environment and honest progress updates.
06
Automated tests, edge cases, security checks, performance checks and data validation before anything goes live.
You get: a release checklist and confidence at launch.
07
A planned release with backups, a rollback path and, where needed, careful migration from your old system or spreadsheets.
You get: a calm go-live with no big-bang risk.
08
After launch I monitor, patch, support and keep improving what I built.
You get: a named owner for your software, plus an optional ongoing retainer.
Confidential by default
Because I work alone, your information doesn't pass through a team, a sales pipeline or an account manager.
Signed before any sensitive detail is shared.
I request only the access the work requires and remove it when it ends.
Your name, data, screens and code are never shown to anyone else.
Credentials in managed secrets, never in chats or code, and production data kept out of development wherever possible.
At the end, access, credentials and documentation are handed back to you.
Fewer hands means fewer places your information can leak.
Need to talk through a specific security or compliance requirement? Raise it in the first call.
An honest answer
Ask me anything technical. I'll answer plainly, in the first call, for free.
I'll walk you through how I'd build your system, before you commit.
I can describe delivered work in anonymised, technical detail under your own NDA.
Start small. A scoped first milestone lets you judge the work itself.
Questions
Ready when you are
NDA first, then the details. You'll hear back from me, not a sales team.
Start a project