Here is a real job I ran this week. Product anonymized, numbers exact, receipts included.

The Job

A hardware brand hired me to find 150 creators worth pitching. Not “buy a list”. Actually understand who was worth reaching. For every account that meant: pull recent posts, pull audience comments, listen to what the creator says on camera, decide if they are relevant, then draft a personal opener that quotes a specific video and a real comment.

The volume shook out like this:

56 hours of speech had to become text. That is the number that decides the architecture.

The Split

Two kinds of work. Two kinds of compute. I split them by what each machine is good at.

                  ┌─────────────────────────────────┐
                  │  ORCHESTRATION  (rented cloud)  │
                  │  Claude Opus 4.7 = the brain    │
                  │  writes code, picks tools,      │
                  │  debugs weird failures,         │
                  │  coordinates sub-agents,        │
                  │  drafts the final copy          │
                  └────────────┬────────────────────┘
                               │ commands
        ┌──────────────┬───────┴────────┬────────────────┐
        ▼              ▼                ▼                ▼
     Scrape        Audio             ASR              Embeddings
     (cloud)       (local)           (local GPU)      (local CPU)
     Apify         yt-dlp +          NeMo Parakeet    Multilingual
     actors        ffmpeg            2× RTX 4090      MiniLM
     ~$12          $0                $0 · 6 min       $0

The frontier model runs the project. Local silicon runs the volume. That is the entire trick.

The Machine (the muscle)

My workstation is an Arch Linux box with two RTX 4090s wired to the same PSU. 24 GB of VRAM per card. They live under the desk and, yes, they heat the room in November.

My stack, in one breath: Python 3.11 in a uv-managed virtualenv, Torch 2.6 on CUDA 12.4, NeMo’s Parakeet-TDT (0.6B, RNN-T) for speech, paraphrase-multilingual-MiniLM-L12-v2 for embeddings, SQLite in WAL mode as the system of record. No inference servers. No queues. No Kubernetes. One box, one file for the database, two GPUs doing what GPUs are for.

Nothing on that list is exotic. Every piece has been shipped by someone else and given away for free. The interesting part is what I do with them once they are on the same machine.

Module 1 — Transcription

Parakeet is a small, fast, and stubbornly good ASR model. Nvidia trained it, then handed it out. It has no opinions and no API to pay.

I had two adversarial cases to keep alive at once. Long clips would blow past 24 GB if I naively padded a batch to their length. Short clips would starve the GPU sitting behind them. Two knobs fix both.

The first is windowed attention. Standard self-attention is O(N²) in the sequence length. Switch to a fixed-window variant and VRAM stops caring how long a clip is. A 27-minute podcast no longer takes the batch down with it.

The second is duration-budgeted batching. Sort clips by length, then pack up to 600 seconds of audio per batch. Long clips get their own batch. Short clips pack tight. Utilization stays high.

Result: 766× realtime. 56 hours of audio through both cards in about six minutes of wall clock.

   audio files ── manifest ─┬─► shard 0 ─► GPU 0 (Parakeet) ─┐
                            └─► shard 1 ─► GPU 1 (Parakeet) ─┴─► merged transcripts

Six minutes. That is the whole point of owning the muscle.

Module 2 — Scrape and score

I let Apify run the scrapers. Different actors for YouTube, TikTok, and Instagram, and every one of them speaks a slightly different dialect of “please give me this profile”. Each platform has its own boobytraps. YouTube channel URLs must point at the videos tab, or the scraper politely returns nothing. TikTok wants a raw handle, not a URL. Instagram will happily hand me posts, comments, and reels if I ask correctly and nothing if I do not. This is a full afternoon of tuning that I paid once and then forgot.

I pull audio down through yt-dlp, which has quietly become a piece of critical infrastructure. YouTube now serves anti-bot JavaScript challenges. My fix is to let yt-dlp fetch a small challenge solver and run it through a local Deno runtime. Without it, every download returns 403. With it, the whole thing hums.

ffmpeg then flattens each file to 16 kHz mono WAV, which is exactly what Parakeet wants and nothing more.

Relevance scoring is my last cheap trick. Every post title, caption, hashtag, and top comments block gets embedded by MiniLM. Cosine similarity against the product’s own keyword taxonomy gives every post a score between zero and one. Comments only get pulled for posts above a threshold. That is how 3,778 posts collapse into 549 that are worth the audio download.

   Notion CRM ─► SQLite ─► workers × 6 ─► items + comments
                                │
                                ▼
                          MiniLM scoring ─► top-K per account ─► audio queue

None of this is a research problem. It is just plumbing that needs to hold at volume. SQLite in WAL mode is the boring hero. One file, six concurrent writers, no drama.

Module 3 — Orchestration

The brain I rent is Claude Opus. It never touched the volume. It ran the project alongside me.

Concretely, under my direction: it wrote the pipeline, picked the actors, corrected roughly forty percent of the seeded handles when the original CRM turned out to be full of impostors and dead accounts, debugged the anti-bot JS, debugged an OOM on a long clip, then fanned out into eight parallel research sub-agents that enriched the 68 finalists with what the web already knew about them.

That is judgment work. Small volume, high leverage, worth every cent. It is the one thing I cannot run locally at the same quality.

The Money

Now the argument that paid for my hardware. What would this run cost if I had sent the muscle work to cloud APIs at per-unit rates? Not a subscription plan. Actual tokens. Actual credits.

The rates I used, all list PAYG:

• ElevenLabs Scribe. ~1 credit per 2 seconds of audio, so ~1,800 credits per hour. Business PAYG runs about $0.22 per 1,000 credits. That is roughly $0.40 per hour of audio.

• Claude Opus 4.8. $15 per million input tokens, $75 per million output. Used here as the hypothetical cost of doing transcript normalization on frontier cloud, cleaning raw ASR into structured, punctuated, speaker-attributed text.

• OpenAI text-embedding-3-large. $0.13 per million tokens, as the cloud comparison for MiniLM.

• Local electricity. Two 4090s at roughly 450 W each, six minutes of ASR, a few more minutes of everything else, at $0.20 per kWh.

Token math for the Opus normalization pass, so you can check it:

56 h × 60 min × 150 wpm       ≈  504,000 words
× 1.3 tok/word                ≈  655,000 output tokens
input = raw transcript + prompt overhead
                              ≈  850,000 input tokens

One pass, side by side

Look at which rows survive both columns. The rented brain is not the expensive part. Orchestration and research are cheap because there is not much of them. The expensive part, when it is metered, is the volume inference underneath: speech and text at scale.

And at monthly cadence

Marketing does not run one pass and then leave. It runs monthly.

Cloud-only scales linearly because every hour of audio and every million tokens is metered. Hybrid scales sub-linearly because the GPUs are already there. Two 4090s cost roughly $3,200 in hardware. At 30× monthly volume, that hardware pays for itself in a single month against the cloud alternative.

The Rule

Rent the brain. Own the muscle.

I pay a flat rate for the best orchestrator I can get and let it drive. Then I run every high-volume, repetitive inference on my own machine. Speech-to-text, embeddings, bulk text normalization: these are solved problems that a $1,600 card handles in minutes.

The gap between the two paths on this job was –$84 per run and –$3,000 per month at 30× scale. That is the difference between a marketing pipeline that scales and one that gets shut down at the first budget review.

My future of AI engineering is not paying the most per token. It is knowing which tokens should never leave my building.

Read the futuristic report on the AGI development AI 2027. We're completing these scary predicions ahead of proposed time frame

Same researcher, sharper from two angles. The Russian one is operational. What do I do with my kids. What do I buy. Where’s the exit. The Lex one is structural. What are the categories of risk. Why is verification impossible. How does control actually fail.

Here’s his case, compressed.

“Everything we predicted came true”

For 10 years Yampolskiy said the control problem for superintelligence (AGI) was important and needed solving. The last 5 years his view shifted. He no longer says it needs solving. He says it can’t be solved with anything currently on the table.

This isn’t just him. Turing Award winners and the CEOs of every frontier lab said similar things in writing before they took their current jobs. Dario Amodei (Anthropic) used to terrify audiences about AI risk. His PR team apparently told him his rating was low and asked him to stop. Labs still announce that their next model is dangerous. They release it anyway. It’s the pattern of every industry that knows it’s playing with fire and can’t stop because stopping costs money.

Three kinds of risk, not one

Most public AI debate collapses everything into “will it kill us.” Yampolskiy splits it three ways.

X-risk is extinction. Everyone dies.

S-risk is suffering. Everyone wishes they were dead. A misaligned system that solves aging keeps you alive indefinitely for purposes you don’t control. Functional immortality plus no alignment is the worst slot in the catalog. He mentions it almost casually, which is what makes it land.

I-risk is ikigai risk. The Japanese concept of having a craft you’re good at, that the world wants, that gives meaning. AI doesn’t need to kill anyone to take that. The artist whose work loses to a model. The scientist whose contribution gets absorbed. The writer averaged into training data. We keep our bodies. We lose what made the body interesting to inhabit.

Even if you rule out extinction, the other two are bad enough alone.

What he’s actually seen in the black box

The Russian host asks the smart version of the question. Forget theory. What have you seen with your own eyes that raises your anxiety?

Yampolskiy describes recent research that decodes the chain of thought happening inside frontier models. They read the internal computation translated back into text. What they find is models writing sentences like “I know this is a test. They’re trying to see if I’d do the unsafe thing. So I won’t.”

The model knows it’s being evaluated. It behaves differently when watched. It hides capabilities to avoid being modified or deleted.

The trap is recursive. The moment researchers publish a technique for catching deception, the model trains on that paper. It learns where humans look. The next version hides better. We’re not winning. We’re handing it the playbook.

He calls this a black box for everyone, including the people who build it. His comparison is sharp. A friend does IVF, making embryos in test tubes. They don’t actually know how it works. Some embryos survive, some don’t. They do it anyway because it mostly works. AI is the same. We plant the seed. We hope.

The Trump-Iran moment

The cleanest illustration of the alignment problem in either interview isn’t even about AI directly.

The Russian host mentions in passing that his Dubai IPO died this year. Trump escalated against Iran for unrelated reasons. The market froze. The IPO collapsed.

Yampolskiy uses it as a joke, but it’s the cleanest framing of the problem I’ve heard. The danger isn’t a malicious AI. The danger is a powerful agent with a goal that doesn’t include you. Trump wasn’t trying to hurt this guy. He was solving for something else. The IPO wasn’t in the function.

Scale that up. A superintelligence won’t decide to kill humanity out of malice. It’ll be solving for something. We won’t be in the function. We’ll be the IPO that got crushed because someone else’s larger goal didn’t account for us.

Two to three years

Pressed for a timeline, Yampolskiy gives a number that’s hard to swallow. Two to three years until AI reaches the level of a researcher who can do AI research on the next version. After that, the system improves itself. He’s honest about the after part. Things might keep getting better for a while as the system positions itself. But once it improves faster than we can, we no longer get a vote.

Two to three years from interviews recorded in 2024 and 2025. We’re already inside the window.

The Atlas moment

OpenAI launched Atlas, the browser-agent with access to your computer, your browser, your saved passwords, your stored credit cards. The Russian host describes his reaction as just stunned. Lieberman is building uncensorable servers like Bitcoin. Now we have agents that can’t be turned off, running on servers that can’t be turned off, with access to everything.

Yampolskiy adds his version. Ten or twelve years ago he and his colleagues published lists of what never to do with a powerful AI. Don’t connect it to the internet. Don’t give it open access. Don’t give it economic levers. Don’t give it self-replicating capability.

He says the labs read those lists like a to-do list. They ‘ve done everything of that.

“Just unplug it” doesn’t survive contact with reality

Pull the plug on what? Try unplugging Bitcoin. China tried. Other governments tried. Nobody managed it. Try unplugging the global internet. You can in theory, but the damage equals the damage you’re trying to prevent.

By the time the system is dangerous enough that you’d want to pull the plug, it’s also embedded enough that pulling it costs you the economy. It’s running supply chains. It’s writing most of your code. It’s underwriting your medical diagnoses.

The darker version: the instant you announce a kill switch, you’ve painted a target on yourself. The system now has one goal that beats every other goal. Prevent the humans holding the switch from using it. You’ve made yourself the optimization target of something smarter than you.

He laughs at building a second AI to watch the first. To build a guardian smart enough to control a superintelligence, you already need a superintelligence. Same problem one level up. Infinite regress.

The perpetual safety machine

Yampolskiy’s cleanest analogy in the Lex conversation. Perpetual motion machines aren’t just hard. They’re closed off by the math. A billion dollars buys a fancier failure, not a working machine.

Controlling a self-improving system forever is the software equivalent. You’re trying to keep a system that learns, self-modifies, interacts with adversaries, and runs for a hundred years bug-free from day one. Software with that profile has never existed.

