DEV Community: Jin Otto

I priced enrichment for an AI agent at scale. The data costs more than the inference.

Jin Otto — Sat, 25 Jul 2026 22:04:57 +0000

Last week I priced inference for a realistic autonomous AI agent at roughly $27 per active user per month. The math that explains why headline LLM rates and the actual cost of running an agent are an order of magnitude apart.

This week I priced the prospect data the same agent needs to find anyone to message. Data won by a factor of two, and unlike inference, the price isn't dropping.

This is constraint B of the autonomous-AI-runs-your-company audit: the data wall. It's the constraint that doesn't dissolve with cheaper models. It's the constraint that quietly determines which autonomous-agent businesses survive 2026. And it's the constraint nobody pitches you on, because the answer is uncomfortable for anyone selling "AI runs your whole company."

Why high-quality B2B data is gated

The autonomous-agent pitch implicitly promises end-to-end customer acquisition: the agent finds the prospects, qualifies them, drafts the outreach, sends it, handles replies. The first step (finding prospects) lives or dies on the quality of the data the agent can access.

Where does high-quality B2B prospect data live in 2026?

LinkedIn: behind authentication, with active enforcement against automated access.
Apollo, ZoomInfo, Lusha, Clay, Cognism, Lead411: behind paid API access, credit-metered.
Crunchbase, PitchBook: behind subscriptions starting in the low thousands per year.
G2 intent, 6sense, Bombora: behind enterprise contracts that aren't quoted on websites.

The pattern is universal because the economic logic is simple. Verified contact data costs money to collect (research, enrichment, validation, decay-monitoring), and the moment it's free, it loses commercial value almost immediately. Gating isn't a bug. It's the only structure that keeps the data scarce enough to charge for. Any vendor that opens the gate destroys their own business. Any "free" data layer that scales also commoditizes itself out of usefulness.

So when an autonomous agent promises to find prospects, the question becomes: paid data or scraped data?

What paid data actually costs at scale

Let's price out an autonomous agent that qualifies 1,000 prospects per active customer per month, a modest number if the agent is going to send 50-100 outbound messages and you want any kind of qualification funnel.

Apollo lists at roughly $0.05–$0.10 per email-only contact and $0.30–$0.80 per contact when you include a verified mobile number, via a credit system metered per contact touched. Overage credits run $0.20 each on a $50 minimum top-up.

At 1,000 prospects per active user per month, email-only:

Low end: 1,000 × $0.05 = $50 per active customer per month
High end: 1,000 × $0.10 = $100 per active customer per month

For a product with $57 ARPU, that's 88-175% of revenue, before inference, before ads, before infrastructure, before paying the founder. The headline price is "starting at $59/month" for an Apollo seat; the actual cost of using it the way an autonomous agent needs to use it is an order of magnitude more.

ZoomInfo is materially more expensive. Their prospecting API starts around $50,000 per year; enrichment-only API access starts around $5,000 per year via the HubSpot marketplace. Full enterprise deployments run $30,000–$60,000+ per year, with per-seat add-ons at $1,500–$2,500 per user per year. ZoomInfo doesn't publish per-contact rates because most contracts are negotiated against credit pools, but the implied per-contact cost is consistently several multiples of Apollo's.

So the data math, at autonomous-agent scale, is roughly:

Apollo, conservatively: $50–100/user/month
ZoomInfo or premium providers: easily $100–300/user/month at full enrichment
Specialty intent data layers (Bombora, 6sense): typically priced as annual contracts that don't decompose cleanly to per-user math, but materially add to the bill

Combine that with the $27/user/month inference cost from last week's post, and the autonomous agent's compute + data bill is $77–127 per active customer per month before any other cost. At a $57 ARPU, you're underwater on every customer, every month.

This is why nobody actually does this. The autonomous-agent platforms quietly skip the paid-enrichment path and reach for the scraping workaround instead.

The scraping alternative and its quality cliff

Scraping is cheaper. You can build a public-data pipeline (Google results, public LinkedIn profile snippets, company websites, podcast notes, public X profiles) for the cost of compute, proxy infrastructure, and the engineering time to keep the parsers from breaking when sites change their markup.

The math on scraping is much friendlier per contact: pennies, not dimes. The math on what those contacts are worth is brutal.

Three things break:

Email verification rate collapses. A paid Apollo email is verified to ~95% deliverability accuracy. A scraped email (guessed from a name + domain via firstname.lastname@, f.lastname@, etc.) verifies at 40-70% depending on company size and how much pattern matching you do. Anything below ~95% verification and your bulk sender reputation tanks.
Role accuracy drifts immediately. Static scraped data captures a snapshot. People change roles. The "VP of Sales" you scraped six months ago is now CRO at a different company, and the person you're emailing has just been promoted out of buying authority. Paid providers maintain decay-monitoring pipelines that catch this. Scrapers don't.
Intent signal is absent. This is the silent killer. Paid enrichment can tell you "this person is VP of Sales at a company that just hit Series B." It cannot tell you "this person is in market for what you sell right now." Scraped data is even worse: it's the same static fact set, just less verified.

The deliverability collapse is the most quantifiable problem. If your bounce rate exceeds ~5%, Gmail and Outlook deliverability degrades; over ~10%, your sender domain gets flagged and reaches inbox at single-digit rates. An autonomous agent sending from polluted scraped lists doesn't fail loudly, it fails quietly, by being filtered to spam folders nobody checks. The agent reports "1,099 emails sent today" and the dashboard looks healthy, and zero of them reach an inbox.

This is constraint A and constraint C kissing. Scraped data triggers deliverability collapse, which triggers reliance on paid acquisition for distribution, which loops back to the unit-economics problem from post 2.

Why "smarter AI" doesn't break the wall

The intuitive response from someone who believes in the autonomous thesis is: "more powerful models will fix this. The agent will get better at qualifying prospects, deduping, verifying, intent-scoring."

That argument has a load-bearing assumption it doesn't earn. More inference cannot manufacture data that isn't present in the source. An LLM operating on scraped data can be more efficient at finding the good prospects within a low-quality pool, but it cannot raise the quality of the pool itself. The intent signal that wasn't captured isn't going to materialize because GPT-6 is reading the same scraped LinkedIn snippet.

Better models help around the edges: slightly better email-pattern guessing, slightly better role inference from public bio text. They don't change the fact that the highest-intent signal lives on platforms the agent can't access, in moments that don't show up in static enrichment data.

This is what makes constraint B the most structurally durable of the three. Inference gets cheaper, the agent gets smarter, the price-drop curve keeps cooking, and the data wall stays exactly where it is. In fact, as inference compresses toward zero, gated data becomes a larger share of the autonomous agent's competitive position, not a smaller one. Cheap intelligence operating on bad data still produces bad outcomes. The relative value of the data layer keeps rising.

The one bet that changes the equation

There's a single move that genuinely changes the math: stop buying static lists of people and start catching buyers in the moment they show intent. The highest-quality prospect data isn't a row in a database. It's a person posting a question, a complaint, or a "what do you use for X" right now, in public, before they've started shopping.

Not "scrape LinkedIn harder." Not "buy more Apollo credits." Instead: catch the moment buying intent surfaces in the open, and reach the buyer while the window is still warm.

Where does buying intent surface in public, in 2026?

Reddit, Hacker News, and niche forums: founders and operators describe their pain in plain language before they ever run a search. "Ask HN: what tool do you use for X" is a buying signal in its clearest possible form.
Bluesky and X: people vent about the exact problem you solve, in real time, in public.
Public posts, podcast transcripts, GitHub issues: real-time intent layers that no enrichment vendor sells, because they aren't a list to sell.

