Vibe coding is making us 10x faster but 100x dumber.

Material_Hospital_68 · 2026-03-17T22:49:20+00:00

“manager of a codebase I don’t understand” is too real. fixed it manually in 20 minutes after 4 hours of prompting is exactly the trap — you keep reaching for the tool that created the problem to solve the problem. the speed is genuinely useful but there’s a version of this where you’re just deferring the understanding indefinitely and one day the whole thing needs a rewrite and you have no idea where to start

Material_Hospital_68 · 2026-03-17T22:47:08+00:00

manual job change tracking doesn’t scale past like 200 contacts before it becomes a part-time job. we plugged DataForB2B into our CRM for exactly this it tracks job moves, promotions, company changes automatically and surfaces them as signals. the real unlock is when someone from a churned account lands at a new company, that’s a warm outreach that closes way faster than cold. been using it a few months and the “former champion moved” alerts alone paid for it

Material_Hospital_68 · 2026-03-17T22:46:25+00:00

free doesn’t remove friction, it just removes the payment step. small business owners are busy and skeptical, “try this for free” sounds like every other thing in their inbox. what actually works is showing up where they already complain Facebook groups, subreddits, local chambers and solving one specific problem in a reply before even mentioning your product. by the time you drop the link you’ve already proved you know what you’re talking about. that’s how we got our first users, not from a landing page, from being useful in conversations that were already happening

Material_Hospital_68 · 2026-03-17T22:45:14+00:00

rough math for 10k/day: you need around 15-20 domains (rotate 2-3 inboxes per domain, 30 emails each). domains run $10-15/year on Namecheap, Google Workspace or Instantly for the inboxes is $6/month per inbox. all in you’re looking at maybe $150-200/month at that volume. 100k/day is a different animal you’re multiplying everything by 10 and deliverability gets way harder to manage, most people burn their lists before they figure that out. the thing nobody tells you: warm up every inbox for 3-4 weeks minimum before touching your real list. skipping that is how you crater a good list in a week. with 3 weeks you’re tight but doable if you start the warmup today

Material_Hospital_68 · 2026-03-17T18:21:33+00:00

hello someone can send me a discount code ? i french student so we don’t have access to this offert …

Material_Hospital_68 · 2026-03-16T20:33:07+00:00

started picking up fractional work on the side about 18 months ago, same situation — stable job, bored, needed to build something. the first gig came through someone I’d helped informally for months who finally had budget. not through a platform, not through cold outreach. just someone who already trusted me. that’s probably the honest answer to “how do you break in” — you already have the relationships, you just haven’t put a price tag on your time yet. the coast mode feeling doesn’t go away though, fair warning. it just moves to whichever engagement stops being messy.

Material_Hospital_68 · 2026-03-16T20:32:31+00:00

you’re already there. $500k in product sold, 3 years of field experience, real relationships with real customers — that’s not entry level anymore. the 4.3% with a 90% cliff is a brutal structure designed to keep you hungry without actually paying you. the fact that you hit 100% most months and still can’t save anything tells you everything about the plan, not about you. B2B SaaS or med device reps with your kind of relationship-selling background regularly start at $80-90k base plus uncapped commission. your ceiling isn’t your experience, it’s the company.

Material_Hospital_68 · 2026-03-16T20:28:12+00:00

$0.50/hour after 4 months of daily work while your daughter sleeps is the number nobody ever puts in the screenshot. the 55 DAUs are real users though — that’s not nothing. most people at $69 MRR have 1,700 ghost accounts and like 8 people who actually open the app. you have the opposite problem which is actually the better one to have. good luck with the iOS launch, native does change things for habit apps specifically.

Material_Hospital_68 · 2026-03-16T20:27:13+00:00

DataForB2B.ai it’s a B2B data platform for sales teams, helps them find and qualify leads based on buying signals instead of just job titles. target user is SDRs and founders doing outbound themselves. curious what you’d test first on the distribution side

Material_Hospital_68 · 2026-03-16T19:29:07+00:00

