Jonathan Koo

learner, disciple. gtm @overflow_app | econ, biz @nyuniversity

[Jonathan Koo @jonathanbkoo]

@jack_9947 @AlfieJCarter 244

[Fivos Aresti @fivosaresti]

6 workflows to master if you’re in GTM engineering:

1) Inbound Orchestration.

Every:

• Form fill
• Demo request
• Newsletter signup

ALL routed automatically through:

• Clay
• Customer(.)io
• Cal(.)com
• Tally
• HubSpot.

2) TAM Sourcing.

Every account worth selling to, with the full buying committee mapped through:

• Apollo
• AI Ark
• Ocean(.)io
• DiscoLike
• Apify
• Serper.

3) Automated CRM Enrichment.

• Validate
• Normalize
• Enrich
• Score
• Segment
• Update CRM.

Built once, runs on every new record.

4) Automated Outbound.

End-to-end sequences across email through:

• Instantly
• HeyReach (linkedin)
• OutboundSync (cold calls)

5) Signal Tracking.

• First-party
• Second-party
• Third-party signals

Each trigger their own play.

6) Content Engineering.

• Sales calls captured by Ergo
• Objections surfaced
• Content ideas generated
• Calendar updated
• Marketing notified.

Master these 6 and the rest of the GTM team moves faster behind you.

[Jason ✨👾SaaStr.Ai✨ Lemkin @jasonlk]

54% of Anthropic's new enterprise logos in 2026 came through self-serve.

Self-serve enterprise. Real ACV. Real terms of service. No AE in the loop.

Anthropic's Head of Industries Eleanor Dorfman walked through at SaaStr AI 2026 last week how they rebuilt the entire sales org in 30 days after Claude Opus 4.6 broke their demand curve in December.

👉The constraint: couldn't 3x or 4x the sales team fast enough without lowering the recruiting bar.

The thesis: don't buy a new stack. Thread Claude through the one you already have.

What they kept:

1⃣ Clay for enrichment
2⃣LeanData for routing
3⃣ @salesforce as system of record
4⃣@Gong_io for call coaching
5⃣Ironclad for contracts
6⃣@slackhq for everything else

What they added: Claude as the connective tissue between all six.

The four moves:

1/ Killed the PLG vs SLG orthodoxy. Launched enterprise self-serve in January. Intercom Fin guides the buyer through the journey. Now 54% of new enterprise logos.

2/ Threaded Claude through the existing stack. Every AE starts the day with a "morning brief" Skill that pulls context from Gmail, Gong, Slack, Salesforce, @intercom, Greenhouse.

3/ Made Slack the front door for every support function. Slack ticket in, Jira ticket out. Claude triages and resolves inline if it matches precedent. Escalates with full context if not.

4/ Codified what the best reps do as Skills. Every new rep gets a sales plug-in with 5 Skills: morning brief, call prep, customer follow-up, competitive intel, create-an-asset.

Anthropic didn't replace anything. They invested in the stack they already had and let Claude be the seam between everything.

Most companies will spend 2026 evaluating AI-native sales platforms. But Anthropic did it with its current stack + Claude.

Almost none of it required new software.

[Jonathan Koo @jonathanbkoo]

@AlfieJCarter Bible

[Jonathan Koo @jonathanbkoo]

@yanndine GTM

[Jonathan Koo @jonathanbkoo]

@JJEnglert GTM guide

[Jonathan Koo @jonathanbkoo]

@JJEnglert GTM guide

[Jonathan Koo @jonathanbkoo]

@iamliamsheridan Metrics

[Jonathan Koo @jonathanbkoo]

@Kaynvas Would love the prompt!

[Jonathan Koo @jonathanbkoo]

@iamliamsheridan Prompts

[Jonathan Koo @jonathanbkoo]

@iamliamsheridan Claude

[Jonathan Koo @jonathanbkoo]

@aryanXmahajan Agent

[Hunter Horsley @HHorsley]

In 2006, every section of Craigslist was a $1b marketplace startup waiting to happen.

In 2026, every section of PWC's website is a $10b AI startup waiting to happen.

[Anish Moonka @anishmoonka]

If Claude Code or Codex just one-shotted an app for you, Read this.

Now you gotta go through every screen and find the 47 edge cases that break it. Users will do things you never imagined. Then comes auth, database setup, API rate limits, error handling for when the server goes down at 2am. You need analytics to figure out what users actually do vs what you think they do. App Store optimization, screenshots, descriptions, review responses. Privacy policies, terms of service, data compliance. Push notifications that actually work without being annoying. Performance optimization because that smooth demo gets real laggy with real data. State management across the whole app. Caching strategy. Offline support. Responsive design across 15 different screen sizes. Testing on older devices that somehow still exist. CI/CD pipeline so deploys don't eat your weekends. Then users start requesting features you never planned for and suddenly your clean architecture needs a rewrite.

The first version is maybe 10% of the actual work. Building is easy. Shipping and maintaining is where it gets real.

[Damian Player @damianplayer]

we are living in the jack-of-all-trades era. a generalist with AI tools is replacing the specialist who only knows one thing. depth used to win.

now it's range + leverage.

[Luke Simmons @lukedsimmons]

https://t.co/1mpmfWWmGy

[Boris Cherny @bcherny]

I'm Boris and I created Claude Code. I wanted to quickly share a few tips for using Claude Code, sourced directly from the Claude Code team. The way the team uses Claude is different than how I use it. Remember: there is no one right way to use Claude Code -- everyones' setup is different. You should experiment to see what works for you!

[George from 🕹prodmgmt.world @nurijanian]

every PM who wants to survive the AI era should watch this video (75 mins)

@gokulr shares how product management is fundamentally changing

my notes below but you have to watch the whole video:

[Jonathan Koo @jonathanbkoo]

@dimitarangg Ai

[Dev Shah @0xDevShah]

universities are about to realize that they had been selling the wrong product for the 150 years. they thought they sold knowledge, then information became free. they pivoted to selling credentials but now credentials are just proxies. in the post-ai era the universities who survive will realize they were always selling 3 things: network, status signaling, and a 4 years of protected time to become an adult.