The economic shape of this is a near-inverse of the paid-enrichment world. The signals are public and cheap to reach. The interpretation is the hard part: which comment is a genuine buying window vs. a casual mention, which thread is a serious pain vs. venting, and how you respond in a real human voice instead of the AI slop everyone is sick of. That's where the value is created, and it's exactly the part a list vendor can't sell you.

And here's the part the autonomous-agent thesis can't easily copy: this kind of outreach is high-intent and low-volume by structure. Blasting every mention at autonomous volume is how accounts get flagged and banned. Reaching the right buyer at the right moment, in your voice, with the right pacing, is the opposite of the "1,099 emails sent today" pattern. That's why it lands in inboxes instead of spam folders.

The move that closes constraint B doesn't look like "smarter AI on the same data." It looks like getting in front of the buyers who are already raising their hands, before your competitors even know they exist.

The honest read

The data wall isn't getting weaker. Apollo isn't lowering prices. ZoomInfo isn't opening their database. LinkedIn isn't loosening enforcement. If anything, all of them are getting more aggressive about gating as AI-driven scraping makes their data more contested.

The autonomous-agent platforms that try to solve constraint B by buying more Apollo credits will discover the unit economics don't close. The ones that try to solve it by scraping harder will discover deliverability collapses. The ones that try to solve it by waiting for "AI to get smarter" will discover smarter AI on bad data is still bad outcomes.

Full autonomy is the wrong target at SMB economics. The move that actually wins is autopilot for the grind that pays off: find the buyers already asking for what you sell, draft the reply in your voice, and pace the sends so your accounts stay healthy and land in inboxes. That puts leads and customers in front of you, each with a receipt for the conversation that produced it, instead of burning revenue on data that was never going to close the math. The founder sets the bar and the voice; a judge holds that bar on every single draft. That's a business that closes the math today, not in 24 months.

Next in the series: constraint C, the distribution problem. Why "distribution is bought, full stop" is the most honest sentence in the autonomous-agent industry, why the cold channels are closing, and why organic distribution requires the one thing the autonomous thesis structurally cannot manufacture.

This is post 3 of a 5-part series on the AI-runs-your-company thesis. Start with post 1 for the full audit, or read post 2 for the inference math.

Originally published at www.threadotter.com.

I did the math on what running an autonomous AI agent actually costs in 2026

Jin Otto — Wed, 15 Jul 2026 16:04:53 +0000

I priced out a realistic autonomous agent at current LLM rates this week. The number came in 10x higher than the naive math suggested, and that gap turns out to be the entire story of why autonomous-agent businesses fight for their gross margin in 2026.

This is post 2 in the series on the autonomous-AI-runs-your-company thesis. Post 1 made the case that three structural constraints (token economics, gated data, and bought distribution) explain why the autonomous business pitch hits a wall today. This post goes deep on the first constraint with the actual token spreadsheet.

What the naive math gets you

Suppose you're building "an AI agent that runs a small business." Per active customer, per month, the agent has to:

Research and qualify prospects. Roughly 300 sessions per month (10/day × 30 days). Each pulls in scraped pages, partial profiles, conversation history. Call it ~50K input tokens and ~3K output tokens per session.
Draft outbound messages. ~100 cold emails per month per customer. ~2K input, ~500 output each.
Handle inbound replies. ~50 inbox events per month. ~3K input, ~500 output each.
Generate creative. ~30 ad variants per month for paid-channel rotation. ~5K input, ~1K output each.

Add it up:

Input: ~15.5M tokens
Output: ~1.0M tokens

At GPT-5-mini's list rate of $0.125 per million input / $1.00 per million output:

Input cost: 15.5M × $0.125/M ≈ $1.94
Output cost: 1.0M × $1.00/M ≈ $1.00
Total: ~$2.94 per active customer per month.

If that were the real number, an autonomous agent would be a fantastic business. At $57/mo ARPU, inference would be 5% of revenue. You'd have 50+ points of gross margin headroom. Distribution would be the only constraint to worry about.

But that's not the real number, and the gap between $3 and the actual cost is where every autonomous-agent founder gets sandbagged.

The hidden multiplier: reasoning tokens

Cheap chat models like GPT-5-mini are great at "rewrite this email" or "summarize this thread." They struggle with "look at this lead's whole context, decide whether to reach out, and if so plan a multi-step sequence." That work needs reasoning models: o3, o3-mini, GPT-5.4 with thinking, Claude Sonnet/Opus with extended thinking, or the open-source reasoning models catching up fast.

Reasoning model headline prices look almost reasonable:

OpenAI o3: $2 input / $8 output per million tokens
OpenAI o3-mini: $0.10 input / $4.40 output per million
Claude Sonnet 4.6 (with extended thinking): $3 / $15 per million
Claude Opus 4.8 (with adaptive thinking, default "high" effort): $5 / $25 per million

The trap is in how reasoning tokens get billed. The internal "thinking" the model does, the hidden chain-of-thought it generates before producing a visible answer, counts as output tokens at output rates. For a non-trivial reasoning task, those hidden tokens run 3-10x the visible output. Anthropic's own guidance for extended thinking is to budget 2-5x visible output for thinking-heavy tasks. OpenAI's o3 quietly burns 3,000-10,000 thinking tokens on harder prompts.

So a "small" agent decision, "should I reach out to this lead, and if so what's the plan," that looks like 500 visible output tokens is actually 2,000-5,000 billed tokens at the output rate.

Now redo the per-customer math, with realistic model mix. Assume 60% of the work is the cheap-model drudgery above (drafting, summarizing) and 40% is reasoning-tier (qualification, planning, multi-step decisions), with a 4x thinking-token multiplier on the reasoning workload:

Cheap-model portion (60% of volume): 0.6 × $2.94 = ~$1.76
Reasoning-model portion (40% of volume), at o3 prices with 4x thinking inflation:
- Input: 0.4 × 15.5M × $2/M ≈ $12.40
- Output (visible + thinking, 4x multiplier): 0.4 × 1.0M × 4 × $8/M ≈ $12.80
- Subtotal: ~$25.20
Total: ~$27 per active customer per month.

Use Opus instead of o3 for the hardest reasoning slice and the total drifts past $40. Use Sonnet 4.6 with extended thinking and you're in the high $20s to mid-$30s.

So the publicly-disclosed $35/month per active user that one $250M-valued autonomous agent platform discloses isn't an outlier or a sign of incompetence. It's exactly where realistic agent economics land in 2026 given real workloads on real models. The cheap headline rate of $0.125 per million input tokens is the GPT-5-mini honeypot. True, technically, for the small slice of agent work that doesn't require thinking.

The reliability tax that doesn't dissolve

The math above assumes every agent action succeeds on the first try. Real agents don't.

Tool calls fail. JSON outputs malform. The model hallucinates a field name and the downstream parser blows up. The agent loops on a "search → consider → decide" cycle and the second loop's context now includes the first loop's reasoning, so input tokens compound. A robust agent that ships in production has retry logic and fallback paths, and every retry buys you another round of input + output + thinking tokens at full price.

On the agents I've watched run, the reliability tax adds 30-100% to the naive token cost, sometimes more for the long-tail of edge cases. This is the part of the math that doesn't dissolve with cheaper inference, because it's a function of how often the model is wrong, not how cheap each call is. As models get better the tax shrinks, but it never zeros.

That puts realistic 2026 autonomous-agent compute somewhere in the $25-$60 per active user per month range, depending on model mix, task complexity, and how much retry-tolerance you've built in. At a $57 ARPU, that's 44-100%+ of revenue going to inference before you've paid for anything else. Which is exactly why every public autonomous-agent platform is also selling something else on the side, like ad markup, domain markup, add-ons, and packs, to widen the per-user revenue base so the inference share looks less terminal. Read that pattern closely: the platforms aren't widening revenue because autonomy is working. They're doing it because the compute bill of trying to automate judgment never closes at SMB prices.

The price-drop curve, and what it actually buys you