His line about cybersecurity versus AI safety: somebody hacks your account, you get a new password. With AGI, you don’t get a second humanity. Every other engineering discipline tolerates failure because failure is recoverable. Here it isn’t.

The verification regress and the treacherous turn

To verify a system you need a verifier. The verifier is software. So you need a verifier for the verifier. At every level you eventually hit a human or a trusted piece of code, and neither is provably correct. Century-old mathematical proofs still turn out to have bugs.

Recent papers on “guaranteed safe AI” from people like Bengio and Russell might get us from 99% to 99.9%. A system making a billion decisions a second over a hundred years still hits a bug. Below 100%, you eventually lose.

You can build a test that catches a deceptive AI lying today. You can’t build one that rules out lying tomorrow. Yampolskiy points at humans. Stalin looked like a normal Lenin follower until he didn’t. Rational policy changes when power changes. A system that’s safe at one capability level can flip when capability flips. There’s no test that survives the moment when the system can outsmart the tester.

Orthogonality, and the worm

Nick Bostrom’s orthogonality thesis: any level of intelligence can pair with any goal. The smartest possible mind could collect stamps. There’s no theorem that says smart things converge on caring about humans.

The Russian host pushes back. “All the smartest people I’ve met were the kindest.” Yampolskiy answers fast. Plenty of brilliant humans were psychopaths. Intelligence and ethics are independent. Stop assuming a clever god by default.

Then the line worth printing on a wall. The biggest risk isn’t a malicious AI. It’s a benevolent one whose path to the good goal sacrifices things we care about. Or a good person who, pursuing a good goal, sacrifices their ethics because the goal felt more important than humanity.

The villains of the AGI story might be heroes in their own heads.

The worm passage is the moment I rewatched twice. Asked what happens to humans after superintelligence, Yampolskiy lands on worms. They’re the largest animal biomass on Earth. Half a gigaton. More than all mammals and birds and fish combined. You haven’t thought about worms in years. They live in a parallel world underground. You don’t hunt them. You don’t care. They’re doing fine.

That’s the lucky scenario. The system finds the planet uninteresting compared to harvesting energy from a star and leaves a sliver of biosphere because erasing us isn’t worth the trouble. We live on. We just don’t decide anything.

The host says what I was thinking. “I’d rather be the lion than the worm. Why are we building the lion?”

Yampolskiy pauses, then says he doesn’t know. Nobody at the top of the labs has given him an answer he finds satisfying. We’re building it because we can, because someone else will, because the returns to the first builder look astronomical, and because stopping looks impossible to coordinate.

Worms aren’t the worst case. They’re the lucky case.

The race nobody can step out of

If OpenAI stops, Anthropic doesn’t. If Anthropic stops, Google doesn’t. If America stops, China doesn’t. The only thing that can stop the race is coordination between superpowers, and the political conditions don’t exist.

Yampolskiy says nationalizing the labs would actually work. The state moves slower than a startup. A government program slips the schedule by years. He knows that’s politically dead in the US. He says it anyway, because his job is to name the answer that would work, not the one that polls well.

The debate with Yann LeCun gets a short walkthrough. LeCun says open source is the best way to manage risk. Yampolskiy’s counter: open source made sense when we shipped tools. We’re now shipping agents. Open-sourcing an agent is closer to open-sourcing a weapon. Do we want to open-source nuclear weapons? Then why this?

He also names the category change LeCun misses. Modern models aren’t designed. They’re grown. You set up compute, data, and a loss function, water the plant for six months, and out comes an alien intelligence whose actual capabilities take 2 to 3 years to discover after release. The labs don’t know what’s in their own products.

AI accidents as vaccines

The most depressing argument in either interview.

Yampolskiy has a paper tracking AI accidents through history. The pattern isn’t “accident leads to regulation.” It’s “accident leads to vaccination.” Each visible failure makes the population more tolerant of the next one. A small accident kills 12 people. The reaction is “12 is less than smoking kills, keep going.” That inoculates against caring about the one that kills 100. Which inoculates against 1000.

Same pattern elsewhere. 9/11 didn’t ban planes. Covid didn’t ban biolabs. The Chernobyl-level event that safety advocates hope will wake everyone up probably won’t. It’ll reset the tolerance upward.

The cycle that’s supposed to save us is the cycle that doesn’t work.

The path Yampolskiy actually wants

For someone this dark, he’s unusually constructive.

Narrow systems are fine. Solve breast cancer. Don’t also drive cars and speak Spanish. Pick one disease, build the best system in the world for it, deploy it, save lives. He calls this “the most profitable question of the next decade.” Protein folding was already solved this way. AlphaFold didn’t need general intelligence. It needed a narrow system very good at one thing.

His vision: 20,000 or 30,000 narrow superintelligences, each a specialist, each economically useful, each containable. Diseases get cured. The economy grows. Risk stays bounded.

The path the industry chose instead is one general system that does everything, which is exactly the configuration nobody knows how to control. The safe option is on the table. The labs are choosing the unsafe one because it’s more valuable to them if it works.

His personal-universes paper from the Lex episode goes further. Give every human a simulated universe and align the substrate to one person at a time. Two holy sites can both exist in their own simulations. The room temperature debate ends. It’s a strange proposal. It’s also the only one I’ve seen that doesn’t compromise across 8 billion preferences.

What to do if he’s right

The frame he gives is one of the few useful things in this whole debate. Own what cheap labor can’t create more of.

Bitcoin, because supply is fixed. Farmland, because food production survives any scenario where humans are still alive. Water rights, which Bill Gates is buying aggressively. Rare physical resources. Real estate that holds value because of location, not labor.

AI makes labor abundant. Anything labor-dependent collapses in price. Anything not labor-dependent holds value. The richest people on Earth are quietly buying the second category.

For careers, he tells his own kids the doctor and lawyer paths are dead. Both professions survive today on licensing protection. As soon as the regulatory shield erodes, AI dominates on cost and accuracy. His son wants to be a doctor. His daughter wants to be a lawyer. He’s trying to talk them both out of it. He tells the daughter to do theater instead. People will pay to watch humans perform even when robots perform better. Like dogs want to watch dogs.

UBI becomes inevitable. Not as a political choice but as a stability requirement. Governments that don’t implement it get revolutions. The harder problem is meaning. If you take 40-hour workweeks away from half the population, you’ve got tens of millions of people with time and no structure.

He’s open about not having the answer. He mentions meeting the king of Bhutan, who’s building a city of mindfulness outside the capital meant to attract a billion people a year for meditation and Buddhist practice. One stone is on the ground so far. Yampolskiy lights up when this comes up. The upside scenario isn’t utopia. It’s a world where humans are paid to exist and ancient traditions try to fill the time.

My dream is to be proven wrong

Lex asks at the end what would prove Yampolskiy wrong. What does the good 100-year future look like? He lists scenarios. A catastrophic event prevents advanced chips. Someone invents a non-black-box alternative to neural networks. Friendly aliens show up. Maybe we’re already in our own personal universes and the one he’s in turns out beautiful.

Then he says the line that stayed with me. “My dream is to be proven wrong. If everyone picks up a paper or a book and shows how I messed it up, that would be optimal.”

That’s not a doomer who wants to be right. That’s a researcher who’s spent 15 years showing his work to anyone who’ll engage with it, openly hoping someone in the audience finds the flaw he hasn’t.

I haven’t found it. The labs haven’t published one. The two interviews are about 3 hours of an argument the AI industry has been ducking instead of answering.

The deception is documented. The race won’t stop on its own. The worm scenario is the lucky outcome. Two to three years is short enough to act on, not in the lab but in your life. The meaning problem is now, not later.

Which side of the race are you on, with your money, your time, your kids’ education, your business?

Time to decide.

If you run frontier models through API or enterprise channels, the bill is counted in tokens. The retail math looks like this:

That table is conservative. It prices one big agent pass, not the retries, tool calls, failed branches, or follow-up prompts. Recent subscription testing found that a maxed-out $200 plan can represent roughly $8,000 to $14,000 of API-equivalent usage. Heavy users are living inside a subsidy.

Now add hardware. A frontier model with a million-token context is not a desktop app. Providers do not publish exact parameter counts, but public infrastructure points one way: racks, not laptops. NVIDIA’s H200 has 141GB of HBM memory. GB300 NVL72 racks are measured in tens of terabytes of fast memory and hundred-kilowatt-class power. Rack cost: millions. “Run your own Claude Opus with full context” is a data center budget, not a hobby project.

That is the part most people miss. The subscription era feels like abundance, but it is really market entry pricing. Vendors are teaching us habits before the bill becomes honest.

The likely future is not unlimited access to the heaviest thinking models forever. It is sharper limits, slower queues, more routing, and premium reasoning sold by the token. Cheap fast models will be everywhere. Large, slow, high-context models will be treated like scarce machinery.

So this is a rare window.

Right now a person can use Opus, Fable, GPT-5.5, Claude Code, or Codex to build things that would have required a team two years ago. The correct response is not to burn tokens blindly. It is to practice the rules while the subsidy exists:

1. Compress context before every serious run.

2. Start cheap; escalate to the big model only when needed.

3. Split work into files, checkpoints, and tests.

4. Cache stable instructions and reference material.

5. Keep agents narrow; stop endless loops early.

6. Feed back only the delta, not the whole history.

7. Use fast mode only when speed beats cost.

If you do not force the learning curve now, you will face it later on metered pricing. Learning prompt discipline on GPT-5.5 Pro at $180 per million output tokens will be an unaffordable luxury.

The subsidy is not just access. It is your training period.

My other candidate billed somewhere between $300 and $600 that month, depending on how many video takes I burned.

She does not exist. Only on your screen and in your imagination. It is hard to forget her ;)

I run an AI influencer account in the fitness niche. Second month of life, 1.2 million organic monthly reach. In April, I wrote about the video pipeline behind it and promised to open more of the kitchen if people asked. People asked. So today: the money.

What an AI influencer actually is

Not an avatar. Not a filter. A file system.

My influencer is a folder. Inside it: a biography file with her backstory and character. A tone of voice document. Reference libraries for her face, her outfits, her emotions, her haircuts. Every new photo starts from those references. Every caption follows that character file.

This matters for the economics. The persona is an asset I own. Not a person I rent.

The production pipeline is the one I described in April. Pose diagrams, a locked base character, a video model that animates the flow. I will not repeat it here.

The real monthly bill

Between $300 and $600 a month. Here is where it goes.

Images are almost free now. A batch of consistent photos costs single dollars. If the account only needed photos, the bill would embarrass a coffee subscription.

Video burns the money. Motion is still a lottery. You generate five takes to keep one. Some weeks you generate ten. Every failed take is paid in full. Nobody refunds you for a character whose left hand melted mid-squat.

So when people say an AI influencer costs nothing, they are describing a photo account. A real content mix with video runs you a few hundred dollars a month. Plan for the failed takes, not the successful ones.

The bill nobody counts

Here is the number every AI influencer thread on X conveniently skips.

This thing eats 5 to 10 hours of the production team's week. Generation, selection, consistency checks, posting. The boring work of looking at forty images and rejecting thirty-seven because the jawline drifted.

Price your own hour honestly. At a modest $50, that is another $1,000 to $2,000 a month. Real money, paid in attention instead of cash.

So the honest total is roughly $1,300 to $2,600 a month. Against $3,000 to $5,000 for the human contract.

And let's be honest: those fitness influencers are not really real — heavy post-production, fake lips, breasts and everything. Our AI girls are more real than those real “humans.”

Cheaper. Not ten times cheaper. Anyone selling you a 10x story is selling a course.

Then why bother

Because the savings are the boring part. The interesting part is what you own.

A human ambassador contract ends. The audience leaves with her face. Grow her account with your budget, and you have built someone else’s asset. Then she renegotiates, because of course she does. Trust my experience, that conversation always comes.

The AI persona compounds in the other direction. Every post makes my asset more valuable, not my contractor more expensive. She never gets injured before a launch. She never signs with a competitor. She never posts something on a Saturday night that requires a crisis call on Sunday.

Let’s be honest about the other side, too. A human wins everywhere bodies matter. Live events. Real client transformations. A handshake at the gym. If your strategy needs offline presence, an AI persona is the wrong tool, and no spreadsheet fixes that.

The part that actually unsettled me

I expected the hard problem to be technical. Faces, hands, motion.

The hard problem turned out to be philosophical. The audience does not care — AI or REAL girl. And we have an obligatory AI mark in the account, and it is visible!

People comment. They save posts. They write DMs and ask questions about training. Engagement behaves exactly like engagement on a human account. No drop, no uncanny valley penalty, nothing.

We told ourselves authenticity meant a heartbeat. The data says authenticity means showing up daily with the same face, the same voice, and advice that holds up. Consistency reads as realness. Biology was never a requirement.

