On this page9
- The job your bio is actually doing
- The four bio formats and when to use each
- What goes in the journalist-facing bio
- What goes in the conference-facing bio
- The one-liner: hardest format, most used
- The headshot brief
- The three most common bio mistakes in Web3
- Building the asset library
- What good looks like: side-by-side
How to Write a Founder Bio That Journalists Actually Use
The bio sitting in your press kit right now is probably killing your chances with both audiences who read it. Journalists skim it looking for one credential that lets them slot you as a source. Conference programmers scan it for proof you have a specific point of view, not a job title. And podcast hosts want to answer one question before they say yes: "will this person be interesting for 40 minutes?"
Most Web3 founder bios fail all three tests. They're either a LinkedIn-style credential list ("co-founder of X, previously at Y, board member of Z, Forbes 30 Under 30...") or they read like a company pitch deck with the founder's face attached. Neither tells the journalist what she needs to know. Neither tells the conference programmer what he needs to hear.
I've written and workshopped bios for founders across Fluence, GAIA, WalletConnect, RARI Foundation, and a dozen others. The bios that land press quotes and speaking slots share a specific structure. The ones that don't land almost always fail for the same three reasons.
---
The job your bio is actually doing
Your bio isn't a resume. It isn't a sales page. It's a credibility shortcut.
A tier-1 trade reporter at CoinDesk has 200 emails in her inbox today. She's writing a piece on DePIN compute. She needs a source who can say something beyond the press release. When she lands on your bio, she has one question: "Is this person worth a 15-minute call?"
Your bio has to answer that in 60 words or fewer.
A conference programmer for TOKEN2049 is reviewing 400 speaker submissions. He's not building an education program. He's building a lineup that makes people want to attend. Your bio has to tell him: "This person has a non-obvious point of view and an audience that will fill seats."
Two different readers. Two different jobs. One bio template can't serve both.
This is the core mistake. Founders write one bio and paste it everywhere. A journalist-facing bio and a conference-facing bio have different structures, different emphasis, different word counts. You need both, and you need to know when to send which.
---
The four bio formats and when to use each
The long bio (250-300 words). Goes on your press kit page and your speaker page. This is the one that gets lightly reused when a publication writes a profile. It has room for a founding story, a credential or two, and a human detail. Don't mistake length for license to list everything.
The short bio (75-100 words). This is your workhorse. It goes in pitch emails, in the speaker submission form, in podcast booking notes. A journalist will copy-paste 40-60 words of this into their piece. Write it so those 40-60 words are accurate and quotable even out of context.
The one-liner (25-35 words). Used in Twitter/X bios, article author tags, panel program books. One sentence. One credential. One category claim.
The headshot brief. Not a bio in the traditional sense, but it lives adjacent to your bio and kills more opportunities than founders realise. I'll cover it last.
---
What goes in the journalist-facing bio
A journalist-facing bio has three components and three only:
- What you built or led (one specific thing, not a list)
- Why that makes you a credible source on the topic the journalist is covering
- A single data point that proves scale
That's it. No founding story. No vision statement. No "passionate about decentralization."
When I was placing Tom Trowbridge at Fluence for DePIN coverage at CoinDesk and Decrypt, the bio that worked wasn't about Fluence's roadmap. It was about what Tom had seen at the protocol level across DePIN infrastructure projects, framed around the specific question journalists were trying to answer: does DePIN actually generate revenue, or is it just TVL theater? The bio positioned him as someone who had data on that question. The call requests came in.
For GAIA's founders, the bio that unlocked the Forbes piece framed CEO Matt Wright not as "founder of a decentralized AI platform" but as someone operating AI agent infrastructure at scale, with a node count that gave the claim teeth. The journalist had a data point she could put in the lede.
The formula, plainly stated: [Name] [verb] [specific thing] at [company], where [credentialing phrase that connects to the journalist's story topic]. [One number that proves it.]
"Tom Trowbridge co-founded Fluence, a DePIN compute network that connects 3,000+ independent data centers for cloud-alternative workloads."
That's a journalist bio. Not a company bio with Tom's name in it.
---
What goes in the conference-facing bio
Conference programmers are reading for argument, not achievement. They want to know what position the speaker will defend on stage.
Value addition >>>>> Fancy titles or bio's Shilika Jain on X, 13 Apr 2022
I wrote that five years ago and it's still the sharpest way I know to say this. Conference programmers have seen every credential. They're not shortlisting you because you're a co-founder. They're shortlisting you because you have something to say that the other 399 applicants don't.
Your conference bio should do this:
- One sentence: your current role + company (the credential)
- One sentence: the specific claim you'll make on stage or defend in the panel
- One sentence: the proof that you've done the work behind the claim (published op-ed, protocol you built, specific dataset you hold)
That's 3 sentences. Not 3 paragraphs.
"[Name] is co-founder of [X], a [category] protocol with [number] in [metric]. She has argued publicly that [specific contestable claim] and will defend that position at [event name]. Her op-ed on this topic ran in CoinDesk in [month]."
The linked prior talk or published piece is not optional. Programmers for TOKEN2049, Consensus, and ETHDenver all want evidence you can hold an argument under live pressure. A YouTube link to a 10-minute panel is worth more than three paragraphs of bio.
---
The one-liner: hardest format, most used
Your one-liner will be copy-pasted into more places than any other version: article bylines, Twitter bios, the caption on the stage photo that 400 people will see. It has to work as a standalone credential claim.
The failure mode is vagueness: "Building the future of decentralized AI." The success mode is specificity with a category claim: "Co-founder at GAIA, building decentralized AI agent infrastructure. 400K+ nodes."
One trick I use with founders: write the one-liner as if a journalist had to describe you in 25 words for a roundup. Would those 25 words make a reader want to click on your name? If not, rewrite.
---
The headshot brief
Your headshot is doing PR work before your bio gets read. A blurry photo from a conference after-party, a pixelated crop from a group shot, or a hyper-produced corporate head-and-shoulders against a white wall all send signals before the journalist opens the bio.
For press kit headshots, what you want: - Minimum 1600px square, JPEG, clean background - Shot that reads well at 80x80px (thumbnail in article bylines) and at 400x400px (profile feature) - No logo watermarks on the photo itself - A version in color and a version that works in black-and-white for print
For conference submissions, the headshot often goes live on the event website two months before the event. It's the face on the promotional artwork. Every senior person reviewing your submission sees it. "Professional" isn't the bar. "Recognizable and consistent with your online presence" is.
Keep one canonical headshot across your press kit, your conference submission folder, your LinkedIn, and your X profile. Inconsistency makes you look like a different person on each platform, which is a small friction that adds up when a programmer is Googling you at 11pm.
---
The three most common bio mistakes in Web3
Listing protocols instead of outcomes. "Previously at Polygon, Starknet, and Ethereum Foundation" is a list of logos, not a credential. What did you do there? What did you ship? What can you say on the record about what you learned?
Writing the company bio with your name in it. This is the most common error I see in press kits. The bio reads: "Jane co-founded XYZ Protocol, which is building the leading infrastructure for [category]." That's not Jane's bio. That's the company boilerplate with Jane's name attached. Journalists can see the difference in one sentence. The bio has to be about Jane's point of view, not about the company's positioning.
Burying the credential. A surprising number of founders hide the most citable fact in the fourth sentence. A journalist's eyes stop reading after sentence two if nothing has caught her attention. If your credential is "built the first DePIN compute marketplace with real revenue," that goes first. Not last.
---
Building the asset library
A bio that works doesn't exist in isolation. It lives alongside a short quote, a headshot, a link to a prior talk or op-ed, and a two-sentence pitch on what you can comment on.
I build this as a single-page press asset doc for every founder I work with. Four sections: long bio, short bio, one-liner, and a "comment topics" list. The comment topics list is three to five specific questions the founder can answer on the record. When I pitch a journalist on an expert commentary placement, I send the short bio plus two comment topics. The journalist can see instantly whether this source is useful for her piece.
most projects think that PR is asking a media to publish an article about their company what it actually is - creating a storyline, working on the messaging & narrative, pitching to targeted journalists, reaching out to them with well-curated pitches, following up & more! Shilika Jain on X, 13 Apr 2023
The bio is the narrative's anchor. Everything else in a pitch, a speaker submission, or a media kit flows from the credibility that bio either establishes or doesn't. Get that anchor wrong, and the rest of the packet doesn't matter.
---
What good looks like: side-by-side
Most bios I see for the first time in a new client engagement look like this:
Before: "Jane Doe is the co-founder and CEO of XYZ Protocol, a groundbreaking blockchain infrastructure platform revolutionizing the way developers build decentralized applications. With 10+ years in tech, Jane previously worked at multiple leading companies in the fintech and crypto space. She is a thought leader in Web3 and a frequent speaker at major industry events."
Zero credentials a journalist can use. Zero argument a conference programmer can shortlist. Every sentence is either vague or a product pitch.
After: "Jane Doe co-built XYZ Protocol's fee-sharing infrastructure, now processing $40M in monthly developer payouts across 12 L2 networks. Before XYZ, she led developer relations at [Named Protocol] for three years. She writes on protocol revenue models for CoinDesk."
Four times fewer words. Four times more useful. A journalist writing about L2 economics has a source. A conference programmer knows exactly what Jane will argue on stage.
The rewrite takes 20 minutes. The placement opportunities it unlocks can take years off your PR timeline.
---
If you want a bio review, I run a 30-minute teardown call where we work through your current assets — bio, pitch doc, headshot brief — and identify exactly what's blocking placement. No deck. No proposal. Just the work.