A sample Operations Map
This is what you get after the free sit-down. It's based on a real map for a concrete products manufacturer we work with, with names and numbers left out.

1. The business at a glance
What they make
Precast concrete walls, made to order and delivered to the site.
Who buys
Fence installers, contractors, developers, HOA managers, utility districts and cities.
The team
Two owners (site prep and crews; delivery and collections), a business developer and two callers.
How they find work
Researched contact lists called on a cycle, and bids tracked in a workbook.
2. How work moves today
Each step, who does it, how it's done now, and where it slips.
| Step | Who | How it's done today | Where it slips |
|---|---|---|---|
| Pick who to call | Callers | Scroll a shared contacts spreadsheet | Same company called twice; due callbacks missed |
| Call and log it | Callers | Personal phones; a note in the sheet, if at all | Outcomes and promised callbacks lost |
| Send documents | Callers | Personal email with attachments | Wrong revision sent; nothing saved to the contact |
| Hand off a hot lead | Caller to business developer | A text or a call | The conversation starts over |
| Bid and proposal | Business developer | A row in a bid workbook, PDFs by email | Revisions and follow-up dates drift |
| Won: hand off to the yard | Business developer to owners | A phone call | Address, contact and site details retyped or missing |
| Check stock and reserve | Owners | A walk through the yard | Sales promises panels that are already spoken for |
| Hand tasks between people | Everyone | Texts and memory | Nobody knows whose turn it is, so steps wait |
| Site prep, crews, delivery | Owners | Calls, texts and memory | Trucks booked before the site or the money is ready |
| Collect payment | Owner | Invoices and phone calls | Sales tax, shipping and commissions split by hand |
| Track costs by job | Owners | Receipts and the bank statement | Materials, trucking and labor not tied to the job, so profit is a guess |
| After delivery | Nobody | Nothing | No feedback, no review request, no next project |
3. Who's involved, and how they hear about things
Everyone who touches a job, inside and outside the company.
| Person | How they hear about changes now | What they need |
|---|---|---|
| Owners | Calls from the business developer | Won jobs with site details, crew and delivery dates, what's paid |
| Business developer | Texts from callers, the inbox | Hot leads with history, bids due, proposals to revise |
| Callers | The spreadsheet | Today's calls, the right script, history |
| Prospects and contractors | Calls and emails | The right documents and a callback when promised |
| Site contacts and truckers | Phone calls | Delivery time, access, the load |
4. The software and tools in use
| Tool | What it's used for | What it misses | Cost |
|---|---|---|---|
| Two spreadsheets | Contacts by customer type; bids and results | No call queue, no history, easy to overwrite | Included |
| Phones | Calling | Nothing logged, no scripts | Monthly plan |
| Proposals and documents | Doesn't attach to the contact or reset follow-ups | Included | |
| Invoices, texts and calls | Delivery and payment | No link between the sale, the site and the payment | Staff time |
Results so far: the business developer gets 6 to 8 hours a week back, each caller gets about 20% more done, the system turns up 7 new prospects a week, and 1 more of them converts.
What it connects to
The system sits in the middle and talks to the tools the team already uses, so nobody types the same thing twice.
| Connects to | What flows | Which way |
|---|---|---|
| Spreadsheets the team keeps | New leads and bids, brought in on a schedule without overwriting notes | In |
| The phone system | Click-to-call, call logs and transcripts | Both |
| The shared email inbox | Documents from templates; replies reset follow-up dates | Both |
| Online payments | Deposits and final payments, tied to the job | In |
| Accounting software | Invoices, payments and costs by job | Out |
| Text messages | Delivery-day notices to customers and site contacts | Out |
| Review sites and a feedback form | The check-in after delivery and the review request | Both |
5. What we'd build
In order, so the team feels the difference right away.
First: a calling queue
Each caller's list for the day, by customer type, one call per company, with the right script and the history on one screen.
First: outcomes that set the next date
Every call result sets the next follow-up. Promised callbacks come first, and a real email resets the clock.
First: documents from templates
The current proposal or product sheet, sent from the shared inbox and saved to the contact.
Next: bids beside the calls
Each bid's revision, pricing and result next to the contact, with other projects at the same company.
Next: sale to operations
A won bid reaches the owners with the address, contact, scope and a site-prep checklist. Crews and deliveries are scheduled from it.
Next: inventory everyone can see
Panels and posts on hand, what's reserved for which job, and what to pour next.
Next: task hand-offs
Each step has an owner. When one finishes, the next person is told and the job moves on.
Later: costs by job
Each payment splits into sales tax, shipping, commissions and operations, and materials, trucking and labor are tied to the job, so profit is real.
Later: the customer's page
Customers answer site questions and pay online.
Later: closing the loop
After delivery, the customer is asked how it went. Problems go to an owner; happy customers get a review request and a check-in on their next project.
6. What goes away
- Scrolling the spreadsheet to decide who to call
- Notes and promised callbacks that lived nowhere
- Proposals sent from personal inboxes
- The phone call that handed a won job to the yard
- Walking the yard to see what's in stock
- Trucks booked before the site or the money was ready
- Guessing at profit per job
Fall as orders and updates reach people on their own
Rise as every hand-off carries the full job
Spreadsheets, texts, email and the yard, or one screen
Illustrations, not measurements.
7. What we'd need from you
- The contact and bid spreadsheets, and a handful of past jobs
- The call scripts and document templates you use now
- About an hour with each person on the team
- One person who'll be our go-to during the build
8. Scope and fee
Every map ends with a fixed price for exactly what's in it.
| Item | What it covers | Price |
|---|---|---|
| The build | Everything in section 5 marked First and Next, set up, moved over and taught to the team | Fixed, paid in three parts |
| Monthly subscription | Hosting, support, fixes and small changes, month to month | Set in your map, month to month |
| Later pieces | The items marked Later, priced when you want them | Quoted separately |
| Travel | Only if we travel outside the area | At cost |
Use it as long as it fits. If your business changes, let us know and we'll adapt it with you. We maintain it for as long as it makes sense.
9. Timeline
| When | What happens |
|---|---|
| Weeks 1 and 2 | Two days with the team, on site or by video |
| First month | We build the first pieces and move your information over |
| Months 2 and 3 | Your team uses it on real work, and we adjust it every week |
| After that | Month-to-month subscription: we keep it running and add the next pieces |
Every map is different. Yours will be written around how your business runs.