How Can Deep Tech Founders Write a Good Brief for Strategic Communications Advisory
If you are reaching out to a strategic communications advisor, the quality of the response you get is shaped almost entirely by the quality of the brief you send. A vague brief produces a generic proposal — a deck, a website refresh, a PR campaign, priced and packaged. A precise brief produces a strategic conversation about what your venture actually needs, which may or may not be any of those things.
This is not a process document. It is a thinking document. Most of the work of writing a good brief is the work of diagnosing your own situation honestly, and that diagnosis is the part founders most often skip. If you find yourself unable to write certain sections below, that is itself useful information: the section you cannot write is usually where the real engagement needs to begin.
A good brief is short. One to two pages is enough. The discipline is in what you leave out, and in being willing to write what you would rather not.
Three traps to avoid before you start
The wishlist trap. The most common bad brief reads: "We need a new pitch deck, a website refresh, and a PR push around our Series B." This is a list of vendor purchases, not a brief. It tells the advisor what you think the answer is. A good advisor's first job is to test whether your answer is right — and your wishlist makes that harder, not easier. Replace tactics with the friction that produced them. "Investors keep asking the same clarifying question after our pitch" is a brief. "We need a new pitch deck" is a purchase order.
The hiding trap. Founders systematically omit the uncomfortable parts: what isn't working, what the board is unhappy about, where the technology is genuinely uncertain, which stakeholders have lost interest, what the last agency failed to deliver. Advisors who can actually help you need this information. Advisors who cannot will fill the gap with assumptions, and you will spend the engagement correcting those assumptions instead of solving the problem. Hiding the hard parts is a tax you pay twice — first to write the brief, then to undo it.
The symptom trap. "Press misquotes us" is a symptom. The underlying friction might be that you are explaining things for the first time in adversarial channels because you have no owned channel where your thinking already lives. "Investors don't get it" is a symptom. The underlying friction might be that the financial language you use was borrowed from software companies and does not translate scientific progress legibly. Symptoms get treated. Root causes get fixed. A good brief names both, and is honest that the founder may not yet know which is which.
The seven sections of a good brief
These are the sections every strategic communications brief in deep tech should contain. Aim for one or two paragraphs per section. If a section runs to a page, you are still describing rather than diagnosing.
1. What you actually do — including what is still uncertain
Write the version of your venture you would not put on the pitch deck. Two short paragraphs:
The technical paragraph: what the technology actually is, at the level of mechanism, written in plain language. If you cannot do this in plain language, that fact belongs in the brief.
The commercial paragraph: who pays you (or will pay you), for what, and at what stage of validation that revenue currently sits.
Then add three or four sentences on what is not yet known: which scientific assumptions remain to be validated, which regulatory pathways are unclear, which customer segments are unproven. This part feels uncomfortable to write because pitch culture trains founders to project certainty. Resist that training here. The advisor needs the honest map. Without it, every artifact built will eventually misrepresent the venture.
Include your TRL band. It changes what the advisor can credibly help you say.
2. The precipitating moment
What happened recently that made you reach out now, rather than three months ago or three months from now? There is almost always a specific trigger: a board meeting that went sideways, a fundraising round that took longer than it should have, a journalist piece that misframed you, a partnership that quietly stopped returning emails, a regulator who asked an unexpected question, a competitor who claimed your category language first.
If you genuinely cannot identify a trigger and you have simply "been thinking about this for a while," ask yourself what changed in the last sixty days. Something usually did. That something belongs in the brief.
3. The friction
Name the conversation that is not landing the way you need it to. Be specific about three things:
Who the stakeholder is, named as narrowly as possible. Not "investors" but "the late-stage infrastructure investors we are approaching for our pre-FID round." Not "regulators" but "the certification body whose decision in Q3 determines our timeline."
What they are interpreting that they should be interpreting differently — and what the gap looks like in their words, not yours.
What happens if the friction persists for another twelve months. Concrete consequences, not abstract risk.
If you cannot describe the gap in the stakeholder's own language — what they actually say or believe — that is the first signal that you have not yet had the diagnostic conversation you need.
4. What you have already tried
List previous attempts honestly: agencies engaged, consultants hired, in-house hires made, frameworks adopted, books read and applied. For each, write one sentence on what worked partially and one sentence on what did not, and your best current theory about why.
This section protects both you and the advisor. It prevents the engagement from rerunning experiments that already failed. It also reveals something diagnostic: founders who have tried five tactical interventions without identifying the underlying issue are usually demonstrating that the underlying issue is not tactical. The pattern of past failures is sometimes the clearest signal of where the real work lies.
5. Your hypothesis about the underlying issue
Using the cluster check below, name your best current guess about what is actually going on. State it with appropriate humility:
"Our working hypothesis is that this is primarily a category creation problem — investors and analysts keep filing us under [adjacent category] which mispriced our defensibility. But it could be a translation problem in disguise: when we explain the category clearly, listeners understand it but cannot repeat it. We would like the advisor to test this hypothesis before designing the engagement."
A good advisor will take this seriously and may agree, partially agree, or push back hard. All three responses are valuable. What you want to avoid is a proposal that simply mirrors your hypothesis without examining it. Write the hypothesis to be tested, not to be flattered.
6. What success looks like in twelve months
Three to five concrete, observable outcomes. Not "better positioning" or "improved narrative" — those are inputs, not outcomes. Examples of well-formed outcomes:
"Late-stage infrastructure investors describe us using our own category language without prompting in their internal memos."
"Board meetings no longer require ten-minute clarifications about technical progress before strategic discussion can begin."
"At least two analyst reports in our space reference our category framing by name."
"I personally have a stable five-version explanation repertoire I can deploy across investor, regulator, customer, journalist, and policy audiences without improvising."
"Our public validation roadmap is referenced by partners and journalists when they discuss our progress, replacing the speculative coverage we currently get."
Mix external outcomes (how others describe you) with internal ones (how you operate). The internal ones are often the more important and the more often forgotten.
7. Constraints, scope, and decision-makers
This section is where most briefs are weakest, and where most engagements fail later. Include:
Budget range. A real one. Advisors who can serve you within a given range need to know that range; those who cannot are doing both of you a favour by saying so early.
Timeline. When the precipitating moment becomes acute. Some briefs have a hard external deadline (a fundraising round, a regulatory milestone, a partnership announcement); others do not. Be honest about which.
Internal capacity. Who in your team can support the work, how many hours per week, with what authority. Engagements fail more often from internal capacity gaps than from advisor failure.
What is genuinely off-limits. Legal constraints, regulatory boundaries, board sensitivities, IP exposure, geopolitical factors. These shape what can and cannot be communicated and the advisor needs them up front, not in week six.
Out of scope. State explicitly what this engagement is not. Common exclusions: pitch coaching, generic media training, branding and visual identity, performance marketing, founder personal-brand work disconnected from the venture. Saying what is out keeps the brief tight and prevents drift.
Decision authority. Who signs off on the brief, who has veto on the work, who must be involved in major decisions. If your board chair must approve the narrative spine, the advisor needs to know that on day one.
The cluster self-check
Most deep-tech communications briefs cluster into one of seven categories. Read the seven below and identify which one or two describe your situation most accurately. The honest answer is rarely a single cluster — overlap is normal — but one is usually primary.
A — The translation gap. You can build the technology but you cannot reliably explain it without distortion. Investors, board members, or customers ask the same clarifying questions repeatedly. Non-experts leave conversations impressed but cannot repeat what was said. Different audiences walk away with different versions of what you do. If this is you, the brief is about building a stable explanation repertoire — a small set of versions of the same core narrative, deployable across audiences, anchored in a structure like Context → Logic → Essence → Analogy → Relevance.
B — Category creation. Your technology does not fit the boxes the market currently uses. Stakeholders compare you to the wrong adjacent companies. Customers ask which existing budget line they should use to buy from you, and there isn't one. You find yourself reaching for new vocabulary that has not yet stabilised across your decks, website, and interviews. If this is you, the brief is about naming and defending a category — building the conceptual anchor, the boundary definitions, the "why now" argument, and the artifacts (whitepaper, glossary, vision document) that travel through the ecosystem on your behalf.
C — Ecosystem embeddedness. You are technically credible but commercially isolated. Partnerships start enthusiastically and die quietly. Customer conversations feel like education sessions that never convert. Different ecosystem actors — universities, regulators, incumbents, infrastructure owners — interpret you through incompatible frames. You cannot describe your role in the ecosystem in a single sentence. If this is you, the brief is about building a stakeholder-tailored narrative system that holds across audiences — partners, customers, regulators, and scientific peers each able to see themselves in your story without contradiction.
D — Investment worthiness signalling. Fundraising feels longer and harder than it should given your technical progress. Different types of investors (VC, corporate, government, infrastructure) give contradictory feedback on the same pitch. The board asks for narratives the technical team finds unrealistic. You sense that you are using software-style metrics on deep-tech progress and that this is making you look slower than you are. If this is you, the brief is about making scientific progress legible to heterogeneous capital — translating technical milestones into financial language for each investor type, and sequencing capital deliberately so each round produces signals that unlock the next.
E — Regulatory and policy communication. Approvals, certifications, or standards are shaping your timeline. You interact with ministries, standards bodies, or international regulators. Messages used commercially are being reinterpreted in policy contexts, or vice versa. Your technology touches dual-use, national security, climate, or health domains, and you are not yet fluent in those conversations. If this is you, the brief is about aligning your regulatory, commercial, scientific, and public messages so they reinforce rather than contradict each other — and positioning you to participate in shaping standards rather than reacting to them.
F — Crisis and issues exposure. A safety event, data integrity question, ethical controversy, missed milestone, or geopolitical exposure has occurred or is plausibly imminent. Your instinct is to control the narrative or go quiet. Internal and external messages are diverging. A delay is being framed as a failure by stakeholders you cannot ignore. If this is you, the brief is about building issues infrastructure before the moment arrives — an issues map, a boundary language set, a public validation artifact, a governance review rhythm — or stabilising the current situation if the moment has already arrived. Stabilisation is not spin; it is restoring legibility under pressure.
G — Media presence and executive voice. Your media activity is reactive, episodic, or inconsistent. Your public voice does not feel like the same person across formats — LinkedIn, podcast, keynote, casual conversation. Hype cycles drag you into claims you later regret. You have no owned channel where your long-term thinking lives. Your board treats communication as marketing rather than governance. If this is you, the brief is about building a mature media presence system — a stable narrative spine, a channel hierarchy, a small set of reusable artifacts (mechanism diagram, validation roadmap, ecosystem map, ethical statement), and a cadence governance rhythm that sustains coherence over years rather than campaigns.
If two clusters fire equally, name both in your brief and ask the advisor to help you decide which is primary. If five fire equally, your underlying problem is probably not in any single cluster — it is in the leadership architecture beneath them, which is the next section.
A short health check on yourself as the communicator
Before you finalise the brief, consider these four honest questions. They are not part of what you send to the advisor, but they shape what you are actually asking for.
Can you translate? Can you explain your technology to a non-expert without distortion, and to an expert without oversimplification? Do you connect technical milestones to commercial implications without prompting? When something is genuinely uncertain, can you say so without losing authority?
Do you integrate? Are your communications with the board and key stakeholders rhythmic and proactive, or episodic and reactive? When setbacks happen, do you communicate them early — or do you try to solve them first and report them resolved? When you brief externally, are you synthesising across technology, finance, and regulation, or delivering fragments?
Can you orchestrate? Do you know which director, advisor, or ecosystem partner to activate for which kind of help? Are you comfortable asking for it explicitly? Or are you trying to be the one voice for everything — investor pitch, board narrative, regulatory dialogue, customer conversation, public commentary — alone?
Are you still learning? Do you receive feedback on your communication style constructively, or defensively? Do you ask for mentoring on negotiation, organisational design, investor language? Or are you performing a certainty you do not have because you believe vulnerability undermines authority?
The pattern of weakness across these four questions tells you something important about the engagement. A founder weak on translation needs an advisor who can build explanation infrastructure with them. A founder weak on integration needs governance rhythm work. A founder weak on orchestration needs board and ecosystem work. A founder weak on learning posture needs coaching first — because no communications project will hold if it is undone the moment the advisor leaves the room.
Be honest. The most expensive mistake in this entire process is hiring an advisor to fix the artifact when the upstream issue is the operating system underneath it.
One-page brief template
Use this structure. Keep the whole thing to one to two pages.
VENTURE BRIEF — STRATEGIC COMMUNICATIONS ADVISORY
Date: __________
Prepared by: __________
1. WHAT WE DO (HONEST VERSION)
Technical (1 paragraph):
Commercial (1 paragraph):
TRL band:
What is genuinely uncertain (3–4 sentences):
2. WHY NOW
Precipitating moment:
What changed in the last 60 days:
3. THE FRICTION
Stakeholder (named narrowly):
Gap between what we say and what they hear:
Consequence if it persists 12 months:
4. WHAT WE HAVE ALREADY TRIED
(Brief list with one-line outcomes)
5. OUR HYPOTHESIS
Primary cluster (A–G):
Possible secondary cluster:
What we want the advisor to test about this hypothesis:
6. SUCCESS IN 12 MONTHS
External outcome 1:
External outcome 2:
External outcome 3:
Internal outcome 1:
Internal outcome 2:
7. CONSTRAINTS AND SCOPE
Budget range:
Timeline / hard deadlines:
Internal capacity (who, how many hours/week):
Off-limits topics or claims:
Out of scope (explicit exclusions):
Decision-makers (sign-off, veto, must-be-looped-in):If a section is genuinely empty, write "unknown — would like the advisor to help diagnose" rather than leaving it blank or making something up. Honesty about what you don't know is more useful than confidence about what you haven't yet figured out.
A final note
Writing this brief well will take you between two and six hours, depending on how clearly you have already thought about your situation. That investment is the cheapest part of any strategic communications engagement. The cost of skipping it — vague briefs, generic proposals, six-month engagements that produce artifacts disconnected from the underlying problem — is the most expensive mistake founders make in this part of the venture-building process.
If you find that you cannot write certain sections, that is not a failure of the brief; that is the brief telling you where the conversation needs to begin. Send it anyway, with the gaps marked honestly. A good advisor will recognise the gaps as the most useful information in the document.
