Client work
Dispatch
Bulk email with tenant isolation, controlled sending and safe failure handling.
Read case studyFrom business process
to working system.
I design, build and ship the software behind the workflow.
Hiring an engineer?
Explore my experienceHave a project?
Discuss a build73 projects, nearly all built solo, end to end. Where a build was shared, the role line says what was mine.
Selected work
Browse the archive
Client work
SignFlow
Approval routing, signatures and sealed documents.
Architect & sole engineer
Read case study
Client work
Procurement Intelligence
Supplier offers turned into explicit purchasing decisions.
Architect & sole engineer
Read case study
Client work
Pikora
From web frontend contribution to end-to-end mobile product delivery.
Full-Stack & Mobile Engineer
Read case study
Case study
Furniture Valuation CV Pipeline
Image-based furniture evaluation, resale prediction and scam detection.
ML / AI Engineer
Read case study
Case study
Interior Scene Segmentation Pipeline
Fine-tuned vision models for precise interior scene segmentation.
AI / ML Engineer
Read case study
Case study
CarCheck NG
Vehicle history reporting for Nigeria. A working MVP with mock data adapters disclosed throughout.
Architect & sole engineer
Read case studyHow I work
Explore the stack From the first input to the handover.
Understand
Start with the workflow: the inputs, the people and what breaks today.
Incoming formats
Supplier offers
XLSXProduct catalogue
CSVBusiness rules
BRIEFArchitect
Make the data, decisions and boundaries explicit before building around them.
Decision model
offerscoredecision
BUYNEGOTIATEREVIEWIGNORE
Ship
Build the whole path, including the permissions and the ways it can fail.
Release checks
Authentication & roles
Audit trail
Deployment pipeline
Handover
Leave a system someone else can operate, with the documentation to match.
Ready for the next person
architecture.mdrunbook.mdoperator-sop.mdWorking togetherSomething worth
Something worth
building?
Tell me about the workflow, the team,
or the problem you keep working around.
What do you charge?
€70 an hour as a baseline, covering architecture, backend, frontend, deployment and documentation. Where a project can be scoped properly up front, I prefer to quote a fixed price.
When could you start?
Usually within a week, sometimes the next day. The variable is how much research a project needs before I can scope it responsibly. Most engagements run four to twelve weeks; some become ongoing work.
Can you take over an existing codebase?
Regularly. Several projects here began as existing repositories. The case studies explain what I inherited, what I changed, and the role that was mine.
How do you handle confidential work?
Client systems are described by sector, never by name. I share the problem, my contribution and the stack without exposing client data or private source. Any permitted demo captures use invented data. The artwork here is conceptual.
What do I get at the end?
A deployed system, the repository, and documentation written for whoever runs it next: architecture notes, a runbook, and operator SOPs.