Case Study • Vidora

How We Turned a YouTube Info Business Into a $370K+ Recurring Revenue Product

A YouTube coaching business doing $5 million a year had a method its students trusted, and a research process they still did by hand: finding ideas worth making, checking which channels were monetized, and writing a script from scratch for every video.

We turned that process into a single usage-based platform, so its revenue grows with how much students publish. It crossed $30,000 in monthly revenue in its first month, has attracted more than 1,000 subscribers, and has generated over $370,000 in lifetime revenue.

$370K+
Recurring software revenue
$30K/mo
Monthly revenue in month one
1,000+
Subscribers since launch
8 weeks
From development to launch
The Problem

The Expensive Problem

A $5 million coaching business where each student paid only once

At Ionio, we approach every project through a two-layer framework.

Layer 1: how does this help users achieve their goals 10x better, faster, or cheaper?

Layer 2: how does solving that problem create compounding business value?

Our client ran a coaching program that taught people how to build and earn from YouTube. It was a successful business doing $5 million a year, run by a small, focused team with a proven program and a funnel that kept bringing in new students.

Every student paid once to learn the method. That single purchase was the business's only source of revenue, so each month began with finding and enrolling new students.

Preparing One Video

Layer 1 · For the User

Ten tabs for one video, now one platform.

Layer 1: The User Problem Every student hit the same wall before they could publish anything. For every single video, they had to:
  • Pick a topic and search YouTube for videos already performing on it
  • Check each video's views, the size of the channel behind it, and whether it was monetized
  • Pull transcripts and paste them into ChatGPT to tease out an idea and a first draft
  • Write the title, description, tags, and hashtags, usually in a separate tool for each

The tools that existed covered fragments. The best-known research tool returned a list of videos with view and subscriber counts, then left every next step to the user. SEO tools were a row of single-purpose generators.

The steps were identical every time, and every student did them the same way. A routine like that is a product waiting to be built.

Paid Once vs Paid Monthly

Layer 2 · For the Business
MONTH PAYSONCE PAYS EVERYMONTH NOTHING MORE COMES IN M1M2M3M4M5M6 ONE SALE SELLABLE

A course is paid once, a subscription is paid every month.

Layer 2: The Business Problem Students paid once, went through a cohort with a fixed end date, and moved on. To fill the next intake, the business had to spend on ads and distribution all over again.

The business also had very little enterprise value, because it was only worth as much as its next cohort. Revenue reset to zero every time an intake ended, leaving nothing recurring or predictable to value it on.

The audience was real, but the model only captured its value at the first sale. The business could only be judged on how well the next intake filled.

That made it a launch business. It was hard to grow predictably, and harder still to sell.

A research and scripting platform gave the business:

  • A recurring revenue line: monthly subscriptions alongside one-time course sales
  • Higher lifetime value: students who paid once now had a reason to keep paying every month
  • Enterprise value: a software product with its own paying subscribers, which gives the business an asset it can be valued on
  • Revenue tied to publishing: the more students use the platform, the more value they get from producing videos, while increased usage generates more revenue for the platform through credit-based pricing.

Why This Was Hard

We had built every individual part before. The APIs were mature, and the AI layer was a set of focused prompts. The difficulty sat in three product and pricing decisions, each of which decided whether students would keep paying after the first month.

Covering the Whole Job in the Same Build
Scope

The client asked for video search and script generation. On their own, those make a tool students use once and drop. To keep students subscribed month after month, the product had to take a video from topic to publish-ready, which meant adding channel analysis and a full publishing toolkit. All of that had to fit into a fixed-price, eight-week build without stretching the timeline.

What this meantMore of the job, in the same eight weeks.

Costs That Grow With the Best Users
Metered

We first planned a flat monthly subscription. But API costs varied by action, so the students who used the platform most would also cost the most to serve, and our best users could become our least profitable. We switched to credit-based pricing, with each action priced by its API cost, so heavier use meant more videos for students and more revenue for the platform.

What this meantThe best users became the most valuable ones.

Competing With Free Tools Students Already Used
Switching

Students were already getting by with YouTube search, a stats tool, ChatGPT, and a few free SEO generators. To be worth paying for every month, the product had to beat that setup from the first session. We mapped which tools students used, in what order, and where they lost time between them, then designed every screen around closing those gaps.

What this meantClearly faster than the tools students already had.

Students already knew how to research a video. The job was to put that whole routine in one place, and price it so the busiest students became the most valuable ones.

Classical-style painting depicting a lively Bacchanalian scene with numerous figures, some nude and adorned with grapevine wreaths, dancing and drinking amid a wooded landscape. Central figures include a woman draped in blue riding a goat-like creature, others playing instruments, holding wine vessels, and engaging in playful revelry. The foreground shows a fallen jester’s costume and broken masks. Tall trees and a dusky sky form the background, evoking a festive and mythological atmosphere.
The Philosophy

