Codarity · copy review

LifeSci Events

148 lines · compounding · Attraction leads · life sciences · 24 written by claude-opus-5, cached

model wording onwrite it againno answersreferrals · not invited · nobody holds itreferrals · lost to familiarity · dedicated personfound by strangers · lost on price · external help
01

Cover

The first two sentences. If these do not land, nothing else is read.

  1. coverTitle

    Market briefing for LifeSci Events

  2. coverStanding

    Prepared for Sara Parigian. This is research about your market and where your firm sits in it, ending in a path. It is not a proposal.

02

Your answers

Reflects their four answers back before anything is asserted. Absent when they have not answered.

  1. answersIntro

    You answered four questions. They are here first because everything after this reads differently depending on them.

03

How your buyers decide

The 221-day claim, before it is applied to them.

  1. buyingBehaviourIntro

    Before anything specific to your firm, one thing about how your buyers behave, because it explains most of what follows.

  2. buyingBehaviourClose

    5 in every 100 of your buyers are actively looking right now. 12 are forming a view without talking to anyone. 83 are not looking at all and will be at some point. Almost all marketing in this market is built for the first group. The work that compounds is built for the second.

04

Who is actually in the room

Five seats. The section the ideas all point back at.

  1. committee.emphasisNote

    Investor days and congress presence are corporate-communications territory here, so the sponsor seat is usually the one that matters and compliance sits behind every decision.

  2. committee.leadSeatweighted for this market

    The one whose neck is out

  3. committee.sponsor.optimisingForThe one whose neck is out

    a result they can point at in a board meeting. The event is a means to something they have already promised upwards.

  4. committee.sponsor.afraidOfThe one whose neck is out

    spending a large number and having nothing defensible to show for it. Not failure exactly, ambiguity.

  5. committee.sponsor.questionThe one whose neck is out

    If I am asked in six months whether this was worth it, what do I say?

  6. committee.sponsor.reassuredByThe one whose neck is out

    a supplier who talks about outcomes and measurement before they talk about production values.

  7. committee.owner.optimisingForThe one who has to run it

    a delivery that does not consume them. They have done this before and they know exactly which parts go wrong.

  8. committee.owner.afraidOfThe one who has to run it

    a supplier who is impressive in the pitch and unreachable in week six. They have been burned and they remember it.

  9. committee.owner.questionThe one who has to run it

    When something goes wrong at 6pm the night before, who actually answers the phone?

  10. committee.owner.reassuredByThe one who has to run it

    specifics about process, escalation and named people, rather than a showreel.

  11. committee.brand.optimisingForThe one guarding how it looks

    something that feels like them and lands with their audience, not a generic event with their logo on it.

  12. committee.brand.afraidOfThe one guarding how it looks

    cheapness. A stand, a stage or a room that undercuts everything else they have spent the year building.

  13. committee.brand.questionThe one guarding how it looks

    Will this look like us, or like an event company's idea of us?

  14. committee.brand.reassuredByThe one guarding how it looks

    evidence the supplier understands their market and their audience, not just their sector.

  15. committee.finance.optimisingForThe one who signs it

    predictability. A number that does not move and a process that survives an audit.

  16. committee.finance.afraidOfThe one who signs it

    scope creep, and being the person who approved the thing that overran.

  17. committee.finance.questionThe one who signs it

    What is the number, what changes it, and what happens if we cut it by twenty per cent?

  18. committee.finance.reassuredByThe one who signs it

    commercial clarity offered early and unprompted, rather than extracted during negotiation.

  19. committee.internal_user.optimisingForThe one who has to live with it

    the event doing the job they need it to do: pipeline, a launch that lands, a team that comes back motivated.

  20. committee.internal_user.afraidOfThe one who has to live with it

    an event that is beautiful and useless. Lots of photographs, no conversations that went anywhere.

  21. committee.internal_user.questionThe one who has to live with it

    What do I get out of this on the Monday after?

  22. committee.internal_user.reassuredByThe one who has to live with it

    a supplier who asks what happens after the event before they ask about the venue.

05

The 221 days before they call you

