How to Survive Your First Year Running a Video Studio: The Lessons We Learned at LeoStudio

The first year of LeoStudio was not a success story.

I want to be honest about that, because every studio's "about" page tells the same story—the scrappy beginning, the lucky break, the steady climb. Ours wasn't like that. Our first year was a sequence of expensive mistakes that we survived mostly by luck and stubbornness. We underpriced our work. We took clients we shouldn't have. We built a process that broke under pressure. We hired the wrong person at the wrong time.

And somehow, at the end of it, we had a business. A real one, with real clients and real revenue and a real point of view about what we did and why.

This article is the honest version of that year. Not the highlight reel. The mistakes, the numbers, the moments I wanted to quit, and the four lessons that now shape every decision we make. If you're starting a studio, or any service business, this is the retrospective I wish someone had written for me—because most of what I learned in year one, I learned by paying for it.

If you want to see what the studio looks like now, after all those mistakes, the work is on leostudiohq.com. Every case study there is a project that benefited from a mistake we made in year one.

Mistake 1: We Priced by the Hour

The first thing we got wrong was the most fundamental. We charged by the hour.

It seemed logical at the time. We were new. We didn't know how long projects would take. Charging by the hour meant we'd get paid for however long the work took. No risk of underestimating. No awkward conversation about scope.

The problem is that hourly pricing punishes efficiency and rewards slowness. Every hour we got better at the work, we earned less for the same output. Every project we completed made us faster, which made us cheaper, which meant we had to take more projects to make the same money, which meant we had less time to get better at the work.

We also had no idea how to estimate. Our first project, we quoted fifteen hours. It took forty. We ate the difference because we'd quoted a number and we weren't going to break it. That single project taught me that hourly pricing without experience is just a slower way to lose money.

The deeper problem was that hourly pricing framed the work as time instead of value. A 90-second onboarding video that cuts time-to-value from 14 days to 4 is not "twenty hours of animation." It's a business outcome worth far more than the hours it took to produce. When you price by the hour, you're telling the client that your value is your time. It's not. Your value is what happens after the video goes live.

We switched to fixed project pricing at the end of year one. It changed everything. We started quoting based on the outcome, not the effort. We started turning down projects that didn't justify the price. And we started making more money on fewer projects, which gave us the time to get better.

Mistake 2: We Said Yes to Everyone

For the first eight months, we said yes to every project that came through the door.

A local restaurant wanted a promo video. Yes. A fitness brand wanted an explainer. Yes. A startup wanted a product demo with a two-week deadline. Yes. A nonprofit wanted a fundraising animation with a budget that barely covered our costs. Yes.

The logic was survival. We were new. Every project was portfolio. Every client was a referral source. Saying no felt like turning away revenue we couldn't afford to lose.

But saying yes to everyone meant we were never great at anything. We were competent across a dozen industries and expert in none. Our work looked good, but it didn't work the way it could have, because we didn't understand the problem deeply enough to solve it.

The breaking point was a project that I should have refused. A client in an industry we knew nothing about wanted a video for a product we didn't understand, on a timeline that was impossible, for a price that was too low. I said yes anyway. The project took three times as long as we'd estimated, the client was unhappy with the result, and we lost money on it. That project cost us more than the revenue it brought in.

That's when I understood that saying yes to the wrong client isn't free. It costs you the time you could have spent on the right client. It costs you the reputation you build with the work that isn't your best. And it costs you the energy you need to get better at the thing you're actually good at.

We started saying no. It was terrifying. It also changed the business. The clients who stayed got better work. The work got a point of view. And the point of view attracted more of the right clients.

This is the story I told in more detail in the article about how we chose the SaaS onboarding niche. That decision—to narrow, to specialize, to say no—was the direct result of learning this lesson the hard way.

Mistake 3: We Built a Process That Broke

Around month four, we built a production process.

It had seven stages. Brief, script, storyboard, review, production, revisions, delivery. Each stage had its own document, its own approval gate, and its own timeline. On paper, it was a beautiful thing—the kind of process you'd find at a studio with ten times our size.

It broke within two months.

The problem was that the process was built for a studio that didn't exist yet. It assumed a client who could make decisions quickly. It assumed a reviewer who understood the script. It assumed a timeline that didn't slip. None of those assumptions held.

The seven stages became fourteen because every stage had a feedback loop that took twice as long as the stage itself. The approval gates became bottlenecks, because the client was busy and the approval sat in an inbox for a week. The timelines became fiction, because every project had a unique constraint that the process didn't account for.

We spent the second half of year one rebuilding the process around one principle: fewer decision points, faster loops. We cut seven stages to four. We locked the reviewer list at three people. We capped revisions at two rounds. We built the landing page in parallel with the production instead of after it.

The simplified process wasn't as impressive on paper. It was dramatically better in practice. Our projects got faster. Our clients got happier. And we stopped losing weeks to approval delays that we couldn't control.

The lesson wasn't "have a process." We had a process. The lesson was "have a process built for the studio you are, not the studio you wish you were." A process that assumes a perfect client is a process that fails the moment the client is human.

