Can one person carry
my software?
It is the first question most people ask, and a fair one. Here is the honest answer: one operator with 25+ years of engineering, plus a team of ten specialized AI agents I have built and trained.
Judgment stays human.
The busywork does not.
The reason a solo operator can deliver and maintain production software is a clear split between what needs experience and what needs throughput.
I make the decisions that carry risk
Architecture, security, data modeling, and product trade-offs are where a build succeeds or fails in 18 months. Those stay with me, backed by 25+ years of building software before AI existed.
The agents do the repetitive work
Scaffolding, boilerplate, first-draft code, tests, and content drafts go to a team of ten specialized AI agents I have built and trained. That is where the speed comes from, without cutting the corners that matter.
Everything ships through one accountable person
No account managers, no offshore handoffs, no junior-dev surprises. Every decision and every line of code passes through me, so the work stays coherent and you always know who is responsible.
Monthly sprints you
can actually read
Every web app build runs as monthly sprints on a board like this one. Below is the first month of a sample plan for a made-up events company.
Foundation and the shared calendar
-
Numbered, worked in order
One board per month. You always know what is being built this week and what comes next.
-
Your part is on the card
What I need from you, and by when. If it arrives late, the cards after it move back by the same amount.
-
Reviewed every Thursday
A short check-in each week. The last one is the month review, where next month is planned.
-
Honest about uncertainty
Plans are best-case. Later months are planned loosely, then in detail at the review before them.
A shortened view. See all 37 cards in the Lantern Hall Venues plan →
Pick a company.
See how its build runs.
Four established businesses and four startups. The companies are made up, and the plans use the same format as real client builds.
Lantern Hall Venues
An events group with three venues replaces spreadsheets and email threads with one place for bookings, contracts, deposits and event-day run sheets.
- Month 1 Foundation and the shared calendar
- Month 2 Inquiries and holds
- Month 3 Contracts and deposits ★
- Month 4 Event day
- Month 5 Reports and the full pilot
- Month 6 All venues live and handover ★
Ridgeway Freight Brokerage
A regional freight broker replaces a whiteboard, a shared spreadsheet and email chasing with one system for loads, carriers, paperwork and invoicing.
- Month 1 Foundation and your data
- Month 2 The load board ★
- Month 3 Carrier onboarding and compliance
- Month 4 Rate confirmations and driver check-ins ★
- Month 5 Proof of delivery and shipper tracking
- Month 6 QuickBooks, reports and the pilot ★
- Month 7 Everyone live and handover ★
Halden Equipment Rental
A two-yard equipment rental company replaces phone calls, paper tags and memory with one system for availability, contracts, check-in photos and maintenance.
- Month 1 Foundation and the fleet list
- Month 2 Customers, reservations and contracts
- Month 3 Check-out and check-in on a tablet ★
- Month 4 Maintenance on hour meters ★
- Month 5 Transfers, delivery and the River Road pilot
- Month 6 Both yards live and handover ★
Bramble & Oak Veterinary Group
A four-clinic vet group shares one medication and supply inventory and one staff schedule, so stock and shifts move to where they are needed.
- Month 1 Foundation and one item list
- Month 2 Lots, alerts and transfers ★
- Month 3 Purchasing and the controlled-substance log
- Month 4 One schedule for four clinics ★
- Month 5 Pilot, go-live and handover ★
Saltmarsh Charters
A two-founder startup builds one place to book local fishing and boat charter captains, with deposits, weather rules and payouts built in.
- Month 1 First-version scope and a prototype in front of captains ★
- Month 2 Captains, boats and trips
- Month 3 Booking, deposits and payouts ★
- Month 4 Weather, reviews and the beta ★
- Month 5 Fixes, public launch and handover ★
Plotkeeper
A solo founder turns the paper, spreadsheets and email behind community gardens into one app for plots, renewals, waitlists and volunteer hours.
- Month 1 Scope, prototype and the foundation ★
- Month 2 Garden setup, plot maps and renewals ★
- Month 3 Waitlist, volunteer hours and announcements ★
- Month 4 Pilot renewal season, fixes and launch ★
Keystone Tutoring
A two-founder tutoring startup launches a first version that matches families with vetted local tutors and shows parents progress after every session.
- Month 1 Decide v1 and test the idea ★
- Month 2 Tutors and family requests
- Month 3 Matching, booking and session notes
- Month 4 Packages, tutor pay and the beta ★
- Month 5 Fixes, launch and handover ★
ShiftSwap
A two-founder startup builds a phone-first app where restaurant staff swap and pick up shifts, and managers always know who is working.
- Month 1 Scope, prototype and foundation
- Month 2 Schedules on every phone
- Month 3 Swaps, open shifts and the rules ★
- Month 4 Pilot, billing and launch ★
Speed without cut corners takes discipline
Solo delivery removes coordination overhead, but it only works with real engineering discipline: type safety, input validation, automated tests, audit logging, and security built in from the start rather than patched in at the end. That discipline is what let a full rebuild and data migration reach production in under four months on TowerSight, without a QA team standing by.
See it on TowerSight →Questions about how a build runs
How long does it take to build a custom web app?
It depends on scope. In the sample plans on this page, a startup's first version takes 4 to 5 monthly sprints, and an operations app for an established business takes 5 to 7. Every build starts with a clickable prototype in the first month, so you can use the product before it is coded.
What is a monthly sprint?
One month of work on its own board. The board has numbered cards, worked in order, grouped by week. Each card says what I build and, where it applies, what I need from you and by when. There is a short check-in every Thursday, and the last one of the month is the review where the next month is planned.
What do I need to provide during a build?
Decisions, access and real data at specific points, such as your current spreadsheets, document templates or an hour to test a feature with your team. Each one is on a card with a due point. If something arrives late, the cards after it move back by the same amount, and the plan says so.
What happens when plans change?
Plans are best case and are expected to change. Months further out are planned loosely, then in detail at the month review before them, so a new priority goes into the next board instead of derailing the current one.
Who owns the code, the data and the accounts?
You do. Hosting, email and payment accounts are created in your business name and you invite me in, so I never need your passwords. The code and data belong to you from the first day.
Can one person really carry a production web app?
Yes, with the right split. I make every architecture, security and product decision, backed by 25+ years of building software. A team of ten specialized AI agents handles the repetitive work such as scaffolding, first-draft code and tests, and everything ships through me.
Have a build you want carried?
Tell me what you are working with and where it is stuck. If it is a fit, we will book a scoping call, and I reply personally.
Let's Talk →