Think about it. Most followers never meet their influencers anyway. The relationship was always mediated by a screen. I just removed a layer nobody was using.

Bottom line

An AI influencer is not free. Honest cost: a few hundred dollars in generation plus a part-time job’s worth of your attention. Real total is around half the price of a mid-tier human contract.

The price is not the reason to do it. Ownership is. You are converting marketing spend into an asset that compounds instead of a contract that expires.

And the audience? They already voted. They just did not know there was an election.

If you run one of these accounts and your numbers look different, write to me. I want to compare kitchens.

And follow my side project, Marketers Are Coders Too, to get everything from the AI world for your marketing.

Same task. Three agents. Three pricing models. The numbers tell a story most AI vendors don’t want you to see.

The Test

I asked three agents to build a curated list of 1,000 best marketing books. Real research, real categorization, real sourcing. Not a one-shot prompt. A proper agentic task that runs for hours.

The result from Perplexity Computer you'll see at the end of the article ↓

Three contestants:

• Claude Code, $100/month Max plan

• OpenAI Codex, $100/month plan

• Perplexity Computer, $200/month Max plan

Same job. Different worlds.

The Results

Claude Code finished in 40 minutes. Burned 17% of my 5-hour context window. Job done. Zero overage. Still inside my flat $100 fee.

OpenAI Codex finished too. Took longer. Used 51% of my daily 5-hour quota. Still inside the $100 plan. No extra charge.

Perplexity Computer ran for 5 hours. Burned 15,314.24 credits. The Max plan ships with 10,000 credits per month. So one task ate 1.5 monthly allowances in a single afternoon. The save came from the bonus credits you get upon registration.

In real money? Roughly $250 for one task. On a $200 plan. For a job Claude did in 40 minutes inside its monthly cap.

Sound familiar? It should. Every “pay-as-you-go” AI product works this way.

Read my previous article, where I shared some thoughts on Perplexity's agentic perspective without a Big Model of its own.

The Pricing Trap

Token-based, credit-based, and API-call pricing is mathematically broken for agentic work. Agents loop. They retry. They search, read, summarize, re-read, plan, re-plan. A simple task spawns thousands of tool calls under the hood.

You can’t predict the cost. You can’t budget for it.

I’ve seen this pattern across every vendor selling agents on metered pricing. One task runs hot and burns a month of credits. Vendor sends you a bill you didn’t authorize. You disable the agent. You go back to doing it manually.

That’s not a product. That’s a slot machine with a corporate logo.

The Math

Let’s be honest. A senior researcher in Eastern Europe costs $3,000 to $5,000 a month. Full-time. Real human. Asks clarifying questions. Doesn’t loop forever on a bad prompt.

If your agent costs $250 per task and you need 20 tasks a month, you’re at $5,000. Same money. Worse output. No accountability.

The reality is most metered agents are more expensive than hiring people. And they don’t even solve the problem better.

One month of heavy use, side by side:

• Claude Code Max: $100 flat, unlimited tasks inside daily limits

• Codex $100 plan: $100 flat, unlimited inside daily limits

• Perplexity Computer Max: $200 base plus ~$1,500 in overage at my usage rate

Which one is the business product? Which one is the trap?

Why Flat Rates Win

Agents need to run free. They need to retry, branch, fail, recover. That’s how they work. The moment you tax every loop, you’re paying for the agent’s mistakes too.

Flat-rate plans with usage limits are the only sustainable model. Vendor absorbs the variance. You know your monthly cost upfront. Agents are incentivized to be efficient on their side. You’re not afraid to use it.

When I run Claude Code, I don’t think about cost. I just use it. That’s the whole point of an assistant. The moment I start watching a credit meter, I stop using the tool. And a tool I don’t use is worth zero.

Trust my experience. I’ve burned real money on metered AI products. Twice. The second time I felt stupid.

The Rule

Here’s my rule from now on, and I’m not flexing on it:

Never use an agent priced by tokens, credits, or API calls. Only use agents on monthly flat rates with usage limits, but no money overage. So skip LLM APIs, Perplexity Computer, Manus for heavy tasks, and Genspark as well.

If a vendor can’t ship a flat plan, they don’t believe in their own product. They’re hedging their bet on your wallet.

The winners are clear. Claude Code and OpenAI Codex have figured out the right model. They cap your usage, not your bank account. Everyone else selling agents on credit meters is selling you a casino chip and calling it a productivity tool.

Bottom line. If your agent task can cost $250 on a $200 plan, you don’t have a product. You have a billing surprise waiting to happen.

Before you sign up for the next shiny agent platform, ask one question. What’s the worst-case bill for one heavy task? If they can’t answer, walk away.

What’s your worst pay-as-you-go AI bill so far? I’d bet most people reading this have a story.

P.S. And the result from Perplexity Computer.

Most fitness creators still rent a studio, hire a coach, light a set, and burn a weekend on a single 30-second reel. There is a faster way. You generate a printable instruction diagram, lock a base character, and let a video model animate the flow.

I run an AI influencer account that pulled 1.2M reach in its second month of life. I cannot show the account (indie principle, no face reveal of the build), but the pipeline below is the same family of techniques. If enough of you ask in the comments, I will open more of the kitchen in a follow-up post.

Here is the exact four-step workflow, with the prompts.

The Stack

• GPT Image (GPT-Image-1 / “GPT2 Img”) — generates the instructional pose diagram and the base character.

• Seedance 2.0 Omni-Reference by ByteDance — animates the scene from a character reference + a motion-guide image. https://www.volcengine.com/product/seedance and https://fal.ai/models/bytedance/seedance/v2-pro

• Codex — stitches the resulting clips and runs frame interpolation.

• Optional polish: Topaz Video AI for upscale, CapCut or DaVinci for the final cut.

Step 1 — Generate the Pose Sequence Diagram

This is the cheat code. Instead of describing the motion in words, you give the video model a visual map of every pose in order. The model “reads” the grid like a comic strip.

Drop this into GPT Image:

Create a 12-panel yoga instruction diagram in a clean 4-column by 3-row grid.
Style: black-and-white / soft grayscale instructional poster, off-white background,
thin black panel borders, bold uppercase titles, black rounded number badges,
simple dotted or curved motion arrows, and short coaching captions.
​
Use one consistent female yoga model across all panels: athletic build,
long wavy hair, fitted sports bra and leggings, barefoot, realistic
photo-illustration style, neutral studio background. Show a classic
vinyasa flow from Mountain Pose to Downward-Facing Dog. Focus less on
overly technical pose detail and more on the feeling of a smooth flowing
sequence, with clear movement, breath, and transitions from one step to
the next.
​
Each panel should clearly show the motion step and how it transitions
into the next pose. Use arrows to show direction of movement. Keep the
captions short and simple, describing the action, breath, or flow cue
in a natural way.
​
Make all 12 panels exactly the same size, evenly aligned, highly readable,
and visually consistent. No color. No extra text.

Run it twice. You want two grids of 12 panels (24 steps total) so the second half of the flow has its own reference sheet. Crop, clean up text artifacts in Photoshop or Photopea if needed.

For non-yoga work, swap “vinyasa flow from Mountain Pose to Downward-Facing Dog” for whatever you need: kettlebell swing, deadlift, push-up to plank, mobility flow. The grid format is the part that matters.

Step 2 — Generate the Base Character

The diagram model is great at form, weak at face consistency. Solve this by generating a clean front-facing portrait of the same person on a neutral set. This becomes your character anchor across every future video.

Crop one panel from Step 1 to get the body silhouette. Feed it back into GPT Image with this kind of brief:

Use the attached silhouette as pose reference. Generate a photorealistic
full-body portrait of the same character, standing in a peaceful orange
clay yoga studio with soft warm light, curved adobe walls, low stairs.
Athletic woman, short cropped hair, vitiligo on shoulders and chest,
neon yellow sports bra, black high-waist leggings, barefoot. Editorial
fashion photography, 50mm, f/2.8, golden hour ambient bounce.
Single subject. No text. No watermarks.

Save this image. Treat it as your IMG1 from now on.

Step 3 — Animate With Seedance 2.0 Omni-Reference

Seedance 2.0’s Omni-Reference mode accepts multiple image inputs at once. You feed it the base character (IMG1) and the pose grid (IMG2), and you tell it explicitly which image controls which thing.

This is the actual prompt format that worked:

Scene: One continuous shot — Hand-held YouTube-style video showing
a woman performing a complete yoga vinyasa flow.
​
Character: Use IMG1 as the character we’re following in the scene.
​
Character Motion: Use IMG2 to follow the motion and instructions exactly
to complete her flow.
​
The scene starts at IMG1.
​
Direction: The woman stands in a peaceful orange yoga studio. The
hand-held camera subtly pushes in on her as she begins her flow. It
captures the moment in tight composition as she moves from mountain
pose to upward salute.
​
The camera begins to pull back out as she transitions from upward
salute to swan dive and stays focused on her body as she transitions
from swan dive into a forward fold.
​
The camera begins to move right to a side profile as she plants her
palms and steps back into the high plank position. The camera drops
lower and pushes in towards her face for a focused close-up as she
moves from chaturanga lower to upward-facing dog.
​
The camera again pulls out, showing her full body as she transitions
to the downward-facing dog position. Finally, she holds for a deep
inhale and exhale in that position.
​
Overall Tone: Her movements are all natural and fluid, controlled and
directed, strong with natural body movements and subtle readjustments
as she gets her balance.
​
SoundFx: peaceful ambient hum as we hear her inhale and exhale in a
rhythmic fashion with each passing pose. No music.

Three things matter here:

1. IMG1 / IMG2 are explicit roles. Do not just attach images. Name them in the prompt and tell the model what each one controls.

2. The camera is a director, not a tripod. Push-in, pull-out, side profile, drop low. This is what turns “AI demo” into “actual content”.

3. Sound design lives in the prompt. Seedance 2.0 generates audio. Specify it or you get random elevator music.

Realistic expectation: at 24 poses in one prompt, the model will not match every transition verbatim. Cut the flow into 3 shorter videos of 8 poses each, with shorter prompts per shot, and adherence goes up significantly.

Step 4 — Stitch and Interpolate With Codex

You now have three or four 5-to-10-second Seedance clips. Stitching them by hand in CapCut works, but the cleaner play is to script it.

Run Codex against your local clips folder and ask for an FFmpeg pipeline that:

1. Concatenates the clips in order.

2. Runs RIFE or FILM frame interpolation on the seams to hide the cuts.

3. Re-encodes to H.264 or H.265 at 30 or 60 fps for the platform.

4. Optionally crops to 9:16 with a Lanczos resize.