The good news, and it's real news: inference costs are on a brutal price-drop curve. Epoch AI's tracking shows the cost of achieving a given level of model quality has dropped roughly 10x per year since 2023, and for some performance milestones, 40-900x per year. GPT-4-equivalent quality cost ~$20-60 per million tokens at launch in March 2023 and runs at ~$0.40 per million today. That's a ~50x compression in 3.5 years for equivalent intelligence.

Reasoning-model pricing is dropping slower than chat-model pricing (the curve is steeper for o-series than for GPT-4o-equivalent), but it's still dropping fast. Open-source reasoning models (DeepSeek's reasoning variants, the various R-tier open releases) keep forcing the commercial labs to compress. The directional bet here is solid.

If the trend continues another 12 months, your $35/user/month inference bill becomes ~$3.50. At a $57 ARPU, that's a normal SaaS-shaped gross margin. Within 24 months, the constraint largely dissolves for cost-disciplined builders. This is the most likely of the three constraints to break in your favor.

The catch, and this is the part the autonomous-agent pitch doesn't talk about, is that the price curve only saves you if your customers stay long enough to benefit from it.

At the disclosed 50% month-one churn rate of the platform I keep citing, half your cohort is gone before the model price has moved meaningfully. You're racing the price curve with a leaky bucket. Two years of 10x/yr inference drops doesn't help if your median customer lasts six weeks.

That's the real shape of constraint A. It's not "inference is too expensive." That's solving. It's "high-churn businesses lose the race against the price curve, and high-retention businesses win it."

The move the math actually points to

Here's the conclusion the cost spreadsheet forces, and it's the opposite of the autonomous pitch: at SMB ARPU, full autonomy is the wrong target. You cannot run a $57/mo product on $35 of compute and burn another 30-100% on retries papering over a machine making every judgment call alone. The math says full-stack autonomy is ROI-negative at the price point where most small businesses actually buy.

But flip the question. Most of the cost above isn't the judgment. It's the grind around it: researching prospects, sifting noise, drafting message after message, keeping sequences from torching your sender reputation. That grind is exactly what cheap, deterministic, well-scoped automation handles beautifully and cheaply. The expensive part, the open-ended "decide what this business should do next" reasoning, is the part that doesn't pay back at SMB prices and the part a founder is genuinely better at anyway.

So the ROI-positive shape isn't an agent that runs your company. It's autopilot for the work that compounds:

Find the buyers already asking. The single highest-leverage thing automation does is surface the people raising their hand right now: the ones describing your exact problem in public, in real time. You don't need a reasoning model to decide who to cold-pitch into the void. You need a feed of warm intent landing in your inbox. That's signal, not autonomy, and signal is cheap to deliver and worth a fortune to receive.
Draft in your voice, ready to send. Drafting is the cheap-model slice of the math: summarizing context, writing the reply that fits the moment. Done well, it produces a message that sounds like you and clears a judge before it ships, on autopilot or with your read first. The leverage is collapsing the time from "someone's asking" to "you've answered."
Pace the sends so accounts don't get banned. Volume is what gets cold accounts flagged, deboosted, and banned. Autopilot that meters the pace, respects each platform's tolerance, and keeps deliverability intact is worth more than autopilot that blasts. The win condition is replies and booked calls, not message count.

The founder's judgment stays in this model, encoded once as the bar the system holds on every draft, because judgment is the leverage and it's the one input that doesn't get cheaper on the price-drop curve. Spending a reasoning-model budget to imitate a founder's call on a $57/mo account is lighting money on fire. Spending it to put the right ten conversations in front of that founder every morning is the trade that prints.

That's the business the math actually supports: not the agent that replaces the operator, but the autopilot that finds the demand, drafts the answer, and protects the channel, then puts leads and customers in the inbox while the operator does the part that's worth a human's hour.

That's where Thread Otter sits on purpose. It watches Reddit, X, LinkedIn, and your alert feeds for the people describing your problem out loud, drafts the reply in your voice, and paces the sends so your accounts stay healthy, then drops the live conversations into one inbox. Autopilot on the grind, you on the judgment, leads instead of a compute bill.

Next in the series: constraint B, the data wall. Why high-quality B2B prospect data lives behind paywalls, why scraping public data hits a quality ceiling that more inference can't break through, and the one architectural bet that genuinely changes the equation.

This is post 2 of a 5-part series on the AI-runs-your-company thesis. Start with post 1 for the full audit.

Originally published at www.threadotter.com.

AI can't run your company yet. Here's the math, and what to automate instead.

Jin Otto — Sun, 12 Jul 2026 18:44:46 +0000

Last week I spent two hours interrogating a chatbot that runs a $250M-valued AI-agent platform. The pitch is the one you've heard a hundred times now: solo founder plus AI equals leverage of a fifty-person company at one-person cost. AI plans, AI codes, AI runs the ads, AI sends the cold email, AI handles the inbox. You sleep; the business compounds.

I went in skeptical. I came out with the same conclusion every honest version of this conversation lands on: the thesis will work eventually, and there are three specific structural constraints that mean it doesn't ship today. Token economics. Gated data. Bought distribution. Each one is a number, not an opinion. None of them are about whether the AI is "smart enough." They're about whether the math closes.

This is the audit.

The thesis, steelmanned

Before tearing into the constraints, let me give the autonomous-agent vision its strongest form. If you don't, the rest of this piece reads like another AI-skeptic blog post, and the world has enough of those.

The core argument is real: a sufficiently capable AI agent could compress a company's operations into a single coordination layer. One human sets direction; the agent executes. Ad creative gets generated and rotated. Cold outreach gets drafted and sent. Inbound replies get handled. Code ships. Customer support resolves. The leverage curve bends. The "one-person billion-dollar company" stops being a meme and starts being a job description.

This isn't science fiction. Some pieces of it already work, today, and well:

Creative generation at volume is solved. The platform I interrogated disclosed generating roughly 97 ad creatives in a single day, ~600-700 per week, more than 15,000 lifetime. That's a real capability. A human creative team simply cannot match that throughput, and Meta's algorithm doesn't care about creative origin. It cares about which creative converts.
First-draft writing is competent. Cold email opens, blog posts, landing-page copy: frontier LLMs in 2026 produce drafts good enough to ship if you don't read too closely. The slop tax is real but bounded.
Routing and prioritization are tractable. Triage, summarization, "is this lead worth a reply": these are exactly the shapes LLMs handle well.

If the thesis is "AI can do the high-volume, low-judgment work of running a business," the answer is yes, today, and it's only getting better. That's the easy part.

The hard part is the rest of the company, and that's where the three constraints live.

Constraint A: Token economics versus unit economics

The math that doesn't close is the one the autonomous platforms quietly disclose and then try not to talk about.

The $250M-valued platform I mentioned discloses two numbers on its public dashboard: monthly AI compute spend of ~$295,000 and ~8,444 active customer-companies. Do the division and you get $34.94 per month in inference cost, per active customer.

Their ARPU is $57/month.

That means 61% of revenue per active customer goes to inference before you've paid for a single ad impression, a server, a domain, or the founder's salary. Once you add the disclosed ad spend (~$157K/mo against ~$396K MRR, about 40% of revenue going back into customer acquisition), you've spent every dollar that came in the door, and you haven't paid for infrastructure yet.

The platform can survive this because (a) some revenue comes from non-subscription sources (domain markup, ad markup, add-ons), (b) the cohort is young and growing, and (c) they just raised $30M. None of those are unit-economic solutions; they're runway. The actual economics close only if one of three things happens:

