Today we’re introducing the world's first AI Workforce for Marketing Ops: a team of AI agents that converts 30% more inbound into demos/ signups. Marketing teams spend millions on inbound, but 50% of leads never convert b/c they're lost to long forms, poor targeting, and slow follow-ups. Here’s how the AI Workforce works → 🧵

RT @danielfazio: The Indian prospect’s face when you tell them they can’t get access for free and pay after they get results t.co/O…

Such a great product to work on!

vibe coded a CRM with Claude in a weekend. contact records, pipeline stages, deal tracking, the whole thing. felt like a genius. lasted about 2 weeks before I realized I made a terrible mistake. so here's what happened. we're a small team, 2 sales reps, and I convinced myself we didn't need HubSpot. why pay for something Claude can build in 48 hours right? Claude built it. it worked. I was walking around the office like I just saved us $15K a year in software spend. then week 2 hit. a routing rule broke. nobody knew how to fix it except the engineer who built it. he was heads down on product. the lead just sat there unassigned for 3 days. nobody even noticed until the prospect emailed us asking why nobody followed up. that was the first crack. then we tried to hire a sales rep. first question in every interview: "what CRM do you use?" when I said "oh we built our own" the energy in the room just died. every single candidate knew HubSpot or Salesforce. nobody wanted to learn some homegrown tool that one engineer built in a weekend. I watched 3 great candidates lose interest in real time. that was the second crack. then I tried connecting Apollo. then Clay. then our email sequences. every single tool in our GTM stack has native HubSpot and Salesforce integrations. connecting them to our vibe coded CRM meant custom API work for every. single. one. more engineering time. more things breaking at 2am that nobody knows how to debug. that was the third crack and I was done. the thing nobody tells you about vibe coding your business tools is that building the V1 is the easy part. like genuinely easy. Claude will build you a beautiful CRM in a weekend. the hard part is everything after that: who maintains it when something breaks at 11pm on a friday who onboards new hires onto a tool with zero documentation who builds and maintains every integration manually who fixes the schema when your AI agent corrupts a field the answer to all of those is "you" and eventually you get tired of being the answer to all of those. established CRMs feel like overkill when you have 2 reps. but the migration you're avoiding now costs 3x more when you have 10 reps. ask me how I know. two weeks in I got tired of explaining our homegrown CRM to sales candidates who just wanted to use HubSpot. so we went back to HubSpot. hubspot wins again 🤷‍♂️

congrats @kathrynwu1 and OpenMart team!!! this looks awesome

interview with @PayPal

I got into @ycombinator solo After 7 rejections Before the batch: -$2.1M raised alone -Sold 200K ARR -6M views I'm building the first database sandbox @ArdentAI We let you infinitely clone any Postgres DB in <6s so coding agents can test code on a 1:1 of prod Time to win

Awesome team and product

Can you vibe code your own CRM? Yes. Should you vibe code your own CRM? No.

this same thing will happen for marketing btw

hiring PSA for early-stage founders: there are two types of employee candidates 1. ones who want to work at a proven rocketship 2. ones who want to help you build the rocketship we've never gone wrong hiring the second type

Founders: Here is a product feature prioritization framework that works at Surface 👇 Build everything really fast

This wasn't the plan. But here we are. My team at Surface Labs accidentally built something the market doesn't have a name for yet. We thought we were just going to sell better "Typeform" to founders. But teams using Surface have literally changed how they work: 1/ A customer just replaced 5 tools with it and told me to raise our prices. 2/ Growth marketers are launching new same-day inbound experiments. 3/ Designers are building pixel-perfect funnels without code. 4/ SDRs check Surface before their CRM. 5/ Ops teams have finally stopped bothering the devs (just kidding) Somehow we ended up managing the entire top-of-funnel lead journey: 𝗖𝗮𝗽𝘁𝘂𝗿𝗲. 𝗗𝗲-𝗮𝗻𝗼𝗻𝘆𝗺𝗶𝘇𝗮𝘁𝗶𝗼𝗻. 𝗘𝗻𝗿𝗶𝗰𝗵𝗺𝗲𝗻𝘁. 𝗦𝗰𝗼𝗿𝗶𝗻𝗴. 𝗤𝘂𝗮𝗹𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻. 𝗦𝗽𝗮𝗺 𝗣𝗿𝗲𝘃𝗲𝗻𝘁𝗶𝗼𝗻. 𝗥𝗼𝘂𝘁𝗶𝗻𝗴. 𝗡𝘂𝗿𝘁𝘂𝗿𝗲. 𝗔𝘁𝘁𝗿𝗶𝗯𝘂𝘁𝗶𝗼𝗻. 𝗗𝗮𝘁𝗮 𝗦𝘆𝗻𝗰𝘀. 𝗠𝗼𝗻𝗶𝘁𝗼𝗿𝗶𝗻𝗴. 𝗘𝘅𝗽𝗲𝗿𝗶𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻. I'm not a fan of inventing categories, but I don't think Surface fits into existing buckets. We spent months trying to figure it out. Next week, I'll tell you.

this is genius

lol

the more our own business grows, the better we’re getting at selling to other companies because now I know how i would like to be pitched, which features and ROI arguments actually matter and what’s fluff

awesome product and team!! we got it live and making *actually useful* code base revisions in under 30 min

the entelligence ai team is super responsive to product feedback!!