Your business runs on a spreadsheet that's one bad paste away from breaking.

• Every Monday someone copies last week's tab, pastes in the new numbers, and prays the formulas hold.
• There's a database from 2009 that runs half the shop, and nobody's allowed to touch it because the guy who built it is gone.
• The quote lives in one spreadsheet. The hours live somewhere else. The invoices live in accounting. Nobody connects them — so nobody knows which jobs made money.

If one of those sounded like your Tuesday, keep scrolling.

The work

Four builds on the bench, shown warts-and-all.

All four are demonstration pieces on realistic sample data — no client's real numbers are on this site. You can poke every demo, and nothing asks you for anything.

Four builds are on the bench. One more is in the shop — a dead-stock finder. Ask me about it.

Prices

What things cost

Typical ranges below; your exact price is fixed in writing before work starts — and once it's in writing, it doesn't move.

• Spreadsheet rescue / single automation typically $2,500–$7,500

  Where you land in the range depends on how your data arrives (Excel/CSV exports, QuickBooks reports — we agree the format first); if it's messier than that, I tell you before we start, not after, and quote the cleanup separately. Worked example: rebuilding the broken nine-tab scheduling workbook in the demo above would run about $4,500 and take three weeks.

• An internal tool (job tracking, quoting, inventory) typically $5,000–$25,000

  Scoped in writing, with what's included — and what isn't.

• Every build includes a 60-day warrantyincluded

  If something I built breaks, I fix it free, and you hear back within one business day — both written into the contract, not promised in an email.

• Keep-it-running support (optional) $500–$2,000/month

  Nothing I build needs me to survive: it's boring, documented, mainstream tech any developer can maintain. The retainer is for changes and new ideas, not life support.

• First step, if you want one: a look-under-the-hood session [FILL: e.g. $250], flat

  One hour with your actual spreadsheet or process; you get a written plan and an exact fixed quote. Credited toward any build.

New practice — no testimonials yet. That's why the prices, the contract, and a working demo are all on this page.

First three builds: [FILL: founding-client discount, e.g. 25%] off, in trade for a written, named case study.

How it works

Four steps, no mysteries.

1. You show me the problem. Call or text. If you want a priced first step, the look-under-the-hood session is one hour with your actual spreadsheet or process — [FILL: e.g. $250] flat, credited toward any build.
2. I put it in writing. You get a written plan, a realistic schedule, and an exact fixed quote. Once it's in writing, it doesn't move.
3. You get working software. Built to the written scope, with a 60-day fix-it-free warranty and a one-business-day response — both in the contract.
4. You own all of it. The code, the accounts, the domain, and a plain-English manual — yours from day one, handed over in a folder you can actually read.

Own it

When I'm done, you hold the keys.

The code, the accounts, the domain, and a plain-English manual are yours from day one. Here's exactly what a handover looks like: a real example handover folder you can browse. And here's the actual contract you'd sign — download it, read it at your kitchen table, no email address required.

I do this work on a contract basis and take a limited number of builds at a time. You get a realistic schedule up front, in writing.

The whole exit plan, spelled out →

Fair questions

The ones you were going to ask anyway.

"What if you get hit by a bus?"

Fair question; it's the right one to ask anyone like me. Everything I build is boring, documented, mainstream technology. You own the code and every account from day one, and the handover folder includes a manual written for the next developer — whoever that is. See exactly what you'd be holding: the example handover folder.

"What happens when it breaks the week you're slammed?"

Every build comes with a 60-day fix-it-free warranty and a one-business-day response commitment — both in the contract, not in a promise. After 60 days the optional support plan covers it, and because you own the code and the manual, any developer can step in if you'd rather not wait for me.

"Are you available full-time?"

No, and I won't pretend to be. I work on a contract basis and take a limited number of builds at a time. What you get instead of a body in a chair: a fixed price, a written schedule, and software that doesn't need me to keep running.

"Why are your prices on the page?"

Because nobody else's are, and you were going to ask anyway.

"Do you use [whatever's in the news]?"

I use whatever tool does the job and costs you the least to own. The fancy parts, where they exist, are described on each project's "How it's built" page.

About

The short version

More than a decade in the tech industry building [FILL: one plain-English line about the kind of systems Addison can publicly describe working on]. [FILL: short plain-English line about one past project Addison can publicly describe]. Lives in Hudson.

I work on a contract basis and take a limited number of builds at a time — so every build gets a realistic schedule, in writing, before work starts.