7 steps · 15 min read

Product launch outreach playbook for agencies

A seven-step workflow for agencies using a prospect’s product launch to qualify one service gap, owner, outreach route, and stop state—without inventing need.

Who this is for: B2B agencies and lean client-development teams deciding whether a verified product launch supports research, an existing-relationship handoff, one narrow service question, or no outreach.

A prospect’s product launch can create work an agency understands, but it does not create an open brief. Verify the release, identify one current launch job, find who already owns it, and test whether a narrow service gap is visible before choosing any outreach route. A launch announcement alone does not prove need, budget, dissatisfaction, or permission.

This playbook starts after the product-launch signal verification guide has established what changed and the current release state. It is for agencies considering client-development outreach after another company launches its own product. It is not a media-relations plan, a launch campaign for an existing client, or a reason to contact every person named in an announcement.

Step 1. Verify the launch and its current state

Preserve the original company source before interpreting the event. Record the product, service, feature, tier, version, or market offer; the intended audience; the visible dates; the geography; the access path; and the state you observed. Treat discovery alerts, syndicated articles, directories, employee reposts, and generated summaries as leads to the source, not proof of the release.

Visible source	What it can support	What it does not establish	First agency action
Company announcement or newsroom post	The company publicly described a named release or plan	Availability, adoption, operating strain, an agency brief, or budget	Open the product, documentation, and access sources
Waitlist, preview, beta, or early-access page	A defined audience may be able to request or receive limited access	General availability, launch scale, customer uptake, or a service gap	Record eligibility, geography, timing, limits, and current call to action
Release notes, documentation, pricing, signup, or purchase path	A current feature, setup path, package, or access condition	Internal ownership, success, urgency, supplier dissatisfaction, or purchase intent	Check whether the path matches the announced offer and date
Customer, support, hiring, partner, event, or workflow evidence	Possible execution around one launch-related job	Cause, scope, a missing capability, or permission to pitch	Keep each source separate and test one cautious job hypothesis
Old launch page, recap, award, or directory listing	A historical release may have existed	That the launch is current, unfinished, commercially active, or relevant now	Find a current source or expire the route

Keep planned, waitlisted, private preview, beta, phased rollout, generally available, delayed, paused, withdrawn, superseded, completed, and unknown states distinct. A published page can remain online after the underlying release changes. Recheck the state before any follow-up.

Step 2. Map one launch job to one agency capability

Do not turn the launch category into a shopping list. A new product does not automatically require new positioning, creative, paid media, demand generation, sales enablement, lifecycle email, implementation, customer success, analytics, PR, or web work. Start with one job the public evidence makes plausible, then ask what would have to be true for your agency to help.

Launch evidence	Plausible current job	Still unknown	Safe next route
A new audience and use case are named	Clarifying positioning and audience-specific proof	Whether the current message is weak or externally owned	Review public assets; do not diagnose from the announcement
Early access has a documented onboarding path	Coordinating education, activation, or handoff work	Current performance, ownership, capacity, and outside-help need	Find the current operating owner and execution evidence
Several launch assets serve different channels	Maintaining message and measurement continuity	Whether the channels share a brief or already have specialist owners	Map the visible owners and incumbent suppliers first
Customer questions identify one repeated setup issue	Improving one public education or support handoff	Frequency, business impact, internal resolution, and service priority	Answer publicly available context or research; do not manufacture a crisis
The launch is generally available with no separate execution evidence	No supported agency job yet	Nearly everything about ownership, pressure, and outside help	Watch, learn, or close the route

Write the hypothesis as a question a reviewer can reject: “The new partner tier may create a partner-enablement handoff across the launch page and sales material; current ownership and outside support are unknown.” Avoid conclusions such as “their launch messaging is bad” or “they need our agency.”

Step 3. Find the in-house owner, supplier, and relationship route

The founder, product leader, spokesperson, author, and person who shared the news are not automatically the buyer for agency services. Find the current owner of the one launch job. Then check whether an internal team, incumbent agency, freelancer, implementation partner, platform partner, customer, or existing commercial relationship already covers it.