The centrepiece. Commend, then finding, then what it costs them.

  1. presence.frame

    Everything after this hangs off one number. In B2B event services the gap between a buyer starting to look and a buyer making contact averages 221 days. Nearly eight months of deciding, almost all of it in private, and almost all of it before anybody picks up a phone.

  2. presence.commendmust run before the finding

    Start with what is already begun, because it is further than it feels. LifeSci Events has made a start on publishing a point of view where they already read. None of that is nothing. It is the difference between building on something and starting from scratch, and it is why the rest of this is a sequencing question rather than a standing start.

  3. presence.finding

    Now the part that is harder to see from inside. A buyer in this market spends 221 days researching before they make contact. Across the 10 places we can actually check, LifeSci Events is present at 0 of them and absent from 90 per cent. Every gap sits early: being findable when a buyer asks an AI assistant, being found on the questions they search months earlier, appearing somewhere that is not your own website and reaching the right accounts before they are looking.

  4. presence.consequence

    That is the whole of it. Not a pitching problem, not a pricing problem. For roughly 221 days a buyer is forming a shortlist you are not on, and by the time they enquire they have already chosen. The work you lose this way never appears as a loss, because you were never invited to bid for it. It looks like a quiet quarter.

  5. presence.notVisibleNoteidentical on every report, deliberately

    Two things on that list we have deliberately not scored, and they are the same two on every briefing we produce. Whether you are approaching named accounts directly, and whether you can see which of these actually produces work. Nothing outside your business reveals either, so guessing would be worse than useless. They are the first two questions worth asking on a call, and between them they usually explain more than the rest of the list.

  6. presence.bridge

    What closes that gap is not doing more of what you already do well. It is being demonstrably the firm that understands corporate event contracts better than anyone else, in the places your buyers are already looking, for the whole of those 221 days. That is what the rest of this is.

  7. presence.row.ai_searchnot yet · asks an AI assistant who the credible suppliers are

    no substantive content surface, so there is nothing for an assistant to cite

  8. presence.row.organic_searchnot yet · searches the problem, months before searching for a supplier

    no content surface at all, so no way to be found on a question

  9. presence.row.thought_leadershippartly · reads their feed and forms a view of who understands this work

    the founder is active but in bursts rather than on a rhythm

  10. presence.row.earned_coveragenot yet · sees the name somewhere that is not the supplier's own website

    the research found no press, awards or third-party features to point at

  11. presence.row.paid_socialnot yet · is not looking yet, and needs to have heard of you before they are

    no LinkedIn advertising

  12. presence.row.paid_searchnot yet · types a buying-intent search once the brief is real

    no paid search

  13. presence.row.retargetingnot yet · disappears for four months mid-cycle, then comes back

    no retargeting, so a buyer who leaves mid-cycle is gone

  14. presence.row.lead_magnetnot yet · wants the thinking without having to talk to a salesperson yet

    nothing to exchange for an email address, so interest arrives anonymous or not at all

  15. presence.row.nurturenot yet · is 221 days from enquiring and will forget you in 30

    no route to stay in contact between briefs

  16. presence.row.outboundcannot tell from outside · never comes looking, because they already have someone

    nothing outside your business can show this. It is the first thing worth asking about

  17. presence.row.published_proofnot yet · checks you can actually do the work, once you are on the list

    the delivery record is not readable by anyone who has not worked with you

  18. presence.row.measurementcannot tell from outside · (not a buyer touchpoint: whether you can see any of the above)

    nothing outside your business can show this. Over 221 days it is the difference between knowing and guessing

07

Your buyer market

Their market, sized. Suppressed for unmapped markets.

  1. buyerMarketIntro

    This is the size of the reachable buying side of your market at the seniority that signs off event work. It is not a list of prospects. It is the ceiling on how large the always-on layer can usefully get before targeting has to narrow.

08

What your competition is doing

Peer behaviour. Suppressed under 25 peers.

  1. peerBehaviourIntro

    This is what the firms you are up against are actually doing to get found, taken from our own research rather than a survey. Most of them are in the same position you are: strong on proof, absent from everything before it. Where a bar is short, that is room nobody is competing for.

  2. peerBehaviourLines[0]

    33 of 48 publish written proof of delivered work.

  3. peerBehaviourLines[1]

    25 of 48 keep a content surface running.

  4. peerBehaviourLines[2]

    6 of 48 have somewhere for interest to land.

  5. peerBehaviourLines[3]

    37 of 48 stay in contact between briefs.

  6. peerBehaviourLines[4]

    7 of 48 are buying attention.

  7. peerBehaviourLines[5]

    13 of 48 have a visible founder or leader.

