Enterprise-quality software.
A fraction of the cost and time.
AI helps move routine development forward quickly: drafting code, exploring test cases, and handling repetitive tasks. Experience guides the decisions that require context—understanding your business, choosing what matters first, and spotting problems before they become expensive. My process brings the two together, using AI for the groundwork and hands-on engineering judgment to shape, review, and deliver the solution.
Start with a conversationOur process
How a project runs
From the first conversation through launch and support, see what happens and what each of us contributes.
30 minutes
Discovery
Tell me where work gets slow or frustrating. We’ll discuss priorities and whether I can help.
You do
- Show how the task works today.
- Explain what needs to improve.
I do
- Ask questions about the workflow.
- Check fit and availability.
2–4 days
Scope
We define deliverables, estimated timing, and a fixed price before building.
You do
- Choose what matters first.
- Review and approve the plan.
I do
- Document workflows, screens, and exclusions.
- Explain pricing and ongoing costs.
2–8 weeks
Build
I share working previews in small increments so you can try the solution as it develops.
You do
- Try realistic tasks in the preview.
- Share feedback at agreed check-ins.
I do
- Develop and test the solution.
- Flag decisions and changes to scope.
3–5 days after build
Launch
After the build, we check the full workflow, put it live, and walk through how to use it.
You do
- Review with the people using it.
- Give final approval against the scope.
I do
- Deploy and check account access.
- Hand over source code and agreed documentation.
30 days, then optional care
Support
The first 30 days cover fixes. After that, choose ongoing care or a handoff to another developer.
You do
- Report issues with examples.
- Choose the ongoing help you need.
I do
- Fix defects within the agreed scope.
- Explain maintenance and handoff options.
AI-assisted development
Tools help.
Experience decides.
I use AI to help with repetitive code, test ideas, and refactoring. I review the output, test the behavior, and remain responsible for what I deliver.
My 10+ years of engineering experience guide the decisions: what to build, how it should work, and whether it fits your business.
Ownership & handoff
Your software.
A clear way forward.
Your project includes a source-code handoff and the documentation and access agreed in the scope. Ownership terms and any third-party licenses are recorded in the agreement.
We plan for maintenance and a future developer, so you have a practical path forward after launch.
Ownership
Your custom software, on final payment
- Source code
- Yours
- Database & data
- Yours
- Hosting accounts
- In your name
- Domain
- Yours
- Our licence fees
- None
- Lock-in
- None
Your business data remains yours. Custom code ownership transfers on final payment under our agreement; third-party libraries keep their own licenses. Hosting, domains, and outside services may have ongoing charges, which we identify in your written scope. I build with established technologies that another developer can maintain. If you decide to move on, you receive the project repository, documentation, and a handover conversation to help the next person get started.
Common questions
You might be wondering
Do I need to know anything about software?
No. Your knowledge of the business is what matters. I’ll explain options and decisions in everyday language.
What if I’m not sure what I need?
That’s a useful starting point. Bring a recurring problem or an example of work you’d like to make easier. We can explore the options together.
Can you improve tools we already use?
Often, yes. We’ll look at the tools you have and their capabilities before recommending replacements or custom development.
Does every project require custom software?
No. A setting change, an existing product, or a small integration may be enough. The recommendation should fit the problem.
Can we start with something small?
Yes. We can scope one useful improvement first, then discuss further work based on what you learn.
Will I be involved during development?
Yes, at agreed review points. You’ll try the work and give feedback. We’ll discuss the expected time commitment before starting.
What if my requirements change?
We’ll talk through the effect on priorities, cost, and timing, then agree on any adjustment before building the change.
Can you help after launch?
We can discuss maintenance, support, or further improvements. The arrangements depend on the project and my availability, and are agreed separately.
Your next step
It starts with “here’s the problem.”
Bring the problem. We’ll figure out the possibilities together.