Builds 2 to 4 persona cards with the user and puts each lead in one. Use before writing to a new list, or when messages sound generic or repeat the job title.
The ICP (in the search plan) says which companies. A persona says which person inside them and what to say to them: a role in a situation, never a person with a life. The title finds the card; the card writes the message, never "I saw you are Head of X".
Blocks: Persona cards v1 and Who is who on linkedin-outreach-method's Plan and personas
page (its "3 premiers messages" band comes from the v1 cards at once, via linkedin-messages), Who is who
again on Invitations to send; each its own page only when this skill runs alone. Before drawing a block,
read references/artifacts.md (its section).
bereach_memory_list, fullContent: true, for offering and user-profile; the offering's "Personas"
section is the starting point.references/sources.md); inside
linkedin-outreach-method, after its question round.bereach_plan_searches ran here: each group (a role in one segment) goes
into the Found by of its card; groups that would get the same first message share one card, even across
segments; roles the plan guessed end in (guess).Asked in linkedin-outreach-method's one question round, only what Step 1 left empty or (guess):
Before drafting, read references/persona-card.md (Core, Rules) and references/frameworks.md (Which card
field comes from which framework); the band names only a framework the cards visibly apply.
Draft 2 to 4 cards. Cards are short: a seller writes a message from them in one read. A line that is not the
user's words or a reply ends in (guess). Get right:
Deliver: Persona cards v1, provisional by design; an answer given later is saved and the block republished in place.
bereach_memory_save, type: "offering", only on a change. It replaces the whole entry: the full
existing text (or what they sell, from the question round) plus a ## Personas section with every card
and any validated templates.bereach_plan_searches; a Why now, Signal or Proof picks its door in
linkedin-outreach-method's references/search-doors.md.Before sorting, read references/persona-card.md (ICP, plan groups and cards; More: Not this persona).
Untouched people first, then each search's, from the row (title, company, whyNow); no profile data:
amber pas de profil : N. Keep on the row any fact settling the persona, dated (month and year).
CHECK until
the brief shows it.whyNow falls in, or whose ICP the
company is in, else CHECK. A batch rule for titles outside a card's Found by adds them to it on the
same rule row; else they stay CHECK.sure: the title matches exactly one card's Found by and nothing puts the company outside its ICP. Enough to tag.CHECK: two cards fit with nothing to split them, or the company is outside the ICP. No tag, no message
until the user picks; the others go on.HOLD, no message; on the user's yes,
bereach_contact_update with the list's campaignId and lifecycleStage: "rejected".bereach_contact_update, all contactIds of one persona, tags: { add: ["persona:<short-name>"] },
one short name per persona everywhere.Only when the user asks for a score: bereach_check_fit with the campaignId, icp as the plan's ICPs in
their words, personas as "<short-name> (title, title, title)" (3 titles at most). Tag from
fit.persona; it hides and blocks nobody.
Deliver: Who is who. Sure rows need no yes; open rows are held and asked on Invitations to send, never a stop of their own. Its total is the count every later page reads.
linkedin-messages writes one template per persona from Why now, Pain, Proof, Objection and Offer, line 1 from the lead's brief (every person briefed before every message), else the moment line, never their title or headline. A reply asking for something is evidence for the Offer.
After 7 days linkedin-outreach-method draws Results per persona (tag persona:<short-name>,
bereach_inbox for replies). Then, with the user, never on a partial read:
seen in N replies; contradicted ones are rewritten; an answer is asked again only
when replies contradict it, and a new objection's answer is the user's.pause; the user picks.bereach_contact_update per persona, tags: { add: [new], remove: [old] },
then save again (Step 3).Deliver: Persona cards v2, only the changed lines, one decision.