Custom software · Greenville, South Carolina
The spreadsheet got you this far.
Stray Angle builds custom internal software for small service companies — job tracking, crew scheduling, materials, follow‑up. Built around how your business already runs, not how a software company thinks it should. You own what I build.
The situation
You already know where it hurts.
None of this means anyone did anything wrong. It means the business outgrew the tool, which is what happens to every spreadsheet that works.
- 01 One file, six workflows. It holds together because one person keeps the whole thing in their head. That person cannot take a vacation.
- 02 The same job gets typed in three or four times. Quote, schedule, work order, then again into whatever system does the invoicing. Every retype is a chance to get it wrong.
- 03 Nobody can answer “what’s left on that job?” Not without a phone call. Scope lives as a sentence in a cell, so nothing can be counted, ticked off, or used to trigger anything.
- 04 Finished work disappears. Rows get deleted when a job closes. Then a warranty claim arrives and the record of what was actually installed is gone.
What I build
The layer between scheduled and complete.
Most service businesses have decent software for selling the work and decent software for billing it. The gap is the middle — and that is where the spreadsheet lives.
Job & project tracking
What’s scheduled, what’s done, what’s left, and what it’s costing in hours. Scope becomes a checklist instead of a sentence.
Materials & ordering
Orders trigger off accepted work instead of memory. Nothing reaches install day missing the one part with a two‑week lead time.
Crews & scheduling
Who’s where, which shared equipment is committed, and what can honestly be booked this week without moving something else.
Fits what you already pay for
Field service platforms, e‑signature, payments, accounting. Where there’s an API, the retyping stops. Where there isn’t, I’ll tell you plainly.
How it works
No discovery phase that bills for four months.
You should know what you’re buying before anything gets built, and you should see it working long before it’s finished.
Read the real thing
I go through your actual spreadsheet and talk to whoever maintains it. Most of the answer is already in there.
Written proposal
Fixed scope, fixed price, plain English. Including the parts I think you should leave out of version one.
Build in the open
Working software in weeks, not quarters. You use it as it comes together and say what’s wrong while it’s still cheap to change.
Handover
The code is yours, in your own repository. Support after that is a capped monthly retainer or simply as‑needed — your call, not a lock‑in.
See something real before you commit.
Every business is different, so I build a working prototype before anyone signs anything. This one covers project‑based wildlife and exclusion work — a job board, scope as a live checklist, a materials pipeline, trapping limits and a follow‑up queue. Every name and figure in it is invented.
Open the demoWho this suits
Small enough to move, big enough that it matters.
If two or three of these sound like you, there’s probably something worth building. If none of them do, I’ll say so rather than sell you a project.
- Roughly 5 to 50 people, with crews working out in the field
- Project or job‑based work that doesn’t fit a recurring‑service system
- Already paying for software that does most, but not all, of the job
- A shared spreadsheet has quietly become the system of record
Get in touch
Tell me what your spreadsheet looks like.
That’s genuinely the whole first conversation. Send a note about what you run on today and what keeps breaking, and I’ll tell you honestly whether this is worth building.
joel@strayangle.com