In this article
Two questions before a demo commitment
Compensation software evaluations move slowly because the stakes are high. An error in a compensation run affects every employee at the company. Buyers know this and they ask specific questions before they agree to a demo.
The two questions are usually the same at any company size. Can it handle the volume of employees we have? Has it completed the full compensation workflow, hard parts included?
A first message that cannot answer both questions, or that makes a claim about one and hopes the other does not come up, will lose the first meeting.
Employee volume is the first proof point
Employee volume proof means a documented case where the software processed a payroll or compensation run for a company comparable in size to the prospect. The proof needs a number.
A case study from a company with 200 employees does not satisfy a buyer with 8,000. The worry is that the software has not been tested at their scale.
Mach reads case studies, customer stories and product pages when it builds your Brain. It does not check them for volume claims, so check that you have a number yourself.
Workflow completion is the harder proof
Workflow completion proof is harder to provide because compensation workflows vary by company, jurisdiction, and benefit structure. A buyer wants to see that the full workflow ran to the end.
Claims such as "processes payroll", "handles complex compensation" and "integrates with HRIS" do not answer this question. They describe capability. A buyer asking about workflow completion wants a documented run from start to close.
If you have a reference customer who completed a full workflow for a comparable buyer, that reference is more valuable in the first message than any feature description.
How Mach pulls the relevant evidence
When Mach researches a compensation software buyer, it judges the company against each sign in your ideal customer profile, such as size or region, and marks each as met, not met or unknown.
The brief then names your closest case studies from the Brain, matching on industry first, with a line on why each is like the company. Mach does not match on employee volume or jurisdiction, so check that yourself.
When research finds a matching case study, the first message leads with it. When none matches, the draft carries no proof.
What to do when the evidence does not match
When the proof does not match the prospect's profile, the choices are to send a message that acknowledges the gap honestly, delay the outreach until you have a matching reference, or target a different segment where your proof is stronger.
A message that claims proof it does not have will be caught in the first meeting. The damage is a lost deal, a lost reference and a buyer who tells others about the gap.
Honesty about a gap in the first message can itself be a differentiator. "We have not processed at your scale before, but here is what we have done and what we would do differently" is a stronger opening than a claim that falls apart in the first question.
Check your evidence before the first message
Before the first outreach to a compensation software buyer, check your case library against their employee count. If you do not have a matching case, decide which of the three responses above applies.
Keep the case evidence in the Brain rather than in a separate document. Mach can use it when building research briefs. Evidence that lives only in a slide deck cannot be referenced automatically.
After the first meeting with a compensation buyer, record what questions came up about proof. If the same proof gap appears in multiple first meetings, it is worth addressing before the next campaign to this segment starts.
