How I work
One job at a time, in three steps.
Map how the work moves. Connect what you already run. Let the software do the retyping that shouldn’t need a person.
The order matters. Connect things before you’ve looked, and you just wire the mess together faster. Add AI before the basics hold, and it drafts from bad numbers.
-
01
Look at one job and see where it really waits.
I follow one job from the first call to the invoice: every stop, every handoff, every place it falls through the cracks. It might be a quote, an order, a repair or a delivery. I call that the Operations X-Ray. It’s paid up front, and it’s the same flat price for every business. It ends with two fixed prices, a smaller fix and the full one, and a clickable preview of the smaller fix so you can see it before you choose.
I start where the paper is. The clipboard of work orders, the whiteboard in the shop, the folder that rides from the counter to the office, the notebook on the dash. Each one is a handoff somebody set up because the software didn’t do it.
- Operating Map
- Two fixed prices
- Yours either way
-
02
Connect what you already run.
If the fix is worth doing, I connect the tools you already use, like your accounting, CRM, spreadsheets, email or shop software. They get connected around how your people actually work, not how some software company thinks you should. Nothing you use today gets ripped out, and the price is fixed before the build starts.
- Fixed price
- Your own accounts
- Nothing ripped out
-
03
Let the software take the busywork.
Once the basics hold, I add reminders, drafts and AI where they help. A follow-up nobody owned becomes a reminder that goes to a named person. Where AI writes a first draft, a person still checks it and decides.
- Typed once
- Drafts, not decisions
- A person decides
Then I stay.
After it goes live, I stay and work with your people for 30 days and make adjustments as the business changes. Then you get a plain handoff: what’s running, where it runs, how to restart it, and the logins in your name.
The first three months of System Care come with the build. Around day 90 we time real jobs again, and you get the measured result plus a list of what’s worth fixing next. After that, the way to keep it improving is a monthly Operating Review: it owns a number you care about, ships changes every month, and System Care comes with it. If a system is done changing, yearly care keeps it running as built. Either way it’s yours, and ending never switches anything off.
Plan on the first version missing something. When your people see it working, somebody will say “warranty jobs don’t go that way.” That’s know-how that’s been living in someone’s head, finally showing up. It’s what the 30 days together are for.
- 30 days together
- Plain handoff
- Logins in your name
The Operating Map
A plain drawing of how one job really moves.
Every stop the work makes, who touches it, where it waits and where it gets typed again. It’s what I build from, and it means the know-how stops walking out the door when someone leaves. You get it at the end of the X-Ray, and it’s yours whether or not you build the fix with me.
- 1Counter call, written on a padPhoneTyped once, at the counterPhone → one record
- 2Retyped into an email to the officeEmailNot neededentered once
- 3Waits on the one person who knows the priceWaits 3 daysStill needs the priceReminder goes to Kim, the named backup
- 4Keyed into the quote spreadsheetSpreadsheetNot neededentered once
- 5Keyed into the CRM a third timeCRMNot neededentered once
- 6Quote goes out on day sixEmailQuote goes outEmail, from the same record
Stops 2, 4 and 5 are the same details typed again. Stop 3 is the costliest wait.The order is typed once and flows to email, the spreadsheet and the CRM. The wait now has an owner.
Sample job for illustration. Yours will have its own stops.
- 01Fit conversationA plain talk about one job. No pitch and no sales sequence.
- 02Operations X-RayPaid up front. The same flat price for every business.
- 03Your Operating Map and two fixed pricesA smaller fix and the full one. The map is yours, build or no build.
- 04You decideBuild it, or stop here and keep the map.
- 05System Build, fixed priceConnected to what you already run.
- 06Go liveYour people run it day to day.
- 0730 days togetherI stay in the work and adjust as it settles.
- 08Plain handoffWhat’s running, where, how to restart it, and the logins in your name.
- 09Keep it improvingA monthly Operating Review, with System Care included. Or yearly care alone keeps it running as built. Ending either never switches anything off.
Seeing it pay off
Spending real money on how your business runs can feel like a lot.
I’ve sat on the buying side of enough software demos to know that feeling. So you don’t have to take my word for what this is worth. In the X-Ray, I time how long your people take on real jobs. Once it’s live, I time the same jobs again. One page shows the difference in your own hours, and it grows with every piece we add. When you can see it paying off, the next step just makes sense. If something isn’t paying off, the page shows that too.
Below is a made-up example of that page, which I call the Payback Map. The numbers are made up to show what the page looks like, not taken from a real client. With a monthly Operating Review, it gets updated every month.
Pick the kind of work closest to yours.
Example Co · 3 locations · about 140 people · month 9 after go-live
Gross margin
29.3%
was 28.4% · up 0.9 points
From your invoicesWork that used to go unbilled
988
lines now on the invoice
From your invoicesDays to get paid
22
was 34
From your invoicesRush charges
3 a month
was 14
From your recordsWork done twice
4 a month
was 11
From your recordsGross margin, month by month
Dashed line: before, from your last six months of records. Circle: the month it paid for itself.
Not counted yet: sales growth, repeat customers, and calls that used to go unreturned. They go on the page after a year of history, and only what your own records show.
Hours back so far
674
since the build went live
TimedAt this pace
1,042 a year
about half of one person’s year
ProjectedThe owner’s own hours
3 a week
fewer “where does this stand?” questions
Timed- Order to invoiceBuild · month 1
14 min → 3 min each × 3,900 jobs a year
715 hours a year
- Quote follow-upChange · month 4
6 min → 1 min each × 2,100 quotes a year
175 hours a year
- Supply reordersChange · month 6
9 min → 2 min each × 1,300 reorders a year
152 hours a year
Times describe the work, never a person, and they’re never used in anyone’s review.
Paid for itself
month 7
what came back passed what went in
From your invoicesSince then
Ahead every month
the gap grows with each change
From your invoicesWhat counts as coming back
Money only
hours stay on their own page
From your recordsWhat you’ve put in and what’s come back, month by month
Grey: what you’ve put in. Green: what’s come back. Circle: paid for itself. Dashed: projected.
Each change the Review ships adds to what comes back. What you’ve put in counts the Review every month, not just the first three. Months 10 to 12 are projected at this pace. On your own page, both lines carry your real dollar amounts.
Example Co · 3 locations · about 140 people · month 9 after go-live
Gross margin
29.3%
was 28.4% · up 0.9 points
From your invoicesWork that used to go unbilled
988
lines now on the invoice
From your invoicesDays to get paid
22
was 34
From your invoicesRush charges
3 a month
was 14
From your recordsWork done twice
4 a month
was 11
From your recordsGross margin, month by month
Dashed line: before, from your last six months of records. Circle: the month it paid for itself.
Not counted yet: sales growth, repeat customers, and calls that used to go unreturned. They go on the page after a year of history, and only what your own records show.
Hours back so far
674
since the build went live
TimedAt this pace
1,042 a year
about half of one person’s year
ProjectedThe owner’s own hours
3 a week
fewer “where does this stand?” questions
Timed- Order to invoiceBuild · month 1
14 min → 3 min each × 3,900 jobs a year
715 hours a year
- Quote follow-upChange · month 4
6 min → 1 min each × 2,100 quotes a year
175 hours a year
- Supply reordersChange · month 6
9 min → 2 min each × 1,300 reorders a year
152 hours a year
Times describe the work, never a person, and they’re never used in anyone’s review.
Paid for itself
month 7
what came back passed what went in
From your invoicesSince then
Ahead every month
the gap grows with each change
From your invoicesWhat counts as coming back
Money only
hours stay on their own page
From your recordsWhat you’ve put in and what’s come back, month by month
Grey: what you’ve put in. Green: what’s come back. Circle: paid for itself. Dashed: projected.
Each change the Review ships adds to what comes back. What you’ve put in counts the Review every month, not just the first three. Months 10 to 12 are projected at this pace. On your own page, both lines carry your real dollar amounts.
Example Co · 2 yards · about 60 people · month 9 after go-live
Waiting time now charged
412 stops
on the invoice since month 1
From your invoicesDays to get paid
26
was 41
From your invoicesEmpty miles
13%
was 18% of miles driven
From your recordsDamage claims filed
27
was 9 · now filed on time
From your recordsLate fees paid
1 a month
was 6
From your recordsDays to get paid, month by month
Dashed line: before, from your last six months of records. Circle: the month it paid for itself.
Not counted yet: new customers, more loads booked, and fewer drivers quitting. They go on the page after a year of history, and only what your own records show.
Hours back so far
1,248
since the build went live
TimedAt this pace
1,862 a year
about one full person’s year
ProjectedThe owner’s own hours
4 a week
fewer “where does this stand?” questions
Timed- Delivery paperwork to invoiceBuild · month 1
22 min → 6 min each × 5,200 loads a year
1,387 hours a year
- Load status callsChange · month 4
4 min → 1 min each × 6,000 calls a year
300 hours a year
- Driver logs and fuel slipsChange · month 6
10 min → 3 min each × 1,500 slips a year
175 hours a year
Times describe the work, never a person, and they’re never used in anyone’s review.
Paid for itself
month 6
what came back passed what went in
From your invoicesSince then
Ahead every month
the gap grows with each change
From your invoicesWhat counts as coming back
Money only
hours stay on their own page
From your recordsWhat you’ve put in and what’s come back, month by month
Grey: what you’ve put in. Green: what’s come back. Circle: paid for itself. Dashed: projected.
Each change the Review ships adds to what comes back. What you’ve put in counts the Review every month, not just the first three. Months 10 to 12 are projected at this pace. On your own page, both lines carry your real dollar amounts.
Example Co · 1 plant · about 90 people · month 9 after go-live
Scrap and remakes
1.9%
was 3.1% of jobs
From your recordsJobs quoted below cost
7%
was 17%
From your recordsMachines waiting on material
9 hours a month
was 31
From your recordsLate-shipment charges
1 a month
was 5
From your recordsOvertime hours
260 a month
was 420
From your recordsScrap and remakes, share of jobs, month by month
Dashed line: before, from your last six months of records. Circle: the month it paid for itself.
Not counted yet: new customers, bigger orders, and shorter lead times. They go on the page after a year of history, and only what your own records show.
Hours back so far
801
since the build went live
TimedAt this pace
1,373 a year
about two-thirds of one person’s year
ProjectedThe owner’s own hours
5 a week
fewer “where does this stand?” questions
Timed- Job ticket to shop floorBuild · month 1
25 min → 8 min each × 2,400 jobs a year
680 hours a year
- Material check before a jobChange · month 4
12 min → 3 min each × 2,400 jobs a year
360 hours a year
- Ship and invoiceChange · month 6
15 min → 5 min each × 2,000 shipments a year
333 hours a year
Times describe the work, never a person, and they’re never used in anyone’s review.
Paid for itself
month 8
what came back passed what went in
From your invoicesSince then
Ahead every month
the gap grows with each change
From your invoicesWhat counts as coming back
Money only
hours stay on their own page
From your recordsWhat you’ve put in and what’s come back, month by month
Grey: what you’ve put in. Green: what’s come back. Circle: paid for itself. Dashed: projected.
Each change the Review ships adds to what comes back. What you’ve put in counts the Review every month, not just the first three. Months 10 to 12 are projected at this pace. On your own page, both lines carry your real dollar amounts.
Example Co · 2 offices · about 35 people · month 9 after go-live
Days to close a file
22
was 31
From your recordsFiles sent back
9%
was 24% · something missing
From your recordsLate and extension fees
1 a month
was 7
From your recordsDays to get paid
24
was 38
From your invoices“Where’s my file?” calls
90 a month
was 260
From your recordsDays to close a file, month by month
Dashed line: before, from your last six months of records. Circle: the month it paid for itself.
Not counted yet: more files taken on, repeat customers, and referrals. They go on the page after a year of history, and only what your own records show.
Hours back so far
814
since the build went live
TimedAt this pace
1,368 a year
about two-thirds of one person’s year
ProjectedThe owner’s own hours
4 a week
fewer “where does this stand?” questions
Timed- File intakeBuild · month 1
35 min → 12 min each × 1,800 files a year
690 hours a year
- Chasing signaturesChange · month 4
20 min → 6 min each × 1,800 files a year
420 hours a year
- Status updates to customersChange · month 6
6 min → 1 min each × 3,100 updates a year
258 hours a year
Times describe the work, never a person, and they’re never used in anyone’s review.
Paid for itself
month 7
what came back passed what went in
From your invoicesSince then
Ahead every month
the gap grows with each change
From your invoicesWhat counts as coming back
Money only
hours stay on their own page
From your recordsWhat you’ve put in and what’s come back, month by month
Grey: what you’ve put in. Green: what’s come back. Circle: paid for itself. Dashed: projected.
Each change the Review ships adds to what comes back. What you’ve put in counts the Review every month, not just the first three. Months 10 to 12 are projected at this pace. On your own page, both lines carry your real dollar amounts.
Example Co · service crews · about 45 people · month 9 after go-live
Jobs billed the same day
94%
was 52%
From your invoicesFinished jobs that used to go unbilled
140
now on the invoice
From your invoicesNo-shows
14 a month
was 38 · reminders go out
From your recordsSecond trips
19 a month
was 46
From your recordsDays to get paid
17
was 29
From your invoicesJobs billed the same day, month by month
Dashed line: before, from your last six months of records. Circle: the month it paid for itself.
Not counted yet: new customers from calls returned, repeat customers, and reviews. They go on the page after a year of history, and only what your own records show.
Hours back so far
969
since the build went live
TimedAt this pace
1,798 a year
about one full person’s year
ProjectedThe owner’s own hours
3 a week
fewer “where does this stand?” questions
Timed- Call to scheduled jobBuild · month 1
9 min → 3 min each × 7,800 calls a year
780 hours a year
- Rebuilding the daily scheduleChange · month 4
90 min → 25 min each × 250 days a year
271 hours a year
- Job notes to invoiceChange · month 6
12 min → 4 min each × 5,600 jobs a year
747 hours a year
Times describe the work, never a person, and they’re never used in anyone’s review.
Paid for itself
month 5
what came back passed what went in
From your invoicesSince then
Ahead every month
the gap grows with each change
From your invoicesWhat counts as coming back
Money only
hours stay on their own page
From your recordsWhat you’ve put in and what’s come back, month by month
Grey: what you’ve put in. Green: what’s come back. Circle: paid for itself. Dashed: projected.
Each change the Review ships adds to what comes back. What you’ve put in counts the Review every month, not just the first three. Months 10 to 12 are projected at this pace. On your own page, both lines carry your real dollar amounts.
Questions
Questions that come up.
Straight answers. If yours isn’t here, ask me directly: blake@operations-layer.net.
Is Operations Layer software?
No. I don’t sell software. I connect the software you already have and build the small pieces that tie it together, in your own accounts.
What happens in the X-Ray, and how much of our time does it take?
A few working sessions with the people who know each part of the job. There’s nothing to prepare. Walk me through how the job goes on a normal day, and I’ll ask the questions. At the end you get the map, two fixed prices (a smaller fix and the full one), and a clickable preview of the smaller fix. The preview runs on made-up examples and isn’t connected to your systems. I show it at the readout so you can see the fix before you choose.
Do you replace our current software?
No. I connect what you have. If something can’t be connected, I’ll tell you plainly and you decide what to do about it.
Will the work stop while you build?
No. It’s like adding a bay onto the shop: the old bays stay open the whole time. Nothing switches over until you’ve seen the new piece work.
What if my people won’t use it?
That’s a big part of what I watch for in the X-Ray: how your people really work and what they’ll ignore. I’d rather build something small they use than something big they work around. If it’s slower than writing it on the pad, I built it wrong. And I’m in the work with them for the first 30 days after it goes live.
Can AI just do this for us?
Not by itself. When AI reads scattered, retyped records, it writes wrong answers with a straight face. I get the job typed once first. Then AI can draft from your own records and show where each line came from, and a person decides.
Do our files and data need to be perfect first?
No. I start with what exists, where people already look and what they trust. The work is shaped around that, not around how it ought to look on paper.
Do I still need my IT person?
If you have one, yes. I don’t set up computers, fix printers or run your network. I work on how the job moves between your software. Plenty of family businesses don’t have an IT person, and you don’t need one to work with me.
What if I stop after the X-Ray?
Then you keep the map and the plan, and you don’t owe me anything more. Build it yourself, take it to someone else, or set it on the shelf.
How do engagements work, and what does it cost?
Everything starts with a paid Operations X-Ray: one part of your operation, at the same flat price for every business. From there, most work is a System Build at a fixed price. I stay in the work for 30 days after it goes live, and the build comes with its first three months of System Care. After that, the way to keep it improving is a monthly Operating Review, with System Care included. If a system is done changing, yearly care keeps it running as built, renewed only when you say yes. Ending either one never switches anything off. You always know the scope and the price first, and nothing is billed by the hour.
Why one person and not a firm?
Because you’re hiring the person who does the work. And because everything is built in your name, with a plain handoff, you’re never stuck with me.
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.