Should I build or buy?

Buying wins for most businesses, and the first week here decides it. If an existing tool does the job, I set that up and say so. Custom software is for the part of your business nothing on the market fits, and most businesses have one such part, not five.

What does custom software cost?

A custom tool is scoped in writing and priced by the scope. Because I use AI as the engineering team and review every line myself, a tool that used to take months takes weeks, and the price follows. You see the number before you commit, and the first working version ships inside the scope, not after it.

The code is yours from the first commit. It lives in a repository under your name, deploys on infrastructure you control, and is documented so any developer can pick it up. Nothing routes through me and nothing depends on me staying.

What happens when it breaks?

A tool built here ships with tests for the parts that matter, error logging that alerts a person, and a runbook. Most fixes are minutes. Support afterwards is by the hour, and most clients use a few hours a quarter to add something rather than fix something.

Who actually writes it?

AI writes most of the code and I direct, review and reject. My staff carry parts of the build and the documentation. Nothing ships without me reading it, and I am the one on the call.

The tool you priced, then shelved.

Every owner has one. The inventory system that would finally match the books. The job board the crews would actually use. The portal that would stop the phone ringing with the same question. You got a quote, it had a comma in it, and the spreadsheet lived another year.

I build internal software for Southwest Florida businesses the way I built it for my own: in weeks, in your repository, and only when nothing you can buy does the job.

Send me the situation How it works

I read every one and reply within the day. When an off-the-shelf product covers it, I tell you which one and stop there.

Fort Myers, serving Lee, Collier and Charlotte counties
My own companies run on software I built
Scoped in writing, priced before work starts
Your repository, your servers, documented for the next developer

Twelve

companies operated, six of them his own, on software he built

790+

products in a catalogue that started at 105, run from one internal tool

15,868

records synced between two systems every run, zero failures

Thirty

live sites generated and shipped from one engine

The tools that get built

Inventory systemOne count that is true, on a screen your staff will use, tied to what you sold and what it cost.Intake and schedulingEvery request captured once, put on the right calendar, and visible to everyone who needs it.Dispatch and job trackingEvery job from booked to paid on one board, with photos, notes and the crew's progress from the field.Billing and collectionsInvoices raised when the work happens, reminders on a schedule, and a cash position you can read on a Monday.Reporting dashboardThe numbers you actually run the business on, pulled from your systems, on one screen, every morning.Customer portalA place your customers log in to see their order, their job, their documents and their invoices, so they stop calling to ask.Storefront and catalogueA store or catalogue built from one product record, fast, on Shopify or as code, with the inventory and the books agreeing.Landing pagesFast, plain landing pages built from data, one per service or offer, that load in a blink and send the lead to your CRM.

How it works

Week one. Build or buy.

A written map of the process the tool has to serve, and an honest read of what on the market already does it. Most engagements end this week with a purchase recommendation instead of a build. The ones that continue have a specification.

Weeks two and three. The build.

Code in your repository, deployed to your infrastructure, with a working version in front of your team by the end of week two. Tests where they matter. A runbook alongside.

Week four. Your team on it.

Staff using the tool on real work with me watching what they do and where it fights them. This is where the specification gets corrected to reality.

After. It runs.

You own it. Support afterwards is by the hour if you want it. Most tools built this way run for years with a few hours of attention a quarter.

Built for the trades I have run

The tool a metals dealer needs is not the tool a contractor needs. These five are the sectors I have built software inside, and each page names the four tools that trade actually runs on.

Precious metalsMetals dealers, coin shops, refiners and vault operators running the counter on a point-of-sale, a pricing spreadsheet and a filing cabinet.Luxury retailJewelers, watch dealers and galleries whose client book is a salesperson's notebook and whose repairs live on paper tickets.ConstructionContractors and trades estimating from a price list in a spreadsheet, scheduling on a whiteboard and invoicing from memory.Legal servicesSmall law firms and referral groups whose intake is an email inbox and whose practice software stops at the matter.Real estateBrokerages, locators and property managers running transactions, commissions and lease dates across agents' private spreadsheets.

Where I work

Each market here imposes one rule on what a custom tool has to do. The city pages say what it is and what to build first.

Fort MyersSeason doubles the load and halves the staff. The tool carries the summer office.NaplesHigh-ticket, low-volume, and a client who notices a wrong name on a document.Cape CoralThe owner is in a driveway. The tool has to work from a phone, or it does not exist.Bonita SpringsA Lee side and a Collier side of every job. The tool stores the county on every record and branches on it.EsteroYoung businesses with five subscriptions. Consolidate into one tool before you build.Punta GordaOwners near an exit. The tool is the documentation a buyer pays for.

Build it, buy it, or make what you have do it.

Six ways to get the tool. Each page says where that way wins, where it is the wrong choice, and whether my own companies run on it. Most businesses should buy. I will say so when it is true.

Custom codeA tool written for your process, in a repository you own. For the part of the business that is genuinely yours.Off-the-shelf ERPNetSuite, Odoo, Zoho One. Everything in one system, for a company several sizes larger than most that ask.No-code buildersSoftr, Bubble, Glide. A working screen in days, on a platform you rent. Right until the moment it is not.Spreadsheets and AirtableSheets, Excel, Airtable. The system most businesses actually run on. Right longer than people think, wrong later than they notice.ShopifyThe right store for most retailers. The build is the data, the theme and the connections, not the platform.WordPressThe platform half the web runs on. Right for content and for a store you already have. Slow and brittle when the plugins pile up.

Straight answers

Should I build or buy?: Buying wins for most businesses, and the first week here decides it. If an existing tool does the job, I set that up and say so. Custom software is for the part of your business nothing on the market fits, and most businesses have one such part, not five.
What does custom software cost?: A custom tool is scoped in writing and priced by the scope. Because I use AI as the engineering team and review every line myself, a tool that used to take months takes weeks, and the price follows. You see the number before you commit, and the first working version ships inside the scope, not after it.
Who owns the code?: The code is yours from the first commit. It lives in a repository under your name, deploys on infrastructure you control, and is documented so any developer can pick it up. Nothing routes through me and nothing depends on me staying.
What happens when it breaks?: A tool built here ships with tests for the parts that matter, error logging that alerts a person, and a runbook. Most fixes are minutes. Support afterwards is by the hour, and most clients use a few hours a quarter to add something rather than fix something.
Who actually writes it?: AI writes most of the code and I direct, review and reject. My staff carry parts of the build and the documentation. Nothing ships without me reading it, and I am the one on the call.

Tell me what is in the way.

A short form and a same-day reply from the person who would write the code. When buying covers it, the reply says what to buy.

Send me the situation Email instead