Why the Best-Sounding Proposal Is Often the Weakest
The security market has a quiet problem: it selects for salesmanship, not for security. The providers who are easiest to find and most fun to talk to are often the ones who put their money into selling rather than into the work.
That flips the signal you'd expect. A provider who tells you honestly what can and can't be done sounds less confident than one who promises the world, so the honest answer reads as weakness at exactly the moment it should read as competence. Meanwhile the smooth pitch, the one with an answer for everything, feels safe. Feeling safe and being safe aren't the same thing. A proposal is a sales document, and the ones built to impress are built to move you past the questions a careful reader would stop and ask.
None of this means a good-looking proposal is bad. It means presentation tells you nothing, so you have to read past it to the specifics, where selling and doing finally separate.
Red Flag: It Promises Instead of Describes
The first thing to watch is whether the proposal describes work or sells outcomes.
A describing proposal tells you what the Officer will do, when, and to what standard. A selling proposal reaches for sweeping words it can't be held to: the safest, the most trusted, the top choice, language you can't measure and can't pin down. When a document leans on superlatives and stays quiet on specifics, the superlatives are there to fill the space where the specifics should be.
The sharpest version is the claim that nothing will go wrong. No one can honestly say that. A serious provider tells you what happens when something does, because on a long enough timeline, something will. A proposal that tells you the year will be perfectly quiet isn't being confident. It's being careless with a claim it can't keep, and that same looseness will show up later in the work.
Red Flag: The Scope Could Belong to Any Site
Read the scope and ask a simple question: could this exact page be sent to a hundred other properties with only the address changed?
If it could, nobody walked your site. A real proposal reflects your property: your access points, your hours, the specific risks you raised, the posts that actually need covering. A generic one describes security in the abstract, promises trained professionals without saying what they're trained in, and mentions reporting without saying what you'd receive or when. The template is the tell. It means the provider is selling you a category, not a plan for your building.
Red Flag: The Rate Is Surprisingly Low, With No Detail
A bid well under the others isn't automatically wrong, but it's automatically a question.
A low rate has to come from somewhere, and the fixed costs, taxes and insurance, don't move. What moves is the Officer's wage, the training, and the supervision. So a rate that undercuts everyone else, with no explanation of how, is pointing at what got cut. The proposal that earns trust is the one that can show why its number is what it is. The one that just lands low and stays quiet is asking you not to look.
Red Flag: It Never Says What It Can't Do
The most useful sentence in a proposal is the one that admits a limit, and a document that only says yes has left that sentence out.
A serious provider will tell you when you need less than you asked for, when a risk is outside their scope, or when a timeline is tight. That honesty costs them something in the moment, which is exactly why it's rare and exactly why it's worth looking for. A proposal with no edges, no trade-offs, and no honest no isn't a stronger offer. It's a sales document that decided disagreeing with you was bad for closing.
Reading a Proposal, Side by Side
| Where it shows | A red-flag proposal | A serious proposal |
|---|---|---|
| How it sounds | Impressive and certain | Specific and honest |
| The scope | Generic, could fit any site | Written for your property |
| On what could go wrong | Says nothing will | Says what happens when it does |
| The rate | Surprisingly low, unexplained | Explained and tied to the work |
| Supervision and reporting | Unmentioned or vague | Named and scheduled |
| What it won't do | Never mentions a limit | Tells you plainly |
I ran a training scenario once where I played a picky customer and let someone sell me on a car. He was smooth, likable, helpful the whole time. And he made most of it up. Is there an outlet back here? Sure, to your left. There wasn't. Do the seats heat and cool? Yep, both. I asked if the seat got hot just to catch him, and he said yes. So I sat there and let it burn me, to prove the point.
Every answer felt positive. He was stacking up wrongs the whole time, and it cost him more than an honest I don't know ever would have. A proposal works the same way. The one that answers every question with a confident yes isn't the safe pick. It's the one to read twice.
Before You Sign, Read It Again
Before you sign, run through the proposal one more time and check:
- Does it describe what the Officer will actually do on your site, or mostly tell you how good the company is?
- Could this scope be sent to any property with only the address changed?
- Does it name supervision and reporting, or leave them vague?
- If the rate is low, does the proposal explain how, or just land under the others?
- Does it admit a single limit, trade-off, or thing it won't do?
- Does anything in it sound too certain to be true?
A yes to the last question, or a no to the ones before it, isn't a reason to panic. It's a reason to ask the provider to fill the gap in writing before you sign.
How We Handle It at ARDENT
We'd rather lose a proposal for sounding less impressive than win one by promising something we can't stand behind. So our proposals tend to read plainer than the pitch next to them. We put the specifics in, what we'll cover, how the post is supervised, what you'll get in writing, and we say the parts most sales documents leave out.
That includes the honest no. If you've asked for more coverage than the risk calls for, we'll tell you, even though the smaller number is the one that costs us. If a piece of what you need sits outside what we do, we'll point you to who does it well. We think the limit we name up front is the best evidence you have that the rest of the document is true.
None of that closes as fast as a proposal built to dazzle. It just holds up better once the work starts, which is the only test that counts.
Key Takeaways
- The clearest red flag is a proposal that sells certainty instead of describing the work.
- This industry rewards salesmanship over security, so the smoothest pitch deserves the most scrutiny.
- Superlatives and promises fill the space where specifics should be.
- A scope that could fit any site means nobody studied yours.
- The most trustworthy proposal is the one willing to name a limit, a trade-off, or an honest no.
Frequently Asked Questions
Is a Polished, Professional Proposal a Bad Sign?
No. Presentation isn't the problem, and a serious provider can look sharp too. The red flag isn't that a proposal looks good, it's that it sounds impressive while staying quiet on the specifics. Judge it on what it describes, not on how it's designed.
What If Every Proposal I Get Has These Red Flags?
Then the questions do the work the proposals didn't. Ask each provider, in writing, what the Officer does, how the post is supervised, what reporting you'll receive, and what they won't do. The document that fills those gaps honestly moves to the top, whatever it looked like at first.
Aren't Strong Assurances a Good Thing?
An assurance that a provider will make things right when something goes wrong is reasonable. An assurance that nothing will ever go wrong is a sales line, because no one can honestly say that. The second kind should raise your caution, not lower it.
Should a Proposal Really Admit What It Can't Do?
Yes, and it's one of the strongest green flags there is. A provider willing to name a limit or turn down a piece of the work is showing you the honesty you're actually buying. The proposal that only says yes has told you the least.
The Cheapest Bid Also Sounds the Most Confident. Now What?
Treat the confidence and the price as two separate questions. Confidence isn't coverage, and a low number isn't a bargain until you know what it left out. Ask both providers to show the wage, the training, and the supervision behind the rate, and let the specifics decide.