the endurance audit · softwarebuilt it fast? now people depend on it.

Find out what breaks first,before your users do.

free · 30 minutesfit callBook an intro call →

You built it fast, maybe with AI tools, maybe with contractors, and now real people depend on it. In about two weeks I go through your code, hosting and costs, work out what breaks first as you grow, and give you a list of what to fix, most urgent first.

The Software Audit from Restless Tech. Fixed price, starting at $5,000. Free 30-minute fit call.

Is the risk in how your team works, not the code? See the Operations Audit, F2 →

§ 1 · the problemBuilt top down, one feature at a time.

AI tools can take an app from idea to paying customers in a few weeks. I use them every day, and that part is real. But when you're not technical, the app gets built top down. Every idea becomes a feature bolted onto the last one, and nobody plans for the day an outside service goes down, the database doubles, or the hosting bill shows up.

Most of the code works. Look closer and the same job is done two different ways in two places, there are hardly any tests, and nobody fully knows how it fits together, sometimes including you. With ten users you'd never notice. With ten thousand, strangers find every crack.

Right now this is a few weeks of fixes. During an outage, with users watching, it’s a lot worse.

§ 2 · signs you need itSound familiar?

tick what applies · 0 of 5

If two or more of these hit home, it's worth a 30-minute call.

Book an intro call →

§ 3 · how it worksFour steps. About two weeks.

Tell me where it's going.

A 30-minute call about what the product does, who uses it, and where the business is heading over the next year or two.

I read everything.

With read-only access to your code, hosting and dashboards, I trace how the system really fits together. I never change anything live.

I break it on paper.

For every part that matters: what happens when an outside service or the database goes down, what fails first at ten times the users, and what that costs.

I walk you through it.

A one-hour call where I go through what I found and what to do first. It's recorded, and everything I hand over is yours to keep.

§ 4 · what you getA plan you can act on, with me or without me.

1
System map
How your product actually fits together: services, data, third parties and who owns what.
2
Failure register
What breaks first, ranked by how likely it is and how much it would hurt, including the patterns AI-built code tends to leave behind.
3
Scale & cost curve
Where the ceiling is, roughly when you hit it, and what your bill looks like on the way there.
4
Security & operations check
Secrets, logins and access control, exposed endpoints, backups, monitoring, deploys and rollback.
5
Team readiness
Whether a new developer could get productive tomorrow, where the single points of failure are, and who to hire first and when.
6
Roadmap
What to fix now and what can wait, with rough effort for each, tied to where the business is going.

§ 5 · pricingFixed price. No surprises.

starting at

$5,000

The price depends on how big the system is. I'll recommend a scope on the intro call, and you'll know the exact price before anything starts. Expect about two hours of your time in total.

FocusedOne product: its code, data and infrastructure.about two weeks

StandardA product with several services, integrations or apps, like web plus mobile.about three weeks

DeepMultiple systems, or a platform with serious data, compliance or scale needs.three to four weeks

If you hire me to fix what I find, the full audit fee comes off that work.

my guarantee

The clean-bill-of-health promise

If your system is in good shape, I'll say so in writing: a dated clean bill of health you can show investors, buyers or customers, plus a plan for your next stage of growth and a short list of warning signs to watch. I won't invent problems to justify a fee.

§ 6 · proofBuilt for systems that can't go down.

I plan every system around how it's going to fail, then make sure it fails gently. I build with AI tools every day too, so I know where they cut corners. Here's some of that work.

case 1 · in the field

GridPulse

the situation

Live timing for endurance racing: three timing systems on three different clocks, unreliable trackside internet, and every phone in the paddock expecting the green flag at the same moment.

what I built

A real-time pipeline designed around how it fails: each audience degrades differently, spare capacity waits on standby, and the whole system was load-tested at 50 times the expected viewers before race weekend.

what changed

Millions of messages delivered across multi-day race weekends, for a running cost of roughly $100 a month.

case 2 · in the field

American Endurance Racing

the situation

A national endurance racing series: 6–9 race weekends a year, about 50 cars and 500 people per event. Registration, timing and penalties all have to work under race-day pressure.

what I built

The entire platform, built and run for 8+ years: registration and payments, check-in and waivers, live timing, RFID pit lane tracking, automatic penalties, championships and SMS alerts.

what changed

$5M+ in registrations processed and thousands of active users, on a system designed around race-weekend load spikes.

case 3 · in the field

thanks.io

the situation

A direct-mail startup that needed to send personalized, handwritten-style mail at real scale.

what I built

The core platform from the first build onward: custom handwriting rendering (years before AI could do it), a full US address database, and integrations partners send mail through.

what changed

Grew to 500,000 pieces of mail a month.

§ 7 · faqQuestions, answered

We built it with AI tools. Is that a problem?: No. That's who this is for. AI-built code tends to break in the same handful of ways, and I know them because I build with these tools every day.
Are you going to tell us to rewrite it?: Almost never. The audit is read-only, and the roadmap leans toward targeted fixes over starting over. Most systems just need a handful of the right repairs.
What access do you need?: Read-only access to your code, hosting and any dashboards. Nothing gets changed, and you can remove my access the day the readout is done.
We don’t have a technical person. Can we still do this?: Yes. The readout and roadmap are written for the people running the business, with the technical detail attached for whoever does the work.
Are you just going to try to sell us more work?: The roadmap is written so anyone can carry it out, including your own developers. If you do hire me to fix things, the audit fee comes off the bill.
What happens after the readout?: Up to you. Fix it yourselves, have me fix the weakest parts, or keep me on as your part-time CTO with Crew Chief (F5).

back page · free 30-minute call

Find the crackswhile they're cheap to fix.

Start with a free 30-minute call. I'll ask what you've built and where it's headed, tell you honestly whether the audit fits, and suggest a scope.

restless tech · built to endurehello [at] restless [dot] tech

Reply card

step 1 of 2 · about you

Find out what breaks first,before your users do.

§ 1 · the problemBuilt top down, one feature at a time.

§ 2 · signs you need itSound familiar?

§ 3 · how it worksFour steps. About two weeks.

Tell me where it's going.

I read everything.

I break it on paper.

I walk you through it.

§ 4 · what you getA plan you can act on, with me or without me.

System map

Failure register

Scale & cost curve

Security & operations check

Team readiness

Roadmap

§ 5 · pricingFixed price. No surprises.

The clean-bill-of-health promise

§ 6 · proofBuilt for systems that can't go down.

GridPulse

American Endurance Racing

thanks.io

§ 7 · faqQuestions, answered

Find the crackswhile they're cheap to fix.

Reply card