Custom Software Development
I turn the need found in the diagnosis into software built around your workflow, not a package you adapt to.
- Duration
- Monthly, three-month minimum
- Engagement
- Monthly retainer
What you get
- An application designed around how your company actually works
- A working release every month — regular small steps, not one big delivery
- Production setup: deploy, backups, monitoring and a rollback plan
- Security and data-protection review of authentication, authorisation and data flow
- Handover training and documentation for the people who will use it
Ideal for
- Companies that have found off-the-shelf software does not fit how they work
- Teams that completed a diagnosis and picked their priority
- Anyone who wants software that grows with the business, not a one-off project
Not included
- Fixed-price, fixed-scope projects — scope is agreed monthly
- 24/7 on-call support
- Hardware, networking or system administration
- Taking over software written by another team
Why I do not recommend a package
Off-the-shelf software is designed for the average company. Your competitive advantage lives in whatever you do differently from average. Buying a package usually means giving that difference up and adapting to the software instead.
I learned this in my own businesses. I run operations for five brands at Siam and wrote most of the systems I use, because the available ones did not fit how we work. SRCAI, the platform I built for driving schools and vocational certification centres, exists for the same reason and runs in production today.
How we work
A monthly rhythm. At the start of each month we pick two or three items together. At the end of the month you have a working release. There is no big project delivered in six months — there is a system that works a little better every month.
Scope flexes, budget does not. We decide the work at the start of each month. If priorities change, next month changes; the contract does not get rewritten.
The code is yours. You have repository access from day one. If we part ways the system stays with you and another team can pick it up. My business model does not depend on locking you in.
What I say up front
I came to software later. I spent eighteen years in industry and trade — production planning, quality, running my own business, trade finance. For the past eighteen months I have been building products with AI-assisted development.
That makes me strongest where the hard part is understanding how the work happens. If you need deep engineering — high-performance infrastructure, embedded systems — I am not the right person, and I will tell you that in the first conversation.