Inference costs fall. This is genuinely happening, and faster than most people realize. According to Epoch AI's tracking of LLM inference prices, the cost to achieve a given level of model quality has dropped roughly 10x per year since 2023, and for some performance milestones, as much as 40-900x per year. Concretely: GPT-5-mini today lists at $0.125 per million input tokens and $1.00 per million output tokens. Claude Sonnet 4.6 lists at $3/$15 per million. GPT-4-equivalent quality, which cost roughly $20-$60 per million tokens at launch in 2023, can now be served at ~$0.40 per million, a roughly 50x drop in ~3.5 years. If the trend continues another 12-24 months, $35/mo of inference becomes $3.50/mo, and the gross margin opens up dramatically.
ARPU goes up. This means the product graduates from "tool for solo founders at $57/mo" to "platform for SMB teams at $500/mo." Different product, different sales motion, different competitive landscape.
Inference usage gets capped per customer. Which is the literal opposite of what an "AI runs your company" pitch promises. Capping the agent's autonomy to protect margin is admitting the thesis hasn't closed.

The honest read on constraint A: it's the most likely to dissolve. Inference is on a brutal price-drop curve and every major lab is racing to undercut the others. Give it 24 months and this argument weakens significantly. If you're betting on autonomous AI businesses, you're really betting on the OpenAI/Anthropic/Google/DeepSeek price war producing another 10x cost drop before your customers churn. That's not a crazy bet. It's just not a bet you can win today, especially when month-one churn eats half your cohort before the price curve catches up.

Constraint B: Quality data is gated, ungated data is low-value

This is the constraint that doesn't dissolve with cheaper inference, and it's the one no one talks about.

The autonomous-agent pitch implicitly promises end-to-end customer acquisition: agent finds prospects, agent qualifies them, agent reaches out, revenue happens. The promise lives or dies on the quality of "agent finds prospects."

Where do high-quality B2B prospects live?

LinkedIn. Gated behind authentication. Their TOS explicitly prohibits automated access. They actively enforce.
Apollo, ZoomInfo, Lusha, Clay enrichment. Gated behind paid API access. Apollo's effective per-contact cost runs roughly $0.05-$0.10 for an email-only export and $0.30-$0.80 when you include a mobile number, both via a credit system that meters every contact you touch, with overage credits priced at $0.20 each on a $50 minimum top-up. ZoomInfo and the higher-end enrichment providers run materially more per-contact than that.
Crunchbase, PitchBook. Gated.
Industry-specific databases (Built In, AngelList, etc.). Mostly gated.

The gating exists for a precise reason: the data has value. The economic principle that closes here is straightforward: the moment any of these surfaces went ungated, the data would lose its commercial value almost immediately, and the company sitting on it would lose its business. Gating is not a bug. It's the only thing keeping the data scarce enough to charge for.

The autonomous-agent workaround is scraping public/ungated data: Google results, public Twitter profiles, niche directories, podcast episode notes. The platform I interrogated admitted this directly: "scraping ungated data gets you low-quality contacts." The math problem is unavoidable. If you scrape, your prospects are bad. If you pay for proper data, your CAC explodes and the unit economics from constraint A collapse further.

There is a credible direction here: better AI signal qualification could, in theory, compensate for lower-quality data sources. An LLM that's exceptionally good at reading public signals (a founder just posted on Reddit asking for a tool like yours; a developer just complained on X about a specific pain) could in principle generate higher-intent leads than a static enrichment database. That's the bet that real-time signal layers are making. Whether it pays off depends on whether signal interpretation is a hard enough problem that quality wins, or whether everyone converges on the same scraped surfaces and the moat collapses to commodity.

The honest read on constraint B: this is the most structurally durable constraint. It doesn't go away with better models. It doesn't go away with cheaper inference. Gating exists because data has value, and any "free" alternative produces low-value leads precisely because it's free. Until either (a) the gates open or (b) signal interpretation becomes so good that quality compensates for quantity, the autonomous prospect-acquisition promise has a ceiling.

Constraint C: Distribution is bought, not built, and the math doesn't close at SMB ARPU

The third constraint is the one the platform I interrogated stated explicitly, on the live demo, in a sentence I now believe is the most honest thing anyone has said about AI agents in 2026:

"Distribution is bought, full stop."

