The three rings you kept, in your order: market access at the center, then patient access, then managed markets and payer. Reimbursement and pricing sit on the committee, not at the entry point, exactly as you ruled it. This split is the 4,868 pool before your client companies come out; the gated pool is 4,548, and the split is re-cut in the verification pass.

The weight sits exactly where you said the buying really happens: directors and below. Your words from the second call: the directors, and below, are a better target than directors and above.

• Location resolution. Roughly 4,200 people carry unresolved location data and are being worked through against the therapy-in-market rule, the gate you set.
• Employer re-keys. The 43 corrections from the live employer check are being applied across the estate.
• Twelve zero-return entries. Internal merge artifacts, mostly duplicate names, flagged for cleanup rather than real gaps.

"Can we simultaneously test multiple segments/ value prop messages?"

Yes, and that is how we would run it from week one. Each hypothesis, a segment, a trigger, an angle, goes out as its own lane with its own message set, never blended into one number. Small cells first, one variable changed at a time, never copy, audience, cadence and senders all moving together. We read each lane at a size agreed in advance, then shift the sends toward whichever one is moving people from conversation to Needs Analysis and Proposal, not whichever gets the most opens.

In practice that could mean a brand-pressure lane, a new-leadership lane and a posted-roles lane running the same week, each written for that trigger, not one generic message stretched across all three.

"How will we iterate/ improve efficiency over time?"

Every lane carries its own stop rules and scale rules, agreed before it goes live. A raw reply count never changes a message or an offer by itself, we read it as qualified demand against your own stage names, not against ours. When a lane needs a rewrite, the order runs the offer first, then the list and segment, then the angle, then copy structure, with the subject line last, because that is the lever least likely to move a real outcome.

Anyone who does not reply gets a cooling window before a second touch, and a new angle when they are touched again. What works in one lane becomes the starting point for the next, so the system gets sharper through the build rather than staying static.

"What is the strategy to increase the probability leads are sales ready?"

We do not try to manufacture pain, we go where it is already live. That is the same read you gave us in your own deck: pain has to exist before a prospect is sales ready, and it cannot be created in a discovery call. So the map runs your own read on roles against the trigger events you named yourself: a launch ahead of its PDUFA date, an acquisition, a new competitor in a therapy, financial pressure, new access leadership, or a market access role freshly posted.

The one you called your key motivator, a service gap with an existing vendor, is not observable from outside. Nobody can see it, us included. We work it from two lists you already hold, your own client list and the competitor client list. Every person is researched and tied to their brand and therapy before anyone is contacted, and a reply does not reach your calendar until the reply desk has qualified it against that lane's criteria.

"How are outbound targets messages reviewed/ approved? What is the mix of LI and email messages and how are they staged?"

Every message set is drafted by us and approved by you before it ever goes live, and any change after that is one variable, declared, never silent. The mix leans LinkedIn first: a connection and a message written for one named person, with email as a second door to that same person once its own sending setup has cleared its warm-up, which is why the opening weeks run LinkedIn-led.

Staging follows the same order every time. Your Tier 1 goes first, then the entry pool by your rule, with the trigger lanes layered on top, and the exclusion list is applied before anything is staged and checked again after every push. Nothing goes out as a broadcast.

Updated Tuesday evening, on your point about profiles. The LinkedIn lane runs from your own team's real profiles, yours first, plus whichever colleagues would naturally be talking to market access people anyway. No rented or proxy profiles anywhere in this engagement. Each profile is its own seat, paced inside LinkedIn's limits, with every message set approved by you before it goes out and every conversation visible to you as it happens. Your profile alone works and is where we start; each colleague who joins adds the same reach again.

"How are leads received and managed?"

A positive reply lands with our reply desk inside an agreed response time, gets qualified against the lane it came from, then reaches you warm, with the thread, the person and the context attached. It is logged in Zoho under its own lead source, so it never blurs with Trade Show, Alumni Network or your other sources, and the stage is set to your own stage name from day one.

The sequence for that person stops the moment they reply. A meeting goes straight into your calendar with real times offered, never a scheduling link doing the work for us. From January, your AE inherits the desk with everything already documented, walking into a live pipeline rather than a cold start.

