Skip to content

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.

Book a free call
a printed operations map spread on a table, with notes and a coffee cup beside it

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.

StepWhoHow it's done todayWhere it slips
Pick who to callCallersScroll a shared contacts spreadsheetSame company called twice; due callbacks missed
Call and log itCallersPersonal phones; a note in the sheet, if at allOutcomes and promised callbacks lost
Send documentsCallersPersonal email with attachmentsWrong revision sent; nothing saved to the contact
Hand off a hot leadCaller to business developerA text or a callThe conversation starts over
Bid and proposalBusiness developerA row in a bid workbook, PDFs by emailRevisions and follow-up dates drift
Won: hand off to the yardBusiness developer to ownersA phone callAddress, contact and site details retyped or missing
Check stock and reserveOwnersA walk through the yardSales promises panels that are already spoken for
Hand tasks between peopleEveryoneTexts and memoryNobody knows whose turn it is, so steps wait
Site prep, crews, deliveryOwnersCalls, texts and memoryTrucks booked before the site or the money is ready
Collect paymentOwnerInvoices and phone callsSales tax, shipping and commissions split by hand
Track costs by jobOwnersReceipts and the bank statementMaterials, trucking and labor not tied to the job, so profit is a guess
After deliveryNobodyNothingNo 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.

PersonHow they hear about changes nowWhat they need
OwnersCalls from the business developerWon jobs with site details, crew and delivery dates, what's paid
Business developerTexts from callers, the inboxHot leads with history, bids due, proposals to revise
CallersThe spreadsheetToday's calls, the right script, history
Prospects and contractorsCalls and emailsThe right documents and a callback when promised
Site contacts and truckersPhone callsDelivery time, access, the load

4. The software and tools in use

ToolWhat it's used forWhat it missesCost
Two spreadsheetsContacts by customer type; bids and resultsNo call queue, no history, easy to overwriteIncluded
PhonesCallingNothing logged, no scriptsMonthly plan
EmailProposals and documentsDoesn't attach to the contact or reset follow-upsIncluded
Invoices, texts and callsDelivery and paymentNo link between the sale, the site and the paymentStaff 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 toWhat flowsWhich way
Spreadsheets the team keepsNew leads and bids, brought in on a schedule without overwriting notesIn
The phone systemClick-to-call, call logs and transcriptsBoth
The shared email inboxDocuments from templates; replies reset follow-up datesBoth
Online paymentsDeposits and final payments, tied to the jobIn
Accounting softwareInvoices, payments and costs by jobOut
Text messagesDelivery-day notices to customers and site contactsOut
Review sites and a feedback formThe check-in after delivery and the review requestBoth

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
Phone calls to find out where a job stands
System goes liveBeforeAfter

Fall as orders and updates reach people on their own

Jobs that reach the yard complete
System goes liveBeforeAfter

Rise as every hand-off carries the full job

Places to look for one job
BeforeOne system

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.

ItemWhat it coversPrice
The buildEverything in section 5 marked First and Next, set up, moved over and taught to the teamFixed, paid in three parts
Monthly subscriptionHosting, support, fixes and small changes, month to monthSet in your map, month to month
Later piecesThe items marked Later, priced when you want themQuoted separately
TravelOnly if we travel outside the areaAt 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

WhenWhat happens
Weeks 1 and 2Two days with the team, on site or by video
First monthWe build the first pieces and move your information over
Months 2 and 3Your team uses it on real work, and we adjust it every week
After thatMonth-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.

Want to see if this would help your business?

A free call, then a free Operations Map: how your business runs today, what we'd build, and a fixed price. Yours to keep either way.

We take on only 2 or 3 new businesses a quarter. See a sample Operations Map →

Book a free call