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.

  1. 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
  2. 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
  3. 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.

Example map · made-up business
  1. 1Counter call, written on a padPhoneTyped once, at the counterPhone → one record
  2. 2Retyped into an email to the officeEmailNot neededentered once
  3. 3Waits on the one person who knows the priceWaits 3 daysStill needs the priceReminder goes to Kim, the named backup
  4. 4Keyed into the quote spreadsheetSpreadsheetNot neededentered once
  5. 5Keyed into the CRM a third timeCRMNot neededentered once
  6. 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.

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.

Payback Map · Example CoExample screen · sample data

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 invoices

Work that used to go unbilled

988

lines now on the invoice

From your invoices

Days to get paid

22

was 34

From your invoices

Rush charges

3 a month

was 14

From your records

Work done twice

4 a month

was 11

From your records

Gross margin, month by month

29.6%28.8%28.0% Before: 28.4% (last 6 months) Build live + change + change Paid for itself 123456789

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.

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.

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.