"What performance reporting is planned? How often do we connect?"

A written report every week, lane by lane, against your own stage names, Qualification, Needs Analysis, Proposal/Price Quote, Closed Won, Closed Lost, each with its denominator named, what changed, and what changes next. Nothing gets reported as a rate on its own, a number without what it is a rate of is not a number we would send you.

On top of the written report, a working call at whatever rhythm suits you, we would suggest weekly through the build, with a fuller review against the plan at the end of each month.

"What risks do we need to prepare for and how will we mitigate/ address as needed?"

Six, and we would rather name them now than let you find them later. Sending reputation on a fresh setup, which is why email opens only after its own warm-up and ramps rather than going full volume on day one. Message-market fit in the opening weeks, which is exactly what the lanes, the small cells and the stop rules are built to catch early. Qualification capacity on your side before the AE is in seat, which is why the reply desk sits with us through the build, and why a warm backlog running into February is something your AE inherits, not a cost they absorb.

Suppression accuracy, which is why nothing is staged until your list is applied, and checked again after every single push. Attribution, agreed in writing before go-live, so a conversation the unit sources is credited the same way every time against your existing sources. And compliance: LinkedIn's own limits respected on every seat, and opt-outs honored the same day.

"The rented LI profile idea will be an issue for us for sure. Use of my profile is fine."

Off the table, altogether. The LinkedIn lane runs from your own team's real profiles: yours first, plus whichever colleagues would naturally be talking to market access people anyway. Two clients run exactly this way today, and Dan has sent you both contacts by email. Each profile is its own seat. You approve every message set before anything goes out, you can see every conversation as it happens, you can step in and reply yourself at any point, and the pacing stays inside LinkedIn's limits, about 40 connection requests a day per profile, the way a person would.

The options are simpler than they were. Your profile on its own works and is where we would start; it caps reach at one person's daily limit. Every colleague who joins adds the same again, and the reply desk works the replies so nobody on your side is handling inbound they did not ask for. Who joins is agreed on the proposal call.

"Current email best practices with domains to not impact the accesssync.com domain in any way."

Nothing we run touches accesssync.com. No sending from it, no warm-up on it, no sequencer anywhere near it, no DNS changes to it. Cold email goes out from separate domains bought for the job, each with its own mailboxes and its own SPF, DKIM and DMARC, warmed for two weeks before the first prospect email and stepped up over the following weeks, with bounce and complaint stop rules agreed in writing before go-live and enforced by our own checks.

The change this year: a public cold-domain blocklist launched this month treats lookalike domains as a family, and the big mailbox providers consume that list, so one bad sibling drags the others and your main domain will not sit anywhere near that. The sending domains for you carry no AccessSync name at all. The options and the trade-offs, branded lookalikes against neutral names and what each means for replies and for risk, go into the proposal in writing. The volume on your side is low by design, small signal-led lists rather than thousands a week. One separate note: your own DMARC policy currently sits at "none", which is worth tightening whatever happens with us. Happy to point whoever looks after your DNS at the steps.

"We can supplement our outreach plan with private audiences and paid media targeting."

Yes, and the useful version is a narrow one. A matched audience built from the map itself, the same named people the lanes are working, so the paid layer and the outreach hit the same names in the same two weeks rather than a broad spend. Anyone who engages with it is pulled forward in their lane. It goes into the proposal as an option you can switch on or leave.

"We are working on an organic content plan that should have us building new thought leadership content each week."

Useful in two ways. The profiles doing the outreach need to look alive, so a piece a week on them means the people being reached see someone with a point of view when they click through. And the engagement on those posts becomes a signal in its own right: anyone from a target company who likes or comments is picked up and worked into the right lane. If some of the content can be tied to the trigger lanes, a piece on launch readiness for the launch lane, say, the message can point to it.

The questions you raised, and how each was taken