Visible ownership state	What it means	Route
Existing client or active opportunity	An account owner, current brief, commitments, and contact policy may already exist	Route internally; do not start a cold launch sequence
Named incumbent agency, partner, or specialist	At least part of the work has an external owner	Respect the relationship; research only a genuinely separate gap
Named in-house launch owner	One person or team can explain the current work	Use one narrow question only if fit, gap, proof, and channel are sound
Shared or cross-functional ownership	The job spans teams and may not have one commercial buyer	Find the operating handoff; do not message several stakeholders in parallel
Procurement or public request for support	A documented process or invitation may control participation	Follow the stated process and scope; do not bypass it through private outreach
No current owner or supplier evidence	The route is unresolved, not open	Research, watch, or stop

Resolve customer, prospect, partner, referral, former relationship, competitor, vendor, candidate, opt-out, complaint, bounce, and suppression states before opening a channel. If several people at the account appear relevant, choose the one current job and owner. Do not create artificial buying-committee certainty from the launch team page.

Step 4. Test service fit, proof, delivery capacity, and conflicts

A relevant service category is not enough. The agency must be able to deliver the narrow job now, show proof at the same evidence grain, and handle conflicts or exclusions before asking for attention. A case study from another market, product type, launch stage, or team model may not transfer.

Account fit: does the company, product, market, geography, stage, budget model, and working style fit the agency?
Job fit: does the agency own the exact launch job, or only an adjacent service category?
Proof fit: can the agency show a relevant method, artifact, teardown, or outcome without inflating attribution?
Delivery fit: is the appropriate team available in the release state and timeframe the evidence supports?
Supplier fit: is the job unowned, shared, or explicitly open rather than already covered?
Conflict fit: do category, client, confidentiality, geography, exclusivity, or partner conflicts require disclosure or exclusion?
Contact fit: is there a suitable relationship, channel, lawful basis, and no stop state?

Keep a reviewer-facing reason brief. It should be challengeable, not a score that hides assumptions.

Field	Required record
Source	Original URL, publisher, visible date, observation date, and exact claim
Release state	Planned, preview, beta, phased, generally available, delayed, completed, unknown, or another evidenced state
Current launch job	One provisional operating job tied to visible execution
Owner and supplier	In-house owner, incumbent agency or partner, existing relationship, shared state, or unknown
Service gap	What may be unowned or changing—and the evidence that makes it a question
Fit and proof	Why the agency can credibly help with this exact job and what would disqualify it
Conflict and stop state	Exclusivity, confidentiality, competitor, opt-out, complaint, bounce, suppression, or policy boundary
Message change	The sentence, artifact, or question that would not exist without the verified evidence
Route and expiry	Research, internal handoff, public response, invited reply, narrow question, hold, or stop—with a recheck date

Use the free Buyer Intent Signal Prioritizer to review evidence, fit, freshness, message impact, and the next route. It does not turn a launch into an agency opportunity.

Step 5. Choose timing from evidence state

Do not use a universal launch-day, 48-hour, 14-day, or 30-day timer. Agency timing follows the release state, current job, owner, supplier, relationship, and invitation. An announcement can be fresh but too early. A later public question can create a more useful route than the launch itself.

Evidence state	Timing decision	Allowed next step
Announcement only	The release, work, owner, and supplier remain unclear	Verify or watch; no agency pitch
Preview or phased release with visible execution	One job may be active, but ownership and outside-help need are unresolved	Research the owner and current coverage
Public request, brief, referral, or invitation	The source defines a current participation route	Respond through that route with fit, disclosure, and scope
Existing relationship plus one current uncovered job	The account owner can verify whether a conversation is useful	Internal handoff or one reviewed check-in
Incumbent coverage, internal execution, completed work, or no service gap	The launch does not support a new agency route	Learn, hold, or stop
Delayed, withdrawn, stale, contradicted, poor-fit, or suppressed	The original reason is invalid or prohibited	Close and preserve the state

Build the selected route with the free Outbound Workflow Builder only after the owner, service gap, proof, and stop state are reviewable. One channel is enough. Do not open LinkedIn, email, and a public reply in parallel because the launch feels time-sensitive.

Step 6. Write one narrow, evidence-led agency question

The message should do one job: ask whether the evidenced launch work is current and correctly owned, then offer one small relevant artifact. Do not diagnose the launch, imply failure, list every agency service, manufacture urgency, or use congratulations as a wrapper for a generic meeting ask.

