Most guard companies do not have a sales process. They have a phone number, a rate, and a template. That is enough to stay the same size forever. What follows is a process — five stages, each with a decision at the end of it — that a two-person office can actually run.
Stage 0: know what you are selling
Nobody buys guard hours. They buy the removal of a problem they own personally:
- A property manager whose tenants complain about the parking structure at night
- A facilities director who got asked in a board meeting what security costs and could not justify it
- A GC whose copper keeps disappearing from an unfinished floor
- An HOA board that has one loud resident and no incident record to answer them with
Your proposal should name their version of that problem in the first paragraph. If you cannot name it, you have not qualified the lead — you have received one.
Stage 1: source and qualify
Where the opportunities come from. Property management companies (one relationship, many sites), commercial brokers who know who is leasing and expanding, general contractors, insurance brokers who recommend security to reduce premiums, RFP databases for government and institutional work, and local search — a prospect who found you by typing “security guard company” plus a city name is closer to buying than any cold call. Referrals from existing clients remain the cheapest source; ask for them by name, at a specific moment, not as a general plea.
Qualify before you invest. A site walk and a real proposal cost you the better part of a day. Before you spend it, get answers to five things:
- Who signs, and who else can say no? The facilities manager who called you rarely has final authority.
- Why now? A renewal date, an incident, an insurance requirement, or a new build. “Just looking” means a competitor’s rate is being tested against yours.
- What is in place today, and what specifically is wrong with it? Vague dissatisfaction usually means the real problem is price.
- What is the decision timeline and process — direct award, three bids, formal RFP?
- Is there a budget, and is it a number or a hope?
Score every lead against these before you agree to a site visit. Disqualifying early is not lost business; it is the hours you get back to spend on the deals you can win. What institutional buyers weigh is set out in property manager buying criteria, and formal public bids have their own rules — how to bid security contracts and respond to an RFP.
Stage 2: the site walk
This is the stage that separates you from the companies emailing a rate sheet. Go at the hour the risk exists — if the concern is 2 a.m., the walk happens at 2 a.m., not at 10 in the morning.
Walk with a checklist and produce something:
- Perimeter and access points, and which ones are actually unlocked at night
- Lighting gaps and camera coverage, including cameras that are pointed at nothing
- Where people and vehicles enter, and where they enter unofficially
- Post positions with a reason for each — not “one guard at the lobby” but “lobby post covers the only unbadged entry between 6 p.m. and 6 a.m.”
- A proposed patrol route with checkpoint locations
- Anything the client is currently paying for that is not working
Leave with photographs and hand back a short written assessment within a few days, whether or not you win. That document is the sales asset. A competitor quoting a price has given the client nothing to compare against it.
Stage 3: the proposal
Structure it so that the first page can stand alone, because for the executive who signs, it often will.
1. Their problem, in their words. Reference what you saw on the walk and what they told you. Specifics only.
2. The program, not the headcount. Instead of “two officers, 24/7, at X per hour”, describe what is delivered: posts and hours with a rationale, patrol frequency with checkpoint verification, incident reporting with photo evidence and a named notification path, reporting cadence, and the escalation chain with names and response times.
3. Evidence you can deliver. Comparable properties you cover, your supervision structure, training and licensing, your reporting samples, and the service commitments you are willing to put in the contract. Only commit to what you already measure.
4. Pricing, complete and unambiguous. Rate, coverage, what triggers overtime or holiday billing, what is included, and what is not. Hidden costs discovered in month two poison the relationship permanently.
5. Transition plan. Clients fear the switch more than they dislike the incumbent. Lay it out day by day: overlap with the outgoing provider, supervised solo operation, then independent coverage with daily check-ins tapering to weekly reviews. Put dates on it.
The section-by-section structure, including the parts buyers skim and the parts they score, is in the security proposal template guide.
Stage 4: price with discipline
Do not compete on rate alone. The client won on price leaves on price, usually within a year, and takes your margin with them on the way out.
Price from the bottom up instead: pay rate, plus payroll taxes, workers’ compensation, benefits, uniforms and equipment, supervision, recruiting, and a realistic allowance for overtime and callouts — then your margin. If the resulting bill rate loses the bid, you have learned something true about that account rather than winning a contract that will underperform for three years. The full build-up is in bill rate vs. pay rate.
Justify the difference concretely. When a prospect says a competitor is cheaper, do not defend the number — compare the deliverable:
| What they are quoted | What you are proposing |
|---|---|
| Reports at end of shift or later | Incident reports filed from the scene with photos |
| ”We patrol hourly” | Checkpoint scans with time and verified location per point |
| Monthly summary emailed | A client login with activity, patrols and incidents at any hour |
| Call the office during business hours | A named escalation chain with a response commitment |
| Whatever training the officer had | Documented licensing and site-specific post orders |
Licensing requirements are set at state level and vary substantially, so state yours accurately for the state the site is in rather than reaching for a generic claim — security guard license requirements by state covers where to check.
Offer structure, not discounts. Tiered options — a base program and an enhanced one — let a client choose down instead of negotiating your rate down.
Stage 5: follow up until you get an answer
Silence after a proposal is not a no; it is usually an internal process you cannot see. Run a fixed sequence so it does not depend on anyone remembering:
- Day 1: confirm receipt, offer a call to walk through the proposal.
- Day 3: send something useful and specific — a sample report from a comparable property, or one detail from your site walk you did not include.
- Day 7: call. Ask directly what would need to be true for them to move forward.
- Day 14: ask for a decision or a date. “Should I keep this open, or close it out?” gets an honest answer more often than another check-in.
- Day 30+: move them to a slow nurture and diary the renewal date of whatever they chose instead.
Log every touch and every loss reason. After thirty proposals you will know which stage you actually lose at, which is worth more than any general advice about persistence.
Demo the operations platform
In the meeting, open the laptop and show live guard locations, a recent tour with checkpoint times, an incident report with photos, and the client portal the client would receive. It is the only part of your pitch a prospect can verify in the room, and it reframes the conversation from promises to evidence. Track your win rate before and after you start doing this — that comparison, from your own pipeline, is what tells you whether it is working.
CGuardPro runs one plan at $5 per user per month, everything included, with a 7-day free trial and no card required, plus a one-time $299.99 implementation fee — cheap enough that the demo asset costs less than a single lost bid.