Mistake 4: We Hired for Growth Instead of for the Work

In month seven, we hired our first full-time employee.

We hired for growth. We wanted someone who could help us scale—who could manage more projects, handle more clients, take work off my plate. We wrote a job description for a producer. We hired someone with agency experience. We gave them a pipeline to manage.

It was the wrong hire. Not because they were bad at their job. They were good. They were bad at our job, which was different. Our studio didn't need a producer. Our studio needed a scriptwriter. The bottleneck wasn't project management. The bottleneck was the quality of the scripts, and I was the bottleneck because I was writing all of them.

We spent three months trying to make the hire work before admitting the mistake. The producer had nothing to produce because the scripts weren't ready. The scripts weren't ready because I was overwhelmed. The pipeline stalled. We paid three months of salary for a role we didn't need, and we delayed hiring the role we did need by a quarter.

The lesson wasn't "don't hire." The lesson was "hire for the bottleneck, not the org chart." The org chart says a growing studio needs a producer. The work says a studio with a script problem needs a writer. The org chart is a theory. The work is the truth.

We eventually hired a scriptwriter. She was the single best hire we made in the first two years. But we lost a quarter to the mistake before we got there.

Mistake 5: We Didn't Measure Anything

For the first ten months, we didn't measure the work.

We delivered videos. We got feedback. We moved on. We had no idea whether the videos actually worked. We didn't know if they reduced churn, lifted activation, or changed any behavior at all. We measured our success by whether the client liked the video, which is a different thing entirely.

The turning point was the SaaS project I've written about before—the onboarding video that cut time-to-value from 14 days to 4. The client sent us the numbers. And for the first time in the studio's history, we had proof that a video had done something measurable.

That proof changed everything about how we worked. We started asking clients for the metric before we started the project. We started building analytics into the delivery. We started treating the video as an intervention with a before and after, not a deliverable with a like or dislike.

The result wasn't just better client relationships. It was a better studio. When you can measure the work, you can get better at it. You can test hypotheses. You can throw away what doesn't work. You can build a body of knowledge instead of a portfolio of pretty things.

We now know, with numbers, that our onboarding videos cut time-to-value by an average of 62% and reduce first-month churn by roughly a third. We know that silent-first design outperforms audio-first design by a wide margin. We know that opening with the user's pain outperforms opening with the brand every single time. None of that knowledge existed in year one. All of it came from measuring.

What We'd Do Differently

If I could go back to the first day of LeoStudio, here's what I'd tell myself.

Price by the outcome, not the hours. From the very first project. Even if you don't know what the outcome is worth, guess high and adjust. Hourly pricing is a trap that gets worse the better you get.

Say no to the wrong client, even when you need the money. The wrong client costs more than the right client pays. The time you spend on work that isn't yours is time you don't spend on the work that is.

Build the process for the studio you are, not the studio you want. A simple process that holds up under pressure beats an elegant process that breaks. Fewer stages. Faster loops. Three reviewers, not seven.

Hire for the bottleneck, not the org chart. The org chart is a theory. The bottleneck is the work. Look at the work and hire for what it actually needs.

Measure everything from day one. Even when the client doesn't ask. Even when it's hard. Even when you're not sure what to measure yet. Measurement is how you get better. Without it, you're just making videos.

Narrow earlier. We waited two years to specialize. We should have done it in year one. The earlier you narrow, the more time you have to get deeply good at the thing that matters.

What We're Building Next

A year of mistakes doesn't just teach you what to avoid. It teaches you what to build.

Here's what's next for LeoStudio. We're going deeper into the SaaS onboarding space, not broader. We're building more of the measurement infrastructure into every project—the analytics setup, the cohort tracking, the dashboards that prove the video worked. We're expanding our work with complex B2B SaaS products, the ones with multiple roles and layered onboarding needs, because that's where the problem is hardest and the impact is largest.

And we're writing more. This article is part of that. The thinking behind the work is as valuable as the work itself, and for a long time, we kept it to ourselves. That was a mistake too. The lessons we learned the hard way are lessons other studios and founders can learn without paying the same price.

You can follow all of it on leostudiohq.com. The case studies are there. The thinking is there. And if you're a SaaS founder with an onboarding problem, the contact page is there too.

The Final Word

The first year of LeoStudio was not a success story. It was a survival story. We made almost every mistake a young studio can make, and we made them in the open, with real clients and real money on the line.

But we survived. And more importantly, we learned. Every mistake in this article is now a rule we follow. Every expensive lesson is now a process we've built. Every failure is now a story we tell new clients, because it's the reason we're better at this than we were a year ago.

If you're in your first year of building something, here's the honest truth. You will make mistakes. You will make the same mistakes I made, or different ones, and they will cost you money and time and sleep. The question isn't whether you'll make them. It's whether you'll learn from them. The studio that survives year one isn't the studio that avoided mistakes. It's the studio that turned every one into a rule.

That's what we did. That's what we're still doing. And if you want to see the results—the work that came out of all those expensive lessons—go to leostudiohq.com. Every project there is proof that the mistakes were worth it.