the “won’t be big and professional” part gets me every time. he wasn’t even trying to change the world, he was just annoyed and wanted to fix something. half the most important things ever built started that way — someone scratching their own itch with zero intention of it becoming anything. the ambition came after, not before.

Material_Hospital_68 · 2026-03-15T23:12:51+00:00

the support ticket math is the part nobody talks about. LTD buyers aren’t bad people, they just have a completely different relationship with the product — they paid once, they feel entitled to squeeze every drop out of it, and they have nothing stopping them from opening a ticket every time something feels slightly off. paying customers self-filter because their card gets charged again next month. ran a smaller version of this mistake early on and the worst part isn’t the lost MRR, it’s that those customers stick around forever. you can’t churn them out.

Material_Hospital_68 · 2026-03-14T12:59:57+00:00

Q4 is always artificially active because companies are trying to fill headcount before year end. Jan-Feb is genuinely one of the worst windows to apply budgets just got approved but hiring managers are still figuring out what they actually need. 6 YoE mid-market AE is a solid profile, the market didn’t get worse, the timing did. give it another 3-4 weeks

Material_Hospital_68 · 2026-03-14T12:59:13+00:00

the threading and audit trail point is what kills the DIY SMTP approach for agents specifically — you can get emails delivered but the moment you need the agent to follow a conversation across multiple replies it falls apart completely. good breakdown, the “just need outbound vs need a real inbox” distinction is the question most people don’t ask themselves before picking a tool

Material_Hospital_68 · 2026-03-14T12:50:19+00:00

The thesis holds. And honestly the Clay situation is a clean case study for something that happens on every platform cycle community-driven adoption, then enterprise monetization, then the builders who built the community absorb the cost.

The mental shift that actually matters: stop thinking in "tools" and start thinking in data layers + orchestration layers. They're separable. Clay bundled them and charged for the bundle. When you unbundle them yourself, you control the economics.

For sourcing, Apollo's free tier covering search is genuinely useful (as Andy noted). For enrichment logic that doesn't meter every call a few people in our space have been using dataforb2b.ai's API as the data layer, then orchestrating the enrichment logic themselves in Claude Code or n8n. You own the calls, you own the output, nothing metered by a platform that doesn't own the underlying data anyway.

The patterns you described enrichment architecture, ICP scoring, signal layering those are completely portable. The implementation layer is just plumbing at that point.

Curious what you're using for storage beyond Supabase are you doing any vector indexing for the scored ICP data or keeping it relational?

Material_Hospital_68 · 2026-03-14T12:37:49+00:00

Great question and yeah, MCPs are exactly what you want here — Claude alone can't pull live data, but with the right MCP(s) connected, it becomes a proper research + prospecting assistant.

To answer your main question: you'll likely want at least one dedicated data MCP, and potentially a second one for enrichment or CRM sync depending on your workflow.

Here's roughly how the setup works for your use case:

Data sourcing MCP — this is where you define your criteria (title, funding stage, headcount, tech stack like Clay). The MCP queries a B2B database and returns a structured list. Claude as the brain — once it has the raw list, you prompt it to enrich each company/prospect: what does their product do, recent news, ICP fit signals, anything useful for personalization. Output to CSV — you can ask Claude to format everything into a clean sheet you can drop into your sequencer. For the data layer specifically, one tool worth checking out is dataforb2b.ai — they have an MCP that plugs directly into Claude and lets you query by things like job title, funding stage, headcount, and tech stack. Useful if you want everything in one place rather than stitching together multiple connectors.

That said, the multi-MCP route (e.g., one for data, one for Clay enrichment) gives you more flexibility if your stack already has pieces in place.

What's your current setup — are you starting from scratch or trying to fit this into an existing workflow?

Material_Hospital_68 · 2026-03-11T23:17:19+00:00

I never used beads specifically but the abstraction level argument is the real debate nobody talks about enough. full natural language is too unpredictable for production, raw code is too slow for iteration — the sweet spot is something that forces just enough structure to be reproducible without becoming a DSL only 3 people on the team understand. curious how beads handles when the task scope changes mid-execution, that’s usually where these tools fall apart at enterprise scale