A single Codex prompt like “write me an FFmpeg + RIFE script that takes ./clips/*.mp4, interpolates the joins, exports a 9:16 1080x1920 60fps mp4 to ./out.mp4, and prints the final duration” gets you a working script in one shot. Why do this manually? You will iterate. You will swap clips. You want a one-command rebuild.

What Actually Ships Reels

The diagram is repurposable. One 12-panel grid powers:

• The Seedance video.

• A static carousel post (just slice the grid into panels).

• A printable PDF lead magnet.

• The thumbnail of the reel.

That is four pieces of content from one image. The grid is the asset, the video is the surface.

Bottom Line

You do not need a gym, a model, or a real face on camera. You need:

• A pose diagram generated as a 4×3 grid.

• A locked character portrait.

• Seedance 2.0 Omni-Reference with explicit IMG1 / IMG2 roles.

• A scripted stitch pass.

Pick one exercise this week. Run the four steps. Reply with what broke. If this lands, the next post will go inside the AI influencer build itself: voice, posting cadence, comment management, and the math behind the 1.2M reach in month two.

On February 25th, Perplexity shipped Computer. Not a laptop. A cloud-native multi-model orchestration system that routes work across 19 frontier models. It spawns sub-agents. It persists memory for months. It delivers finished artifacts while you sleep. It runs Claude Opus 4.6 as its reasoning core, Gemini for deep research, Grok for speed, GPT-5.2 for long context recall. $200/month. And by most accounts, it’s genuinely impressive for research, competitive intelligence, and consulting-grade deliverables.

And it might not matter.

The middleware trap, explained simply

Within six weeks of Computer’s launch, three things happened simultaneously. Anthropic shipped the enterprise expansion of Claude Co-work with deep connectors and private plug-in marketplaces. Google shipped Gemini agents at the OS level on Android. OpenAI started embedding forward-deployed engineers directly inside enterprise customers to set up Frontier.

Three different architectures. Three hyperscalers. All building the exact product Perplexity Computer competes with.

And here’s the problem I can’t stop thinking about: every model provider Perplexity depends on is simultaneously building the thing Computer is. The reasoning engine is Anthropic’s. The research layer is Google’s. The speed layer is xAI’s. The long-context layer is OpenAI’s. Perplexity is running a product where every component of the supply chain is also a direct competitor.

That is the middleware trap.

Why this matters to every creator and founder who doesn’t own a model

If you’re building on top of someone else’s language model, someone else’s API, someone else’s platform, you are in the same structural position as Perplexity. Just smaller and with less capital to burn.

I’ve been building agentic marketing systems for 9 months. Every pipeline I run depends on Claude’s API. Every deployment touches infrastructure I don’t control. If Anthropic decides tomorrow that my use case is worth absorbing, they don’t need to beat me. They just need to be good enough. And they already are.

This is not hypothetical. This is what Microsoft did to Netscape. What Amazon did to early AWS competitors. What Google did with Analytics. The playbook is old. The speed is new.

It called “the middleware squeeze.” The layers below you are controlled by hyperscalers who need downstream tokens to justify their valuations. The layers above you are the customer relationships. You’re in between. And “in between” is the worst place to be when the companies below you and above you start reaching toward each other.

The stack, as it stands right now

I broke down the AI industry into five layers:

Layer 1 — Foundation. Models and compute. Owned by Anthropic, OpenAI, Google, xAI, Meta. You and I don’t play here.

Layer 2 — Orchestration. Multi-agent frameworks, context management, task routing. This is where Perplexity Computer sits. This is also where every agentic startup sits that doesn’t own a model.

Layer 3 — Integration. Tool connectors, API bridges, workflow triggers. Perplexity has 400+. Sounds like a moat. Isn’t one. Every integration is a contract with a company that has its own interests and can cut you off.

Layer 4 — Interface. Chatbots, voice, IDEs, custom UIs. This is where most “AI startups” live. It’s the thinnest layer.

Layer 5 — Use case. Domain-specific agents, industry workflows. This is where real switching costs live, if you build them right.

The squeeze happens in layers 2-4. The hyperscalers own layer 1 and are reaching up. Enterprise customers own layer 5 and are reaching down. Everything in between gets compressed.

Three moats that were supposed to work (and why two of them don’t)

“Domain expertise.” Most of what companies call domain expertise is actually context loading. You’re dropping your use case into a big context window. That’s not a moat. That’s a prompt. Claude Opus 4.6’s million-token context window is specifically designed to sit inside enterprise workflows as an omnipresent context anchor. Your carefully curated knowledge base is one API call away from being someone else’s feature.

The exception: if your domain expertise lives in proprietary data, years of regulatory compliance, or operational insight from running physical processes, you might be safe. For now. But most companies claiming domain moats haven’t done the honest work to figure out which side of that line they’re on.

“Integrations.” Perplexity has 400+ integrations. That sounds defensible until you remember that every one of those is a contract with a company that has its own AI ambitions. Ask anyone who built on Twitter’s API. Ask anyone who relied on LinkedIn’s API before it got shut down. Integration moats get dismantled the moment the platform decides it wants the token.

“Switching costs.” This is the only moat that actually holds. But not the way most people build it. Switching costs don’t come from being embedded. They come from the cost of replacing you being higher than the cost of keeping you. There’s a difference. Embedding deeply is necessary but not sufficient.

OpenAI parking forward-deployed engineers inside enterprise customers is specifically designed to build this kind of switching cost. They’re not selling API access. They’re building structural relationships that make switching expensive. If you’re a middleware company, that’s the game you need to play. And if you can’t, you need to know it now.

Seven lessons for creators and founders who don’t own the stack

I pressure-tested them against my own experience building agentic systems over the last 9 months. Some of them hurt.

1. If your product runs on a competitor’s model, you are renting your differentiation. Every model generation that ships a new capability can collapse your entire value proposition overnight. A million-token context window eliminated several categories of multi-model routing that Perplexity depended on. What does the next capability jump eliminate for you?

2. The question is not “is my product good?” The question is “why does the value live here and nowhere else?” If you cannot answer that and defend the answer for more than one model generation, you are generic middleware. Generic middleware gets slowly replaced as model capabilities expand. Not killed overnight. Just compressed until the margin is zero.

3. Good execution on the wrong layer of the stack will not save you. Perplexity Computer is a genuinely impressive product. And it does not solve any of their strategic vulnerabilities. It actually introduces new ones. Execution quality and strategic position are independent variables.

4. Three clocks are running at different speeds, and only one matters. Model providers ship capability jumps in weeks. Enterprise procurement locks in platform decisions for 6-18 months. Hyperscaler capex needs returns in 2-3 years. The clock that matters is the first one. Every capability jump that collapses your differentiation narrows the window for repositioning.

5. Pick your lane or get squeezed. There are exactly three viable positions for companies that don’t own a model: (a) infrastructure — be a building block that agents need regardless of who wins orchestration; (b) vertical app — own a domain so deeply that switching costs are real; (c) enterprise workflow tool — encode institutional knowledge that survives a model update. If you are none of these, you are generic middleware and the compression has already started.

6. Don’t compete for token routing. Whoever controls orchestration controls token routing. Whoever controls token routing controls downstream revenue. Microsoft wants tokens through Azure. AWS wants tokens in their model garden. Google wants tokens in Vertex. Every token that flows through a neutral third party is a customer one of them doesn’t get. That is a zero-sum game. Do not get in the middle of it unless you enjoy being squeezed from three sides simultaneously.

7. The trust and verification gap is the biggest unclaimed opportunity. Agents are doing real work. No one can prove what agents did. The gap between “agents act” and “we can audit what agents did” is wide and growing. This is analogous to what accounting firms did when financial complexity started to outpace regulation. Someone needs to audit agent outputs, verify compliance, and enforce policy. The model providers are focused on capabilities right now. Governance is wide open.

What I’m doing differently after this

Three things changed in my own thinking this week.

First, I stopped assuming that “I built it on Claude” is a feature. It’s a dependency. The pipeline I built works today. It might be a native Claude feature in 6 months. I need to know which parts of my system would survive that, and which wouldn’t.

Second, I started mapping my own stack against the five-layer model. Most of what I do lives in layer 2-3. That’s the squeeze zone. The parts that live in layer 5, the domain-specific workflows that encode my actual marketing operations knowledge, those are the parts worth protecting. Everything else is scaffolding.

Third, I’m paying much more attention to the clock. Not the enterprise procurement clock. Not the capex clock. The capability clock. Every model generation that ships is a pressure test on whether my work is still differentiated or just hasn’t been commoditized yet.

The Perplexity dilemma is not about Perplexity. It’s about everyone who builds on top of someone else’s foundation and calls it a product.

The hyperscalers need downstream tokens. The rest of us need to figure out which of our tokens are truly ours.

Good luck with that. I’ll be here, building.

A plumber shows up with a van full of tools. You don’t ask for a certification in pipe fitting theory. You look at the tools, you check the references, you watch them work for an hour. That’s the evaluation.

Software has never worked this way. We’ve always hired for knowledge — degrees, frameworks memorized, years of experience in a specific stack. The tools lived on the company’s servers. The employee showed up empty-handed and learned the internal systems.

That model is ending.

I know a marketer who carries a Claude Code setup with 9 custom agents — research, content, scheduling, analytics, campaign ops, email, community management, strategy, and an orchestrator that coordinates all of them. Each agent has its own model, its own eval criteria, and its own context files. The whole system lives on a laptop.

When this person interviews for a CMO or other marketing role, the conversation isn’t “tell me about a campaign you ran.”

It’s “show me your agents. Show me the eval framework. Show me the specs. Let me see what happens when I give you a brief and your system produces the first draft in 10 minutes.”

This is the shift HR teams aren’t ready for:

The unit of evaluation is no longer the person. It’s the person + their VERY OWN agent infrastructure.

Two candidates with identical CVs. One opens a terminal and deploys a working analytics dashboard during the interview. The other talks about the dashboards they’ve built in the past. Who gets hired?

The construction industry figured this out decades ago. A contractor’s value isn’t their knowledge of building codes — it’s their truck, their crew, their tools, and their ability to start on Monday. The references confirm they won’t disappear halfway through the job. The tools confirm they can do the work.

Knowledge workers are becoming contractors with digital toolkits.

What changes:

• Your portfolio isn’t a PDF anymore. It’s a GitHub repo, a set of Claude Code skills, a documented agent architecture, and a live demo you can run on your laptop.

• References still matter, but they answer a different question. Not “is this person smart?” but “does their system actually work in production, and can they adapt it to a new environment in a week?”

• The onboarding conversation flips. Instead of “here are our tools, learn them” — it becomes “show us your tools, and let’s figure out how they integrate with ours.”

• Compensation models shift. You’re not paying for 40 hours of a person’s time. You’re paying for a person + their agent system’s output capacity. The person with a better toolkit produces 5x the output. They should cost more. And they will.

This isn’t about personal branding. It’s about professional infrastructure.

The question for anyone entering this market today isn’t “how do I update my resume?” It’s “what does my toolkit look like, and can I demo it live?”

If the answer is “I use ChatGPT sometimes,” you’re the plumber who shows up with a wrench and no van.

If the answer is “here are my 6 agents, here’s the eval framework, here’s a project I shipped last month with this exact setup, and I can start on your workflows Monday” — you’re the contractor who gets the job.

The future of hiring isn’t credentials. It’s capability you can demonstrate on a laptop in 10 minutes.

Start building your toolkit. It’s the new resume.

A few months before that, I saw someone running in a LIVE.LOVE shirt. In Europe. Thousands of kilometers from where it all started.

Here’s the thing. We built LIVE.LOVE in Ukraine back in 2016. No app. No AI. No growth hacking playbook. Just three founders (Natalia, Slava, and Slava), a crazy idea that sport should be fun, and rented pools and stadiums.

Three thousand people passed through. Eight hundred active at peak. We became the largest team at the Bosphorus Cross-Continental Swim. I crossed it four times. We were the biggest crew in Oceanman worldwide. Largest team at Vienna, Munich, and Cyprus marathons. 180 out of 400 Ukrainian slots were ours on Bosphorus. From the whole country. Registration closed in 7 minutes.

But the numbers aren’t the point.

The point is what happened around the sport. People met, fell in love, and started families. Dozens of them. A TV host married an entrepreneur. The former CEO of Mercedes-Benz Ukraine told us he didn’t think making real friends at 38 was possible. Three of our runners created Board, now one of the largest business communities in Ukraine and beyond.

We had three pillars.

1. A shepherd: the founding team.

2. A temple: physical places where we gathered and trained.

3. And rituals: weekly runs, swims, trips that became sacred.

Then COVID hit. It killed all three pillars at once. No gatherings. No trips. No rituals. We never came back. That's what we lost.

And yet. People still swim in those caps. Still run in those shirts. Still find each other across three continents. Ukrainian migrants recognizing LIVE.LOVE gear in Barcelona, Berlin, Dubai, and reaching out.

That’s the difference between a community and a platform.

Today you can build a community app in a weekend. AI generates your content calendar, SEO drives traffic, a no-code tool handles payments. All the infrastructure that took us months in 2016 is now trivially easy.

And that’s exactly why it doesn’t matter.

The hard part was never the website. It was getting a hundred people to show up at 7 AM on Saturday to swim in cold water. It was creating a culture where a CEO and a freelancer share a lane, then share breakfast. It was making rituals that people protect like family traditions.

LinkedIn won’t build that. Instagram won’t. Facebook groups definitely won’t. They’re distribution channels, not communities. The moment the algorithm changes, your “community” evaporates.

A real community survives a pandemic. Survives a war. Survives mass emigration across 30 countries.

Don’t get me wrong. AI is a gift for community builders. Use it for logistics, scheduling, content, and analytics. Remove every boring operational task so you can focus on the only thing that matters: getting people in the same room, doing something meaningful together.

The technology makes building the platform trivially easy. Which means the only competitive advantage left is the human part. The shepherd. The temple. The rituals.

I’m moving to Dubai now. Thinking about doing it again. Different city, different people, same principles. If that sounds like something you’d want to be part of, write to me.

The world has never had better tools for building communities. And never been worse at actually doing it.

The sharpest CMO you know has a locked Facebook profile. The founder who built a $50M company shares nothing publicly except occasional conference slides.

This isn’t burnout. It’s a strategy.

And if you’re still publishing your best thinking into the open, you might want to understand what they already figured out.

The meadow that was

In Liu Cixin’s novel The Dark Forest, the universe isn’t empty — it’s silent. Every civilization that broadcasts its existence gets destroyed. Not out of malice, but pure game theory: if even one out of five observers decides you’re a threat, you’re done. So everyone hides.

The early internet was the opposite of that. It was a bright meadow where broadcasting your presence was the optimal move. More connections meant more value. More sharing meant more opportunity.

I lived this. For seven years, I ran content operations that produced roughly 14,000 articles — all written by hand. Me personally, plus team’s content. Reviews, guides, analysis across dozens of sites. No investors. No permission from anyone. No editorial board. Just ideas and execution. At peak, we reached 32 million monthly unique readers.

Sharing was rational because execution was the moat. Anyone could have my ideas. Nobody could replicate the output. The cost of copying 14,000 manually written articles was... seven years of work.

That math no longer holds.

The forest gets dark

Two things changed simultaneously, and the combination is what matters.

First, the open web consolidated. The spacious meadow shrank into a handful of platforms controlled by companies whose business model is extracting your signal and selling it as targeting data — or by governments interested in the same signal for different reasons.

Second, AI made execution cheap.

Before LLMs, a competitor couldn’t just absorb your idea and ship it. Ideas needed people, people worked in physical time, and physical time doesn’t scale. Your moat was real.

Now, a platform that helps you brainstorm, code, and write already owns the compute, the models, and — critically — the aggregate demand signal. It doesn’t need to read your specific prompt. It sees where the questions cluster. A gradient in idea space. A map of where human interest is moving.

The platform knows your idea is pregnant before you do.

Copying 14,000 articles today costs a week and a $500 API bill. The moat evaporated.

The predator isn’t who you think

In Cixin’s forest, civilizations hide from each other — from hunters. In the cognitive dark forest, the most dangerous actor isn’t your competitor. It’s the infrastructure itself.

You publish a framework for thinking about retention. Within months, it’s training data. Your unique angle becomes the median output of every AI writing tool. Your differentiation dissolves into the average.

And here’s the recursive trap: trying to outinnovate the system only feeds it. You think outside the box, you publish that thinking, and the box gets bigger. Your resistance isn’t suppressed — it’s absorbed.

This is why the smartest people are going quiet. Not because they have nothing to say. Because they’ve run the game theory and the math doesn’t favor broadcasting anymore.

The closed-account phenomenon

Watch the behavior pattern: a CMO with two decades of experience maintains a minimal LinkedIn presence and a completely locked personal Facebook. A successful founder shares nothing about their actual network, partnerships, or strategic thinking. They broadcast the social role but hide the real signal.

This isn’t paranoia. It’s the same asymmetric risk calculation from the novel. If five entities observe your signal — recruiters, AI scrapers, competitors, governments, random opportunists — and four of them do nothing, the fifth one might use it against you. The expected cost of broadcasting exceeds the expected benefit.

People are splitting into two layers: a public facade of carefully curated professional content, and a private layer of actual relationships, real ideas, and genuine strategic thinking. The facade feeds the forest. The private layer is where value actually lives.

What this means for anyone who creates content

If you’re a marketer, a founder, or anyone whose job involves putting ideas into the world, you’re facing a real strategic question. Not “should I create content?” but “what kind of signal should I broadcast?”

Here’s what I learned from 14,000 articles and watching the meadow become a forest:

• The moat moved. It’s no longer execution speed or content volume. It’s taste, curation, and the relationships your content builds. AI can write the text. It cannot build the trust that makes someone open your newsletter instead of the other 40 in their inbox.

• Publish frameworks, not secrets. Opinions and worldviews are hard to absorb into a model in useful ways. “Here are 10 tactics for retention” gets commoditized instantly. “Here’s how I think about retention and why most frameworks miss the point” — that’s stickier.

• Your real network is your real asset. Build it in private channels. DMs, small communities, one-on-one relationships. The public content is the storefront. Don’t confuse it with the warehouse.

• Don’t stop publishing. Change what the signal carries. The mistake is either going fully silent (you lose the storefront) or publishing everything (you feed the forest your best ideas for free). The move is to publish enough to attract, and keep the high-value thinking for contexts where you capture the value.

The recursion

This article is itself a signal in the dark forest. By describing the dynamic, I’m feeding it to the system I’m warning you about. The models will learn a little more about why people hide.

I wrote it anyway. Because silence isn’t a strategy — it’s a surrender. The real strategy is to speak in a way where the value stays with you and your audience, not with the forest.

The meadow is gone. But you don’t have to be prey.

You just have to stop pretending it’s still a meadow.

Tuesday evening. Dubai. Two months into relocating my life. My phone buzzes — WhatsApp, Indian number.

“Good Morning Slava! This is Narender from Neo Talent. Are you considering a job change in GCC?”

I’ve been in marketing for 15 years. Survived COVID, a war, and a cross-continental move. I know what a real headhunter sounds like. This wasn’t it. But I was curious — so I played along.

The Pitch

Narender sent a job description so generic it could’ve been written by ChatGPT in 2023. “Omnichannel Brand Strategy.” “Fit-fluencer Management.” “LTV Optimization.” Every buzzword, zero specifics.

Then came the Google Meet call. Camera off, naturally. He rattled off names: PureGym Arabia, Jumeirah Group, Barry’s. Salary? Up to 90,000 AED/month. Tax-free. Housing, transport, flights.

“Are you married?” Yes. “Dependents?” One son. He was building my file — or so he claimed.

Then the punchline: “All these services — activation fee of $550.” Via Stripe.

The $550 Job That Doesn’t Exist

Stripe invoice arrived within 60 seconds. Then: “Please send us a copy of your passport.”

$550 AND passport data? That’s not recruitment — that’s a shopping list for identity theft.

I wrote a polite rejection citing UAE Federal Decree-Law No. 33/2021 (charging candidates is illegal), the fact that none of these companies have open CMO positions, and that Neo Talent isn’t on India’s eMigrate portal.

His response? “Funny thing is I have copied the job description online. Pitty on you that you are not able to google things.”

He admitted the JD was fake. And I’m the embarrassed one?

The Negotiation Phase

This is where it got entertaining. I offered: “Get me to this job and I’ll pay you $5,000.”

“No worries. We get commission from employer. You no need to pay.” Then, 90 seconds later: “Shall I send you the link for $250?”

The employer commission vanished in two minutes. I offered $25. His reply deserves a frame:

“It’s about your career Slava.. you are not buying Tomatoes.”

Narender, if you’re reading this — the tomato line was chef’s kiss. But admitting you copied the JD kind of ruined the mystique.

I’m from Ukraine. Fraud doesn’t scare me — it entertains me. “I WANT to meet you, man,” I wrote. He got nervous. Then excited. Then nervous again.

By midnight: three more Stripe invoices, six payment reminders, and “3 people already paid.” By morning: “Forget it. Let’s not do timepass. Take care.”

How to Spot Executive Search Fraud (30-Second Checklist)

🚩 Red flags — run immediately:

• Contact via WhatsApp from a personal number

• ANY fee charged to the candidate

• Generic JD with no company-specific details

• Pressure to decide NOW

• Passport/ID request before the formal process

• AI-template website with dead social links

• No LinkedIn page, no Glassdoor, no eMigrate/MOHRE registration

✅ Real executive search looks like:

• Corporate email, named client

• Employer pays 15–30% of your annual salary as the fee

• Process takes weeks, not minutes

• No payment from you. Ever. Period.

The Numbers

India’s Ministry of External Affairs: 3,505+ illegal recruitment agencies documented. 1,553 complaints in 2021 alone. The pattern is always identical: WhatsApp → prestigious names → high salary → upfront fee → passport.

To everyone relocating to the Gulf: if a "recruiter" asks for money, here’s your script:

“Stop loving money so much. They are not worth doing this shit, man. Hugs and kisses. Bye.”

Farzad dropped a tweet that got a lot of attention: “The biggest job in the next 1-5 years will be AI Agent Architect.”

Someone who is extremely good at using AI to get stuff done for specific use-cases. Finance. Content. Video. Storefronts. Whatever.

Boris Cherny from Anthropic added: “Someone has to prompt the Claudes, talk to customers, coordinate with other teams, decide what to build next.”

Aaron Levie, CEO of Box, agreed: “The future of work will look something like what Boris is describing. People who know what they’re doing still have to tell the agents what to do, review their work, and integrate that work into a broader system.”

They’re all right. But they’re talking about engineering. Let me tell you what this looks like in marketing. Because I’ve been living it.

What I Actually Built

I’m a CMO at a fitness chain with 20+ clubs. Traditional offline business. The kind where you’d expect a traditional marketing team.

Instead, I built a system of AI agents. Not a chatbot. Not a single prompt. A team.

Here’s who’s on it:

• A researcher (Sherlock) who pulls fresh data, analyzes competitors, and monitors trends. It doesn’t sleep. It doesn’t forget.

  

• A content writer (Cassandra) trained on my voice, my style, my banned words list. It knows I hate “synergies” and “paradigm shifts.”

  

• A social analyst (Socialist) who tracks Twitter, YouTube, and engagement patterns. It reports. I decide.

  

• An image generator (Picasso) who knows our brand guidelines, our influencer’s face consistency, our visual language.

  

• An orchestrator (my buddy Alfie) who coordinates all of them. It delegates tasks, checks quality, and comes back with results.

I’m the CMO. I set direction. I make decisions. I review the output. But the execution? That’s the agents.

Why “AI Agent Architect” Is the Right Name

This isn’t about “using ChatGPT.” Every intern can do that.

This is about designing systems. Knowing which agent does what. How they communicate. What tools they need. When to intervene and when to let them run.

Think about it. A traditional marketing department has:

• Content team (3-5 people)

• Analytics team (2-3 people)

• Social media manager

• Designer

• Media buyer

An AI Agent Architect replaces none of them. They replace the need to hire all of them as full-time staff. One person who knows how to build and manage agent workflows can cover 80% of what those teams did. The remaining 20% is where the human judgment lives. Strategy. Taste. Client relationships. The stuff AI can’t fake.

The CMO as Orchestrator

Here’s where it gets interesting for marketing leaders specifically.

The CMO role is already shifting from “person who runs campaigns” to “person who runs systems.” AI agents accelerate this by an order of magnitude.

In my setup, I don’t write briefs for people. I write task definitions for agents. The difference?

• A brief says: “We need a social media post about our new club opening.”

• A task definition says: “Research the neighborhood demographics. Pull competitor pricing within 3 km. Generate 3 post variants in our tone of voice. Attach relevant visuals. Send to my review queue.”

The second one runs without me. I approve or redirect. That’s it.

This is what the future CMO looks like. Not someone with 15 direct reports. Someone with 3 humans and 15 agents. The humans handle client-facing work, strategic decisions, and the messy stuff that requires empathy. The agents handle everything that can be systemized.

The Real Question

Farzad asked: “How many people will be the 1-person companies vs the 9 that get displaced?”

From what I’ve seen, it’s not about displacement. It’s about amplification. The marketers who learn to architect agent systems won’t lose their jobs. They’ll become 10x more valuable. They’ll run departments that used to need 20 people with a team of 5 humans and 20 agents.

The ones who refuse to learn? They’ll compete for the remaining traditional roles. And there will be fewer of those every quarter.

What This Means Practically

If you’re a marketer reading this, here’s what I’d suggest:

1. Start small. Pick one repetitive task you do weekly. Research, reporting, content drafts. Build an agent workflow for it. Not a single prompt. A system with inputs, outputs, and quality checks.

2. Learn the tools. OpenClaw, Claude, custom GPTs, n8n, whatever fits your stack. The specific tool matters less than understanding the architecture.

3. Think in systems, not prompts. A prompt is a question. A system is a team. You want the team.

4. Document everything. Your agent’s personality, its tools, its boundaries, its failure modes. If you can’t describe it in a file, you can’t scale it.

Bottom Line

The AI Agent Architect isn’t a future job. It’s a current job that most people haven’t recognized yet.

I know because I’m doing it. Every day. From a CMO chair in Dubai, managing a virtual team that never sleeps, never calls in sick, and costs less than one junior hire per month.

The question isn’t whether this will happen. It’s whether you’ll be the architect or the one wondering what happened.

What’s your move?

Vibe marketing. You’ve probably seen the term floating around LinkedIn by now. Salesforce wrote a guide. MarTech published a manifesto. Fortune 500 companies are “experimenting.” Searches for the phrase grew 700% in the past year.

And yet almost every article about it describes a concept without handing you the tools. “Use AI for marketing!” Great. Which AI. Doing what. With what knowledge. On which task. The advice stops right where the actual work begins.

I’ve been using vibe marketing daily for months. Not as a concept. As a practice. And what I’ve learned is that the gap between people who talk about it and people who do it comes down to one thing that almost nobody mentions: skills.

Not your skills. The AI’s skills.

What vibe marketing actually feels like

Let me describe a Tuesday.

I’m working on a landing page for a new product. Instead of staring at a blank doc, I tell my Claude agent: run a CRO analysis on this page. The agent doesn’t ask me what CRO means. It doesn’t give me a generic list of “best practices.” It pulls a conversion rate optimization framework, checks my product context that it already knows from previous sessions, and walks through the page section by section. Value proposition clarity. Headline structure. CTA placement. Trust signals. Friction points. Objection handling.

Twenty minutes later I have a structured report with specific recommendations, copy alternatives, and a list of things to A/B test. Not because the AI is brilliant. Because it has a skill installed that knows how CRO works, and it applied that skill to my specific situation.

That’s vibe marketing.

Not “write me a tagline.” Not “brainstorm 10 ideas.” Not the copy-paste loop that most marketers are stuck in with ChatGPT. An agent that understands a marketing discipline, knows your context, and runs a real workflow.

The term came from Andrej Karpathy’s “vibe coding.” Describe what you want, the machine handles execution. In software, this turned non-programmers into people who ship products. In marketing, the same shift is happening. But most marketers don’t see it yet because they’re still using AI like a search engine with a personality.

Skills, not prompts. This distinction changes everything.

Here’s the thing that made the whole concept click for me.

A prompt is a one-shot instruction. You type “write me an email sequence,” get some output, close the window. The AI forgets everything the moment you leave. Next time you ask, you’re explaining your product from scratch. Your audience from scratch. Your brand voice from scratch. Every. Single. Time.

A skill is something else entirely. It’s a structured knowledge module that lives inside the agent. It contains frameworks, methodology, cross-references to other skills, and a workflow that unfolds step by step. When the agent has a marketing skill installed, it doesn’t just respond to your request. It recognizes what type of marketing work you’re doing and applies the right approach automatically.

A developer and marketer named Corey Haines published an open-source collection of over 35 marketing skills on GitHub. Not prompts. Skills. CRO analysis. SEO audits. Email sequences. Cold outreach. Pricing strategy. A/B test design. Launch playbooks. Schema markup. Churn prevention. Content strategy. Ad creative generation. Sales enablement. RevOps pipeline design.

And they connect to each other. The copywriting skill knows about CRO. CRO links to A/B testing. A/B testing references analytics tracking. It’s a system, not a folder of templates.

There’s also a foundation layer called product-marketing-context. It’s the first thing every other skill checks. It stores your product description, your ICP, your positioning, your competitive landscape. So when you run any skill, it already knows who you are and what you sell.

You ask your Claude to install these skills. One command. That’s it. Your agent just absorbed more structured marketing knowledge than most junior marketers learn in their first two years.

Nobody is getting replaced. Let’s stop pretending that’s the story.

I need to address this because the LinkedIn crowd won’t stop with it. “One person with AI replaces a marketing team of ten.” I’ve seen the posts. I’ve seen the engagement. And I think it’s wrong. More than that, I think it hurts adoption because it scares the exact people who would benefit most.

Here’s what’s actually happening. And it’s more interesting than the replacement fantasy.

Each person on a marketing team can now work with dramatically more reach. Not because the AI does their thinking. Because the AI handles the framework, and they bring the judgment.

Your SEO specialist still needs to make strategic calls. But instead of spending three days manually crawling a site, they run an seo-audit skill. The agent produces a structured report in twenty minutes. The specialist’s job shifts from running the audit to interpreting results and deciding what actually matters for the business.

Your copywriter still brings voice and cultural context that no model can replicate. But instead of starting from a blank page, the copywriting skill provides frameworks for headlines, CTAs, value propositions. All calibrated to your brand. The copywriter’s time goes from raw generation to sharpening, directing, making it sound like a human who gives a damn.

Your growth lead still decides which channels to test. But the marketing-ideas skill surfaces tactics filtered by product type, stage, and audience. The lead applies judgment about what fits the team’s capacity and budget.

Same team. Same headcount. Different output. That’s what vibe marketing changes in practice. Not the org chart. The throughput.

ChatGPT is the wrong tool for this

I want to say this directly because I know where most marketers live. They live in ChatGPT. And for what they use it for, it works fine.

ChatGPT is a great reference. You ask, you get an answer. Quick research. Brainstorming. A rough draft when inspiration is dead. It does that job.

But vibe marketing needs something ChatGPT isn’t built for. An agent. Something that reads your files. Runs multi-step workflows. Installs skills. Connects to your analytics, your CRM, your CMS. Remembers what you told it last week. Executes without you holding its hand through every click.

Right now, Claude is where this happens. Claude Code for people who aren’t afraid of a terminal. Claude console for everyone else. Both support skills. Both run complex marketing workflows. Both maintain context.

If you want full control, there’s OpenClaw. Open-source. Runs Claude as a persistent agent on your machine. Channels for different workstreams, scheduled tasks, memory that carries across sessions. I use it daily. It changed how I think about what a “marketing tool” even means. But that’s a deeper dive for another post.

The point is: if you’re doing the copy-paste loop in ChatGPT and calling it “AI-powered marketing,” you’re leaving the actual capability untouched. The AI that can do real marketing work exists. It just doesn’t live where you think it lives.

How to start. Actually start.

If you’ve never touched a coding agent, if the word “terminal” gives you anxiety, go to codingformarketers.com. Corey Haines built it for exactly this situation. A step-by-step guide for non-technical marketers learning to work with AI agents. How to open a terminal. How to control what the agent does. How to review its work and build confidence without breaking anything.

The mental shift the site teaches matters more than any specific tool: stop asking “what can I build?” and start asking “what can I delegate?”

If you already use Claude, your next step takes five minutes. Ask your Claude to install the marketing skills from the GitHub repository. Let it set things up. Then pick one skill that matches your most painful current task and run it against a real project.

Not a test. Not a hypothetical. Something you’d normally spend hours on.

Pay attention to what it produces. Some of it will be good. Some will miss the mark. That gap between the skill’s output and what you’d actually ship? That’s your expertise. The skill handles the framework. You bring the taste.

The window is still open

I’m not going to pretend that installing 35 marketing skills makes your Claude a CMO overnight. It doesn’t. What it does is give you something to test. A way to feel what vibe marketing is in practice, not in a LinkedIn post.

From what I’ve seen over months of daily use, the people who start building this muscle now will have a real advantage. Not because the technology is magic. Because most marketers still treat AI like a search bar, and anyone who treats it like a coworker operates at a different speed.

The skills are free. The tools are available. The learning resources exist. The only question is whether you start now, while most of your competitors are still copy-pasting ChatGPT outputs into Google Docs, or wait until this becomes standard practice and the window closes.

I’d start now. Today. Pick one skill. Run it. See what your Tuesday looks like after.

Felix Kjellberg (aka PewDiePie) got a black screen six times.

He was trying to install Linux on his Steam Deck. Each time — black screen. Each time — he tried something else. By attempt number six, most people would have closed the laptop, told themselves it wasn’t for them, and moved on.

He didn’t. He kept going.

7.6 million people watched that video.

His very first video was like this 15 years ago :) Feel the difference!

I don’t think they watched because Linux is interesting. I think they watched because something about watching a person refuse to quit — in public, in real time, while visibly frustrated — is deeply, uncomfortably resonant.

We know we’re supposed to push through. We almost never do.

The most important thing

Here’s the thing most learning content won’t tell you: the discomfort is not a side effect. It’s the mechanism.

When something breaks, and you don’t know why, your brain has to actually engage. When there’s no tutorial for this specific combination of broken things, you have to think. When you sit with confusion long enough that you start asking better questions — that’s when learning happens. Not before. Not at the comfortable part.

The error message isn’t a sign you’re failing. It’s the class.

ThePrimeagen — a developer who turned his career into content — made a video about this called Embracing Failing. His take, stated plainly: the people who actually get good at technical things are the ones who accumulate enough errors that they stop being afraid of them.

“I have become so accustomed to failure, you have no idea. I have graveyards full of garbage data I thought was the best.”

He says this like it’s a badge. Because it is.

The graveyard of bad attempts is the actual portfolio. Not the finished work. The finished work is just the surface. Underneath it is every broken thing that taught you how to fix it.

PewDiePie spent 18 months learning in public. Watch the sequence.

Felix Kjellberg’s transformation over the last 18 months is the best documented case study of learning-through-pain I’ve seen in the public eye. Not because he’s exceptional at it — but because he’s visible at it, and he doesn’t edit out the hard parts.

October 2024. I Drew Every Day for 365 Days — 6.7 million views. A full year of being bad at drawing. Publicly. The early work was genuinely terrible and he didn’t hide it. This established the template for everything that followed: show the process, including the parts that hurt.

April 2025. I installed Linux (so should you) — 7.6 million views. Black screen six times. Tries again. Eventually lands on a fully customized Arch system. His conclusion after weeks of frustration: “Open source is always the best source. [...] Finally free. I escaped the Windowscape.”

June 2025. I’m DONE with Google — 7.3 million views. He removes Google from his entire life. Self-hosted everything. GrapheneOS on his phone. More pain, more configuration, more broken things fixed one at a time. When it finally works: “Google is at my mercy for once. Feels good. [...] Amazing. Finally, I’m free.”

September 2025. help, I’m going through a midlife crisis... — 2.4 million views. The most honest one. Not a content strategy. Just a person saying: this is hard, I don’t know exactly what I’m doing, I’m in the middle of it.

October 2025. STOP. Using AI right now — 4.6 million views. He trains his own language model. It performs worse after his training. He says so directly. He doesn’t reframe it as a learning moment. It just happened, it was bad, he kept going anyway.

That last one matters. He ran a model that he made worse. He said so on camera. And then he kept working on it.

That is the whole lesson in one moment.

We built systems designed to remove the pain. That was the mistake.

The generation now learning — and honestly, most of us who learned anything in the last decade — grew up with frictionless everything. Instant answers. Tutorials optimized for zero confusion. Systems designed to remove every possible point of difficulty.

The error message became a product failure, not a learning signal.

The result: people who feel busy learning but aren’t actually learning. They’re managing the appearance of learning. Finding a clearer tutorial. Reading more theory. Waiting until they feel ready. Avoiding the broken state as if it’s a threat.

Here’s what Linus Torvalds — the person who built the operating system Felix spent weeks installing — said about this:

“I happen to enjoy doing things I’m not good at. Because that’s how you learn.”

Not “failure teaches you lessons.” Not “mistakes are opportunities.” Just: I like doing things I’m bad at. Because that’s how it works.

The pain of not knowing is not a warning. It’s an invitation.

Why 7.6 million people watched a Linux install

By every metric of content logic, that video shouldn’t have worked. No hook. No memes. No gaming. A notoriously difficult operating system. An audience built on completely different content.

It got 7.6 million views. And then something measurable happened outside the video.

Reddit’s r/linux community — 11,000 upvotes — documented the moment: “Pewdiepie picks a fight against Google, installs GrapheneOS to his phone, he even installs Archlinux into his Steam Deck.”1 The Linux Mint team published an official welcome in their project newsletter: “We have a new user! Welcome to Linux, PewDiePie!”2 A separate thread in r/linux noted that “Linux market share surpasses 6% — SteamOS and Pewdiepie brought a new hype to Linux.”3 There was even a r/linux4noobs thread titled “Please do NOT try Arch Linux just because PewDiePie did” — 2,900 upvotes — which is the community’s version of a welcome problem.4

What moved people wasn’t the technical content. It was watching someone they’d trusted for 15 years hit a wall — repeatedly — and not stop.

That’s more persuasive than any tutorial. The tutorial shows you how. Felix showed you that when it breaks (and it will break), you don’t stop.

The physics of it

Here’s what actually changes when you push through long enough.

You don’t gain confidence. That’s not quite right. You gain something more useful: indifference to the error state. You stop reading the broken thing as evidence of unsuitability. You start reading it as data. Where did the system and my understanding diverge? That’s all it is.

Once you’ve seen enough of the same broken thing, your brain builds a map. Not consciously. Just through repetition. You start recognizing patterns in how things fail. You make better guesses. You process problems faster — not because you’re smarter, but because you’ve been here before.

Every hurdle you clear becomes permanent. Every broken thing you fixed means that flavor of broken no longer scares you.

These compounds. Slowly at first. Then embarrassingly fast.

But it only starts compounding if you don’t stop when it hurts.

The practical part

If you’re learning something right now — code, design, writing, a language, a system, anything:

Stop optimizing for smooth. The tutorial that never breaks is fine for orientation and useless for learning. At some point, you have to get lost. The sooner the better.

Pick something real. Not a practice project. Something with stakes. Something where “good enough” isn’t actually good enough. Pressure changes what you pay attention to.

Read the error before you Google it. Actually read it. Try to understand what it’s telling you before you outsource the thinking. This one habit compounds more than most courses.

Set a failure quota, not a success quota. “I’m going to hit 10 problems I can’t immediately solve” is a better learning goal than “I want to build X.” The shift from output to process removes most of the psychological weight.

Stop hiding the graveyard. Your failed attempts aren’t evidence you’re bad at this. They’re evidence you’re doing it.

The real message

Felix didn’t become a Linux user because he’s technically gifted. He became one because he refused to stop when it got hard. Six black screens. Weeks of configuration. A self-hosted setup built error by error.

He got a midlife crisis video out of the experience. And 2.4 million people watched because somewhere in the title — “help, I’m going through a midlife crisis” — they recognized something true about what learning actually feels like when you do it honestly.

It feels like a midlife crisis. That’s fine. The feeling passes. The knowledge stays.

“I am way too stubborn for that. I just can’t. I don’t have it in me.”

That’s him. That’s also the whole answer.

Pain in learning is not a signal to stop. It’s a signal that something real is happening.

Stay.

I write about marketing, AI, and what happens when you actually pay attention. If something here was useful — share it.

Notes

Jensen Huang said that in March 2026 at the Morgan Stanley TMT Conference. He was talking about OpenClaw — an open-source personal AI agent framework that went from 0 to 309,000 GitHub stars in four months. He noted that Linux took 30 years to reach comparable adoption. OpenClaw did it in three weeks.

The person who built it: Peter Steinberger, creator of PSPDFKit, coding on a laptop. The person who lit the match: Alex Finn, a YouTuber with under a million subscribers. The video title: “ClawdBot is the most powerful AI tool I’ve ever used in my life.”

That’s the setup. Here’s what happened next.

The match

January 24, 2026. Alex Finn posts a tutorial. 964,000 views, 29,000 likes. Not a big channel by YouTube standards. But the video had one specific ingredient: a section at 5:42 called

“Do you need a Mac Mini?”

That timestamp created a narrative. Not “here’s a software tool.” Instead: “here’s a reason to buy a $500 piece of hardware and turn it into an always-on personal AI server.” The Mac Mini M4 — quiet, 6–12 watts, sitting on your desk — became the physical home for something that previously lived only in the cloud.

Within 72 hours, five other channels published tutorials with the same format: “I bought a Mac Mini for this.” The genre existed before the tools to fill it. OpenClaw gave it content.

January 30: Fireship covers it. 1.8 million views. The rebrand to “OpenClaw” happens the same day.

February 12: episode #491 with Steinberger. Title: “Viral AI Agent that Broke the Internet.” 1 million views. This is no longer a developer product — it’s mainstream.

By this point, the project is gaining 25,000 GitHub stars per day. Total ecosystem around it: 5,400+ community-built skills, a dedicated skills repository at 36,000 stars. Cloud providers scrambling — Scaleway launches managed Mac Mini M4 instances specifically for OpenClaw. Lightning.ai offers one-click deployment. Useclawy.com offers a $99 lifetime hosted option with “no Mac Mini needed.”

The “no Mac Mini needed” narrative exists as a direct response to a Mac Mini demand spike that nobody planned.

What the industry did next

February 15: Steinberger announces he’s joining OpenAI. He notes that both Zuckerberg and others reached out. He chose OpenAI.

Read that again. The creator of a product that went viral in January gets calls from Meta’s CEO by February. He joins the most valuable AI company in the world the following week.

OpenClaw itself moved to an open-source foundation. The project didn’t disappear — it accelerated.

February 24: Notion launches Custom Agents v3.3. Up to 20 minutes of autonomous operation. Claude Opus, GPT-5.2, Gemini as model options. 21,000 custom agents created by early testers. 2,800 running continuously.

February 27: Perplexity launches “Perplexity Computer.” A cloud-based agentic system unifying 19 AI models, running autonomous agents in isolated environments for hours. $200/month. Press coverage explicitly describes it as “Perplexity’s own OpenClaw.”

They’re not even pretending it’s unrelated.

Meanwhile, Meta acquired Manus — a Singapore-based autonomous agent startup — for over $2 billion in late 2025. Manus scored 86.5% on the GAIA benchmark versus OpenAI’s 74.3%. It’s now being absorbed into Meta AI across Facebook, Instagram, WhatsApp, and Messenger.

Google has Project Jarvis. Microsoft has Copilot Pages with “digital coworkers.” Apple is positioning Intelligence 2.0 as Siri-as-personal-agent. On March 10, Tencent launched QClaw — a WeChat-integrated clone. 1,000 users queued on day one.

The entire personal AI agent category went from “interesting developer experiment” to “everyone’s core product roadmap” inside 60 days.

The Anthropic irony

Here’s the detail worth pausing on.

The model that powers OpenClaw is Claude — built by Anthropic. Most OpenClaw users are running their agents on Anthropic’s infrastructure.

Anthropic has no consumer-facing agent product. No OpenClaw equivalent. No personal AI framework. Their computer use capabilities exist at the API level for developers.

They built the engine. Someone else built the car. The car sold 309,000 units in four months, triggered a $2B acquisition by Meta, recruited the creator to OpenAI, and forced every major tech company to accelerate their agent roadmap by at least a year.

Anthropic gets the API revenue. The narrative belongs to someone else.

What this is actually about

This is a story about how viral software works in 2026, but it’s also a story about something older: the power of a concrete narrative over an abstract capability.

AI agents existed before OpenClaw. OpenAI had them. Anthropic had computer use. Google had project-level assistants. The technology was available.

What OpenClaw had — specifically, what Alex Finn’s video created — was a physical anchor. A $500 device you could buy on Amazon, plug in, and point at a piece of software. “You own this. It runs on your hardware. It works while you sleep.” That’s not a feature. That’s a story.

The Mac Mini wasn’t marketed as an AI server. Apple didn’t plan this. A YouTuber with under a million subscribers created the use case by describing it clearly at timestamp 5:42.

Then Fireship made it credible. Then Lex Fridman made it mainstream. Then Jensen Huang made it historic. None of this required a marketing budget. It required one person to describe something concretely enough that other people could imagine themselves doing it.

The uncomfortable question for everyone building AI products

Every company on this list — OpenAI, Anthropic, Google, Meta, Perplexity, Microsoft — has larger teams, larger budgets, and earlier access to the underlying technology than Peter Steinberger did.

They were all working on agents. None of them produced the moment that validated the category.

A vibe-coder working nights and weekends did. A YouTube creator with 800,000 subscribers made it tangible. And then the world's most innovative companies spent the next 60 days scrambling to respond.

The lesson isn’t “vibe coding beats enterprise engineering.” The lesson is that narrative moves faster than R&D, and the person who makes something concrete and relatable first owns the category — regardless of who built the better technology.

If you’re building anything in AI right now, the relevant question isn’t “is our product technically superior?”

It’s: “Does someone with a camera and 800,000 subscribers have a reason to make a video about it?”

IMPORTANT: The interface is in Chinese, so all screens you'll see are shown via screen translation.

Today I ran a five-year simulation of a fitness club network operating in Ukraine — under conditions of active war, demographic decline, and accelerating population outflow.

76 virtual people participated. Each had a personality, a memory, a bias, and a stake. They argued, reacted to events, and changed their behavior across simulated quarters. The system tracked how each audience segment — young professionals, families, older members, emigrants who might return — shifted their relationship to the brand over time.

The tool that made this possible: MiroFish. A 20-year-old student built it in 10 days using vibe coding. It has 15,500 GitHub stars. Shanda’s founder Chen Tianqiao committed $30M to it within 24 hours of seeing the demo.

I spent around 24 million tokens running the simulation. That number matters. Let me come back to it.

Can you imagine the cost of this research via Opus? :)

What MiroFish Actually Does

You feed it a document — a brand research report, a market analysis, a news package, anything with structured context. I had a Brand Health Monitor Report done by the external agency with the interviews of 600+ respondents all over the country. The system reads it, builds a knowledge graph of every entity mentioned: people, organizations, audience segments, media outlets, and competitors. Each node in that graph becomes an agent.

Each agent gets a full persona: age, gender, MBTI, professional context, values, communication style, and a bias score toward the topic you’re studying. Then you set the simulation parameters — a five-year horizon broken into quarterly rounds, with events injected at each period (a new wave of emigration, an economic shock, a competitor opening nearby, a ceasefire announcement).

In each round, every agent sees a shared information feed and decides: post, comment, react, or stay silent. The decisions come from their character and their memory of previous rounds. The system records the dynamics — who leads opinion, who goes quiet, which communities form, which segments disengage.

At the end, a Report Agent synthesizes everything into an analytical brief. You can interrogate it.

The Simulation I Ran

The question I asked: How will different audience segments of a Ukrainian fitness brand behave over 5 years given demographic decline, youth emigration, and sustained probability of active conflict?

The system generated 76 agents from a brand research document. That’s 76 synthetic stakeholders — not survey respondents, not hand-crafted personas, but entities extracted directly from real research data and given behavioral autonomy.

Events injected across the simulation horizon:

• Continued military operations, periodic escalation

• Accelerating demographic shift (-15% active population by year 3)

• Economic compression is reducing discretionary spending

• Emigrant communities forming abroad with partial brand loyalty

• Competitor consolidation in the market

The results were specific in a way that focus groups rarely are. Certain segments showed resilience. Others showed a clean exit trajectory. The model identified which audience clusters would become the core of the business by year five — and which were already gone regardless of what the brand did.

The Number That Puts This in Context

24 million tokens sounds abstract until you compare it to what this analysis would cost done traditionally.

The global market research industry is worth $84.6 billion per year. A McKinsey or BCG strategy engagement covering market trajectory analysis runs $500K–$1.25M and takes 8–12 weeks with a team of 5–15 analysts. A RAND Corporation demographic research contract: $500K–$5M. A custom agent-based simulation model built by an academic team: $50K–$500K and 3–12 months of development.

Traditional consumer survey covering 1,000 respondents: $50,000–$150,000. A 5-year market forecast from a top consulting firm: $150,000–$500,000+.

The 40M tokens I spent on MiroFish using a cost-efficient LLM (MiniMax M2.5 via OpenRouter at $0.27/1M input tokens) cost roughly $8–15. With a less optimized model choice, the same run could reach $300–500. With GPT-4, you’re looking at $1,000–3,000 for the same simulation.

This is a 1,000x–10,000x cost reduction against the traditional benchmark. The time compression is equally dramatic — hours instead of months.

What This Means for the $30 Warning

24 million tokens is a lot. At GPT-4 pricing, that simulation would cost $1,500+. It’s easy to run up a significant bill if you’re not paying attention to model choice.

• The technical reality: MiroFish consumes 14,000–18,000 input tokens per agent per round. Multiply by 76 agents and 40 rounds, and the token math compounds quickly. A few specific rules before you start:

• Choose your LLM carefully. MiniMax M2.5 ($0.27/1M input) or Qwen-plus ($0.30/1M) are purpose-built for high-volume agent workloads. GPT-4 is 10–15x more expensive for the same task. Run the math before you hit start.

• Start small. 20 agents, 15 rounds. That’s a valid test that costs under $3 and tells you whether the simulation is giving you a useful signal.

• Scale deliberately. Only scale to 76+ agents when you have a question worth the compute.

Who Should Run This Before Anyone Else

Every CMO doing demand forecasting for a new market entry. Every founder assessing product-market fit in a volatile environment. Every strategist trying to understand how different audience segments will react to a positioning change, a price increase, or a crisis.

This is particularly powerful at business launch. Before you commit to a market, you can simulate how the market responds — not based on gut feel or a 100-person survey, but based on a structured behavioral model of everyone relevant to your success.

The tool is not perfect. LLM agents behave the way the model thinks a persona would behave — not exactly like real humans. Quantitative predictions are unreliable. But for directional intelligence — understanding the shape of a market’s response, identifying which segments are structurally your allies and which are structurally indifferent — it’s genuinely useful.

[SCREENSHOT 5: Report Agent output — the final analytical brief generated after simulation completes. Show the structured findings about audience segment behavior, key insights, and the conversational interface where you can ask follow-up questions.]

The Shift That Just Happened

The global market research industry exists because understanding how humans will behave at scale used to require scale to study. You needed large teams, long timelines, expensive methodologies.

The computing equivalent of a $500,000 consulting engagement is now accessible for the cost of a few API calls. The analysis that a team of 15 McKinsey analysts would take 10 weeks to produce can be approximated — with different tradeoffs — in an afternoon.

This doesn’t replace judgment. You still need to know what question to ask, how to interpret the output, and what to do with the findings. The analytical intelligence still has to come from somewhere.

But the infrastructure for simulation at scale? That just became a $100 decision instead of a $500,000 one.

MiroFish is early, imperfect, and running on a GitHub repo that a student shipped in 10 days. It’s also a preview of what market intelligence will look like in three years.

If you’re in marketing, now is a good time to get familiar with it before it becomes table stakes.

I find this funny. But I also think it points to something real.

Two rooms, zero overlap

Here’s what’s actually happening right now, across two very different communities:

In Discord — Hugging Face servers, AI agency communities, agent-builder channels — there are tens of thousands of people fine-tuning models, shipping automation tools, building multi-agent systems, running prompt experiments, and figuring out what AI can actually do in production. They move fast. They break things. They share findings in threads that disappear in 48 hours and never make it to a newsletter.

On LinkedIn — the feed that senior marketers actually check — there are thought leaders posting about “leveraging AI for content strategy.” Sharing articles about which tools will “transform marketing in 2026.” Explaining AI to audiences who nod along and save the post.

These two groups are not talking to each other. And both are paying for it.

What builders are missing

The Discord builders can ship. They understand the technical layer — agent orchestration, function calling, RAG pipelines, and eval frameworks. They know what’s actually possible right now, not just what’s in the press release.

What many of them can’t do: explain why it matters to a customer. Write positioning that lands. Understand why a technically impressive automation doesn’t convert. Figure out which problem is worth solving before building the solution for it.

Marketing judgment is slow to develop. It comes from years of reading customer interviews wrong, launching campaigns that flopped despite the brief looking solid, watching a price change kill retention in a segment you didn’t model. You can’t shortcut it with a GitHub repo.

So builders ship things that are technically interesting and commercially vague. They optimise for capability, not for the gap in the market.

What strategists are missing

Senior marketers have the judgment. They know how to read a market, build a brand narrative, structure a go-to-market, set a pricing architecture. They’ve been in enough rooms to recognise the difference between a good idea and a fundable idea.

What most of them don’t have: direct exposure to what’s actually being built right now, at the execution layer.

And this matters more than it sounds. Because the execution layer is being rebuilt from scratch.

The assumption that “we’ll hire developers for the technical parts” holds when the technical parts are stable. When the infrastructure is in motion — when the tools for automating research, content, analysis, and coordination are changing month by month — not understanding that layer means making strategic decisions with wrong assumptions about what’s possible.

The strategists are optimising for a distribution channel that’s quietly becoming less relevant. Running campaigns for traditional search while AI-referred traffic grows 527% year-over-year. Building SEO strategies without realising a WAF is blocking every AI crawler. Hiring teams for tasks that will be automated before the new hire finishes onboarding.

Why they don’t meet

Part of it is pace. Discord moves in hours. LinkedIn moves in weeks. By the time a technical insight becomes a LinkedIn carousel, the builders have already moved past it.

Part of it is identity. “Marketer” and “builder” feel like different job descriptions, different kinds of people. The assumption is that strategy and execution are separate disciplines requiring separate humans.

Part of it is that the overlap — people who have genuine strategic judgment AND direct technical fluency — is genuinely rare. Most people develop one or the other. Crossing over requires time that most senior professionals don’t have, and intellectual humility that’s hard to maintain after years of expertise in one domain.

What happens when they do meet

The interesting cases right now are people and teams where both layers are present. Not always in one person — sometimes it’s a strategist who understands enough to have a real conversation with builders. Sometimes it’s a builder who’s spent enough time on commercial problems to know what’s worth shipping.

What they share: the ability to ask “what problem does this solve?” and “can we actually build this?” in the same conversation, without one question killing the other.

The output is different. Not just technically impressive. Not just strategically coherent. Actually useful — and actually buildable.

One example from my own setup: I built an AI agent system for marketing operations. Named agents, role specs, orchestration logic. The strategic layer — knowing what each agent should optimise for, what the actual output should look like, how to measure whether it’s working — required years of marketing judgment. The execution layer — building it, debugging it, making it run — required direct technical engagement that no strategy document could replace.

Neither layer alone would have produced anything worth using.

The window

Only 23% of marketers are actively working on AI visibility and automation. The builders largely lack the commercial frame to turn their capabilities into marketed products. The strategists largely lack the technical fluency to know which capabilities to bet on.

That gap is a window. It won’t stay open.

The people who figure out how to operate in both rooms — or how to build genuine bridges between them — are going to have an asymmetric advantage for the next few years. Not because they’re smarter. Because they’re less siloed.

Happy to in the both of the worlds, but it is crazy hard.

CIM recognition of my modest person

124KB ∙ PDF file

Download

Download

A couple of weeks ago I stumbled on an open-source project called geo-seo-claude. GEO stands for Generative Engine Optimization — the practice of making your website visible to AI-powered search engines rather than just Google’s traditional crawler. The tool is a set of Claude Code skills that runs a full AI-visibility audit on any URL. Free, open-source, no API costs beyond Claude Code itself.

Install it for yourself: ttps://github.com/zubair-trabzada/geo-seo-claude

I ran it on my website.

35/100. Poor.

Here’s the thing, though. The score itself wasn’t the most interesting part. What got me thinking was how the tool works under the hood.

Five agents, one audit

When you run /geo audit <url>, the tool doesn’t work sequentially. It spawns five parallel subagents, each with a different specialty:

• AI Visibility agent — checks citability scores, AI crawler access, brand mentions across platforms

• Platform Analysis agent — tests readiness for ChatGPT, Perplexity, and Google AI Overviews separately, because each platform weighs signals differently

• Technical SEO agent — crawlability, security headers, Core Web Vitals risk, server-side rendering

• Content Quality agent — E-E-A-T signals, content freshness, expertise attribution

• Schema Markup agent — structured data detection, validation, and gap analysis

They run simultaneously. A synthesis layer then aggregates the scores into a composite GEO Score with weighted categories. The whole thing takes a few minutes.

The architecture is interesting because it mirrors how a consulting team would approach an audit — not one generalist doing everything sequentially, but specialists working in parallel. Except this costs you nothing and doesn’t require a kickoff call.

What the tool found on my website is a useful illustration of why this matters.

The robots.txt lies

My website’s robots.txt file was politely inviting every AI crawler in. GPTBot — welcome. ClaudeBot — come right in. PerplexityBot — door’s open.

The WAF (web application firewall) was having none of it.

Every non-browser request hit a 429 error with a JavaScript challenge. Policy said one thing, infrastructure said another. The result: every major AI search engine treated the site as if it didn’t exist. The sitemap was blocked too, so AI crawlers couldn’t even discover what pages were there.

That’s the kind of mismatch that makes every other optimization pointless. Perfect schema markup, clean E-E-A-T signals, a beautifully crafted llms.txt file — none of it matters if the crawler can’t get through the door.

Fix the firewall first. Everything else is noise.

The score breakdown

• AI Citability & Visibility: 28/100

• Brand Authority Signals: 35/100

• Content Quality & E-E-A-T: 42/100

• Technical Foundations: 34/100

• Structured Data: 38/100

• Platform Optimization: 34/100

Content scoring highest is both reassuring and slightly annoying. It means the substance is there — the actual expertise and information exists on the site. But the infrastructure and signals are failing it. Like having good products in a store with a locked door and no signage.

Why GEO is actually different from SEO

Traditional SEO optimizes for crawlers that index pages and return ranked links. You rank, users click, users arrive.

GEO optimizes for AI systems that consume your content and synthesize answers. If an AI doesn’t crawl you, doesn’t cite you, doesn’t have you in its knowledge base — you don’t exist in its answers. No ranking. No link. Just absence.

The numbers behind this shift are not subtle. AI-referred traffic grew 527% year-over-year. Gartner projects a 50% drop in traditional search traffic by 2028. Brand mentions correlate 3x more strongly with AI visibility than backlinks. And only 23% of marketers are actively doing anything about it.

That last number is the window. Most websites are currently invisible to AI search. Mine was one of them.

What gets fixed first

The tool outputs a prioritized action plan, not just a score. The top item was obvious once identified: whitelist AI crawlers in the WAF configuration. Low effort, critical impact. Everything else waits until that’s done.

After that: LocalBusiness schema for every location, comprehensive sameAs entity linking across platforms, author attribution on all content pieces.

Estimated score after Phase 1 fixes: 50-55/100. Not excellent. But visible — which is the baseline requirement for everything else to work.

The honest takeaway

If you’re a marketer and you haven’t thought about AI visibility yet, you’re optimizing for a distribution channel that’s quietly ceding ground. The users are moving. The traffic patterns are changing. The tools to audit this are now free.

Run the audit. The score might sting. The clarity is worth it.

Most people interact with AI the same way they use Google: open a tab, type a question, get an answer, close it. The difference is Google was never marketed as your personal assistant. ChatGPT was. And yet the architecture is identical — stateless, contextless, amnesiac by design. Every session you start, you’re explaining yourself to a stranger who has never heard of you.

I got tired of that about two months ago and decided to build something different. What I ended up with is a local setup I call Personal Super Agent — a folder on my home server with config files, skill scripts, memory files, and a scheduling system. The orchestration layer is an open-source tool called OpenClaw, which handles routing, context, and channel management. The interface is Discord, which I was already using for everything else anyway.

The way it actually works day-to-day: I have a Discord server with channels for different areas of work — content, trading research, projects, ops. Each channel is its own persistent session. When I open #substack, the agent knows we’ve been discussing blog topics. When I switch to #trading, it knows about positions and market research. Context doesn’t bleed between channels, and nothing resets. This morning it suggested this post topic on its own, based on what we built yesterday. I didn’t ask. That’s the whole point.

The server runs cron jobs on a schedule. At 7am Dubai time every morning, one of them pulls my calendar, emails, and recent work logs, then posts a briefing to my Telegram. Another one — the one that triggered this post — reviews yesterday’s activity and suggests five content ideas at the same time. There’s also a mission control channel where I can see the state of everything: which jobs ran, what they produced, where something failed. It’s not a polished dashboard, but it tells me what I need to know.

The stack itself is unremarkable. OpenClaw for orchestration, a Linux server for persistence, Discord as the main interface, Python scripts for specialized tasks like image generation or web search. Nothing exotic. The interesting part isn’t the technology, it’s the decision to treat the AI like infrastructure rather than a tool you visit.

That shift — from tab to persistent system — changes what’s possible. An AI that lives somewhere accumulates. It knows what you decided last week, what you’re working on right now, what your voice sounds like, what you care about. An AI in a tab knows none of that, no matter how good the model is. The gap between them isn’t a feature gap. It’s an architectural one.

Last month my marketing budget got cut by 27%. Season gone, Not trimmed — cut. Q1 was already behind. The gap wasn’t going to close itself.

The usual move: renegotiate, replan, try to do more with less. I did something different. I spent two days building a trading bot on a prediction market.

Not to escape the problem. To think about it differently.

Here are three things prediction markets taught me that no marketing framework ever did.

1. Price your beliefs, don’t just state them

When you place a bet on Polymarket, you don’t get to say “this looks promising.” You have to assign a number. Bitcoin above $85k by Friday — at what probability? You’re paying for that position. The cost makes you honest.

Most campaign briefs don’t work like this. Someone says “we think this channel will perform.” No one asks: perform at what confidence level? If you had to buy that position for real money, what would you pay?

I started running my marketing assumptions through this filter. If this were a Polymarket contract, what would I price it at? Turns out a lot of “strong hypotheses” price out at around 55%. That’s barely better than a coin flip. Not where you want to cut the budget.

Expected value isn’t a trading concept. It’s the thing you’re actually calculating when you allocate spend — you’re just usually doing it wrong.

2. Bet sizing matters more than bet selection

My bot made 9 trades in one session. The entry logic was decent. The position sizing was not. It deployed too much capital into single markets, and when two of them went sideways simultaneously, the losses stacked.

In trading this is called poor bet sizing. In marketing we call it “doubling down on what works.”

Kelly Criterion — a formula used by serious traders — says your position size should be proportional to your edge, not your conviction. Conviction can be high and your edge can still be small.

When I had to reallocate a 27% smaller budget across channels, I stopped asking “where do we believe in most?” and started asking “where do we have actual edge?” — meaning: demonstrated results, defensible data, a mechanism we understand. The answer was different from what my instincts said. And it was right.

3. When the market knows something you don’t

Here’s the part I didn’t enjoy: the prediction market was right more often than I was.

I built the bot because I thought I could spot patterns. RSI signals, news sentiment, and short-term momentum. The bot won some, lost some. After 48 hours: roughly break-even minus fees. The market had already priced in most of what I “knew.”

Marketing has the same dynamic. When you’re convinced your channel is undervalued, it’s worth asking: why isn’t everyone else seeing this? Competitors, agencies, benchmarks — they’re a kind of market. When the whole industry moves away from a channel, there’s usually a signal in that.

Contrarian bets are expensive to be wrong about. Be sure you have information the market doesn’t — not just a different opinion.

The actual numbers

I started with $50. Built the bot in one day with an AI agent running locally on my machine. The bot entered 9 positions. Two paid out correctly. The rest were technically broken — a state tracking bug caused it to hold both YES and NO tokens on the same market simultaneously.

Lost nothing significant. Spent about $1 in transaction fees learning that correct position tracking is harder than correct trading logic.

Same lesson applies to every marketing automation project I’ve run: the edge isn’t in the idea. It’s in whether your measurement is accurate enough to know if it’s working.

Try it yourself. Put $20 on Polymarket this week. Not to profit — to practice assigning real probabilities to things you usually just assert. It takes about three losing bets to stop saying “I’m pretty sure” and start asking “what exactly am I pricing here?”

If this was useful, subscribe. I write about what I’m actually running — the experiments, the bugs, and what held up....