The Leverage Test

Distribution has become the scarce part of building software.

Building a product is faster and cheaper than it has ever been. Finding people who will trust it, try it, and pay for it is still the hard part.

Many businesses have already solved that part. Coaches, course creators, and community owners spend years earning an audience, and usually earn from it once per customer. An audience that already trusts you is the hardest part of a software business to build. When a business has one, it has leverage.

We look for three conditions together:

DISTRIBUTION an audience they own A COMPLEX TASK THAT REPEATS research and judgement DOMAIN EXPERTISE knows how it is done The Product
Where all three meet, the product is already waiting.
  • Distribution An audience the business already reaches directly.
  • A complex repetitive task A multi-step job that audience repeats again and again, involving research, several tools, and real judgement, which is exactly the work a SaaS product is built to take over.
  • Domain expertise A deep enough understanding of the audience and the task to build the right product.
THE THREE CONDITIONS DistributionRepeated taskDomain expertise MONTHLY REVENUE M1M6M12 WITHOUT DISTRIBUTIONIt struggles to launchWITHOUT A REPEATED TASKIt gets tried onceWITHOUT DOMAIN EXPERTISEIt misses the pointWITH ALL THREEStudents pay every month
Take one away and the product stalls. All three together keep students paying.

Each condition covers a different risk. Distribution gives the product a route to its first customers. The repeated task gives them a reason to keep using it. Expertise makes sure it solves the problem they actually have. Take one away and the product struggles to launch, gets tried once, or misses the point.

When all three are present, the business is a strong fit for a SaaS product built around them. That product adds a new line of recurring revenue, built on assets the business already owns. Month after month, it builds enterprise value in place of one-time payments that reset with every cohort.

This client met all three. It had students who had already paid for the program, a research and scripting routine each of them repeated for every video, and a method built on knowing what makes a YouTube channel work. Turning that familiar routine into software gave the business its first product that students paid for every month.

A small build lifts a large result only because the long arm, the audience, was already built.

The Product Walkthrough

The Platform in Action

Vidora brings your whole pre-publishing routine into one place. Search a topic, audit your channel, write the script, then review what performed. Every step draws on the same data, so each tool feeds the next.

01 / Discover Ideas

Research the videos that already work

Search any topic and see which videos are already getting views in that niche. Each result shows the channel, its view count, and a high engagement tag when a video outperforms its category. Save the strongest ideas to your research library, and each search takes seconds.

Discover video ideas: a search for small apartment makeovers with results showing views, likes, and engagement tags
02 / Channel Audit

Check channel health in one audit

The audit reviews your channel profile and publishing habits, marking each factor as healthy or in need of work. In this example, the title, about section, and metadata pass, while upload cadence is flagged because the channel uploads less than once a week. Engagement is measured against the category median, so each number shows how the channel compares with its niche.

Channel audit: total videos, subscribers, total views, and a checklist of channel and publishing factors with engagement against the category median
03 / Script Studio

Write a timed script outline

Script Studio turns a topic into a timed outline with an opening hook, main steps, common mistakes, and a closing call to action. Each section carries a time range, so you know the video's length before you record. The video brief beside it sets the target audience, the goal, and the key points, and the finished outline exports in one click.

Script Studio: a timed script outline with an opening hook, steps, common mistakes, and a video brief
04 / Video Performance

Track your last 25 uploads

Video Performance shows averages for views, likes, and comments across your recent uploads, with a chart for each video from oldest to newest. Peaks reveal the videos that worked, and dips show where a format lost momentum. Those results feed back into your next search, so each new video builds on what the last one taught you.

Video Performance: average views, likes, and comments across the last 25 uploads, with views and likes charted per video

What We Built

Ionio owned the product from scope to launch, including the feature set, the credit model, development, deployment, and support.

Discovery & Scoping

The client came to us through a partner agency that works with coaching and course businesses, the first of several clients they went on to refer. The product idea was his. We reviewed the tools his students relied on, researched the APIs underneath, and returned a fixed-price proposal for the full workflow.

The tools students already used

Video search
Channel stats
ChatGPT
SEO generators
Search dataunderneath
Channel dataunderneath
Language modelunderneath
SEO dataunderneath
Fixed priceFull workflow, one proposal

Every tool reviewed, the whole job priced

The Core Platform

One login and four tools, laid out in the order a student already works. Research a topic, unlock a channel, draft a script, then package the video for publishing. Each step is simple on its own. The value is that a routine spread across a row of tabs now runs in one place.

Vidora
Research3 videos found
ChannelsMonetized
ScriptsDraft ready
PublishReady to post

One login, four tools

The Credit System

