Every GTM consultant I know ships some version of the same weekly output: a Google Doc, a slide deck, a PDF proposal, a status email. That's the job description, and it's been the job description for fifteen years.

Jason Mellet just stopped doing all of it.

He posted his shift in the RevGenius Slack a few weeks back. Eva M pushed back with five specific caveats within the hour. What came out of the exchange is the sharpest design debate I've seen in the community this quarter, and it's a preview of where GTM deliverables are headed.

Jason runs a GTM consulting practice. Clients pay him for demand gen, RevOps, growth strategy. The output has always been documents.
Slides. Sheets. Emails with attachments.

He stopped sending any of it. He works in Cursor, Codex, and Claude. When something changes, he tells Claude "publish this update," and the whole thing lands at a live URL.

His pitch:

"The goal is to never have to create another slide, pdf, google doc or sheet or agenda ever again."

The client always sees the freshest version. Nobody hunts for last week's email. Whether the client's on Google or Microsoft doesn't matter. Everyone can open a URL.

The version control problem that consulting has quietly lived with for a decade (deck_final_v3_REALLYfinal.pdf) dies the moment everything lives at one URL as the single source of truth.

Eva M jumped in with a critique that reframed the whole move. She agreed the shift works, but she pointed out something Jason's framing didn't quite name.

"This is where it gets genuinely better than docs, not just equivalent: you can drop smart search right in. Full-text or even semantic ask-a-question search across everything you've ever sent the client."

Her point: a PDF graveyard is unsearchable. A living site where the client can type "what did we agree on pricing" and land on the exact line is a real upgrade. Not a cosmetic one.

This is the piece most people miss when they think about moving off static files. Search is the feature that makes the entire archive productive, and it only becomes possible when the archive stops being a folder of PDFs.

Eva's real value in the thread was that she didn't just cosign the move. She named the five specific moments where HTML-by-default hits friction. Any operator considering the shift should read these before making it.

Eva's synthesis: HTML by default, smart search as the killer feature, export when the situation demands it. That framing is worth stealing whole.

The move itself is interesting. The exchange is what makes it a piece worth writing about.

Jason didn't defend his framing when Eva added the caveats. He absorbed them and shipped a blog three hours later on his own site incorporating Eva's feedback and giving her a shout out inside the post. The whole loop (thesis, critique, refinement, publication) took less than a Slack workday.

That is the actual signal. Not the URL trick. The speed at which two GTM operators inside the same community can turn a rough thesis into a refined piece by pressure-testing it in public.

The community itself is now the R&D layer for how operators ship work. That's what the shift is really about.

If the mechanic transfers to your work (and for most GTM consultants and agencies it does), the questions to sit with are the same ones Eva flagged:

Where does this URL live, and who owns it?
What happens when the client's IT rotates SSO?
How do you handle the procurement stakeholder who needs a PDF for their queue?
When does an "agreed on" line need to be snapshotted, and where?

The move itself is straightforward. The design decisions underneath the move are where the actual work is, and where the difference between "shipping URLs" and "shipping a durable client asset" gets defined.

The static deliverable isn't dead. But it's going to look increasingly outdated next to operators who've built a real living-site workflow.

The gap between the two approaches will show up in how fast the consultant iterates, how much of their archive is productive, and how much of their weekly time gets spent formatting things nobody reads twice.

Jason and Eva both post regularly in the RevGenius Slack. If you want to be in the room when the next design debate happens, join the community here.

And if you want to hear these debates play out live, in real time, with the operators building through them, that's Coffee Talks.

Next Coffee Talk: Thursday at 12pm ET. Bring what you're building, what's stuck, or just bring questions.

Demo Day
(Tuesday, 21st July | 12 PM EST)

Experience the future of GTM with an exclusive look at the essential tech stack for 2026. This no-fluff showcase delivers high-value, 10-minute demos from brands solving real technical challenges, paired with lively community networking and exclusive partner discounts. It’s a straightforward, product-first event designed for immediate impact.

From Workflow Chaos to Operational AI : Real RevOps Use Cases
(Thursday, 22nd September | 1 PM EST | 10 AM PT)

In this session, we're showcasing AI agents built specifically for the event, deployed against real broken RevOps workflows: lead routing, onboarding, forecasting, handoffs, and resurfacing opportunities before they slip. Live builds grounded in real challenges, not generic hype.

We've lined up member-only deals from some of the best go-to-market tools out there.

Are you hiring and want your job featured? Submit a role here.

Want to get your brand in front of 60,000+ revenue leaders?

Partner with us and put your name at the center of the conversation.