Weak message	Why it fails	More defensible version
“Congrats on the launch. You must need help scaling demand. We are a full-service growth agency. Open to a call?”	Invents a gap, claims timing, offers no relevant proof, and makes the launch decorate a generic pitch	“Your release notes show the partner tier is in phased availability, while the launch page sends partners and direct buyers through the same proof path. Is partner enablement still owned in-house? I can share the one-page handoff review we use if it would help.”
“Saw your new product. We can handle branding, web, content, paid, lifecycle, and sales enablement.”	Turns one event into a vendor shopping list and ignores current owners	“The launch page now separates security teams from developers, but both routes land on the same implementation guide. Is that guide intentionally shared? I have a short audience-to-proof checklist if useful.”
“Your launch could perform better. We helped a client grow 300%.”	Diagnoses performance without data and offers an unattributed, non-transferable result	“The public beta brief names activation as the current learning goal. If lifecycle ownership is still being decided, I can send the beta-feedback routing template we use before channel work begins.”

Before approval, a reviewer should answer all of these:

Is the source original, current, and accurately represented?
Is the release state explicit rather than inferred from “launch”?
Does one visible job connect the release to the agency capability?
Is the recipient the current owner or a valid relationship route?
Did we check in-house, incumbent-agency, partner, and procurement ownership?
Is the service gap a question rather than a diagnosis?
Does the proof match the product, market, job, and stage?
Are capacity, conflicts, exclusions, and confidentiality clear?
Does the message change beyond the congratulatory opener?
Is one small artifact or question more useful than a meeting request?
Is one channel appropriate under the relationship and policy state?
Can the recipient correct the owner, gap, and timing without friction?
Are expiry, opt-out, complaint, bounce, and suppression rules attached?

Step 7. Let the reply and current launch state control follow-up

The latest state overrides the original alert. A reply can identify the real owner, confirm incumbent coverage, narrow the job, invite an artifact, defer timing, or close the premise. Silence does not strengthen the launch signal.

Latest state	Workflow action
The recipient corrects the owner	Update the record and ask before any handoff; do not forward the original pitch automatically
An incumbent agency or internal team owns the work	Close the gap or clarify a separate invited scope; do not undermine the current supplier
The person asks for the artifact or names a current job	Send exactly what was invited and let their response define the next step
The launch is delayed, changed, withdrawn, or completed	Retire the old reason and rebuild only from genuinely new evidence
The account requests a future date	Record the agreed date and recheck state, owner, supplier, fit, and capacity then
No response	Do not restate the launch, add channels, or contact several teammates; close or wait for new decision evidence
Opt-out, complaint, bounce, conflict, poor fit, contradiction, or suppression	Stop and preserve the state across future launch alerts

Use the free Campaign Follow-up Planner to turn the latest reply and still-valid reason into a dated continue, hold, reroute, or stop decision.

Three product-launch agency outreach routes

Announcement only, no current launch job

A fitted company announces a new product, but access, execution, ownership, supplier coverage, and outside-help need remain unknown. Verify or watch. Do not send a congratulations pitch.

Existing relationship, one current uncovered handoff

An existing account contact confirms that a phased release created a partner-enablement handoff not covered by the current agency or internal team. The agency has relevant proof, capacity, and no conflict. Let the account owner offer one scoped review and let the client choose whether to expand the conversation.

Named incumbent and completed launch work

The company credits an incumbent agency for the launch, the public brief is complete, and no separate current job is visible. Record the supplier context and close the route. Do not pitch a replacement from a launch alert.

How Funkel AI fits this workflow

When verified public launch context is supplied to a reviewed workflow, Funkel AI can keep the source, release state, buyer-profile fit, current job, owner, supplier context, service-gap question, message reason, route, approval, and stop conditions together. It does not independently verify every launch, reveal private briefs, measure launch performance, diagnose service gaps, identify every incumbent, check legal conflicts, prove budget, supply a lawful basis, create permission for contact, or make every product launch agency buyer intent. See how Funkel AI keeps evidence and human review attached to outreach.

Agencies evaluating whether they should own the outbound system itself can also review the agency-to-in-house outbound comparison playbook. It addresses operating-model ownership; it does not change the qualification rules for this launch route.