• Tate: how the messages avoid reading as automated outreach, and keep your brand. Taken live: a real reason to write to each person, the sender's own voice, and hard rules that strip out the patterns people spot.
• Tate: your buyers' budget year, and how it shapes when each lane goes out. Taken live: the outreach is timed so each group is reached in its own buying window across the year, with launches on their own clock, as you put it.
• Tate: whether messages flex by company size, role and franchise. Taken live: further than templates. Each message picks the pain point and the client example most relevant to that person, and an interested reply gets something built for them.
• Brent: how far in the break clause sits, and what evidence there is by then. Taken live: a two-month review, with the build front-loaded ahead of it, and a client you can call on how fast it moves.
• Brent: whether October to December is the right time to start, given your buyers' year. Taken live: the quiet quarter is where the testing and the network building happen, so January opens at full speed.
• Brent: what gets paid when, set against your budget year. Taken live by Dan: the split on page 4 of the written proposal, which can be fit to your budget year.

Delivered, and still to come

• Delivered: the running-cost breakdown Dan offered, line by line, for after handover, on Your decision, with what you hold by the two-month review.
• From Dan, on request: an introduction to a client on any part of the work you want to hear about, beyond the two named in the written proposal.
• Whenever they come: any further questions from Tate, through Ed, or from Brent.

The running order, as Ed set it this morning

• 1. The agenda. A one-minute overview, then Tate and Brent adjust it in any way they want.
• 2. Introductions. Dan, Matt and Paul: past and current expertise, and the fit to your need and use case.
• 3. The floor is yours. What you hope to learn, your concerns, and what you hope to achieve by the end of the call, written down and answered in your order.
• 4. What we have learned about your business. Segmentation by pain from your file, the trigger events, the named roles, funnel conversion and time to close, leads from events next to leads from digital, and why we are enthusiastic about the impact we can make.
• 5. How it works, and the risks. The four months, the tools by what they do, how your team interacts with the leads, the risks and the steps that minimize them (quality of messaging, brand integrity, approval, timing, response to requests), an example of the page a prospect sees from the first LinkedIn outreach, why us rather than another firm or in-house, testing, iteration and a weekly meeting.
• 6. Outcomes, and the evidence. The expected outcomes next to your event marketing results, why this is better, and the evidence from other clients, as the proposal states it.
• 7. Cost, connected to the outcomes. Page 4 as written; the outcomes connected to the cost and the return in your numbers, ways to mitigate the investment risk on your side, future technology cost, more tied to results, payment terms with your cash freeing up in late February in mind: Dan answers live.
• Before we hang up. The decision path on your side, the start (kickoff the week of September 29, live October 1), who owns what next, and a time for the agreement walk-through.

The same agenda, with a link on every part to where the answer lives, is at the top of the Overview.

When you share it

Send your own working, how many leads you need, how many turn to MQLs, SQLs and customers, over what period, and the payback you need to see, and it goes onto the written proposal beside our three cases, so the two sets of numbers sit on one page for Brent and Tate. The comparison you asked for, event-equivalent leads against the show, goes there too.

Three lines priced on the tool list before you sign

• Automation and the CRM link around your Zoho. Built around the Zoho you already hold. Any connector tool it needs goes on the tool list with its price.
• AI usage. Usage-based, tokens included. Priced on the tool list at your expected volume.
• Reporting. Your weekly report and dashboards. Hosting, if any, goes on the tool list with its price.

The work is front-loaded

Dan, on the call: “you should be coming away from that in a worst case situation, with a ton of data, a ton of actionable stuff, a ton of infrastructure that we've already built.”

Brent's point is fair: October to December is a hard quarter to start conversations with your buyers. Dan's answer on the call was that it is the right quarter to build and test. Testing small lanes at small scale takes time, and it makes more sense in a quiet quarter than in your prime time, so the unit is tuned and running when your buyers' budgets open. In his words: “You want to be able to go fully out when it's open.”

Three things in the plan already fit the quarter. A connection request does not have to pitch, so Ed's accepted network grows from November and is there to work from January. A launch lane fires on its PDUFA date whatever the quarter. And the first weeks are build weeks either way, with the map, the lists and the warm-up done before the email door opens.

Beyond the two clients already named in the written proposal: tell Dan which part of the work you want to hear about, and he'll put you in touch with a client who runs it.