What I build
The layer between the tools you already have.
The pieces that sit between the software you already run, so a job moves from the first call to the paid invoice without being retyped or waiting on one person.
Works with what you already run.
Nobody has to learn a new platform. The software you picked stays, and so do the logins.
- QuickBooks
- Excel
- Google Sheets
- Outlook
- Gmail
- Microsoft 365
- HubSpot
- Salesforce
- Google Drive
- OneDrive
- Dropbox
- Microsoft Teams
- Slack
- Shop and dispatch software
- Text messages
- Paper forms
Names are examples of what I connect to. I’m not partnered with or paid by any of them.
The layer
Your operation, connected into something your people actually use.
Not a new platform with your logo on it. Dashboards, connections and small AI-assisted steps, built around how your work moves and running in your own accounts.
One screen every morning.
Everything that needs attention today, pulled from the systems you already have. No more checking three places to answer one question, and nobody rebuilds it in Excel on Monday.
Typed once, everywhere it’s needed.
A record entered once shows up everywhere it’s needed. The web form goes to the CRM and the accounting without anyone retyping it.
Where’s that order?
Every job has a place to live, and every follow-up has an owner. Status shows up where people already look, so nobody walks the floor to find out.
Drafts, not decisions.
AI drafts from your own records and shows where every line came from. A person checks it and decides. Nothing goes out without a click.
Ask a plain question. Get an answer you can check.
An example of what I could build on top of the software you already run. It shows where every answer came from and drafts the next step. Nothing goes out until a person approves it.
Where’s order 1042?
- Looked in the job sheetHose kits, 2 sets, for Dale
- Looked in accountingSupplier invoice: shipped Monday
- Looked in textsDale asked for Thursday
Waiting on parts, still on time. The hose kits shipped Monday and are due Wednesday. Dale was promised Thursday.
from job sheetfrom accountingfrom texts
Draft text to Dale
“Your hose kits arrive Wednesday. Still on for Thursday pickup.”
Which quotes are waiting on a price?
- Looked in email5 quote requests this week
- Looked in the quote sheet2 priced and sent
- Matched them up3 still waiting
Three quotes are waiting on a price.
Q-1061Linda · gate repair4 daysQ-1063Wes · trailer wiring2 daysQ-1064Pat · pump rebuildtoday
from emailfrom quote sheet
Draft reminder to Kim
“Q-1061 for Linda has waited 4 days. Can you price the gate repair today?”
What jobs are waiting on parts?
- Looked at the job board3 jobs marked waiting on parts
- Looked in supplier emails2 shipping notices
- Looked in accounting1 part never ordered
Three jobs are waiting. One part was never ordered.
#1042Hose kitsdue Wed#1048Seal kitdue Fri#1033Pumpnot ordered · 6 days
from job boardfrom supplier emailsfrom accounting
Draft parts order for #1033
Pump, 1, from your usual supplier. Goes to Kim to check and send.
Built around your business, not the other way around.
Bring me an “I wish this could do that…” or the spot where work keeps getting stuck, and most of the time it can be built, connected or layered onto the software you already run.
By kind of work
Different yard. Same gaps.
A parts counter, a dispatch office and a front office don’t talk alike. Work still gets typed twice, and it still waits on one person.
Your people can fix almost anything. Nobody can say where the part is.
Where I’d look first
A job sits in the shop waiting on a part, and the counter, the shop and the customer each have a different answer about where it is. A repair quote waits on the one person who knows what that job usually runs.
I’d start with one repair, from the customer’s first call to the paid invoice.
Keep what you run. Your shop software and your parts lists stay. I connect what’s around them.
The delivery shows up on time. The paperwork doesn’t.
Where I’d look first
A load goes out Tuesday, but the signed delivery ticket rides around in the truck until Friday, and the invoice waits on it. Who’s out, who’s back and what’s next lives on one person’s whiteboard.
I’d start with one delivery, from the time it’s booked to the time it’s paid.
Keep what you run. Your phones, your schedule board and your accounting stay. I tie them together.
Your crew builds it right. What the job made shows up a month later.
Where I’d look first
An order gets keyed in at the front desk, written up again for the floor, and typed a third time for the invoice. Whether a job made money shows up after the month closes, if it shows up at all.
I’d start with one order, from the quote to the day it ships.
Keep what you run. Your production sheets and your accounting software stay. I make them agree.
The paperwork gets done right. It just goes through too many hands.
Where I’d look first
A request comes in by email, and each desk types the same names and numbers again. When a customer calls to ask where things stand, the answer is in somebody’s inbox, and that somebody is at lunch.
I’d start with one request, from the email it came in on to the day it’s done.
Keep what you run. Your office software and your email stay. I connect the handoffs between them.
Your crews do good work. The callback depends on who remembers.
Where I’d look first
A call gets written on a pad in the truck and typed in later, if the pad makes it back. Estimates go out, and the follow-up happens when somebody remembers.
I’d start with one call, from the first ring to the paid invoice.
Keep what you run. Your scheduling software and your books stay. I connect the call to both.
Don’t see your business here? It’s probably the same gap. Email me what you do, and I’ll tell you straight whether I’m the right fit.
What you keep
Here’s what stays yours, whatever happens.
Ask any vendor what you’d keep if you stopped working with them. Most honest answers are “not much.” Here’s mine, spelled out in a simple agreement before anything starts.
One person, and you hold the keys. Hiring one person can feel risky if that person holds the keys. So I don’t hold them. Your people run it day to day, and every build ends with a plain handoff: what’s running, where, how to restart it, and the logins in your name.
Everything I build lives in your operations layer. It’s yours: you can remove me with one step, and it keeps running. The first build sets it up: one login per person instead of shared ones, a written checklist for when someone leaves, and a practice run at handoff where we remove a test login and mine, then check that the work keeps moving.
Here’s the kind of page you’d get at the end. One page your people can run from without me.
I stay in the work for 30 days after it goes live, and the first three months of System Care come with the build. After that, a monthly Operating Review keeps it improving, with care included. If a system is done changing, yearly care alone keeps it running as built, renewed only when you say yes. Ending either one never switches anything off.
Parts counter · web orders
What’s running
- Web order form → CRM → accounting. Typed once, at the form.
- Morning view: a shared sheet in your own file account.
- Quotes with no answer after 3 days go to Kim.
Where it runs
Your email and file account, your CRM, your accounting software. All billed to you.
How to restart it
Order not in accounting by the next morning? Open the connection page, find the order, click Run again. Still stuck: email me while it’s under care. After that, this page tells whoever you hire next how it’s wired.
Logins in your name
Owner on every account: the company email. Admins: Kim and Sam. My access is listed here. You can shut it off any time.
Start with one job
Stop working around your software. Make it work together.
Tell me where work gets stuck between people, departments, documents or systems. I read every note myself and reply directly. No pitch and no sales sequence. Just a conversation about one job.
The email opens with four short prompts already in it. Three lines is plenty. I’ll write back myself and tell you straight whether I’m the right person for it, even if the answer is no.
Prefer email? blake@operations-layer.net
Your starting point
The Operations X-Ray is a paid look at one part of your operation, from where it starts to where it ends, at the same flat price for every business. The price isn’t listed here. You’ll hear it in the first conversation, before anything starts.