Your development team,
on a monthly retainer.
This is an ongoing development partnership, not a project with a finish line. I build and maintain the custom web applications your business runs on - with a direct line to me and no account managers in between.
A partnership, not a project
Software is never really finished. It needs fixes, changes, and new features as your business changes. So I don't sell a one-time build and disappear - I stay on as your development team, month to month, and the work continues as long as it's useful. A first build is just where the partnership starts.
Is this the right fit?
I'd rather qualify out early than start a bad-fit engagement. Here's who this works for - and who it doesn't.
- You have a business running on spreadsheets and taped-together SaaS, and it has stopped scaling
- Off-the-shelf software nearly fits, but the gaps cost you real hours every week
- A previous developer left you a stalled or half-finished build
- You already have an app and need someone to own its ongoing development
- You want one accountable partner, not an agency with account managers
- You want a one-time build with no ongoing relationship after launch
- You need a large in-house team on-site, or work that can't leave your building
- You want the cheapest possible quote over the right architecture
How the retainer runs
No mystery, no account managers. Every month follows the same simple rhythm.
Prioritize
We start with a short discovery and prioritization pass - agreeing on what matters most for the weeks ahead.
Build
I build against that list in cycles - real, tested code, with progress you can see rather than a black box.
Deploy
Work ships to production as it's ready, not saved for one big risky release at the end.
Direct access
You talk to me - the person writing the code - the whole way through. No layers, no hand-offs.
Three ways in
New build
A custom application from scratch - scoped, architected, and shipped, then developed onward month to month.
Rescue
A stalled or half-built project picked up. I audit what exists, tell you what is worth keeping, and get it moving again.
Ongoing development
You already have an app in production. I take over or augment its ongoing development, fixes, and new features.
Click through it before you commit to it
Before any production code, you get a working prototype of your app. Your team taps through real screens and settles what the product should be, and the build starts from a spec that can't drift.
This one is a membership portal for a sports club, filled with sample data. Things to try:
- Renew a family for next season
- Add a junior player to the household
- Switch to the admin side and filter the roster
- Export the member list as a CSV
Monthly, and priced by scope
Every engagement is monthly and recurring. Tiers scale with how much development you need - we settle the number on a scoping call, once the work is clear.
Web apps I've built
A custom bookkeeping web application for the numbers side of running a business. Full case study coming soon.
Visit the live site →A quoting and invoicing web app: build quotes from saved jobs, let clients accept and sign online, and turn accepted work into an invoice with deposits tracked.
Visit the live site →A business-critical safety-inspection app modernized across five framework versions, with its production database and 975,000-row audit trail untouched.
- Laravel 6 to 11
- Versions moved
- 0 to 103
- Automated test coverage
- Zero
- Database schema changes
3 more web apps are in production right now. Work in progress counts as work.
See all work, including in production →The questions that
actually matter
Tell me what you're
working with.
A sentence or two on your business and where the software is stuck. If it's a fit, we'll book a scoping call - no obligation, and I reply personally.
Let's Talk → Message me on LinkedIn

