Agency response to your outbound brief.
This answers the open questions in the brief so you can sign off and we ramp. Each item is structured the same way: our recommendation, why, and what we need from you to lock it. Anything that needs your real numbers or a business call is marked Lars decides.
01
The headline.
The brief is strong enough to launch on. The only things blocking a start are decisions, not strategy.
Recommendations below are ours; final calls tagged Lars decides are yours. Silence on a decision defaults to our recommendation, so a start is safe either way.
02
v5.0 update.
The brief advanced from v3.1 to v5.0, but the open decisions below are still deliberately unresolved. Section 16 of the brief states Lars wants to “work it through with the agency rather than hand down an answer,” so every recommendation here still stands.
One thing hardened in v5.0. Pricing is now a firm rule: no pricing, ever, in any public or outbound channel. No list prices, no ranges, no per-study cost, no cost-per-respondent. The $15/study figure has been removed from the brief. The pricing item in Part 2 is rewritten to match.
03
The play we’re recommending.
Get Qlaris in front of product leaders the week they’re about to build the wrong thing.
Qlaris wins when a product team feels the “we shipped the wrong thing” pain and learns there is a way to get real signal in minutes instead of a six-week research queue. Outbound’s job is to put that realization in front of them at the exact moment they are committing engineering to an unvalidated bet.
01 SIGNAL
A behavioral moment
A public post, a discovery event, a launch. Plus firmographic layers: raises, hires.
02 SOURCE
Where the signal fires
Social listening, Luma and Product Hunt, product communities, funding and hiring data.
03 QUALIFY
Right ICP, real need?
Filter: right title, right stage, real validation moment. If not, drop it.
04 MESSAGE
Situation first, product second
One short note referencing the prospect’s situation. Qlaris introduced only as the fix.
04
Personas we’re going for.
Series A to C B2B / B2C SaaS, roughly 30 to 500 people, ship-fast culture. Thin or no dedicated research function, so Qlaris fills the gap. Persona split 60 / 20 / 20 recommended for phase 1.
Persona 1 · 60%
Head of Product / VP Product / CPO
Owns roadmap risk and the “hit rate” pain. Feels every failed launch personally. Buyer decision authority. Has a landing page today (Persona 1 is proven-page, majority-volume).
Persona 2 · 20%
Product Managers
Validating before they spend engineering cycles. Lands here, expand up. Sub-page needs the intake-queue framing (reuse existing modules). Phase-2 ramp.
Persona 3 · 20%
UX research & innovation leads
First-time research hires building the function and choosing tools. Founders / 0-to-1 teams for a faster, self-serve motion. Sub-page needs gated-pipeline framing.
Out of scope
Where we don’t fish
Heavily-regulated enterprises that demand real-human panels, and pre-product idea-stage founders with no budget. We stay in the mid-market product-team lane where speed wins.
05
Signals we watch.
Most outbound hits the right title at a random time. We watch public data for the moment a specific company is about to make an unvalidated product bet, then reach out while the decision is open.
| Category | Signal | Why it fires now |
| Behavioral | A PM publicly wrestling with a build decision on LinkedIn or Twitter | Live indecision is the sharpest possible buying moment |
| Behavioral | Product leader hosting a discovery meetup or workshop | Positions them as receptive to structured discovery methods |
| Behavioral | A maker who just shipped, seeking early feedback | Post-launch validation gap is textbook Qlaris territory |
| Trigger window | Fresh funding round (Series A to C) | Budget and mandate to build. Roadmap gets ambitious in the first 90 days |
| Trigger window | New head of product / CPO hire in first 90 days | New leader wants a fast win. Discovery methodology is where new leaders differentiate |
| Trigger window | Product launch or major feature ship | Iteration cycle now depends on feedback speed. Old research queue no longer works |
| Evergreen | Right ICP, always-on | Fills the pipeline between signal spikes. Runs underneath the signal-led tracks |
The credibility wound in the category is “synthetic users are shallow.” We do not argue it. We use it. Qlaris is the discovery co-pilot for the first 80 percent: kill bad concepts and sharpen the question cheaply, before you commit real humans and real engineering.
06
How we run it.
Two channels running in parallel, each with a distinct job.
Founder-led
Channel 1
Targeted founder outreach
Direct sequences to product leaders and PMs in the ICP. Best for senior buyers and warm, credible first touches.
- 200 quality contacts per week
- Tight ICP targeting: signal fresh in the last 14 days
- Founder review on every send
- “Send me one product question” soft ask in T1
Channel 2
The volume engine
Dedicated mailboxes and domains, warmed and monitored. Carries the signal-led and evergreen tracks with data, personalization, and multiple angles tested.
- Separate sending infrastructure, protects primary domain
- UK / NL / Nordics email-led; DACH LinkedIn-led per compliance (see Part 3)
- Continuous A/B on angles
- Deliverability monitored weekly
07
Event shortlist.
A starting shortlist of events where product and research leaders gather. For each, we source the right attendees and run timed outreach before, during, and after.
| Event | When | Where | Who’s there |
| Priority · Europe (closest to home, highest fit) |
| Future Product Days | Sep 22–24, 2026 | Copenhagen | Product + UX + AI leaders |
| Product-Led Summit Berlin | Oct 21, 2026 | Berlin | Product leaders + PMs |
| Product-Led Summit London | Dec 2–3, 2026 | London | Product + growth leaders |
| ProductCon London | Feb 23, 2027 | London | Senior product leaders |
| Product-Led Summit Amsterdam | May 28–29, 2027 | Amsterdam | Product + growth leaders |
| #mtpcon London (Mind the Product) | June 2027 | London | 1,000+ PMs and product leaders |
| Near-term · Online / US |
| ProductCon: AI Builder Week | Aug 3–7, 2026 | Online | 15,000+ PMs. Biggest near-term online play |
| Lenny & Friends | Rolling | US | Senior product leaders |
| ProductCon SF | Rolling | San Francisco | Product leaders |
| Mind the Product Chicago | Rolling | Chicago | Product community |
| Product Hunt (monthly) | Continuous | Online | Makers + early adopters |
08
Part 1 · The conversion path.
Six kickoff questions from the brief. Our recommendation, why, and what we need from you to lock it.
Q1
Free signup vs booked meeting: which converts, and at what deal size does it flip?
Recommendation
Meeting-first now. Defer free-signup.
Your own data settles it. Every revenue win came through a founder meeting, the free account under-delivers without MCP, and the CTAs currently land on a demo form, not real signup. So there is no proven signup-to-revenue path to run yet. Run Option A (meeting) as the revenue path and Option B (question-first) as the soft top-of-funnel. Hold Option C until the post-signup MCP onboarding ships (see Q5).
On the flip point: self-serve signup only out-converts sales-led once two things are true at the same time: (1) a cold, unassisted user reaches a real “wow” without a human, and (2) the deal is small enough that a founder meeting is not worth the ACV. As a heuristic, self-serve wins below roughly a mid-four-figure ACV and sales-led wins above it, but that line moves entirely on your actual numbers.
Needs from you Lars decides
Your current average deal size / ACV and whether a low-price self-serve tier is even planned. Without that we cannot place the flip line, and neither should you.
Q2
Does “send us one product question” work cold, or read as too good to be true?
Recommendation
Yes, it works, if it is specific, hedged, and gated so it does not drown you in founder time.
“Show, do not tell” is the strongest asset a product like this has, and it removes all buyer risk. Two failure modes to design around:
Too-good-to-be-true: a stranger promising free work reads as a scam unless credibility lands first. Fix with specificity and a limitation in the same breath. Example ask: “Send me one product question. I will run it through our synthetic population and send the output in 48 hours, including where our confidence is low.” The hedge is what makes it believable, and it matches your “honest by design” tone.
Founder-time sink: it does not scale past a certain volume. Fix by keeping volume deliberately low (your own “200 good emails a week”), templating the intake, and having the founder review and send the output rather than run each from scratch.
Where it goes in the sequence: own touch 1 as the soft ask, and do not repeat it while the meeting ask is live (see Q4).
Q3
If meeting-first: direct calendar, qualifying step, or form?
Recommendation
Direct calendar link to the founder, with one or two optional context fields. No qualifying form, no agency call.
The brief already says no agency-side qualification in phase one and volume is intentionally low with tight ICP targeting. At that volume the list is the qualifier. A multi-field form or a qualifying step only adds drop-off. Capture at most “company” and “your one product question” so Lars walks in prepared, and make both optional so they never block the booking.
Q4
How to sequence the soft ask and the meeting ask across five touches without cannibalizing?
Recommendation
One ask per touch. The soft ask owns the open, the meeting ask owns the middle, the breakup owns the close.
| Touch | Channel | Job | The one ask |
| T1 | Email | Hook (ship rate vs hit rate) + prove you are real | Soft: send me one product question |
| T2 | LinkedIn connect | Credibility, trigger reference, founders’ background | None |
| T3 | Email | Proof / pricing case (from touch 3 per claim rules) | Meeting (primary) |
| T4 | Email | Objection pre-empt (published limitations) | Meeting (restated) |
| T5 | Email | One-line breakup, door open | Soft fallback only |
The rule that prevents cannibalization: the two asks never appear in the same message. The soft ask captures the not-ready-to-meet in T1 and returns only as a low-pressure fallback in T5. The meeting ask has T3 and T4 to itself. Each email asks for exactly one thing.
Q5
What product UX is needed before we send cold traffic to free signup (Option C)?
Recommendation
Do not point cold traffic at signup until an unassisted user can go signup to first defensible answer in under ten minutes, and that activation rate is measured on warm traffic first.
Concretely, the gating build is:
- One-line MCP install that works first try.
- A guided first query that returns a real synthetic result within minutes (the activation moment).
- A free tier that delivers genuine standalone value (today it “under-delivers without MCP”).
- The confidence signal (freshness / consistency / coverage) visible in-product, so “honest by design” is felt, not just claimed.
- A stall fallback: if the user does not activate, offer the founder meeting.
Set a bar before opening cold traffic: measure signup-to-first-successful-query on warm/known traffic and clear something like 40 percent activation before spending cold volume on it. Sending cold traffic to an unfinished signup burns leads you cannot re-approach.
Q6
How to instrument, within six weeks, which path works?
Recommendation
Tag by ask, measure per persona, and decide on meetings-held per 100 contacts, not on reply rate.
- Tag every positive reply by which ask it answered (question vs meeting).
- Track the full funnel per path: contacts to positive reply to question-sent or meeting-booked to meeting-held to opportunity to revenue. Never blend personas.
- Run a clean CTA split inside one persona list: half get question-first T1, half get meeting-first T1, everything else held constant. That isolates which opener drives more downstream meetings.
- Decision gate: the brief’s “review after first 500 per persona” is the right sample. Pick the opener with the higher meetings-held per 100 contacts. Reply rate will flatter question-first, which is exactly the trap, so it is not the deciding metric.
- Instrument deliverability separately (domain health, complaint rate, bounce, weekly) so no path is misjudged on a deliverability artifact.
Net conversion-path recommendation: run A + B now (question-first as the soft T1 ask, founder meeting as the primary ask via direct calendar), instrument both, and hold C until Q5’s bar is met.
09
Part 2 · Items to close before ramp.
Two persona landing pages missing.
Recommendation
Do not block launch. Launch Persona 1 first (it has a page and is 60 percent of volume), then bring up minimal researcher and innovation sub-pages before ramping P2 and P3.
Reuse existing modules: intake-queue framing for researchers, gated-pipeline framing for innovation. This de-risks the start (P1 is proven-page, majority-volume) and buys time to stand up the two sub-pages without holding the whole engine.
Nameable references.
Recommendation
Get a written yes or no per logo, per market, before any name appears in outbound. Default to the anonymized framing until then.
At least one or two nameable marquee logos in the marketplace vertical would materially lift credibility with Tier 1 targets. This is high-value and low-effort on your side.
Needs from you Lars decides
The per-logo, in-writing list.
No pricing anywhere · updated for v5.0.
Recommendation
v5.0 made this a hard rule and we align fully. Section 6: no pricing, ever, in any public or outbound channel. The $15/study figure has been removed from the brief. This is now decided, so it is no longer an open item for us. What it changes on our side:
- We will be asked on first reply, and we deflect with zero numbers, every time. Price-free script: “We keep pricing to the conversation with Lars, since it depends on the blend of synthetic and real and the volume. He will walk you through it in about twenty minutes.” No ranges, no “a fraction of”, no “five figures”, nothing a prospect could screenshot as a price.
- On a budget objection we reframe on outcome, not cost: the decision this de-risks, and the cost of shipping the wrong thing, never a dollar comparison.
- Pricing lives only in the founder meeting. That also reinforces the meeting-first path in Q1: the meeting is where value and price are set, so the whole motion should drive to it.
Needs from you Lars decides
Only confirm who states price in the founder meeting. Nothing about pricing reaches outbound.
10
Part 3 · Compliance shapes the motion.
DACH is a priority ICP geography and also your home market, where unsolicited commercial email is legally constrained (UWG) and complaints are costly. This is not a footnote, it changes channel weighting.
DACH
LinkedIn-first
Soft question-ask carried over LinkedIn. Email used conservatively, if at all, on documented legitimate interest.
UK, NL, Nordics
Email-workable
Corporate B2B email with clear sender ID, one-click opt-out, and a documented legitimate-interest assessment. Concentrate email volume here.
Everywhere
Baseline hygiene
Sender identification, physical address, immediate suppression on negative reply, data source recorded per contact. Lawful basis confirmed in writing before first send.
Practical consequence: the email-heavy 5-touch runs cleanest in UK/NL/Nordics, and DACH runs as a LinkedIn-led variant of the same sequence. We will build it that way unless you direct otherwise.
11
Part 4 · Open items we need you to confirm to start.
A short checklist. Our recommended default is in brackets so silence still gives us a safe starting point, but these are yours to set.
-
Conversion path. Our rec: A + B now, C later
Confirm or override.
-
Pricing: decided in v5.0 (no pricing anywhere in outbound; $15/study removed). We align. Lars confirms
Only open piece: who states price in the founder meeting.
-
Nameable logos: per-logo, per-market, in writing. Lars decides
Need your list.
-
Four-week embedded pilot: cold-outbound offer or later-stage? Our rec: later-stage, introduced post-meeting Lars decides
It is too heavy to lead with cold.
-
B2B audiences in scope? ICP says B2C, product handles B2B panels. Our rec: keep phase 1 B2C-only for message focus Lars decides
Treat B2B as a phase-2 expansion once B2C proof is in.
-
Phase-1 volume, geography split, budget. Our rec: 200 quality contacts/week, weight email to UK/NL/Nordics, DACH via LinkedIn, 60/20/20 persona split Lars decides
-
Reply handling when you are unavailable. Our rec: named backup with an SLA who covers scheduling only Lars decides
Every positive reply still routed to you same day.
12
The roadmap.
Three phases across the first 90 days once the open items in Part 4 are locked.
PHASE 1
Build the system
Stand up sending infrastructure, finalize the ICP, wire the public signal sources (starting with funding + leadership-change), build the first target lists, load the first message angles.
PHASE 2
Run the sharpest signals first
Open LinkedIn + email on the highest-intent signals (fresh raise, new product-leader hire), with the evergreen layer underneath. Measure reply and meeting lift per signal type.
PHASE 3
Double down on what converts
Scale the winning signals and segments. Refine the angle on real reply data. Feed proven copy back into the evergreen track.
13
What happens once these are locked.
STEP 1
Three lists, one per persona
Enrich to your fields, apply suppression, map every target to its most recent trigger event with a date.
STEP 2
Stand up the sequences
Email-led in UK/NL/Nordics, LinkedIn-led in DACH, one ask per touch, claims gated to your approved list.
STEP 3
Same-day reply routing
Every positive reply routed to you same day. Weekly review for six weeks.
STEP 4
A+B vs C decision gate
After first 500 per persona, pick the opener with the higher meetings-held per 100 contacts.
With pricing now settled in v5.0, the single biggest unlock on your side is Part 4 items 3 and 6: the nameable-logo list and the phase-1 volume, geography split, and budget. Give us those and we can start the list build immediately.