Build a decision brief before you pitch a senior decision maker. Name all seven fields: the account decision, dated company evidence, likely owner role, adjacent stakeholder roles, unresolved unknowns, access path, and smallest reversible next step. If the brief cannot support the decision, evidence, owner, or unknowns, do not contact. Research first, then choose whether any approach is justified.
Build the Decision Brief
Start with a simple question: what can this person actually decide? A title such as chief executive, chief revenue officer, or vice president tells you where someone sits. It doesn't tell you which decision is active, what evidence the company is using, who can block it, or whether this person owns the next move. If you start with the title, you push every missing fact into the message. Your email then has to invent urgency, relevance, and ownership at once. That is why a concise pitch can still feel presumptive even when you've polished every sentence.
Build the decision brief before you build the message. Think of it as a compact, source-linked record for one account and one possible decision. Give yourself seven visible fields: the decision that may exist, dated company evidence, the likely owner role, adjacent stakeholder roles, unresolved unknowns, the access path, and the smallest reversible next step. Can you support each field without blending evidence and inference? If the decision is vague, the evidence is generic, or the owner is merely the most senior person you found, stop. The brief has done its job by showing you that the approach isn't ready.
Now test the role field more carefully than a contact lookup. Salesforce's Sales Productivity Guide, checked August 31, 2026, records Decision Maker and Detractor as separate buyer attributes and distinguishes Finance, Legal, and Tech department groups. Microsoft Dynamics 365 documentation, checked the same day, treats decision maker, champion, end user, economic buyer, influencer, and technical buyer as distinct opportunity stakeholders. You don't need to copy either label set. Use them to remind yourself that one senior title rarely explains the approval path. Write a likely owner role, not a certainty, and keep the adjacent roles visible until your evidence narrows them.
The seven fields that make the brief usable
- Decision: state the business choice in words the account could recognize, without turning a broad priority into a fabricated project.
- Current company evidence: attach dated first-party pages or filings and record exactly what each one supports.
- Likely owner role: name the function closest to the decision, then mark the role as a hypothesis until verified.
- Adjacent stakeholder roles: record the functions that may shape, approve, block, or implement the decision without assuming that any one of them owns it.
- Unresolved unknowns: preserve missing market, timing, policy, stakeholder, and qualification fields instead of filling them with sales language.
- Access path: identify the evidence-backed route available now, such as a public application process, a referral, or a bounded research step, and do not invent direct access.
- Smallest next step: choose the most reversible action that could reduce one important unknown, including the option to stop.
Bring a tool in only after you can fill those seven fields. If you use OKKI Go for company search or contact discovery, your brief should already supply the company type, role, geography, and exclusions that make the search meaningful. The tool can't turn a missing owner into a verified owner, and a contact record can't prove a decision. Keep the order explicit: first define the account decision and your evidence standard; then use the tool for one bounded research task. Can't your brief define that task yet? Keep researching. More data would create motion without giving you justification.
Decide Whether the Brief Is Ready
Don't measure readiness by the amount of research you've collected. Ask whether your brief can support one next decision without smuggling an assumption into the account record. A company filing can show you strategy, operating dependence, risk, or a change in direction. It can't prove that a team has opened a buying project. A leadership page can identify an executive; it can't prove that the executive owns your narrow decision. A product page can establish what an offer does; it can't prove that the account needs it now. Your readiness test is whether every leap is visible, not whether you've filled every blank.
Match each source to the claim you want it to carry. The SEC's EDGAR search system, checked August 31, 2026, gives you public access to company filings and a dateable source trail, so use it for what a public company disclosed. Add an investor page or official product page when you need context, but keep your role hypothesis marked as inference. As you save each source, record its URL, access time, and sentence-level purpose. Then ask: what doesn't this source establish? That boundary keeps you from turning a strategic statement into urgency or an organizational chart into a buying committee.
Before you choose an approach, run four checks together. Is the decision narrow enough to test? Is your first-party evidence current enough for the claim and attached? Does the likely owner role follow from the decision rather than rank alone? Are the remaining unknowns small enough that one next action can reduce one without asking the buyer to do your research? If the decision is still a category, the evidence merely proves that the company exists in a market, or the owner is a seniority guess, your brief is not ready. Continue the research or stop; don't compensate with more personalization.
A title is not the owner of the decision
Use a relationship map to test ownership, not to decorate the account. Salesforce's relationship map documentation, checked August 31, 2026, describes a view across company levels that surfaces stakeholders, champions, and potential risks before a seller advances a deal. What should you take from it? Visibility isn't advancement, and seniority isn't ownership. Finance may control economic approval, Legal may control terms, Tech may control feasibility, and an operating champion may control internal movement. Name the role whose work would change if the decision were made. Then list who could redirect, approve, or block it. If no source or account signal supports your map, say so and stop.
Turn the Brief Into an Approach
Once your brief is ready, derive the approach in order. Begin with the account decision, not your product category. Which role most likely owns that decision? Use the stakeholder map to decide whether your first path should go through that likely owner, an operating champion, a known relationship, or more research. Next, choose one unknown that you can reduce. Only then decide whether the smallest step is a question, a short evidence exchange, a referral request, a candidate review, or no contact. Let each choice earn the next one. You won't need to hide missing logic inside persuasive copy.
- Write the decision as a choice the account might actually make, and remove any urgency the sources do not support.
- Attach current first-party evidence, its access date, the exact claim it supports, and the boundary it cannot cross.
- Derive the likely owner role from the decision, then keep champions, economic buyers, technical buyers, detractors, and other blockers separate.
- Select an access path that fits the evidence, such as an existing relationship, a role-led route, a referral, or continued account research.
- Ask for the smallest reversible next step that reduces one named unknown; if none exists, record a stop.
This sequence changes how you use tools. Don't begin an OKKI Go search by asking for every senior contact in a broad industry. Begin after your brief defines one plausible company type, one role family, one geography, and the exclusions that would make a result irrelevant. Then review the candidate list as evidence, not as your outreach queue. Choose companies before you discover contacts. Make a separate send decision before you draft anything. The product can support that bounded step, but your brief still has to justify why the step exists.
Sequence the access path after the evidence
If your brief earns a message, make the message smaller. State the evidence that made the decision plausible, explain why you're asking this role, and request one correction or next step. You don't need to explain the entire product, simulate a business case, or claim that the account is ready. Could this person own the defined partner, process, or data decision? Ask that narrow question. If you need a referral, name the decision without pretending a project exists. Keep your stop condition attached: when the recipient, evidence, or decision changes, return to the brief instead of continuing on momentum.
Verify the Smallest Next Step
How do you know the method can stop a real approach? Test it against a real offer and a named company. For this article, we built a source-linked brief for Alarm.com Holdings, Inc. and OKKI Go. We asked whether the team responsible for Alarm.com's international service-provider network should test a small candidate-company search in one defined market. You can inspect the first-party URLs, access time, page screenshots, intermediate brief, visible revision trail, and final decision in the research supplement. This is a documented walkthrough, not an imagined customer story. We didn't unlock or approach a contact.
Our first pass overreached. It treated partner-network importance as urgent demand, guessed that a vice president of international sales owned the decision, predicted a cost benefit, and proposed a demo request. What survived when we checked the sources? The filing supports the importance of service-provider relationships and international expansion, but not a live purchase or urgent gap. The partner page supports an application path, but it doesn't name the person who owns recruitment. The OKKI Go pages establish search and review capabilities, but not a result for Alarm.com. So we kept a likely international channel or partner-development role and marked the exact owner unknown.
Would you approach this account now? No. Four unresolved fields drive the NOT READY result: the current decision owner, the target geography, the approved candidate profile, and the policy for using an external company-search source. Your smallest next step would be internal verification of those fields, not a contact unlock, personalized email, or demo request. If you later verify the owner, one market, the qualification criteria, and the policy boundary, a small result set for human review would be reversible. Until then, your message would ask a decision maker to resolve your research gap. The stop is the observable result of the method working.
The Alarm.com walkthrough stopped before outreach
- Check that the brief names one account decision rather than a broad corporate priority.
- Open every source and confirm its date, publisher, claim purpose, and explicit boundary.
- Separate the likely owner role from every other stakeholder and from any named individual who has not been verified.
- Review deleted or softened claims and confirm that none reappears in the approach as urgency, benefit, or certainty.
- Record READY only when the next step reduces a named unknown without requiring the buyer to complete the account research; otherwise record NOT READY and the stop reason.
Now apply the same test without borrowing the Alarm.com conclusion. Start with your named account, your real offer, and one decision. Preserve the intermediate brief before you polish it. Delete what your sources cannot carry. Does the final brief still name all seven fields: the decision, dated evidence, likely owner role, adjacent stakeholders, unresolved unknowns, access path, and smallest reversible step? If it does, choose the access path that follows. If it doesn't, keep the stop. Your first proof of judgment may be the decision not to pitch too early.
Your decision brief earns its value before you book a meeting. It turns your account research into a bounded choice, keeps unknowns visible, and gives you permission to stop. When your evidence supports a path, take the smallest reversible step. When it doesn't, preserve the brief and keep the pitch unsent.
Frequently asked questions
What belongs in a decision brief before senior outreach?
Name the account decision, dated first-party evidence, likely owner role, adjacent stakeholders, unresolved unknowns, access path, and smallest reversible next step. Keep evidence and inference visibly separate.
Why is a senior title not enough to identify the decision maker?
Seniority shows organizational level, not ownership of a particular choice. Decision makers, economic buyers, technical buyers, champions, influencers, end users, and detractors can play different roles in the same approval path.
When should the brief return NOT READY?
Return NOT READY when the decision is vague, company evidence is generic or stale, the likely owner is guessed from rank, important unknowns remain unresolved, or no reversible next step can reduce one of those unknowns.
How can OKKI Go fit without authorizing outreach?
Use it only for a bounded research step after the brief defines company type, role, geography, and exclusions. Review candidate companies first. Contact discovery and any draft should remain downstream of a separate human decision.
