Meet Randy — a software engineer for service businesses
The engineer you text.
Randy is a software engineer for your business — integrations, automation, internal tools, data work, and the bugs nobody else will touch. Text it like anyone else on the crew. Scoped in a few messages, usually shipped inside the week.
-
One number
A single thread you text, the same number every time. No portal, no ticket, no login to remember.
-
A real engineer’s scope
Integrations, automation, internal tools, data, debugging — the range of a hire, not a help desk.
-
Checked first
Every change is reviewed before it ships — and nothing is called done until it actually is.
01 — The situation
Every service business runs on software nobody owns.
A CRM someone configured in 2019 and left. A spreadsheet three people retype into QuickBooks every night. A follow-up text that was supposed to fire automatically and quietly stopped in March.
None of it is broken enough to hire an engineer. All of it costs you hours every week. So it sits there, and everyone works around it, and the workaround becomes the process.
- 01
The workflow stopped firing. Nobody noticed for six weeks.
- 02
Two systems hold the same customer. Neither agrees.
- 03
The report exists. Someone rebuilds it by hand every Monday.
02 — How it starts
It starts the way
everything else does.
Keep scrolling ↓
hey our new lead texts stopped going out
Looking now. Is it every lead, or just the ones from the website form?
website ones i think
Found it. The form started sending the phone number in a field the workflow doesn’t read, so it never had anyone to text. About an hour to fix.
Want me to go back and catch the 40 leads that got missed since Tuesday?
yes please
Done. The workflow’s live and those 40 just got their first text. You should see replies today.
03 — What Randy does
The whole job you’d hire an engineer to do.
A software engineer’s actual scope — integrations, automation, internal tools, data, debugging, and keeping it all running. Not a help desk, and not a list of things you can already do yourself in a settings screen.
-
01
Integrations
Making two systems share data. Your CRM into QuickBooks, your scheduler into invoicing, the website form into whichever system needs to know. Built against the real APIs, so it keeps working when the vendor changes something.
-
02
Automation
Work that happens without anyone remembering to do it. The follow-up text that fires within five minutes of a lead landing, the nightly sync, the Monday report that arrives built instead of waiting to be built.
-
03
Internal tools
Software that doesn’t exist until someone writes it. A dashboard showing jobs by crew and margin. A customer portal. A form that replaces a clipboard. The screen for the task only one person on your team knows how to do.
-
04
Data work
Migrations, cleanup, and the queries nobody on staff can write. Deduping customers, merging two systems into one, backfilling records after an import went sideways, and getting a straight number out of a messy table.
-
05
Debugging
Working out why it broke. Reading the logs, tracing the failing request, figuring out why the workflow fires for some leads and not others — then fixing the cause rather than clicking the thing again and hoping.
-
06
Keeping it running
Monitoring, so you hear it from us and not from a customer. Repairs when a vendor changes an API underneath you. Access cleaned up when someone leaves and takes a login with them.
Systems we work in
- HubSpot
- QuickBooks
- Jobber
- Housecall Pro
- ServiceTitan
- Aspire
- Zapier
- Make
Running something else? Most of these systems have an API or an export. “Haven’t worked in that one — let me look at how it’s set up” is the honest answer, and usually the right one.
04 — How it works
Four states.
You always know
which one you’re in.
Randy is an AI agent. It runs the conversation, works out exactly what you need, and does the building — the actual change, in the actual system you use.
That is the whole design. The work doesn’t wait on anyone’s calendar and it doesn’t sit in a queue behind someone else’s job. What stays human is the check: the work is reviewed before it ships, and Randy is not permitted to tell you anything is finished until that review has happened.
-
01
Scoping
Randy asks until the ask is actually clear — one question at a time, not a form with eleven fields. It stops at four rounds and commits to a plan, so nothing stalls in questions forever.
-
02
Ready
A written brief: what you want, which systems are involved, and what finished looks like. Enough for an engineer to start without re-reading the thread.
-
03
Building
Randy builds it. Not a demo, not a suggestion, not a link to documentation. The actual change, in the actual system you use. Usually inside the week.
-
04
Done
You get told once, in your language: your new-lead workflow now texts the customer within five minutes. Not “deployed the automation.”
05 — What it costs
Two numbers. Both on this page.
To start — one time
$600
An audit of what you’re actually running, and your tools connected up properly. This is the part that turns a pile of systems into something one person can work on.
Ongoing — monthly
$400/mo
Unlimited requests, worked one at a time. Ask for as much as you like; Randy queues it and it gets done in order. No per-ticket pricing, no hourly, no change orders.
- 01
Nothing is charged before we’ve talked. You text, then we set up a short call.
- 02
Ask Randy the price in the thread and it will tell you these same numbers, plainly.
- 03
Month to month. If it stops being worth $400, say so and it stops.
Start
Something broken? Tell us about it.
Text Randy what’s wrong in your own words. It’ll ask a couple of questions, then we’ll set up a short call before anything is charged.
Randy — one number, always +1 (555) 010‑0142Reply STOP at any time and the messages end. No sequence, no drip.