When I was a system integrator, I knew every day a proposal sat unfinished was another day a competitor could enter the deal.
Getting a proposal in front of a client took one to two weeks. Sometimes longer.
Of course, the scope mattered. But once a customer walked the site with me, explained the problem, and started imagining the solution, the clock was already running.
Now I sit on the other side of that conversation. Every week I am meeting with executives at system integrators, and after the initial discovery call I usually ask to go one layer deeper. Not into features. Into the numbers.
Because there is a window in every project that almost nobody measures. It starts when the site walk ends and it closes when a decision-ready proposal lands in front of the customer.
The site-walk-to-proposal gap is the time between the end of a site survey and the moment a decision-ready proposal reaches the customer. It costs integrators twice. Once in deals that cool while the proposal is being built, and once in margin lost to the rework that late, incomplete documentation creates downstream.
Most teams I talk to have never measured either half.
Why the Clock Starts at the Site Walk, Not the Send Button
A site walk does something to a buyer. They put a face with a name. They describe the problem out loud, maybe for the first time. They start picturing the fix.
That is the high-water mark of their urgency. Everything after it is decay.
Every extra day created an opening for:
- A competitor to enter the conversation.
- The customer’s urgency to fade.
- Another internal priority to take over.
So, I was constantly racing to get proposals out while the opportunity was still warm. Not because anyone was slow. Because the process put a week of work between the customer’s best moment and my ability to respond to it.
The Work That Never Makes It Onto the Calendar
Here is what that week actually looked like for me.
I spent three to four days during most weeks traveling across the country for site walks. By the time I got back to my hotel or home, I still had to organize my notes, sort through photos, build the system design, confirm the equipment, and put together the proposal.
That usually meant long nights trying to catch up.
None of that appeared on a project plan. It was not scoped, estimated, or billed. It was absorbed, by me, after hours, and then repeated the following week on the next job.
When I ask integrator leaders how many hours go into a proposal, the first answer is usually a guess. The second answer, after they think about it, is almost always higher.
The Questions I Ask Integrator Executives
If we cannot speak in financial terms, we are only having half the conversation. So these are the questions I bring to the second call:
- How many hours go into a proposal from start to finish?
- Of those hours, how much gets consumed internally before it ever reaches the customer?
- How much time is spent recirculating, correcting, revising, and chasing missing information?
- What percentage of rework comes from understatements, pricing errors, or scope gaps?
- How often do change orders or unexpected rework get charged back to the business?
Here is what I have realized. Most teams do not actually track rework.
And honestly, I get it.
Why Rework Never Shows Up on the P&L
There is no clean line item that says, “Profit lost because we had to redo the work.”
But that does not mean it is not there.
It shows up in missed details. It shows up in rushed proposals. It shows up in sales and operations going back and forth. It shows up when the field team has to solve something that should have been caught during the site walk.
It shows up in margin erosion.
And over time, it becomes one of the quietest ways profitability leaks out of the business.
Two Costs, One Root Cause
For a long time, I thought of these as separate problems. Speed was a sales problem. Rework was an operations problem.
They are the same problem measured from opposite ends.
When site information is captured on a yellow pad, in a camera roll, and in someone’s head, the proposal cannot be built until that information is reconstructed. Reconstruction takes days, which is the speed cost. Reconstruction is also imperfect, which is the rework cost.
The delay and the errors come from the same source. Documentation that happens after the site walk instead of during it.
That is why fixing one usually fixes the other and why adding more people to either side rarely helps. You are not short on capacity. You are short on accuracy at the front of the process.
The Quiet Math on Your Own Gap
You do not need perfect data. You need a number that makes the tradeoff visible. Pull your last ten jobs and fill this in.
Step one: measure the gap.
- Average business days from site walk completed to proposal delivered = 10
Step two: the speed side.
- Proposals sent per year = 288
- Close rate on proposals delivered after one week = 35%
- Close rate on proposals delivered within 48 hours = 42%
The spread between those two close rates, applied to your annual proposal volume and average deal size, is your delay cost. Most teams have never split their close rate this way, and the first look is usually the uncomfortable part.
Step three: the rework side.
Projects per year = 120
Hours lost per project to clarifications, revisions, and version cleanup = 5
Blended hourly rate = $72
Multiply those three. Then add unplanned site revisits at your all-in cost per trip.
Two numbers. One is the revenue you never booked. One is the margin you booked and then gave back. Neither one appears on a report today.
Try This With Your Team This Week
Pick one recent job that felt normal but took longer than it should have. Then answer three questions together.
- What was the very first detail someone had to chase down after the site walk?
- Where did that information live, and why was it not visible to everyone?
- How many days passed between the site walk and the proposal, and what filled them?
That last question is the one that tends to change the room.
Where System Surveyor Fits
System Surveyor helped me shorten that gap.
Because I documented the site and built the design during the site survey, I had far less work waiting for me afterward. The system design was already taking shape while the customer was standing next to me, which meant fewer assumptions to correct later.
Photos and notes stayed tied to the exact device in question instead of buried in a camera roll. The bill of materials came out of what was actually captured on site, not out of a reconstruction. And because everyone downstream could see the same plan, collaboration happened while the site was still fresh rather than three weeks into the job.
I could move from site visit to proposal faster, even when most of my week was spent on the road.
Speed to proposal is not just an efficiency metric. It protects buyer momentum. It reduces the window for competitors. And it shows the customer that your team can execute with urgency.
The integrators who are going to win in this market are not just the ones selling more projects. They are the ones who understand the cost of how those projects are being sold, designed, handed off, and delivered.
Because growth is great. But profitable growth is the goal.
Are you tracking your site-walk-to-proposal gap today, or is it still hidden inside the process?
FAQs
It is the number of business days between completing a site survey and delivering a decision-ready proposal to the customer. For integrators using manual documentation, that gap commonly runs one to two weeks. It carries both a revenue cost from fading buyer urgency and a margin cost from downstream rework.
Start with projects per year, multiplied by hours lost per project to clarifications and revisions, multiplied by your blended hourly rate. Then add unplanned site revisits at their all-in cost. The estimate does not need to be precise to make the tradeoff clear.
Buyer urgency peaks during the site walk and decays from there. Every additional day gives competitors a window, lets internal priorities take over, and lets the customer’s sense of the problem cool. A faster proposal also signals that your team can execute.
Most rework traces back to information captured after the site walk rather than during it. Missing photos, assumed device locations, unconfirmed equipment, and scope gaps all get discovered downstream, when correcting them costs the most.
Usually not. Delay and rework come from the same root cause, which is incomplete documentation at the front of the process. Adding people to proposal production increases capacity to reconstruct information, but it does not reduce the amount of reconstruction required.
Shelby Chatigny is an Account Executive at System Surveyor, the leading digital platform for physical security site surveys and system design. With 5+ years of experience across the physical security industry, she brings a unique perspective from both the manufacturer and integrator sides. Shelby works closely with customers to modernize site walks, streamline digital design and help teams deliver more accurate, collaborative, and efficient security projects. She enjoys building relationships in the industry and supporting professionals who want to elevate their workflows and scale their business with better tools and clearer communication. Shelby lives in the mountains of North Carolina where she enjoys hiking, reading, writing poetry, playing with her two dogs and spending time with family and friends.