How owners keep a year of proposals and how each one ended, and build next year’s growth plan from the work customers already choose, whether they ever sell or not.
Every proposal a company sends ends one of three ways. The customer says yes, the customer says no, or the customer never decides.
A yes becomes a signed contract and an installation or service visit on the schedule. A no usually arrives as a call or an email, and someone on the team often remembers it. The third ending usually leaves the least behind. Customers seldom call to say a project is off, so the day it ended often goes unrecorded.
Growth targets for 2027 are often established before the year starts, from a revenue goal the company hopes to achieve. A practical approach is to build the plan around actual sales activity and customer decisions from the prior year. A proposal log provides that foundation by tracking every proposal that reached an outcome between November 2025 and October 2026, whether it was won, lost, or ended in no decision. This historical data helps establish a more realistic, informed starting point for future growth.
Maintained consistently over a year, the proposal log reveals which types of work customers are most likely to approve and which opportunities rarely convert into actual business. These insights help leadership make more informed decisions about where to focus growth efforts and how to allocate the team’s time and resources to future proposals. The value extends beyond annual planning, providing information that can improve business performance regardless of whether the company is ever sold.
What goes in each row
Each row is one proposal and how it ended. The columns stay the same for every row:
- Sent date: the month the proposal went to the customer.
- Outcome date: the month the customer said yes or no, or the month the proposal became no decision.
- Customer and work: who it was for and what it covered, such as access control, video, fire alarm, or intrusion.
- Size: the proposal’s total, or a size range when the exact amount is more detail than the sort needs.
- Source: where the opportunity came from, such as an existing customer, a referral, a general contractor’s bid invitation, the website, or the company’s own outreach.
- Outcome: won, lost, or no decision.
- Reason: what the customer said, written down as they said it.
When a project is put on hold, customers rarely communicate a formal decision, making it important to establish a consistent definition for proposals that receive no response. One practical approach is to classify a proposal as “no decision” when the customer indicates they are not ready to move forward or when 90 days have passed without a response. The 90-day period begins on the customer’s expected decision date or, if no date was provided, the sent date. Applying this standard consistently across all proposals supports reliable tracking and meaningful month-to-month comparisons.
The log has no column for who wrote the proposal, on purpose. A proposal is often the work of several people: whoever first spoke with the customer, the estimator who priced the design, the project manager who walked the site. The log records what customers chose and why, so everyone who works on proposals can see which kinds of work customers say yes to.
Much of the first year can usually come from records the company already keeps: the proposal software, if it can export a list, or the sent folder and the job list. Reasons are often harder to recover. Where nobody asked the customer at the time, write “not asked” and leave it there, because the column holds only what customers actually said.
Six rows from an illustrative log
These rows are illustrative, not drawn from any company’s records.
| Sent date | Outcome date | Customer and work | Size | Source | Outcome | Reason |
|---|---|---|---|---|---|---|
| December 2025 | January 2026 | Medical office: two doors added to its access control | Under $10,000 | Existing customer | Won | “You installed our first doors, and they work.” |
| February 2026 | March 2026 | Warehouse: cameras replaced across the yard | $25,000 to $50,000 | Website | No decision | Last reply: “Let’s revisit after our lease renewal.” |
| March 2026 | May 2026 | School: fire alarm replacement | Over $50,000 | General contractor’s bid invitation | Lost | “The general contractor went with a lower number.” |
| April 2026 | June 2026 | Property manager: intrusion monitoring at three buildings | $10,000 to $25,000 | Referral from a customer | Won | “Our other building said you show up when you say you will.” |
| May 2026 | August 2026 | Manufacturer: access control and video for a new wing | $25,000 to $50,000 | Existing customer | No decision | “We couldn’t get it approved this year.” |
| July 2026 | September 2026 | Office building: fire alarm inspection and service agreement | $10,000 to $25,000 | Company’s own outreach | Lost | “We’re staying with the company that installed the system.” |
The September row is one this industry knows well: a customer keeping service with the company that installed the system. Its reason belongs in the log as much as any price does, because it can describe what an installation earns in the years after it is finished.
Four ways to sort the year
Once the year is in, sort it four ways. Each sort answers a question next year’s plan has to settle.
| Sort by | What it shows | The question for 2027 |
|---|---|---|
| Size | Which proposal sizes customers say yes to, and which sizes tend to end in no decision | Which sizes can the plan count on? |
| Source | Which sources bring the proposals customers choose | Which sources deserve more of the team’s proposal hours? |
| Kind of work | Which services customers choose the company for | Which service is ready to grow? |
| Time to decide | How long proposals of each size and source take from sent date to outcome date | What decision dates belong on the proposals still open? |
Proposal size is an important factor to evaluate, particularly in the current market. In September 2026, the editor of Security Sales & Integration highlighted findings from a midyear report covering security and audiovisual integrators, identifying contracts valued between $25,000 and $50,000 as a particularly challenging segment. The editor described projects in this price range as a sticking point for many customers. One suggested approach was to break the scope into smaller, phased contracts.
The log shows whether proposals of that size are harder for your own customers to say yes to. If they end in no decision more often than the others, a phased proposal may suit those customers better: a first phase they can approve this year, with the rest of the work written out for when they are ready.
The source sort shows how much of the year’s won work came from customers the company already serves and the people they referred. Proposals take hours, often from the company’s most experienced people, and the sort shows where those hours led. A general contractor’s bid invitations may bring fewer yeses and some of the year’s largest jobs, and the log lets an owner weigh both.
Time to decide goes straight to the revenue bridge, which asks for a decision date and an honest probability on each open proposal. The log gives both a basis. A probability set from the company’s own outcomes at that size and source can be checked as the year goes, and a decision date drawn from how long similar proposals took can be easier to plan around.
The proposals with no decision
Proposals classified as “no decision” can provide some of the most valuable opportunities in the log. Each represents a customer who expressed interest by requesting a proposal but never formally declined to move forward. As discussed in our earlier revenue planning article, the commercial customers we know develop their budgets for the following year during the fall. A proposal that stalled in the spring may now align with a customer’s new budget and priorities, creating an opportunity to reengage and potentially convert that interest into revenue.
Before the end of 2026, go down the no-decision rows and offer each customer a short call, at the time they named if they named one: is the need still there, and would a different scope or timing help? The need may have passed, or the customer may ask for an updated proposal, sometimes a smaller first phase. Either answer goes in the log.
In the customer’s words
The reason column deserves the most care. “Price,” in the company’s words, and “we couldn’t get it approved this year,” in the customer’s, describe different events. The first sounds like a lost proposal. The second is a timing question, and it belongs with the rows worth a call.
Ask after a yes as well as a no. A customer who chose the company can usually say why in a sentence, and that sentence describes what to keep doing. A short category beside the words, as the attrition ledger keeps for accounts lost, makes the column easy to sort.
When the reason is price, one more question helps: compared with what? A lower price for a smaller scope and a lower price for the same scope call for different responses, and the answer can change how the next proposal describes what is included.
From the log to the plan
Next year’s plan, built from the log, starts with the work customers already choose. If most of the year’s yeses came from existing customers in two kinds of work, the plan can say so, and set aside the time the team needs for proposals in that work. A new service or source gets a starting point to measure against next year.
A year of proposals, and how each one ended, also speaks to a question an outside reviewer often asks early: where does new work come from, and does it come back? The company’s own record answers it row by row, with reasons from its customers. That is the fifth of the five fundamentals at work: a story the numbers back up.
Where we stand
Behind every yes in a proposal log is a customer who decided to trust a company with something new, and the reason beside it records why. We built Halo Service Partners on the conviction that in commercial security, trust is the product. Continuity is the center of how we partner, because the trusted local company is the thing worth protecting. The name stays, the team stays, and the customer relationships stay. What changes is what stands behind them: shared resources across the network, marketing support among them, so an owner deciding where to grow has support behind it, and a company can take the step it has been weighing. Founders choose their own path forward: step back, stay on to lead, or take a larger role across the network.
ProTech Security and Verified Security both run under their own names today, with the leaders and teams who built them still serving the customers who know them.
If you’re thinking about the future
If you own a commercial security company and you are thinking about its future, in any direction, we are glad to compare notes: on how companies like yours decide where to grow, on the market, and on what your next chapter could look like. Somewhere in this year’s proposals, a customer has probably already said why they chose your company, and the log is where that sentence belongs.