--- title: "How to Build a Crypto Journalist CRM: Beats, Sentiment, and Embargo Reliability" description: "Most Web3 teams keep journalist contacts in a Google Sheet that goes stale in 60 days. Here's the schema and workflow for a CRM that actually works when a story breaks." author: "Shilika Jain" date: "2026-06-19T18:01:32.643+00:00" tags: ["media-relations", "journalist-crm", "crypto-pr", "ops", "web3-pr", "earned-media", "journalist-relations", "comms-ops"] canonical: "https://www.shilikajain.com/blog/crypto-journalist-crm-beats-sentiment-embargo-reliability" --- # How to Build a Crypto Journalist CRM: Beats, Sentiment, and Embargo Reliability By [Shilika Jain](https://www.shilikajain.com/authors/shilika-jain) — 6/19/2026 Most Web3 teams keep journalist contacts in a Google Sheet that goes stale in 60 days. Here's the schema and workflow for a CRM that actually works when a story breaks. --- # How to Build a Crypto Journalist CRM: Beats, Sentiment, and Embargo Reliability There is a version of the journalist list that every Web3 comms team has built at some point. A Google Sheet, maybe 80 rows, columns for name, outlet, email, and "notes." Someone made it during a token launch sprint. No one updated it after. Six months later, half the emails bounce, two journalists have changed beats, and the person who built the sheet has left the company. That list is not a CRM. It is an artifact. The Google Sheet problem is not laziness. It is structure. A spreadsheet can store names. It cannot answer the questions that actually matter when you have a story to place: *Does this journalist cover DeFi infrastructure right now, or did they pivot to AI regulation?* *Have they written anything sympathetic to stablecoin issuers, or do they consistently frame that story as systemic risk?* *Did they hold the embargo on the last round, or did something slip at 10pm?* This post is about building a CRM that answers those questions. Not a tool recommendation. A schema, a workflow, and a scoring approach that an in-house comms lead or fractional PR consultant can build in Airtable, Notion, or even a well-structured spreadsheet and actually maintain. ## Why Journalist Data Goes Stale So Fast in Crypto Crypto journalism moves faster than most beats. Reporters who covered DeFi protocols in 2023 may be writing about tokenized treasuries and RWA infrastructure today. Beat shifts happen constantly, and the crypto press cycle, with its shorter attention spans, fewer editorial staff, and higher turnover, accelerates the decay of any static list. Research suggests media contact data has a shelf life of around six months before a significant portion becomes outdated. In practice, the crypto vertical moves faster than that. A journalist who covered your category last quarter may have pivoted entirely. Pitching someone who no longer covers your space does not just waste time. It signals that you have not done the work, and that signal lands before your story does. The consequence of a stale list is not just bounce rates. It is relevance damage. When you pitch a reporter with a story that is clearly off their current beat, you train them to treat your name as noise. That is expensive in a space where relationships compound over years, not campaigns. ## The Schema: What Your Journalist CRM Needs to Track A working journalist CRM for crypto PR has two tiers of data: static fields that change infrequently, and dynamic fields that need regular refresh. Most teams only capture the static layer. The dynamic layer is what makes the CRM actionable. ### Static Fields (Review Quarterly) **Name, outlet, email, X handle, LinkedIn.** The basics, but verify every quarter. Beat changes and outlet moves are common enough that quarterly checks prevent most stale-contact problems. **Primary beat.** Be specific. "Crypto" is not a beat. "DeFi protocol mechanics and on-chain analytics" is a beat. "Regulatory enforcement and SEC action on exchanges" is a beat. The more granular, the better your pitch targeting becomes. Pull this from their last 10 bylines, not their bio. **Secondary beats.** Most crypto journalists cross-cover. Someone who leads on L1 infrastructure may also write about developer tooling or institutional custody. Capture this, because it opens pitch angles you would miss if you only track primary focus. **Outlet tier.** Your internal classification: Tier 1 covers CoinDesk, The Block, Blockworks, Decrypt, Bloomberg Crypto, Reuters Digital Assets; Tier 2 covers strong vertical publications; Tier 3 covers niche and ecosystem-specific press. This drives pitch priority and exclusivity decisions. **Freelance flag.** Critical to get right. Freelancers contribute to multiple outlets without a permanent affiliation, which changes how you pitch them and which relationship you are actually managing. A freelancer who covers DeFi for four publications is more valuable to track correctly than a staff writer at one. **Preferred contact method.** Some journalists take pitches by email only. Others respond faster on X DMs. A few have clearly stated preferences in their bios. Record what you know and update it when it changes. ### Dynamic Fields (Review Monthly or After Each Touch) **Last 10 bylines.** Not their archive. Their last 10 pieces, with dates. This is the single most valuable field in the CRM because it shows current beat, current angle preferences, and current sentiment. Pull it before any pitch. If you automate nothing else, automate a monthly pull of recent bylines into the record. **Category sentiment score.** A 1 to 5 rating of how this journalist has covered your category (DeFi, L1/L2, RWA, stablecoins) in their recent work. Score 1 means consistently skeptical or hostile framing. Score 3 means neutral and factual. Score 5 means sympathetic or enthusiastic. This is not about avoiding critical reporters. It is about matching story angle to framing tendency. A journalist who consistently writes skeptical DeFi pieces is a poor fit for a positive protocol announcement, but may be the right target for a "here is what we fixed" story after an incident. **Embargo reliability score.** A 1 to 5 rating based on direct experience. Score 5 means they have held embargo consistently across multiple announcements. Score 1 means a break has occurred. This score should be your primary filter when building the list for any embargoed announcement. Many experienced PR teams maintain internal records noting which journalists consistently honor embargo agreements. If you have not started that log yet, start it now. **Last touch date and type.** When did you last have contact, and what was the nature of it? Options include: pitch sent, pitch replied to, placement secured, background call, or conference interaction. The touch type matters as much as the date. A background call three weeks ago is a warmer relationship than a pitch that got no response two weeks ago. **Pitch history.** A linked log of every pitch sent, including date, story angle, response (yes, no, or no response), and resulting coverage if any. This is what separates a CRM from a contact list. Without pitch history, you cannot see patterns: which angles land with which reporters, which stories get ignored, which relationships are actually producing coverage. **Social engagement rate.** How often does this journalist engage with content in your category on X or LinkedIn? This is a softer signal, but useful for prioritizing "keep warm" outreach. A journalist who regularly amplifies token launch news is worth a warmer relationship even before they have covered you directly. **Relationship owner.** Which person on your team owns this relationship? In a small team, this might be one person for everyone. In a larger comms function, different team members should own specific journalists. Relationship ownership prevents duplicate pitching, conflicting messages, and the worst-case scenario of two people from your team pitching the same journalist on the same story from different angles. ## The Workflow: How to Keep It Alive The best CRM schema in the world decays without a maintenance rhythm. Here is the minimum viable workflow. **Monthly pull.** Once a month, someone is responsible for updating the "last 10 bylines" and "last touch" fields for every Tier 1 and active Tier 2 contact. This takes roughly 30 minutes per 20 contacts if you have set up Google Alerts or RSS feeds for each journalist's byline URL. **Pre-pitch audit.** Before any pitch goes out, the relevant journalist record gets reviewed. Is the beat current? Is the sentiment score right for this story? Has the embargo reliability score been updated since the last announcement? Reading the journalist's last five pieces, checking how the outlet has covered similar news, and noting recurring angles all sharpen the pitch and update the record at the same time. **Post-placement debrief.** After any placement, positive or negative, update the record. Note what angle worked. Note whether the coverage was accurate and fair. Update the sentiment score if the piece shifts your assessment. Log any feedback the journalist gave during the process. **Post-embargo debrief.** This one gets skipped most often and matters most. After every embargoed announcement, record whether each journalist held the embargo. Update their reliability score. Build this into your post-launch checklist so the institutional memory does not live only in someone's head. **Quarterly audit.** Verify contact information, beat classification, and outlet tier for every record. Remove or archive anyone who has left journalism, pivoted to a non-relevant beat, or gone dark for more than six months. Add new reporters who have joined relevant beats. This is also when you reassess tier assignments based on recent coverage patterns. ## Building the Embargo Reliability Score The embargo reliability score deserves its own treatment because it is the field most teams either skip entirely or track informally. Embargoes are agreements of trust, not contracts. A break may have no legal consequence but it carries real relationship and coverage cost. The score is not about whether a journalist is good or bad. It is about matching the right journalist to the right announcement type. A journalist with a score of 5, meaning a consistent embargo track record and no breaks, belongs on your Tier 1 embargo list for major announcements. They have earned early access and the context that comes with it. A journalist with a score of 3, reliable but untested on time-sensitive news, should receive embargoed material only when you have enough lead time to recover if something slips. A journalist with a score of 1 or 2, where a break has occurred or there is credible concern from pattern behavior, should receive embargoed material only after the window is short enough that any break causes minimal damage, if at all. Log embargo invitations, acceptance or decline, and post-lift behavior for every announcement. Over time, this produces a reliable score that informs every future embargo list decision without relying on anyone's memory of events that happened two campaigns ago. ## The "Who to Call First" View The goal of all this data is a single operational view: when you have a story, you know within five minutes who to call first, who to keep warm, and who to skip. Build a filtered view in your CRM that surfaces, for any given story type, journalists sorted by: beat match to the story angle, sentiment score in the relevant category, embargo reliability if the story requires a hold, and warmth of last touch (how recent and substantive was the last contact). The top five results from that view are your first-pitch list. They are the journalists most likely to respond, most likely to frame the story accurately, and, if the announcement requires an embargo, most likely to hold. This view replaces the guesswork that lives in most comms leads' heads. It makes the institutional knowledge transferable, auditable, and repeatable across campaigns and team changes. When the person who has managed journalist relationships for two years leaves the company, their contacts should not leave with them. ## On Tools: What Platform to Build On Airtable is the natural choice for most teams. It handles relational data well, supports linked records between a journalist table and a pitch-history table, and its interface builder lets non-technical team members surface the "who to call first" view without touching the underlying schema. The operational data model maps cleanly to what this CRM needs. Notion works if your team already lives there and the journalist list is relatively small. It handles narrative-rich records well, useful for logging call notes and qualitative observations, but becomes harder to query and filter at scale. A well-structured spreadsheet (Google Sheets or Excel with named tabs and frozen header rows) works at the start. It will break down as your list grows past 50 active contacts and as you try to maintain relational pitch history alongside contact data. Plan to migrate before you need to. The tool matters less than the schema and the maintenance rhythm. A mediocre CRM that gets updated weekly beats a perfectly structured database that no one touches after the first sprint. ## The Compounding Return The value of a journalist CRM is not visible in the first campaign. It is visible in the sixth. By then, you have accumulated enough pitch history to know which angles reliably land with which reporters. You have built enough embargo track record to trust your list on high-stakes announcements. You have kept enough relationships warm, through value-first touchpoints rather than just pitches, that your outreach gets read instead of filed. The protocols and founders who build durable press relationships are the ones who treat journalists as a long-term asset. The CRM is how you operationalize that intention. It is how you remember what you learned, share it across your team, and apply it the next time a story breaks and you need to know exactly who to call first. Start simple. Build the schema. Maintain the rhythm. The compounding does the rest. --- **Book a 30-min teardown with Shilika** — https://calendly.com/shilikajain/30min/ Canonical: https://www.shilikajain.com/blog/crypto-journalist-crm-beats-sentiment-embargo-reliability