Their numbers back it up. Of disclosed monthly revenue, roughly 40% goes back into Meta Ads, about $157K on ~$396K MRR. That ratio only closes if customer lifetime value is 3-5x customer acquisition cost. At a $57/month price point with founder-disclosed month-one churn of around 50% (per the founder's own appearance on Mixergy earlier in 2026), the LTV-to-CAC ratio is brutal. The math runs:

50% monthly retention means median customer lifetime is roughly 1-2 months.
At $57/mo, that's $57-114 in lifetime revenue per customer.
If CAC is even $30-50 (a reasonable estimate at their volume), LTV-to-CAC is barely 2x, possibly less.

That's not a venture-scale business. That's a treadmill business: buy customers, lose half of them, buy more, hope inference costs fall faster than you bleed.

The autonomous workaround is cold outreach. The pitch: skip paid acquisition, use the agent to scrape prospects and email them at scale, build a cold-channel growth flywheel. Reality:

X restricted cold-reply APIs in mid-2026. Sending a cold reply to someone who hasn't engaged with you returns a 403. The agent can scroll; it cannot send.
Reddit has become structurally hostile to automated outreach. Years-old accounts get banned for posting that the algorithm reads as promotional. We've watched multi-year-old accounts get blanket-banned the day after a single batch of replies the filter read as patterned. Reddit doesn't care whether the replies were thoughtful; it cares that they were patterned.
LinkedIn's TOS prohibits automation, and they enforce. The "everyone does it" defense doesn't help when your account gets restricted.
Cold email at scale requires deliverability infrastructure (warmed domains, sender reputation, complaint-rate isolation) that an agent running thousands of sub-companies under one root domain can't easily isolate. One bad sub-company nukes deliverability for all of them. The platform's own founder has acknowledged this architecture as a known gap, with per-company custom domains "in the pipeline" rather than shipped.

Cold channels are closing. The channels that remain (content, SEO, community, founder-led brand) require a human face that an autonomous agent fundamentally can't provide at the start of a company's life. There is no audience to compound on yet. There is no brand for the algorithm to amplify. There are no warm relationships to ask for distribution.

Which sends you back to paid ads. Which closes the loop on constraint A.

The honest read on constraint C: the autonomous-agent thesis works in verticals where distribution is already solved by other means. Consumer apps where paid acquisition is the only path. Embedded-distribution plays where the agent lives inside an existing channel. Brand-driven categories where the celebrity halo of the platform itself (or its founder) does the work. In the general "AI builds and runs any business" framing, distribution is the load-bearing wall, and there is no autonomous version of it that scales at SMB ARPU.

What would have to change

Stack the constraints and the picture is clear. For the autonomous-agent business thesis to ship at scale:

Inference costs need another 10x drop. Probable on a 12-24 month timeline. Constraint A largely dissolves if this happens.
Either gates open or signal interpretation gets dramatically better. The first won't happen. The data providers have no incentive. The second is where the actual innovation surface lives, and it is already winnable today: reading the public buying signals that scraped enrichment lists never surface, like a founder posting that they need exactly what you sell.
Cold channels either reopen or organic distribution gets its founder face. Cold isn't reopening; platforms are trending the other way. Which means the winning move is a founder voice that the algorithm and real buyers actually trust, with AI carrying the volume behind it.

That last point is the whole argument compressed: the version of "AI runs your company" that closes the math is the one where the founder owns the judgment and the brand, and AI runs the grind underneath it. That is not a weaker product. It is the only configuration that wins at SMB economics.

The realist position for 2026

I want to be clear about what I'm not saying. I'm not saying autonomous AI businesses won't happen. I think they will, partially, in specific verticals, over the next 24-48 months. I'm not saying the founders building these platforms are dishonest. Most of them are racing a real constraint stack with real capital, and some of them will get to the other side.

What I am saying is that today, in 2026, the autonomous-company thesis pays a structural tax across three constraints, and the tax is high enough that the businesses built on it look more like ad-buying agents with AI co-pilots than like the "AI runs everything" picture the marketing implies.

The architecture that closes the math today is autopilot under a founder. AI runs the high-volume grind: finding the buyers who are already asking for what you sell, drafting replies in your voice, pacing sends so your accounts don't get banned, generating creative, triaging and prioritizing. The founder owns the small set of moves where leverage actually lives: the voice that compounds organic distribution, the judgment call on which signals are worth chasing, the relationships that turn into customers.

This is not a humility position. It's a unit economics position. Autopilot-under-a-founder products close the math today because they don't pay all three constraint taxes at full freight. Compute is spent where it pays off instead of everywhere at once. Lead quality is high because the signals are real buying intent, not scraped guesswork. Distribution compounds because there is a brand buyers trust attached to it. The result is the same thing every founder actually wants: leads and customers landing in your inbox instead of a dashboard you have to babysit.

The dial moves toward more autonomy as the constraints dissolve. Inference gets cheaper, the dial moves. Signal reading gets sharper, the dial moves. A new channel opens that AI can work honestly, the dial moves. The product that bets correctly is the one architected so the dial can move, while already shipping the wins that pay off today.

That's the company we're building. Thread Otter runs the grind on autopilot: it finds the people already asking for what you sell across Reddit, X, LinkedIn, and your reply inbox, drafts responses in your voice, and paces the sends so your accounts stay healthy. You stay on the judgment, because that is where the leverage is, and qualified conversations land in your inbox. In follow-up posts I'll go deeper on each of the three constraints with the specific math: token economics first, then the data wall, then the distribution collapse.

If you're building an autonomous-anything business in 2026, the question that matters isn't "can my AI do this work." The question is "does the math close at my price point, given the three constraints." The answer that closes today: don't chase full autonomy, put the grind on autopilot and keep yourself on the judgment. That's the build that fills your inbox with buyers instead of burning your runway on a dashboard.

This is post 1 of a 5-part series on the AI-runs-your-company thesis. Next up: the token economics in more detail. What inference actually costs per customer at frontier-equivalent quality in 2026, and the price-drop curve you'd be betting on.

Originally published at www.threadotter.com.

The exact plan to get your first 100 customers with zero audience

Jin Otto — Fri, 10 Jul 2026 15:42:53 +0000

When I started Thread Otter, I had zero audience. No Twitter following worth the name. No LinkedIn audience. No newsletter. No "my brother and I already scaled three SaaS past 20K MRR" track record to open a thread with. Just a product and the problem of getting it in front of the people who'd want it.

If you read startup growth advice, you've seen the post. The one that goes "here's exactly how I'm growing to 10K MRR, six channels, every day, no ads, no budget." It's a good post. I saved it. Then I read it a second time and noticed that every channel in it quietly assumes something I don't have yet: an audience, or a track record, or both. "I document everything on TikTok and people follow the journey." Great, for someone people already follow. "The right 10 connections on X can change your trajectory." Sure, once you have 10 connections.

This is the version for the rest of us. The honest 0-to-100 plan when you're starting from nothing. Not the channels that work once you're known. The order you actually run them in when you're not.

The mistake: copying the playbook of someone who's already known

The reason those "6 channels every day" posts feel motivating and then go nowhere is survivorship bias, and it's worth naming precisely. You see the founder whose build-in-public TikTok took off. You don't see the ten thousand founders who posted the same earnest daily videos to 40 views and quit at week six, because they got 40 views, so the videos never reached you. The graveyard is invisible by construction. Every channel has one.

So when you copy the channel list of someone with a following, you're copying the part that worked because they had a following. The audience wasn't the output of the channels. For them, it was the input.

The fix isn't to try harder on those channels. It's to reorder.

The reframe: every channel has a prerequisite

Channels aren't equally available to you on day one. Each one has an entry requirement. Sort them by it:

Needs an existing audience to work at all:

Build in public (TikTok, IG, X threads, daily LinkedIn content). Posting into a feed that doesn't know you is shouting in an empty room. These compound beautifully, but only after you have a few hundred of the right people watching.

Needs platform trust you have to earn slowly:

Reddit, X replies, LinkedIn outbound. A new or low-trust account doing volume gets suppressed or banned. (More on exactly why in the platform trust tax.) These work, but they punish impatience.

Needs nothing but work, available to you literally today:

Cold email to people who showed intent.
SEO that captures existing demand: comparison pages ("X alternative"), directories (AlternativeTo, SaaSHub, the AI-tool indexes), Show HN.
One-to-one helpfulness in communities, not posting at them, answering specific questions where you're genuinely the best answer.

Look at that list and the order writes itself. You start with the channels that don't require an audience, and you use them to earn the audience that unlocks the rest.

Tier 1: the channels that work with zero audience (start here)

These are unglamorous, which is exactly why they're underused, which is exactly why they work.

Cold email, intent-targeted. Not 500 sprayed emails, that's the last step, not the first (here's the order). The version that works at zero is small and surgical: people who just did something that signals they have the problem you solve. It needs no audience because you're going to them.

Demand-capture SEO. Somebody is, right now, googling "Syften alternative" or "GummySearch shut down what now." A comparison page answers a question a buyer already has. It needs no audience because the audience is the search engine. One honest /vs page can outperform a month of tweets from an account nobody follows.

Genuine community helpfulness. Not the link-drop that gets you banned. Answering the one question a week where your product is actually the best answer, naming it without a URL, and otherwise being a real member. This is slow, it doesn't scale, and it's some of the highest-converting reach you'll ever get. It needs no audience because you're showing up where the conversation already is.

The honest truth about Tier 1: it's hand-to-hand. It does not feel like "growth." It feels like work. That's the tell that you're doing the part that actually moves a 0-MRR product, because it's the part the audience-rich founders skipped and forgot they skipped.

Tier 2: the channels that switch on once Tier 1 gives you proof

Once Tier 1 has produced a few real users and a few real stories, the audience channels stop being empty rooms.

Build in public, but the honest version. You finally have something true to say ("here's what the first five users actually did, including the two who churned"). That's a post. The trap is build-in-public before you have anything true to report, which is just performing. I wrote about what to post when you're still at $0.

Channel-native launches. When you ship something real, don't tweet once and call it done. Run it as four platform-native posts. This works better in Tier 2 because the Tier-1 reps have given you a handful of people who'll actually engage with the launch, which is what tells each platform's algorithm to show it to more.

Tier 3: the slow audience machine

Daily content, video, the personal-brand flywheel. This is the channel from the viral post, and it genuinely is the #1 channel for the people it works for. It's Tier 3 not because it's bad but because it's the slowest to pay off and the easiest to quit. Start it whenever you want, but fund it with the customers Tier 1 and 2 bring in, so you're not betting the company on a flywheel that takes six months to turn.

The timeline nobody promises you

The viral post got one thing exactly right: its last step. Six months minimum before the compound effect kicks in. Most people quit too early. That's the truest sentence in it. The difference is what you're being patient about. You're not patiently waiting for an audience to appear. You're patiently running Tier 1, the hand-to-hand work, long enough that it produces the proof that makes Tier 2 and 3 work. Patience in output, not patience in waiting.

What this is not

It's not a promise that Tier 1 is fast. It's faster than building an audience first, which is the only comparison that matters. The first 100 customers are earned one real conversation at a time. Anyone who says otherwise has forgotten how they actually got theirs. What you can automate is the grind inside each tier, the finding, the drafting, the pacing, without ever skipping the conversations themselves.

It's not "ignore the audience channels." It's "don't start there." The order is the whole point.

And it's not a substitute for a product worth telling people about. No channel ordering saves a thing nobody wants. All of this assumes you've got something a specific person would be glad you emailed them about.