09

What that means for you

The hinge. Where the whole argument turns.

  1. hingeOpening

    The research reads a firm operating at a level where buyers arrive already knowing roughly who you are. Two things in the research point the same way: enterprise-tier buyers and demand arriving with nowhere to land.

  2. hingeTensioncarries their Q2 answer when they have given one

    The tension is not demand. It is that interest which arrives before a buyer is ready has nowhere to go, so it leaves and comes back as somebody else’s client.

  3. hingeResolution

    The fastest change available to LifeSci Events is not a bigger effort across everything. It is somewhere for interest to land, because it is the one thing every other move depends on and the one thing currently absent. The majority of your traffic that is researching quietly becomes a known contact instead of an anonymous visit. Staying useful between briefs follows it directly, and the rest of the board is ordered behind those two.

10

The full board

The path, before it is broken into pillars.

  1. boardIntro

    This is the whole system, not a proposal. Four pillars, and within each one the two modules that would do the most for LifeSci Events given what the research found. Two are lit for the first quarter. One is marked as deliberately not yet. Everything grey is real work that is simply not the next work.

  2. notYetIntronot yet: Turning up where buyers already are

    One move in Attraction is held back on purpose. Proactive visibility works once there is something credible to land on. Published proof comes first.

  3. matrix.not_yet_reasonfrom the matrix, rendered as-is

    Proactive visibility works once there is something credible to land on. Published proof comes first.

  4. matrix.evidence[0]from the matrix

    enterprise-tier buyers

  5. matrix.evidence[1]from the matrix

    demand arriving with nowhere to land

11

Authority

Whether a buyer can satisfy themselves you are credible without speaking to you.

  1. pillarIntro.Authority

    Authority is whether a buyer can satisfy themselves that you are credible without speaking to you. It is the pillar everything else borrows from.

  2. PLAY_PROOF_ASSETS.labelquarter 1

    Published proof

  3. PLAY_PROOF_ASSETS.summary

    Turning work you have already delivered into evidence a buyer can read before they ever speak to you.

  4. moduleNarration.PLAY_PROOF_ASSETSwhy it is here

    On the board for LifeSci Events because the delivery record is strong and almost none of it is readable by someone who has not worked with you.

  5. PLAY_PROOF_ASSETS.effectwhat changes

    Buyers who are shortlisting quietly get something to shortlist you on. It also gives every other module something credible to point at.

  6. PLAY_PROOF_ASSETS.firstMovefirst move

    Pick three delivered events, one per buyer type, and write each up as a short account of the brief, the constraint and the outcome.

  7. PLAY_PROOF_ASSETS.signalyou will know because

    Enquiries start arriving that reference a specific piece of work rather than asking what you do.

  8. ideas.PLAY_PROOF_ASSETS.positionspositions you asmodel

    a specialist whose delivery record can be checked without a phone call

  9. ideas.PLAY_PROOF_ASSETS.0Article on your site · for the one who has to run itmodel

    An article on who answers the phone at six the evening before an investor day, naming the escalation path, the people on it, and what happens when the room falls over an hour before rehearsal

  10. ideas.PLAY_PROOF_ASSETS.1Article on your site · for the one who has to live with itmodel

    A piece on what a scientific advisory board should leave behind, the usable record of what was actually advised, and why so many end with photographs and nothing anyone can act on

  11. ideas.PLAY_PROOF_ASSETS.2PR angle · for the one guarding how it looksmodel

    A trade press angle on why an investor day that looks cheap reads to analysts as a company short of money, and what the room communicates before anyone speaks

  12. PLAY_SEARCH_AUTHORITY.labelquarter 2

    Being findable when buyers search

  13. PLAY_SEARCH_AUTHORITY.summary

    A small set of pages that answer the questions your buyers put into a search bar before they have a shortlist.

  14. moduleNarration.PLAY_SEARCH_AUTHORITYwhy it is here

    On the board for LifeSci Events because there is no content surface for a buyer to find you on before they have a shortlist.

  15. PLAY_SEARCH_AUTHORITY.effectwhat changes

    You become discoverable to people who are not yet in a buying process, which is when a shortlist is actually formed.

  16. PLAY_SEARCH_AUTHORITY.firstMovefirst move

    List the ten questions you get asked most in a first call. Each one is a page.

  17. PLAY_SEARCH_AUTHORITY.signalyou will know because

    Search starts to appear as a source on new enquiries.

  18. ideas.PLAY_SEARCH_AUTHORITY.positionspositions you asmodel

    the specialist found while a biotech is still working out what the meeting has to do

  19. ideas.PLAY_SEARCH_AUTHORITY.0Article on your site · for the one who has to run itmodel

    A short guide to briefing a partner for an investor day, including the questions you would want them to ask you and the answers that should give you pause

  20. ideas.PLAY_SEARCH_AUTHORITY.1Article on your site · for the one whose neck is outmodel

    The article that says plainly what a corporate event contract in life sciences covers, what sits outside it, and who carries the cost when the date moves

  21. ideas.PLAY_SEARCH_AUTHORITY.2Article on your site · for the one guarding how it looksmodel

    A line by line account of how an R&D day or KOL meeting is actually costed, so the number taken into a finance review survives the review

  22. ideas.PLAY_SEARCH_AUTHORITY.3Paid search theme · for the one who signs itmodel

    Once those pages are live, a paid search theme built on the cost and scope questions rather than the service name, landing on the costing article and not the home page

