You have a sales call at 2pm. The prospect’s current IT provider is a name you half-recognise, and you want a one-page sheet that shows — honestly — where you differ. Not a glossy battlecard full of unverifiable claims. Just a clean grid you can glance at while the call is running. Here is how to build one in about twenty minutes, and how to do it without copying a competitor’s website, breaching the Personal Data Protection Act (PDPA), or pasting anything confidential into a consumer AI tool.
Start with the buyer's decision criteria, not your feature list
Most comparison sheets fail because they are built backwards. The sales team lists everything the product does, then hunts for a competitor gap to sit next to it. The buyer never asked those questions.
Work the other way. Write down the five to seven things this specific buyer actually weighs. For a Singapore SME evaluating managed IT support, that list usually looks something like this:
- Response time when something breaks, and whether it is contractual or best-effort
- Coverage hours — business hours only, or 24/7 with an on-call rotation
- Cybersecurity scope: endpoint protection, email filtering, patching, backup testing
- Pricing structure — per user, per device, or flat monthly retainer, and whether it is annual-only
- Contract length and exit terms
- Who actually answers the phone: in-house engineers or a subcontracted helpdesk
- Reporting — do you get a monthly review, or silence until something fails
Those seven rows become your sheet. Three columns: your offering, the competitor, and a short note column for the caveat. That is it. One page, landscape, readable at arm’s length.
Source every cell from something you can point to
This is where most comparison sheets quietly become a liability. If a row says a competitor charges for after-hours support, you need to know that from their published pricing page, their service description, or a prospect who told you directly — not from a colleague’s memory of a deal three years ago.
Keep a source column, even if you delete it before the call. For each claim, note where it came from and the date you checked. Pricing pages change. A sheet built on a 2024 rate card will embarrass you in 2026.
A few practical rules:
- Public sources only. Pricing pages, service-level descriptions, published case studies, tender documents, and the competitor’s own marketing. All fair game.
- Never scrape a competitor’s client list or lift their proposal documents. If a prospect hands you a rival’s quote, use it to understand the buyer’s requirements — do not reproduce it.
- Mark unknowns as unknown. A cell that says “not published” is more credible than a guess, and it gives you a genuine question to ask on the call.
- Keep it factual, not editorial. “Annual commitment only” is a fact. “Rip-off contract terms” is a comment that will cost you the deal if the buyer likes their current provider.
If your sheet contains any named individual — a prospect’s IT manager, a referral contact — that is personal data under the PDPA. Keep it on company systems with access controls, not on a personal laptop or a shared drive anyone can browse.
Where AI helps — and where it does not
AI is genuinely useful for the mechanical part of this job: turning messy notes into a consistent table, tightening wording so each cell fits, and generating the follow-up email. It is not useful for deciding what is true about a competitor.
Imagine a sales team that has collected six competitor pricing pages and a page of handwritten notes from three discovery calls. A tool like Claude can take that already-public material and restructure it into a tidy seven-row table, flag which rows have no source, and draft a one-paragraph summary of where the offering genuinely differs. That is a real time saving — perhaps an hour of formatting compressed into a few minutes.
What it cannot do is verify a claim. If you feed it an assumption, it will format the assumption beautifully. The output is only as sound as the input, and the salesperson still owns the accuracy of every row.
A word on data handling. Do not paste a prospect’s proposal, contract, internal pricing, customer names, or anything marked confidential into a consumer AI tool. Those tools may retain inputs and use them for training, and in Singapore that can put you on the wrong side of your PDPA obligations and your own client confidentiality clauses.
The safer pattern is straightforward:
- Work from public information, or from documents you have permission to process
- Strip names, email addresses, and account numbers before anything goes near a tool
- Use an enterprise or API tier with training disabled and a data processing agreement in place
- Keep the finished sheet in your CRM or document management system, not in a chat history
For SMEs handling client data at any volume, that last point is not paranoia — it is the difference between a useful internal tool and an incident you have to report.
Using the sheet on the call
A one-page comparison is a conversation aid, not a pitch deck. Do not screen-share it and walk the buyer through every row. That turns a consultative call into a feature recital, and buyers can smell it.
Instead, keep it beside you and use it to ask better questions. “We noticed their support is listed as business hours only — how does that work for your Saturday trading?” is a far stronger move than announcing a difference. You learn what the buyer actually values, and you avoid asserting anything you cannot back up.
If a row is genuinely in your favour, say it once, plainly, and move on. If a row is not — say the competitor is cheaper on paper — acknowledge it and explain what the price difference buys, or does not buy. Buyers in Singapore’s SME market are pragmatic. They reward the vendor who tells them the awkward thing first.
Building the sheet is the easy part. Knowing what to put in each row, and being able to stand behind it, is where Sakal Network’s managed IT and cybersecurity advisory tends to earn its keep — we help teams map their own service commitments against the market, keep the underlying data handling clean, and set up AI tooling that does not create a compliance problem. If your next sales call deserves a comparison sheet you can defend line by line, start with a conversation.