We first planned to price the platform as a standard SaaS subscription, then realised a flat fee would make our most active students the least profitable, so we built a credit system. Each subscriber gets a monthly credit allowance, and every action costs credits in proportion to what it costs to run. We modelled a heavy month from the API costs up (90 searches, 30 deep analyses, and 400 scripts) and set the plan so that month still fit inside it with margin to spare.

Monthly
allowance
Inside
the plan

A heavy month of use

Searches90
Deep analyses30
Scripts400
Margin to spareLeft over

A heavy month, inside the plan

Launch & Support

The platform launched straight to the program's existing students. We then handled support for more than 200 users ourselves, from emails and account fixes to cancellations, so the client owned a software product without having to run one.

IIonio SupportVidora · 200+ users

Priya S.Email

I can’t log in after changing my email

nowResolved

Marcus T.Account fix

My credits didn’t refresh this month

nowResolved

Aisha K.Cancellation

How do I cancel my subscription?

nowResolved

Support run by Ionio

Internal Infrastructure

Technical Infrastructure

The technical goal was to keep the stack mainstream, so the product was fast to build, easy to maintain, and inexpensive to run for every user.

Frontend

React

React powers the student-facing app. Searching, unlocking channels, generating scripts, and building metadata all happen without page reloads.

Backend

Node.js and Express

Node.js and Express handle server-side logic, user accounts, and the credit system. JavaScript throughout kept the stack consistent.

Database

PostgreSQL

PostgreSQL stores user accounts and application data.

YouTube Data

YouTube data and channel statistics APIs

A third-party YouTube data API powers topic search, video data, and transcripts. A channel-statistics API powers the deep unlocks and channel audits.

AI Layer

OpenAI GPT-4

OpenAI's GPT-4 generates scripts, titles, descriptions, tags, and hashtags. Each generator is a focused prompt behind a simple form.

Cloud Infrastructure

Docker on AWS, monitored with Datadog

Docker containers on AWS, with Datadog monitoring and logging in production so the team could see errors and failed API calls as they happened.

The Results

The Business Impact

One student's routine, converted at about $47 a month

Before the platform, every dollar the business earned came from a one-time course sale. That revenue was strong, but it reset with every cohort and relied on the founder's distribution to fill the next intake.

The platform added recurring revenue alongside it. At its peak, around 400 students were subscribed at the same time, paying every month, with or without a new cohort running.

$0 BEFORE · BURSTS AFTER · RECURRING ~400 PAYING AT PEAK
$30K/moIn the first month
1,000+Subscribers since launch
$370K+Lifetime revenue, paying about $47 a month on average

$30,000 a Month in the First Month. The audience already knew and trusted the program, so revenue arrived from the very first month. The platform crossed $30,000 in monthly revenue in its first month.

1,000+ Subscribers and $370K+ Earned. More than 1,000 students have subscribed, paying about $47 a month on average. Over its lifetime, the platform has generated more than $370,000 in revenue.

This changes how the business is valued. Course revenue is hard for a buyer to underwrite, because it has to be sold again each time and much of it rests on the founder's personal reach. Recurring software revenue comes with a subscriber base, a monthly revenue history, and retention figures that a buyer or investor can measure, forecast, and price. SaaS revenue is typically valued at 3x to 5x annual revenue, while course and service businesses are usually valued on a multiple of their EBITDA.

3× 5× SOFTWARE ARMPriced on annual revenue COURSE BUSINESSPriced on EBITDA WHAT A BUYER CAN MEASURE A subscriber base A monthly revenue history Retention figures 3–5×ANNUAL REVENUE, THE TYPICAL SAAS RANGE
The software arm stacks a second, higher-valued asset on top of the course business.

By building a software arm inside an information business, the client now owns a distinct SaaS asset that adds enterprise value on top of the income it earns.

Every student's routine converts into about $47 a month.

Project Roadmap

Our Approach

Seven days of scoping, an eight-week build across two milestones, then support and a roadmap for what came next.

Execution Timeline
Scoping Core product Complete & launch Support
Before the Build: Research and Scoping7 days
  • Reviewed the research, SEO, and channel analytics tools students already used
  • Researched YouTube data, channel statistics, and AI generation APIs
  • Modelled the cost of every action to design the credit system
  • Fixed-price proposal across three milestones, with seven days of scoping before development
Weeks 1 to 4: Core ProductWeeks 1–4
  • Topic and video search, quick and deep channel unlocks, and the GPT-4 script generator
  • User accounts and the credit system
  • First usable version in students' hands by week four
Weeks 5 to 8: Complete Product and LaunchWeeks 5–8
  • Title, description, tag, and hashtag generators, the tag extractor, and a channel audit for students' own channels
  • Staged releases, so students used the core features before the last tool shipped
  • Production deployment on AWS with monitoring, and launch to existing students in late 2023