12

Attraction

Getting in front of people who are not yet looking.

  1. pillarIntro.Attraction

    Attraction is how interest reaches you and what happens to the interest that is not ready to become an enquiry.

  2. PLAY_LEAD_CAPTURE.labelfirst quarter

    Somewhere for interest to land

  3. PLAY_LEAD_CAPTURE.summary

    A path for the visitor who is interested but not ready to send an enquiry, so their interest is not lost.

  4. moduleNarration.PLAY_LEAD_CAPTUREwhy it is here

    This is the first move, because interest that is not ready to become an enquiry currently has nowhere to go. The research is unambiguous on it: demand arriving with nowhere to land. Everything in the quarters after this one assumes it is in place.

  5. PLAY_LEAD_CAPTURE.effectwhat changes

    The majority of your traffic that is researching quietly becomes a known contact instead of an anonymous visit.

  6. PLAY_LEAD_CAPTURE.firstMovefirst move

    One thing worth an email address, built from the proof you already hold, behind a form that asks for very little.

  7. PLAY_LEAD_CAPTURE.signalyou will know because

    A list that grows every month without paid support.

  8. ideas.PLAY_LEAD_CAPTURE.positionspositions you asmodel

    the firm life sciences teams quietly borrow planning material from long before they are ready to talk

  9. ideas.PLAY_LEAD_CAPTURE.0Lead magnet · for the one whose neck is outmodel

    A one page template for writing down, before anything is booked, what an investor day has to prove and how you will know afterwards that it did

  10. ideas.PLAY_LEAD_CAPTURE.1Lead magnet · for the one who signs itmodel

    A budget structure for a KOL meeting or advisory board that separates fixed costs, per attendee costs and the items that normally cause an overrun, built to be pasted into an internal approval

  11. ideas.PLAY_LEAD_CAPTURE.2Lead magnet · for the one who has to live with itmodel

    A follow up checklist for the person left holding the attendee list, covering what has to be captured in the room and what has to be ready in the days straight after

  12. PLAY_ABM.labelquarter 4

    Named-account targeting

  13. PLAY_ABM.summary

    Working a defined list of accounts you want, one by one, rather than waiting.

  14. moduleNarration.PLAY_ABMwhy it is here

    On the board for LifeSci Events because the accounts worth naming are identifiable, and approaching them needs the always-on layer working first.

  15. PLAY_ABM.effectwhat changes

    The highest-value route and the most demanding, because it needs everything else working.

  16. PLAY_ABM.firstMovefirst move

    Fifty named accounts, researched properly, approached individually.

  17. PLAY_ABM.signalyou will know because

    Conversations opening inside accounts you chose rather than accounts that found you.

  18. ideas.PLAY_ABM.positionspositions you as

    the firm that approached them about their situation rather than broadcasting at them

  19. ideas.PLAY_ABM.0Outreach angle · for the one who has to run it

    Open on the problem the one who has to run it has, not on what you do

  20. ideas.PLAY_ABM.1Outreach angle · for the one whose neck is out

    A reason to make contact that would be worth reading if you sold nothing

  21. ideas.PLAY_ABM.2Outreach angle · for the one guarding how it looks

    Lead with what you know about life sciences and biotech, not about yourself