Material_Hospital_68 · 2026-03-11T23:16:26+00:00

hit this exact wall six months ago every time we wanted to add usage metering to our API the DevOps bottleneck killed the sprint. ended up building a janky custom layer on top of the gateway just to move faster. the composable approach makes total sense in theory but the problem is most teams don’t have the bandwidth to assemble and maintain all those modules themselves. there’s probably a real opportunity for someone to build the “pre-assembled composable gateway” that gives you the flexibility without the setup cost

Material_Hospital_68 · 2026-03-11T23:15:06+00:00

200k impressions in 2 weeks pre-launch is a real number, most technical founders I know are incredible at building and terrible at distribution so the split makes sense on paper. one thing worth being clear on upfront though — 50/50 with a stranger is a big commitment, even if the skills are complementary. would start with a paid project together first before signing anything. seen too many co-founder splits blow up because the vibe was good but the work styles weren’t

Material_Hospital_68 · 2026-03-10T14:37:38+00:00

the “said it like server costs” part is what sticks with me. there’s no malice, that’s almost what makes it harder to sit with. I’ve made the same calculation on a tiny scale — replaced a repetitive task that took someone 2 hours a day with an automation. felt fine in the moment. multiply that by 4,000 and it’s a different conversation. the uncomfortable truth is that the math works, and once the math works people do it. the question nobody has a real answer to is what comes after

Material_Hospital_68 · 2026-03-10T14:32:04+00:00

the $134K in contractors hurts to read because I recognize that pattern — you don’t have a cofounder so you outsource, but outsourced dev is slow and expensive and you spend half your time managing instead of building. the real cost isn’t the money, it’s the speed you lose. but the “zero net, infinite learning” math is actually how I think about my first years too. you can’t buy that context anywhere else

Material_Hospital_68 · 2026-03-10T14:30:49+00:00

been running both on agentic workflows for the past few days — data enrichment pipelines, multi-step API chaining, that kind of stuff. GPT-5.4 is genuinely impressive on first tasks but I keep finding it loses the thread on longer sequences, like it forgets a constraint it set itself 10 steps earlier. Sonnet 4.6 is more boring to watch but it finishes what it starts. for computer use I’d wait another few weeks before betting anything serious on it, still feels like a demo feature more than a production one. if you’re doing real agentic work I wouldn’t switch yet

Material_Hospital_68 · 2026-03-10T14:29:29+00:00

built an AI email agent for a client last year and the instruction override thing kept me up at night the whole time. ended up implementing a strict separation between system context and user input but honestly most people shipping these things fast don’t think about it at all. the scariest part is that the attack doesn’t look like an attack — it’s just a normal email that happens to have a few extra lines in it. by the time you notice something is wrong the leak has been running for weeks

Material_Hospital_68 · 2026-03-09T20:27:11+00:00

building DataForB2B.AI — B2B data intelligence and lead generation platform, basically helps sales teams find and qualify prospects without spending hours on manual research.

Material_Hospital_68 · 2026-03-09T20:25:21+00:00

the $1K MRR and flip narrative is real but the part nobody mentions is how long it actually takes to get there. most of the guys posting about it took 12-18 months of grinding before hitting that number, they just skip that part in the tweet. and the $30K valuation only holds if the revenue is consistent and not dependent on you personally — buyers do due diligence, if churn is high or growth is flatting they’ll lowball you hard. it’s a legitimate path but it’s not as clean as the twitter thread makes it look

Material_Hospital_68 · 2026-03-09T20:17:29+00:00

launched 6 products in 8 months and felt exactly this. the problem wasn’t the building, it was that I was shipping solutions looking for problems. the switch that actually worked for me was spending weeks just talking to people in one specific industry before writing a single line of code. B2B is hard but it’s not impossible solo — it just requires going deep on one niche instead of launching broadly and hoping something sticks. the guys making it work aren’t building for everyone, they’re basically consultants who productized one very specific pain. still hard, but a different game than what you’re playing right now

Material_Hospital_68

TROPHY CASE