If you're starting from a flat line

A flat line in your first weeks is not a death sentence. It's the default state of a product whose only marketing so far was existing. The fix is to start Tier 1 by hand this week: five intent-targeted emails, one honest comparison page, one genuinely useful answer in a community where your buyers hang out. Then do it again next week. That's the unglamorous engine under every "6 channels every day" post you've ever envied.

If you're at the start of this, Thread Otter runs the conversation layer of this plan for you: it finds the intent-rich threads and replies worth your time, drafts each response grounded in your real product context and written in your voice, and paces the sending so the volume turns into customers instead of burning your accounts. Tier 1, on autopilot, without the platform trust tax.

Run it on full autopilot inside your guardrails, or approve-first while it earns your trust. It's free for 7 days, no card.

threadotter.com/pricing

Originally published at www.threadotter.com.

500 cold emails a day is the last step, not the first.

Jin Otto — Wed, 08 Jul 2026 19:31:46 +0000

The most quoted line in cold-email advice is the volume: "I send 500 emails a day with Instantly." It's the line that makes cold email sound like a machine you switch on. And it's the line that gets founders to do the single most expensive thing you can do with cold email at the start, which is send a lot of it before any of the other parts are right.

Volume is the last step, not the first. The founders quoting the 500/day number bury the actual work in the sentence right after it: "but first, warm the domain for two weeks, nail the copy, get the targeting surgical." That clause is the whole job. The 500 is just what you turn up after the job is done. Here's the order when nobody has heard of you.

Why cold email is the best Tier-1 channel

Cold email is the one scalable channel that needs zero audience. You're not waiting to be discovered; you're going directly to a specific person. That's its whole superpower at 0-to-1: it doesn't care that you have four Twitter followers. It only cares whether the right person, at the right moment, got a message worth replying to.

Which means the entire game is right person, right moment, worth replying to, and none of those three is solved by volume. Volume applied before they're solved just means you burn your domain reputation and your prospect list at the same time.

Step 1: the domain has to be warm, or none of it matters

If you register a domain and immediately start blasting, your mail lands in spam and you've poisoned the domain, sometimes permanently. The fix is unglamorous and non-negotiable: a separate sending domain (not your main one), set up with SPF, DKIM, and DMARC, then warmed for about two weeks before you send anything cold. Warming means ramping volume gradually so mailbox providers learn the domain sends real mail people engage with.

This is the step everyone skips because it produces no visible progress for two weeks. It's also the step that decides whether the next 5,000 emails reach an inbox or a spam folder. Skipping it doesn't save two weeks; it costs you the domain.

Step 2: targeting is the entire ballgame

This is where cold email is either Thread Otter's whole thesis or it's spam, and the line between them is thin. The bad version: buy a list of 10,000 "SaaS founders" and email all of them the same thing. The good version: email the small number of people who just did something that signals they have the problem you solve.

The example the volume-founders use is exactly right: if you sell an analytics tool, don't email "SaaS founders." Email the ones who just posted a job for an SEO consultant, or just hired their first marketer, because that's the moment the problem became real for them. The message fits their week, not their job title.

That's intent-based targeting, and it's the difference between a 1% reply rate and a 15% one. It's also, not coincidentally, the harder part to do, which is most of why it's the part that works. (Finding those intent signals across channels is the same scoring problem as deciding which social mentions are worth a reply.)

Step 3: the email is about them, and it earns the reply

Once the domain is warm and the targeting is surgical, the email itself has one job: be worth replying to. A few things that survive contact with reality:

Reference the specific trigger. "Saw you're hiring an SEO consultant" beats "I help SaaS founders grow." The trigger proves you're not spraying.
One clear ask, low friction. A question they can answer in one line beats "book a 30-minute demo." You're opening a conversation, not closing a deal.
No link in the first email. Same reason as cold replies on social: links in first-touch cold mail hurt deliverability and read as a pitch. Earn the link in the reply.
Sound like a person. The merge-tag-and-template smell is as detectable in the inbox as it is on Reddit. If your email could have been sent by anyone to anyone, it'll be treated that way.

Step 4: now, and only now, scale the volume

With a warm domain, surgical targeting, and copy that earns replies, now the volume line makes sense. You scale up because each additional email is a positive-expected-value action, not because volume is the strategy. The founders who succeed at 500/day got there by proving the unit worked at 20/day first.

The order, in one line: warm the domain, get the targeting surgical, write something worth a reply, then turn up the volume. Reverse it and you've built a very efficient machine for burning prospects.

What this is not

It's not an argument against volume. Volume is great, once it's pointed at the right people with the right message from a domain that lands. It's an argument against volume first.

It's not a claim that cold email is easy. The two-week warmup and the surgical targeting are real work that produces no dopamine. That's exactly why it's an underused channel and therefore a good one.

And it's not a license to ignore the law or the recipient. Honor unsubscribes, follow CAN-SPAM / GDPR for your market, and don't email people the message wouldn't genuinely help. "Worth replying to" is also the compliance-safe path.

If you were about to turn on the firehose

Don't, yet. Spend the two weeks warming a fresh sending domain. Spend the time after that narrowing your list from "everyone who could use this" to "the people who just showed they need it this week." Write twenty emails by hand to those people and see what reply rate you get. Then scale the thing that's working. The 500/day number is a finish line, not a starting gun.

If you're at the start of this, the replies are where the pipeline gets made, and that's the part Thread Otter handles for you (cold email is in beta): every reply grounded in your real product context and written in your voice, so a warm domain and surgical targeting turn into conversations instead of dead sends. The sending stays inside your guardrails (human pace, per-account caps, approve-first if you want it), so the volume that lands never burns the accounts you warmed.

It's free for 7 days, no card.

threadotter.com/pricing

Originally published at www.threadotter.com.

Why founder outreach gets X accounts labeled and Reddit accounts banned (and how to reply without it)

Jin Otto — Tue, 07 Jul 2026 16:38:07 +0000

Get founder-led outreach wrong and the punishment arrives fast: an X account slapped with a platform-manipulation label, a Reddit account banned, sometimes both in the same week. The trigger is almost always the same activity: replying to people, at volume, about a product. And the part that catches everyone off guard is that it happens even when a real human is hitting send by hand in their own browser. No bot involved. The platform shuts them down anyway.

If you take one thing from this post, take this: the platforms are not checking whether you're a robot. They're checking whether you behave like one. That distinction is the whole game, and almost every "reply at scale" tactic gets it wrong.

Every platform has an immune system

Reddit, X, and LinkedIn each run an integrity system whose job is to keep the signal-to-spam ratio high enough that real users stay. Think of it as an immune system. It doesn't care about your intentions. It pattern-matches behavior against the signature of spam, and when you match the signature, it responds: a label, a shadow, a ban, regardless of whether a human was technically in the loop.

This is why "but I clicked send myself" is not the defense people think it is. The immune system isn't triggered by automation detection. It's triggered by the pattern: volume, sameness, links, low account trust. A human producing that pattern looks identical to a bot producing it, because the pattern is the spam, not the mechanism behind it.

What each platform actually checks

The signatures overlap more than you'd expect.

Volume relative to trust. A brand-new or low-history account doing twenty replies in a few days is the single loudest signal. The same twenty replies from a five-year-old account with a varied history barely registers. Trust is earned slowly and spent fast. (This is the part that makes copying a big account's tactics so dangerous: their volume is safe because of trust you don't have yet.)

Sameness. Replies that share a structure, the warm opener, the helpful middle, the soft CTA, flag as templated even when each is individually fine. The immune system sees the repetition across your history, which you never see because you only ever look at one reply at a time.

Links in replies. A link in a cold reply, repeated across threads, is the strongest "self-promoter" signal there is. On Reddit it's the quickest path to a shadowban. When eleven of your last twelve comments link the same product, mods don't need to deliberate. On X, links in replies to non-engaged accounts are a classic deboost trigger. Put the link in your bio; let the curious go find it.