13

Automation

Giving the hours back. Never removing the people.

  1. pillarIntro.Automation

    Automation here means giving you the hours back, not taking the people out. The conversations stay yours. What goes is the repetitive work stacked around them.

  2. PLAY_NURTURE_ARCHITECTURE.labelfirst quarter

    Staying useful between briefs

  3. PLAY_NURTURE_ARCHITECTURE.summary

    A regular, genuinely useful contact with people who are interested but not buying yet.

  4. moduleNarration.PLAY_NURTURE_ARCHITECTUREwhy it is here

    This runs directly behind the first move, because the buying cycle here runs in quarters and there is nothing keeping you useful across it. On a buying cycle measured in quarters, the two together are worth more than either alone.

  5. PLAY_NURTURE_ARCHITECTURE.effectwhat changes

    On a buying cycle measured in quarters, this is what makes you the name they already know when the brief lands.

  6. PLAY_NURTURE_ARCHITECTURE.firstMovefirst move

    A monthly note to everyone who ever raised a hand. Short, and about them.

  7. PLAY_NURTURE_ARCHITECTURE.signalyou will know because

    Replies from people who went quiet eighteen months ago.

  8. ideas.PLAY_NURTURE_ARCHITECTURE.positionspositions you asmodel

    still useful to a biotech nine months after they first read you

  9. ideas.PLAY_NURTURE_ARCHITECTURE.0Nurture branch · for the one whose neck is outmodel

    A branch for the person who says their real issue is proving afterwards that the investor day was worth the spend, sending one usable measurement idea at a time

  10. ideas.PLAY_NURTURE_ARCHITECTURE.1Nurture branch · for the one guarding how it looksmodel

    A path for the person whose blocker is internal agreement on how the company should look in the room, giving them arguments they can use in a meeting you are not in

  11. ideas.PLAY_NURTURE_ARCHITECTURE.2Nurture branch · for the one who has to live with itmodel

    A quarterly note for the life sciences buyer with no brief yet, one thing learned from running advisory boards and R&D days, sent whether or not they ever reply

  12. PLAY_PIPELINE_WORKFLOW.labelquarter 3

    The same first steps, every time

  13. PLAY_PIPELINE_WORKFLOW.summary

    The tedious sequence every new opportunity goes through, held as tasks and checklists rather than in somebody's head: the questionnaire, the RFP review, the internal sign-offs.

  14. moduleNarration.PLAY_PIPELINE_WORKFLOWwhy it is here

    On the board for LifeSci Events because the same set of steps runs on every new opportunity and none of it is written down.

  15. PLAY_PIPELINE_WORKFLOW.effectwhat changes

    The boring work stops depending on who picked it up and how busy they were. You get the hours back and the process stops varying.

  16. PLAY_PIPELINE_WORKFLOW.firstMovefirst move

    Write down what actually has to happen between an enquiry arriving and a proposal going out. That list is the workflow.

  17. PLAY_PIPELINE_WORKFLOW.signalyou will know because

    Nothing stalls because one person was on site all week.

  18. ideas.PLAY_PIPELINE_WORKFLOW.positionspositions you asmodel

    the same standard of response in your busiest week as in your quietest

  19. ideas.PLAY_PIPELINE_WORKFLOW.0Workflow · for the one who has to run itmodel

    Everything between an enquiry landing and a proposal going out, held as a checklist with a named owner on each step, so nothing depends on who happened to open the email

  20. ideas.PLAY_PIPELINE_WORKFLOW.1Workflow · for the one whose neck is outmodel

    The RFP and vendor questionnaire answers life sciences procurement always asks for, kept in one place and updated once, so a day of assembly becomes an hour of checking

  21. ideas.PLAY_PIPELINE_WORKFLOW.2Workflow · for the one guarding how it looksmodel

    A single check before anything leaves the office, that the proposal, the deck and the site visit notes look like the firm a pharmaceutical brand team is being asked to trust