After Launch: Support and RoadmapAfter launch
  • Eight weeks of included post-launch support: bug fixes and prompt tuning
  • A roadmap proposal in early 2024: YouTube account integration, a personalized idea generator, editable scripts, a stronger script generator, and short-form tools

The same product would move considerably faster today.

In 2023, this took two engineers about two months. That was before AI-assisted development changed how we build.

Retrospective

What We Learned

I.

Scope Around the Student's Whole Workflow

The client asked for two features, video search and script generation. Before writing the proposal, we mapped everything a student did between having an idea and pressing publish. That map had four stages, and the brief covered two of them. Channel analysis and the publishing toolkit sat on the same APIs and GPT-4, so adding them cost very little build time. They also turned a research tool into the place where a video got made from start to finish, which gave students a reason to come back with every new video. Since this project, we map the end user's full workflow before we scope anything a client asks for.

Lesson: Map the full workflow before you scope
II.

Build on Proven APIs Wherever Possible

Every tool in the platform sat on something that already worked. A YouTube data API handled search and transcripts, a channel statistics API handled the unlocks, and GPT-4 handled every generator. Our own engineering went into the flow that tied them together and the credit system around it. That choice kept the first version to eight weeks with two engineers, in 2023, before AI-assisted development, and it left the budget free for the decisions that shaped revenue, which were scope and pricing. We still start every build by asking which parts already exist as a reliable service.

Lesson: Save engineering time for what only you can build
III.

Price Every Action by What It Costs to Run

Classic SaaS pricing assumes one more user costs almost nothing to serve. AI products break that assumption, because every search, analysis, and script calls a paid API. Here, a deep channel analysis cost roughly twice as much as a search, and under the flat fee we first planned, the students who used the platform most would have cost the most. Credits priced each action above its cost, so heavier use always brought in more than it cost to serve. The busiest students became the most valuable ones. We carried the same model into the client's next product, and we now cost out every action before we set a price.

Lesson: Model the cost of each action before you set a price
IV.

Choose the Task Students Repeat Most Often

Students needed help with plenty of things, from setting up a channel to editing footage. The client's idea centred on research and scripting, and the reason it worked as a subscription was frequency. That routine ran before every single video, as often as a student published. With credit-based pricing, frequency carried straight through to revenue, because students who published more used more credits each month. How often a task comes back sets the ceiling on what a subscription can earn from it. It is now one of the first questions we ask when we run the Leverage Test on a new idea.

Lesson: Build on the task that repeats most
The Fit

Who This Is For

For coaching businesses, course creators, and community owners with a proven method and an audience that already trusts them, Ionio can turn that expertise into a software product your audience pays for every month.

The first question we ask is how often your students do the job you want to turn into software. A task they do once makes a useful tool. A task they repeat every week, or before every piece of work, makes a subscription.

Alongside frequency, we look for the same three things this client had.

I.

Distribution

An audience the business already reaches directly, through a program, a list, or a community.

II.

A complex repetitive task

A multi-step job involving research, several tools, and real judgement, which software can take over.

III.

Domain expertise

A deep enough understanding of the audience and the task to build the right product.

Most coaching businesses sell their method once. This one now had software that earned from it every month, and a recurring revenue line that carried on between cohorts.

Eight weeks from a routine students ran by hand to a platform they pay for every month. When an audience already trusts the method, software becomes the recurring revenue line the business was missing.

This YouTube coaching business proved that a program built on years of trust has a software product inside it. The research and scripting routine every student repeated now runs in one place, and the revenue it brings in arrives every month, between cohorts as well as during them.

What made it work was the thinking around the code. We scoped the product around the whole job, priced every action by what it costs to run, and launched to students who already knew and trusted the program.

How we operate
01 // Scope

We map the whole job first. Before we quote, we trace everything your students do between an idea and a finished result, then scope the product around that whole routine so it earns a place in every week.

02 // Pricing

We price for your busiest members. Every action is costed before launch, so heavy use always brings in more than it costs to serve, and your most active students become your most valuable ones.

03 // Launch

We launch to the audience you already have. Your program, your list, and your community become the launch, which is how this platform crossed $30,000 a month in its first month.

When to Talk to Us

You run a coaching program, course, or community, and your students already trust your method enough to pay for it.

They repeat the same multi-step job again and again, and you want income that carries on between launches.

When It's Still Early

Your method is still taking shape, or your audience is still growing.

Build those first. We are always happy to talk it through when the routine is clear.

Next Step

Let's Find the Software in Your Method

A 30-minute call. Tell us about your program and the routine your students repeat, and we will tell you honestly whether it should become a product they pay for every month.

Book an Intro Call Prefer email? contact@ionio.ai
Ionio  |  Turning Expertise Into Recurring Revenue