Loading page…
A productized content service turns recurring B2B blog work into predictable revenue and a production line.
profitable since launch · 14 people
A four-figure monthly service can fund a repeatable delivery system before you build software for the same audience.
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
Brian Casel started Audience Ops as a done-for-you content marketing service for software companies and other B2B online businesses. He formed the idea at MicroConf, launched within 30 days, and had about three paying customers at the start, rising to five within the first two months. Revenue reached roughly $5K–$6K MRR in the first month. After two or three months, he intentionally paused sales to document delivery, build systems, and bring in help. He reopened sales around month six or seven. At the talk, about eleven months after the idea took shape, he said monthly recurring revenue had crossed $38K, the company had been profitable since the beginning, and the team numbered about 14. The service produced 40–50 blog articles for clients in the week of the talk. Casel used the service as a base to explore adjacent WordPress plugins and training for the same audience.
Audience Ops reached its first clients through Brian Casel’s existing network, warm email, and audience. He had spent years building and selling software for online businesses, so the target buyers were peers who already knew his work and understood the value of content marketing.
The quick-reference card — acquisition channels, replication playbook, risks & traps, and our verdict — is members-only.
Join the Unicorn Club — $5/moCancel anytime, in one clickPaste into Claude Code / Codex and get a working version of this product end-to-end.
Two production-grade prompts per idea — a full build spec and an SEO growth plan — plus 10 tailored build specs a week. Members only.
Join the Unicorn Club — $5/moCancel anytime, in one clickEvery claim traces back to a listed source — open any of them and check the number yourself. The exact words are quoted below, with a timestamp that jumps to the second each figure is said.
“Just a couple days ago, I think we crossed 38K MRR.”
2:52 · hear it in the videoData credibility: Brian Casel reports the customer, MRR, profitability, staffing, and weekly output figures in a conference talk. The $38K MRR, initial $5K–$6K MRR, 14-person team, and 40–50 articles per week are founder-reported and unaudited; no financial statements, client roster, margin breakdown, or revenue concentration is shown. The video metadata description says over $30K MRR in nine months, while the talk itself says $38K MRR at roughly eleven months; this entry follows the spoken transcript and does not reconcile the differing time markers.
The first dollars came from selling the done-for-you blog writing and content promotion service to software companies, not from building a self-serve product first. Within the first two months Audience Ops had around five customers and roughly $5K–$6K in monthly recurring revenue.
The first reinforcing loop was customer-funded process improvement. The early clients created enough delivery volume for Casel to see where writing, editing, design, project management, and administration needed to connect.
Casel reduced the risk of an empty launch by selling directly into a market where he already had relationships, then treating the first customer work as operating research.
Our read: Audience Ops began as a done-for-you content marketing service: blog writing and content promotion for software companies and B2B online services. The central product is not a writing marketplace or a single software tool; it is a managed production system that moves work through writers, editors, graphic designers, project management, and support. Casel described a methodical production line that allowed the service to operate without his presence in each client task. This matters because buyers pay for dependable output and reduced coordination burden, not simply words on a page. A founder copying the model should define the editorial promise tightly: who the content serves, what research and editing are included, how revisions work, and where promotion ends. The service can later support adjacent plugins or training, as Audience Ops did, but the recurring delivery has to work first. Clear boundaries protect both margin and client trust when several specialists contribute to one monthly package.
Our read: Audience Ops sold recurring service packages at a price point Casel describes as four figures per month, aiming at a larger business problem than a $49 monthly software tool. At $38K MRR, the business had reached meaningful scale, though the exact package prices and customer count are not part of this account. The model is straightforward: clients pay repeatedly for blog production and promotion, while a staffed process delivers the work. Casel said the business was profitable from the beginning and remained profitable as it reached $38K MRR. A productized service owner should calculate capacity per client, editing and project-management hours, contractor or employee cost, and revision load before quoting a monthly rate. The target is a package with enough scope consistency to train a team and enough gross margin to support sales and account management. The same customer base also gives a low-cost test bed for adjacent products; do not count prospective plugins or training as revenue until they sell.
Our read: The earliest acquisition advantage was access to software founders through Casel’s existing network and audience. He mentions warm emails, referrals, and people he knew in the online business community. Choosing a market he cared about made those conversations credible and gave him a reason to keep investing in the same customer group. The model did not begin with paid advertising or a large outbound operation; founder-led relationships created the first contracts. Once the service had a repeatable production process, Casel hired a salesperson and marketing person to reduce reliance on his own selling. For a new operator, start with specific warm contacts who already publish content or have a visible content gap. Offer a short diagnostic, sell a paid initial month, and ask satisfied customers for an introduction to a peer. Track conversations, proposals, close rate, and retained accounts separately. A personal audience can open doors, but a documented referral and sales process is what makes the channel transferable.
Our read: Casel emphasized people and process more than software infrastructure. The service’s weekly production path included a writer, editor, graphic designer, project manager, and assistant. The team reached about 14 people while delivering 40–50 articles in a week. The company was profitable from the beginning, but the talk does not give cost breakdowns, salary levels, contractor rates, or gross margin, so those should not be inferred. The operational lesson is to model labor per deliverable and keep quality control visible. A content service can lose its economics through uncapped revisions, unclear research standards, client delays, or founder time hidden inside account management. Build templates and handoffs before scaling volume, then review actual hours against each client’s monthly fee. Keep a modest tool stack for briefs, editorial calendars, approvals, and analytics; software only helps if the workflow is already clear. The claimed profitability is founder-reported and does not establish margin at any specific revenue level.
Our read: Copy the sequence: choose a market you understand, sell a recurring service at a meaningful price, learn from the first customers, and pause sales if delivery needs structure. Audience Ops moved from early clients to a production process, resumed sales after several months, and grew to $38K MRR with about 14 people. The strongest transferable idea is that the service can finance both operating knowledge and later products for the same buyer. Change the offer to a niche where you can judge quality and reach buyers directly; content production is crowded, and generic “we write blogs” positioning makes differentiation difficult. Define the outcome and editorial standards before hiring a large team. The risks are labor costs, quality drift, client churn, and overdependence on the founder’s network. Adjacent software or courses can broaden revenue, but they also divide attention. Treat each expansion as a small paid test, and preserve the service economics that gave the company time to build.
The four founder playbooks — first customers, first dollar, the flywheel, the silent stretch — are in the Unicorn Club, on this idea and on all 1,403 others. The story, the numbers, the sources and every later section stay open to everyone.
Join the Unicorn Club — $5/moCancel anytime, in one click