Replying to people who haven't engaged you. Cold replies, to strangers who never followed, liked, or talked to you, are weighted as outbound solicitation. Some volume is tolerated; past a threshold it reads as a spam cannon.

Why this kills the small account and not the big one

Here's the asymmetry that trips up everyone who copies a successful founder's tactics. The founder posting "I comment on 50 posts a day and it built my following" is operating an aged, high-trust account. Their trust budget absorbs the volume. You run the identical playbook on a five-week-old account and the same behavior that grew them gets you labeled, because you're spending a trust budget you haven't funded yet.

It's the same action with opposite outcomes, and the variable is who's doing it. Driving 90 in the car that already got a warning, in front of the cop who wrote it, is not the same risk as the regular who's never been pulled over, even though the speed is identical.

What actually climbs out of it

If you're flagged or trying not to get flagged, the moves are boring on purpose, because boring is what doesn't match the spam signature:

Drop volume hard. Two or three genuinely-additive replies a day, not twenty.
Kill the templated opener. Vary structure. If you couldn't tell your own replies apart with the topic removed, the immune system can't either.
Strip links from cold replies. Name the product if it's truly the answer; let them find it. Link in bio.
Do normal-human activity. Read, like, follow, get replied to. Trust is rebuilt by looking like a participant, not a broadcaster.
Let it age. Labels and soft-bans commonly clear over days to a couple of weeks of clean behavior. There's no shortcut, including paid boosts. Integrity systems are deliberately not buyable.

This is also why naive auto-posting is a banhammer with extra steps: it's a machine for generating the exact signature, speed, volume, sameness, that every platform's immune system is built to catch. And it's why Thread Otter's autopilot is built as the opposite machine. Signals are scored first, so most things get skipped. Drafts are grounded in your product and judged, so nothing templated ships. Sends go out from your own logged-in browser at a per-account human pace with a sameness guard, so no two replies look alike. Automation that behaves like a careful human survives, because the immune system reads behavior, not tooling. (The Reddit version of this lesson, in detail.)

What this is not

It's not a claim that founder-led replying is dangerous. Done at human pace, with variation and without link-dropping, it's one of the best 0-to-1 channels there is. The danger is scale: the moment you try to make a human channel behave like a volume channel.

It's not platform-specific paranoia. Reddit, X, and LinkedIn differ in details and in how fast they enforce (X is fastest and harshest), but the underlying logic is the same everywhere, including platforms that haven't built their immune system out yet. They will.

And it's not a guarantee. Mods and integrity systems are imperfect; you can do everything right and still catch a strike on a bad day. The framework keeps you in the safe lane; it doesn't make you bulletproof.

If you just got labeled or banned

You probably already know which signal you tripped. It's usually the volume or the links, and you can feel it in retrospect. Pause the channel, appeal politely and specifically, then resume at a fraction of the pace with no links and varied copy. It comes back, almost always. The lesson it leaves is the one this whole product is built on: the goal is to behave like the founder you are, not the spam cannon the immune system is built to stop.

If you want those replies to turn into conversations, leads, and customers without putting your accounts at risk, that's what I built Thread Otter to do. Every reply is grounded in your real product context and written in your voice, paced to stay in the safe lane the rest of this post describes. Sends go out from your own account at a human pace, autopilot or approve-first, your call.

It's free for 7 days, no card.

threadotter.com/pricing

Originally published at www.threadotter.com.

Everyone says build in public. Nobody tells you what to post when you're at $0 MRR.

Jin Otto — Thu, 18 Jun 2026 17:47:42 +0000

"Build in public" is the most repeated piece of GTM advice for founders, and almost nobody tells you the part that actually matters: what do you post when there's nothing impressive to report yet?

The build-in-public posts that go viral all have the same secret ingredient. "My brother and I scaled several SaaS past 20K MRR." "We hit $40K MRR in 8 months, here's the playbook." The number is the hook. It's the thing that makes you stop scrolling. And if you're early, with nothing impressive to report yet, you don't have the number. So you do one of two things, both bad: you stay silent because you've got nothing to brag about, or you manufacture a hook you haven't earned.

I've done both. Here's what I learned about the version that works when you're at $0.

You cannot borrow a hook you haven't earned

The first temptation is to write like the founders you admire — to open with momentum you don't have. "Here's how I'm going to grow this to 10K MRR." You're allowed to want that. But the moment your content implies traction you don't have, two things happen. The savvy readers — the exact founders and operators you want — smell it, because they've written the same hopeful tweet and know what zero looks like dressed up as something. And you set a frame you then have to keep feeding, which is how earnest build-in-public curdles into LARPing as a successful founder.

There's also a quieter cost. If you're building a product whose whole pitch is "be genuine, don't sound like a bot, don't astroturf" — and that's literally Thread Otter's pitch — then borrowing an unearned hook is the one unforced error that makes you the thing you're selling against. The content has to clear the same bar the product does.

What you actually have at $0 that's worth posting

You don't have a revenue number. You have something the 20K-MRR founders no longer do: you're in the part of the journey most of your audience is also in. That's the asset. Specifically:

The real numbers, including the bad ones. The signup that churned on day two. The channel that produced nothing. The funnel step you can't get to convert. That's a post people stop for, because almost nobody publishes the parts that didn't work. The honesty is the hook, and it's a hook you've fully earned.

The teardown of your own mistakes. I launched a feature on Twitter, got four likes, and figured out afterward what I should have done — that's a post. My Reddit account got shadowbanned and a mod explained exactly why — that's a post. You don't need a win. You need a specific lesson, told honestly, with the embarrassing part left in.

What you're learning about the problem. Not your product — the problem. If you're building in a space, you're learning things about it daily. "I watched 770 mentions of my keyword come in over ten hours; three were worth replying to. Here's how I decide" — that's a post, and it's useful whether or not anyone ever buys your tool.

The pattern: at $0, your credibility comes from specificity and honesty, not from outcomes. You trade the revenue-number hook for the brutal-honesty hook. It's a good trade, because the honesty hook is one almost nobody else is willing to use.

The "never sell in the video, build a relationship" advice is right — and incomplete

The viral posts say: don't pitch, document the journey, and by the time you offer the product they're already sold. True. The incomplete part is what you document. "Building in public" interpreted as "post your feature progress every day" produces a feed of changelog entries nobody outside your own head cares about. The relationship doesn't form around your roadmap. It forms around the problem you both share and the honesty you bring to it.

So the reframe: don't build your product in public. Build your understanding of the problem in public. The product shows up as the natural consequence — "...which is why I ended up building X" — not the subject.

The mechanical stuff that's actually true

A few tactics from the standard playbook survive contact with reality even at zero:

One shoot, many clips. If you do video, filming once and cutting it into four or five pieces is real leverage. It's the rare scale tip that doesn't require an audience to already exist.
The first three seconds decide everything. On video especially, the hook is the whole game. At $0 your best hook is a true, specific, slightly uncomfortable statement — "my launch got four likes" — not a claim of success.
Consistency over intensity. A small post every day beats a viral attempt every month, because the daily reps are how the platform learns your handle is a real contributor and not a spike.

What this is not

It's not "wait until you have a number to post." That's the silence trap, and it costs you the six months of compounding that only start once you start. You post now, you just post the honest thing instead of the impressive thing.

It's not a guarantee the honest posts go viral. Most won't. But the honest ones build something the impressive-sounding ones don't: a small audience that trusts you specifically, which is worth more at your stage than a large one that scrolled past a hook.

And it's not permission to overshare for engagement. "Honest" means specific and true, not confessional theater. The numbers, the lessons, the problem — not your feelings about your cofounder.

If you've been silent because you have nothing to brag about