14

Architecture

The structure underneath, so none of the above leaks.

  1. pillarIntro.Architecture

    Architecture is the plumbing. Unglamorous, and the reason the other three either compound or leak.

  2. PLAY_PIPELINE_STRUCTURE.labelquarter 3

    One pipeline, agreed stages

  3. PLAY_PIPELINE_STRUCTURE.summary

    Every live opportunity in one place, with stages everyone reads the same way.

  4. moduleNarration.PLAY_PIPELINE_STRUCTUREwhy it is here

    On the board for LifeSci Events because there is no single place that answers what is actually coming.

  5. PLAY_PIPELINE_STRUCTURE.effectwhat changes

    You can see what is actually coming, which is the difference between forecasting and guessing.

  6. PLAY_PIPELINE_STRUCTURE.firstMovefirst move

    Agree five stage names, then move every open opportunity into them.

  7. PLAY_PIPELINE_STRUCTURE.signalyou will know because

    The pipeline answers questions instead of raising them.

  8. ideas.PLAY_PIPELINE_STRUCTURE.positionspositions you asmodel

    able to see which corporate event contracts are actually coming, quarters ahead

  9. ideas.PLAY_PIPELINE_STRUCTURE.0Workflow · for the one who has to run itmodel

    The steps between a first conversation and a signed contract, written down once, so a busy month runs the same way as a quiet one

  10. ideas.PLAY_PIPELINE_STRUCTURE.1What to measure · for the one whose neck is outmodel

    Record the date a contact first appeared and the date they finally enquired, so the months of early work stop looking like waste when someone reviews the year

  11. PLAY_FIRST_TOUCH_ATTRIBUTION.labelquarter 4

    Crediting the first touch, not the last

  12. PLAY_FIRST_TOUCH_ATTRIBUTION.summary

    Recording what a buyer had already seen before they made contact, not just the click that carried them in.

  13. moduleNarration.PLAY_FIRST_TOUCH_ATTRIBUTIONwhy it is here

    On the board for LifeSci Events because the long half of the buying cycle is invisible in what gets recorded, so the work that starts decisions cannot be defended at budget time.

  14. PLAY_FIRST_TOUCH_ATTRIBUTION.effectwhat changes

    On a decision that takes 221 days the last touch is the doorway, not the reason. Crediting only the doorway defunds everything that did the work.

  15. PLAY_FIRST_TOUCH_ATTRIBUTION.firstMovefirst move

    One question on the enquiry form: where had you come across us before today?

  16. PLAY_FIRST_TOUCH_ATTRIBUTION.signalyou will know because

    The channels you were about to cut turn out to be the ones being mentioned.

  17. ideas.PLAY_FIRST_TOUCH_ATTRIBUTION.positionspositions you as

    able to prove which of this started the conversation, not just which one closed it

  18. ideas.PLAY_FIRST_TOUCH_ATTRIBUTION.0What to measure · for the one who has to run it

    Every touchpoint scored by distance from a signature

  19. ideas.PLAY_FIRST_TOUCH_ATTRIBUTION.1What to measure · for the one whose neck is out

    Which of the five seats each touchpoint actually reached

15

Sequence roadmap

The order, and why it is that order.

  1. roadmapIntro

    Four quarters, in dependency order. This is not a proposal for four quarters of work. It is the order the modules have to happen in if they are going to hold, so that if you only ever do the first quarter it still stands on its own. Arrows mark where one module needs another in place first.

16

What sits underneath

The system behind the path.

  1. labyrinthIntro

    Under each of those four pillars sits roughly a hundred smaller moves. Nobody needs all of them, and nobody should try. It is here so the eight modules on your board read as a choice made from the whole picture rather than the whole picture itself.

17

What it becomes

The Eclipse proof point.

  1. eclipseIntro

    Compounding is the part that is hard to picture from the first quarter, because the first quarter mostly looks like effort. Eclipse Global has been running this system for eight years. Their published account is at codarity.com/results/eclipse-global.

18

Next step

The single ask. Nothing else in this section.

  1. nextStepIntro

    The obvious next step is a conversation about the first quarter, not the board and not the roadmap. If the next twelve months are meant to come from corporate event contracts, the first quarter is where that starts, and it is small enough to be worth talking about properly.