Executive Meeting POV Builder
Use this checklist to turn public signals, internal notes, and Vitelis Proof of Value Creation inputs into a point of view senior buyers will take seriously. The goal is simple. If your outreach reads like you did the work on the account, you earn the meeting. If it reads like generic personalization, you lose the room before it opens.
This guide is built for three named accounts at a time. Work one account through all four phases before you write the final outreach.
Phase 1. Prep
Purpose: decide whether the account has enough signal to support a credible point of view.
Checklist
- Account fit is clear - Standard: The account matches your target market, your value points, and a real business problem you can speak to. - Pass signal: You can name the likely business issue in one sentence without using product language. - Fail signal: You only have a company name and a role title. - If it fails: Remove the account or gather more signal before writing.
- Public signal set is complete - Standard: You have at least one recent item from each of these sources where available: - company website or recent news page - executive LinkedIn post - earnings call, press release, or investor update - competitor or category context - recent job postings - Pass signal: You can point to at least 3 distinct signals, and one is recent. - Fail signal: You are guessing from old pages or secondhand notes. - If it fails: Collect fresh public evidence before moving on.
- Internal notes are usable - Standard: You have notes from recent first meetings, your last 10 outbound messages, and the current product wins that map to the account. - Pass signal: You can see what opened well and what fell flat in prior outreach. - Fail signal: Your message history is missing or too vague to compare. - If it fails: Pull the last 10 messages and mark what the buyer reacted to.
- Proof of Value Creation input is specific - Standard: For the three named accounts, you have known pain points, strategic goals, or recent changes. - Pass signal: Each account has at least one concrete business clue. - Fail signal: The input is broad, like “growth” or “efficiency.” - If it fails: Add account-specific context before building the hypothesis.
- There is enough evidence to build a point of view - Standard: You can connect signal, business pain, and a likely meeting angle without stretching. - Pass signal: The account has a clear pattern, not a one-off clue. - Fail signal: The evidence is too thin or contradictory. - If it fails: Stop. Do not force outreach. Move the account to a later round.
Phase pass condition
You pass prep when each of the three accounts has enough signal to support a real business hypothesis.
Phase fail condition
You fail prep if the account fit is weak, the signals are thin, or the evidence does not support a credible point of view.
Phase 2. Build
Purpose: turn raw signal into pain, root cause, and a meeting hypothesis.
Checklist
- Observed signals are listed before interpretation - Standard: Write the facts first. Separate them from your opinion. - Pass signal: Another rep could read the notes and see the same facts. - Fail signal: Facts and guesses are mixed together. - If it fails: Reformat the notes into two lines, one for signals and one for interpretation.
- Buyer pain is stated in plain language - Standard: The pain names a business issue the buyer would care about, such as pipeline quality, cycle time, margin pressure, retention risk, or expansion delay. - Pass signal: The pain is specific enough that the buyer would recognize it. - Fail signal: The pain is generic, like “needs growth” or “wants better results.” - If it fails: Rewrite it around an outcome the account is trying to improve.
- Root cause is tied to the evidence - Standard: The cause explains why the pain exists and connects to at least one signal. - Pass signal: The cause fits the facts and does not require guesswork. - Fail signal: The cause is broad, abstract, or unsupported. - If it fails: Remove the cause or replace it with a simpler one that matches the signal.
- Timing pressure is real - Standard: There is a reason the issue matters now, such as a leadership change, hiring push, market shift, earnings pressure, or new initiative. - Pass signal: You can point to a current trigger. - Fail signal: The issue could wait six months and nothing would change. - If it fails: Find a real trigger or stop calling it a meeting hypothesis.
- The meeting hypothesis is one sentence - Standard: The hypothesis says what the buyer is likely dealing with and why a conversation matters now. - Pass signal: It fits in one sentence and stays concrete. - Fail signal: It turns into a pitch or a paragraph. - If it fails: Cut it down until the message is one clean claim.
- Each of the three named accounts has its own hypothesis - Standard: No copy-paste across accounts. - Pass signal: The account-specific trigger and pain are different where the facts are different. - Fail signal: The same message works for all three accounts. - If it fails: Rewrite from the account outward, not from the product outward.
Simple build template
| Part | What to write | Pass signal |
|---|---|---|
| Signal | What you saw | Fact-based, recent, specific |
| Pain | What the buyer is dealing with | Business issue, not product language |
| Root cause | Why it is happening | Tied to evidence |
| Timing | Why now | Clear trigger |
| Hypothesis | Why the meeting matters | One sentence, account-specific |
Phase pass condition
You pass build when each account has a clean signal, a real pain, a defensible root cause, and a one-sentence meeting hypothesis.
Phase fail condition
You fail build if the hypothesis sounds like marketing, if the pain is vague, or if the root cause has no evidence behind it.
Phase 3. Validate
Purpose: test whether the point of view is believable to a senior buyer and useful by role.
Checklist
- The point of view is specific enough to be checked - Standard: A buyer could confirm or reject the claim based on their own reality. - Pass signal: The claim has a clear subject, problem, and trigger. - Fail signal: The claim is too soft to challenge. - If it fails: Add a stronger business reference or remove the claim.
- The message sounds informed, not decorative - Standard: The outreach uses account facts, not praise or filler. - Pass signal: A senior buyer sees business judgment. - Fail signal: The message opens with “congrats,” “love what you are doing,” or other empty framing. - If it fails: Cut the compliment and lead with the business issue.
- Weak claims are marked for removal - Standard: Every claim has evidence, or it gets cut. - Pass signal: No unsupported statements remain. - Fail signal: The draft contains claims you cannot defend in a live reply. - If it fails: Remove the claim or find proof.
- The executive relevance is obvious - Standard: The message connects to revenue, margin, risk, growth, or strategic execution. - Pass signal: A business leader would care without translation. - Fail signal: The message only matters to a specialist. - If it fails: Reframe the angle around business impact.
- The operator angle is practical - Standard: The operator sees a process, workflow, or execution problem they recognize. - Pass signal: The issue is tied to daily friction. - Fail signal: The message is too strategic to act on. - If it fails: Add one operational detail from the account signals.
- The champion angle is usable - Standard: The champion can forward the note without rewriting it. - Pass signal: The value is easy to repeat inside the account. - Fail signal: The message is too broad or too technical. - If it fails: Simplify the language and give the champion one clean internal reason to share it.
Stakeholder tailoring check
| Stakeholder | What they need | Pass signal | Common fail |
|---|---|---|---|
| Economic buyer | Business impact and timing | Clear reason to care now | Too much detail, not enough consequence |
| Operator | Process friction and execution cost | A problem they own today | Too abstract |
| Champion | Internal story they can repeat | Short, credible, specific | Hard to repeat in a meeting or email |
Phase pass condition
You pass validate when the account point of view holds up for an executive, an operator, and a champion without changing the underlying truth.
Phase fail condition
You fail validate if the message only works for one role, relies on weak claims, or sounds polished but empty.
Phase 4. Launch and refine
Purpose: send a message that is short, credible, and useful, then fix what fails fast.
Checklist
- The opener states the account issue fast - Standard: The first two lines show you know the account and the reason to reach out. - Pass signal: The buyer can tell this is about their business, not your company. - Fail signal: The opener hides the point for too long. - If it fails: Put the account signal in the first sentence.
- The message stays brief - Standard: The outreach gives one point of view and one reason to talk. - Pass signal: Nothing feels padded. - Fail signal: The message turns into a mini white paper. - If it fails: Cut every sentence that does not support the meeting ask.
- The ask matches the level of insight - Standard: The CTA asks for a conversation tied to the issue you named. - Pass signal: The ask feels earned. - Fail signal: The ask is generic, like “hop on a call.” - If it fails: Tie the ask to the business question or the account trigger.
- The message has one clear point of view - Standard: Do not stack three different angles in one note. - Pass signal: The buyer knows what the meeting would be about. - Fail signal: The reader cannot tell which problem matters most. - If it fails: Pick the strongest angle and remove the rest.
- The final draft passes the generic test - Standard: Remove the company name and see if the note still sounds account-specific. - Pass signal: The draft becomes weak without the account detail. - Fail signal: The draft still reads like a template. - If it fails: Add stronger account signal or rewrite from scratch.
Failure-response
Use this when the checklist fails at any point.
| Failure signal | What it means | Remediation |
|---|---|---|
| No recent account signal | The note is built on stale or thin evidence | Collect current public facts before writing |
| Pain is vague | The buyer problem is too broad to matter | Rewrite around one business outcome |
| Root cause has no proof | The logic is speculative | Remove the claim or find supporting evidence |
| Timing is weak | There is no reason to act now | Find a current trigger or pause the account |
| Message sounds generic | The note could be sent to anyone | Add account-specific detail and cut filler |
| Stakeholder fit is poor | The same message will not work across roles | Rewrite the angle for each role |
Phase pass condition
You pass launch and refine when the draft is short, specific, and anchored to a real business issue the buyer will recognize.
Phase fail condition
You fail launch and refine if the outreach still sounds like a template after the final review.
Readiness check
Minimum standard
- Each of the three named accounts has enough signal.
- Each account has one clear pain statement, one root cause, and one meeting hypothesis.
- Each draft has been tested for executive relevance, operator relevance, and champion usability.
- The final outreach passes the generic test.
Next action
- If all four checks pass, send the outreach.
- If any one check fails, fix the failure before you send anything.
- If two or more checks fail, stop and rebuild the account point of view from the prep phase.
Ready to Outperform?
See how Vitelis uncovers value opportunities in your business. Request a 30-minute demo — zero cost, zero data lift.
All rights reserved © Vitelis
Privacy