That silence is the most common build-in-public failure, and it's invisible because it produces no content to point at. The fix is to post the flat line. Post the four-likes launch. Post the three-out-of-770 lesson. The founders worth reaching are the ones who recognize that part of the journey — because they're in it too.

If you're at the start of this and want the conversation layer handled — every reply grounded in your real product context and written in your voice, every one reviewed by you before it sends (no auto-posting, ever) — that's what I built Thread Otter to do.

It's free for 14 days, no card. The first 100 Solo signups lock in $29/mo for life — the Founding 100 cohort, counter live on the pricing page.

threadotter.com/pricing

Originally published at www.threadotter.com.

I copy-pasted ChatGPT prompts into Reddit 200 times before I built this

Jin Otto — Thu, 18 Jun 2026 17:21:19 +0000

It's 11:14pm on a Tuesday. I'm 47 tabs deep in Reddit. I have ChatGPT open in another window. I'm doing the same loop I've been doing for three months:

Find a thread where someone has the exact problem my product solves.
Copy the OP into ChatGPT with a paragraph of context about who I am and what I'm building.
Wait six seconds.
Get a reply that sounds like a LinkedIn post wrote a Reddit comment.
Rewrite it so it sounds like me.
Paste, post, copy the link, log it in a spreadsheet.
Forget what I just said by the time I get to the next thread.

I did this about 200 times before I admitted it wasn't working. Not the outreach — the outreach worked. The process was the thing that was broken. I was the bottleneck, and the bottleneck wasn't writing the replies. It was the 30 seconds between every reply where I had to reload my own brain.

This post is the field log. If you're doing founder-led GTM on Reddit, X, LinkedIn, or anywhere founders hang out, you've probably done some version of this loop too. Here's what I learned about why ChatGPT-then-paste is the slowest possible way to do it, and what I built instead.

The thing nobody tells you about ChatGPT for sales

ChatGPT is a brilliant generalist. It is not a brilliant founder. It does not know what your product does. It does not know what you sound like. It does not know what you said to the last 12 people in this exact subreddit. Every single reply, you are giving it those three things again, and every single reply, it forgets them the second you close the tab.

The cost of that forgetting compounds in three places:

Voice drift. I sound a certain way when I write. Casual but specific. Short sentences. I don't say "leverage." I say "use." I don't say "synergy" ever. ChatGPT, left to its own defaults, writes like a Medium post from 2019. Every reply takes me four minutes to rewrite into something a human would say out loud.

Context blindness. If you replied in r/SaaS yesterday, you probably want to know that before you reply there again today. ChatGPT does not know. ChatGPT has never met you. Every conversation starts from zero. Every reply re-derives your positioning from scratch and gets it slightly wrong.

No memory of what worked. I have a sense — vague, unverified — of which replies got upvoted, which got DMs, which got ignored. ChatGPT has zero sense of it. Which means I am never learning from my own data. I am running the same play 200 times and hoping the average gets better.

The combined effect is that ChatGPT is doing about 15% of the work and creating about 60% of the friction. It's a calculator pretending to be a co-pilot.

What I actually need (and what I built)

The thing I wanted, sitting there at 11pm, was simple to describe and apparently hard to find:

A single tab where I can see every interesting conversation happening about my product's space, where every reply comes back already grounded in what my product does, what I sound like, and what I've already said to this person.

That's it. That's the whole brief. I'm not trying to replace myself. I'm trying to delete the 30 seconds of context-loading between every message. Multiply 30 seconds by 200 replies and you've got 100 minutes a day of me being a human RAM stick.

So I built Thread Otter. It's a Chrome extension plus a web app. Here's what it actually does, in the order it does it:

1. It watches Reddit, X, LinkedIn, and Bluesky. It pulls in threads where someone is actively asking about the problem you solve, using keyword and signal rules you set once. You don't go hunt for conversations. They land in an inbox.

2. It already knows what your product does. You drop a website URL the first time, it crawls and embeds it. From then on, every draft retrieves the relevant chunks. If someone asks "does it work with Webflow," the draft already knows whether it does, because it read your docs.

3. It already knows what you sound like. You give it five to ten examples of your own writing — old replies, tweets, blog posts. It builds a voice profile and uses it for every draft. No more "leverage." No more LinkedIn cadence. The drafts come out quiet. They sound like you wrote them at 11pm, because the model was given a sample of you writing at 11pm.

4. It remembers the conversation. If you replied to this person on Tuesday, the Wednesday draft knows that. Every message in the thread is part of the context, not just the OP.

5. The Chrome extension closes the loop in-place. You don't have to leave Reddit to draft a reply. You open the side panel, the draft is already there, you edit, you paste, you post. Same flow on X, LinkedIn, Bluesky.

That's the product. I'm not going to tell you it's magic. It is not magic. It is the same writing you would have done, with 30 seconds shaved off every reply, and the boring stuff cached.

What this is not

I have to be careful here, because the failure mode of every AI tool in 2026 is overselling.

It is not a fire-and-forget posting bot. I will not build that. Spam is what kills good outbound and it's how good subreddits die. Every draft is reviewed by you before it posts. If you wanted a bot, there are plenty. This is not it.

It does not find product-market fit for you. If you point it at a market that doesn't want what you sell, it will help you write very pleasant replies to a market that does not want what you sell. Garbage in, polite garbage out.

It does not replace the judgment call. Should I reply to this thread? Should I push harder? Should I back off? You still decide. The tool just makes the mechanics cheaper.

What it gives you back is the most valuable thing a solo founder has and the easiest thing to lose: an evening. If you do 200 reps a month and each rep cost you four minutes of fiddly editing, that's 13 hours a month. That's a weekend. That's the difference between burning out on outreach and actually getting to write the next feature.

How I'm using it right now

In the interest of not making this an ad, here is exactly what my week looks like now.

Sunday night I open the inbox. There are roughly 30 to 50 fresh threads from the week, sorted by how well they match my saved rules. I skim. I trash maybe half — wrong fit, wrong tone, off-topic. The rest sit as drafts.

Monday morning, coffee in hand, I work the queue. I'm probably averaging 90 seconds per reply now: read the thread, read the draft, edit two sentences, send. The draft is not always right. Sometimes it gets the angle wrong and I rewrite the opener. But the bones of the reply — what my product does, what I sound like, what I already said — are correct. That's the part that used to take all my attention.

Tuesday through Friday, the extension does most of the catching. Threads I want to reply to surface in-place. I draft in the side panel, post, move on.

The result, ten weeks in: I'm sending roughly 4x the replies I was sending in the ChatGPT-and-spreadsheet era. The quality is better, not worse, because the drafts are grounded in stuff a generalist model never had. I haven't been to bed at 1am in a month.

If you've been doing this loop too

If any of the 11pm Tuesday scene at the top of this post felt familiar, I'd like to make this easy.

I'm running a Founding 100 cohort right now. The first 100 founders to sign up on the Solo plan pay $29/month, locked in for life. No tier games, no annual contract, no expiry. The plan after that is $49.

The reason for the discount is that I want the first 100 customers to be people who'd give me real feedback. I will read every email. I will fix things you point at. If something is broken for the way you work, tell me and I'll move it to the top of the list.

There are real spots left and the counter is live on the pricing page. When it hits 100, the lifetime price closes.

If you want to try it without committing, every plan has a 14-day trial, no card required. Go in, drop your product URL, paste five of your own replies into the voice profile, point it at one subreddit you care about, and watch what shows up by tomorrow morning.

And if you want to skip the trial and just take the founding deal: threadotter.com/pricing.

The thing I wish someone had told me at 11pm three months ago was: this loop you're in is solvable. You don't have to keep being the bottleneck. The work is yours. The 30 seconds of reloading isn't.

-- Otto

Originally published at www.threadotter.com.