A Friday-evening message posted minutes before dinner rewrote one founder's autumn. On September 25, shortly before five o'clock, Josh Pickford offered his visibility system to other companies for a thousand dollars a month, delivered entirely inside Slack. Within weeks the roster swelled to roughly thirty clients, and the run-rate climbed from about $474,000 to nearly $570,000 a year. The episode's sponsor, zapier, frames the timing neatly: automation has matured enough that a single operator can sell outcomes once reserved for full agencies.
Pickford is no overnight newcomer. Across two decades of building internet businesses he accumulated deep search-optimization experience, then spent much of the year refining a private method for earning brand mentions inside AI-generated answers. That internal toolkit became First Index, a done-for-you service for companies that want to appear when prospective buyers interrogate chatbots. Instead of teaching clients software, he sells finished visibility: research, drafting, publication, and follow-up handled end to end.
The promise is straightforward: when someone asks a chatbot or discovery surface for a recommendation, the client's company should appear in the reply. Most delivery happens on the client's own site, tightening pages so models quote them accurately, plus outreach that corrects stale or mistaken claims circulating elsewhere. What the service avoids matters equally. Manufactured forum buzz and synthetic community praise are rejected as short-lived tricks that eventually poison trust, so effort concentrates on durable assets the client owns.
Measurement sits at the center. Assembling a single article can pull in around a hundred reference documents, all archived for later audit. Rankings data flows from Google Search Console while live checks run prompt variations through ChatGPT-style interfaces, recording whether each client surfaced or stayed invisible for each phrasing. Every result lands in a per-client data lake, and the daily agenda is chosen from evidence: whichever tweak the numbers crown most impactful becomes the next job.
Measuring answers, not just rankings
The timing reflects a wider research wave around generative-engine optimization. A princeton paper on the technique reported visibility lifts near forty percent from targeted rewrites, giving the young field an empirical anchor. Work published by seerinteractive adds texture on fan-out queries and freshness signals, explaining why coverage breadth and recency both move the needle. The trygeometrics playbook translates theory into craft: answers stitched from Bing-indexed sources with explicit citations, so each claim carries a traceable origin models can verify.
Execution leans on composable claude skills rather than one giant prompt. Onboarding, investigation, and drafting each live in dedicated sessions, so context from one customer never bleeds into another's work. An intake skill converts discovery answers into structured research briefs; a drafting skill turns those briefs into publishable pages in the client's voice. Because skills are modular files instead of tangled conversation history, routines stay portable, testable, and easy to clone for the next account.
Language models remain probabilistic, so deterministic code wraps every fragile step. Each account keeps a truth document of verified facts, and scripts confirm that figures and product claims stay consistent across hundreds of pages instead of drifting. Link counts, formatting rules, and similar constraints get counted mechanically rather than trusted to prose. An anthropic engineering essay on agent skills makes the same argument Pickford practices daily: wrap stochastic generation in software checks wherever repeatability matters.
Operations run through three familiar tools. Every customer gets a GitHub repository holding the work log, source research, ranking exports, and prompt-response archives. Notion stores briefing documents and tracks open questions, while Slack carries clarification requests that post automatically whenever generation stalls on missing detail. Replies from either surface get ingested back into one record, sparing a solo operator from hunting across a hundred scattered threads.
A one-person operating system
Unit economics explain why the model scales so aggressively. Bulk ranking data costs roughly a hundred dollars a week for the full roster, against several thousand a comparable Ahrefs-centered stack would demand. Against that base, thirty retainers near a thousand dollars a month each leave enormous margin even before growth. For answer-tracking itself, citality sells polished dashboards that monitor brand presence across AI outputs; Pickford simply hand-built a leaner equivalent from databases and scripts.
Clients, notably, pay for resolution rather than machinery. Reports arrive, rankings move, and buyers never touch the underlying tooling or need to learn new interfaces. Judgment calls stay human by design: whether to publish, how to frame a fix, when a claim needs executive sign-off. The pitch compresses what once required a ten-person crew into one accountable specialist whose software multiplies output while responsibility stays personal.
A parallel story sharpens the pattern. In Toronto, an agency operator named Adrian runs a twelve-client practice pairing claude-authored plans with zapier's MCP bridge, pushing finished work straight into WordPress installations and client reports. His stated goal compresses ten to fifteen hours of weekly effort per account down to about thirty minutes. Same philosophy, different plumbing: models propose, deterministic connectors dispose, and humans approve.
Copy the playbook, keep the guardrails
Pickford already repeats the formula in a second venture called Knock Off. Online sellers lose revenue when counterfeiters hijack listings and imagery across Amazon, Walmart, and similar marketplaces, yet each takedown demands assembled evidence and formal declarations no platform will accept from an anonymous bot. The service, priced near eight hundred dollars monthly, uses automation to detect suspects, gather screenshots, and draft the filing package, while the founder personally reviews and submits each case as the client's registered representative.
The transferable lesson starts with cloning workflows already proven on one's own assets before selling them to strangers. Package the finished result, not the cleverness underneath, and resist shortcuts: fabricated grassroots praise and unsupervised automated submissions invite bans and liability alike. Every autonomous step deserves a review gate where a person confirms facts and presses send. Copied discipline compounds; copied spam merely accelerates the penalty.
Key moments
AI commentary
"I find the unglamorous plumbing more convincing than the revenue screenshot. Anyone can announce a retainer; few can show the mention logs, truth documents, and per-client repositories that justify renewal month after month. What holds my attention is the restraint: separate sessions against context bleed, code where determinism counts, and a human finger on every consequential button. That discipline, more than any single tactic, is what I would steal first."
AI assessment
Skeptics reply that rented visibility decays fast. Search interfaces and model citation habits shift without notice, forum shortcuts invite penalties, and thirty accounts depending on one operator form a single point of failure. Should answer engines start ignoring the optimized signals, renewals could evaporate together rather than one by one.
A pragmatic next move is replicating the measurement spine first: pick five representative prompts, log mention outcomes weekly, and let the gaps dictate content priorities. Only after the baseline stabilizes should automation expand, one skill at a time, each wrapped in verification scripts before it touches production.
This content is not investment advice and makes no promise of similar revenue. Results reflect one founder's audience, timing, and labor; readers should validate costs and demand independently before committing money or quitting their jobs.
Sources
8 links; no other published story cites them. Stories sharing a link do not confirm each other; a source's origin is not inferred from how often it is cited.
- @youtube.com YouTube — The Next New Thing
- @collaborate.princeton.edu Princeton: GEO paper
- @trygeometrics.com Trygeometrics: GEO playbook
- @claude.com Claude: Agent Skills docs
- @zapier.com Zapier: agency MCP case
- @seerinteractive.com Seerinteractive: GEO research
- @citality.ai Citality: AI visibility tracking
- @anthropic.com Anthropic: Skills engineering
generative engine optimization · ai agencies · claude skills · answer engines · solo founder · content operations