You Deployed a Service With No Revenue Endpoint: Future of Filmmaking by Renzo Merbis
You Are Running a Service That Scales to Zero
You have built a technically sound video production service. You can capture clean footage, deliver polished edits, and handle client requests across formats and platforms. Your work is solid. Your clients are satisfied. Your reel demonstrates competence that took years to develop.
And yet your revenue has a hard ceiling. Every project resets to zero. You quote a flat rate, deliver the work, invoice, and start looking for the next project. Your income is a series of disconnected transactions — no compounding, no residual value, no recurring revenue from past work. You are running a stateless service: every request is independent, nothing persists between calls, and the only way to increase throughput is to increase hours.
If you built software this way — a service with no state management, no event-driven architecture, no mechanism for a single deployment to generate value over time — you would call it a scaling problem. You would not solve it by writing faster code. You would solve it by rearchitecting the system.
That is the premise of Future of Filmmaking by Renzo Merbis ($365, 40 lessons, 14.2 hours). It is not a production course. It is a business architecture course for videographers who are technically capable but commercially stateless. The full independent breakdown is available on Course To Action.
The Problem Is Not Your Output Quality. The Problem Is Your Service Contract.
Here is the reframe most freelance videographers miss, and it maps directly to a pattern every developer has seen:
You think the problem is that you need more clients, better marketing, a stronger reel, or higher production value. You think the constraint is on the supply side — if you just shipped better work, the revenue would follow.
But the constraint is on the integration side. Your service has no contract that ties your output to the client's revenue. You deliver a video. The client uses it. If it generates $200,000 in sales over the next year, you earned the same flat $3,000 fee as if it generated nothing. Your compensation is decoupled from impact. There is no callback, no webhook, no event listener connecting your work to the value it creates downstream.
In software terms: you deployed a microservice with no revenue endpoint. The service processes requests, returns a response, and has zero visibility into what happens after the response is consumed. You are operating without observability into your own business impact.
Merbis's argument is that the fix is not to produce better video. The fix is to rewrite the service contract so that your compensation is structurally coupled to client outcomes. And the deployment pipeline for that contract rewrite is what the course teaches.
The Six-Step Video Strategy: A Deployment Pipeline for Revenue-Coupled Content
The framework I want to go deep on is the Six-Step Video Strategy — Merbis's content planning system that transforms video production from an isolated deliverable into a revenue-integrated deployment pipeline. Here is how each step works, mapped to concepts systems thinkers already understand.
Step 1: Audience Definition (Service Discovery)
Before you write a line of code — or in this case, before you storyboard a single frame — you define exactly which service consumer you are building for. Not "small business owners." Not "people who need video." A specific segment with specific behaviors, specific platforms, and specific revenue patterns.
This is service discovery. You are identifying which downstream systems will consume your output, what protocols they speak, and what data formats they accept. A video built for e-commerce conversion on Instagram has a completely different contract than a video built for B2B lead generation on LinkedIn. The audience definition determines the interface specification for everything that follows.
Step 2: Emotional Target Identification (Request Schema)
Once you know who the consumer is, you define what state change the content needs to produce. Merbis uses his Five Core Emotions framework here — Fear, Curiosity, Frustration, Empathy, Excitement — as the enumerated type for the emotional state the video should trigger in the viewer.
Think of this as the request schema. You are not just defining what the video contains. You are defining what transformation it performs on the viewer's state. A video that targets Curiosity has a different structure, pacing, and hook pattern than a video that targets Frustration. The emotional target is the expected input-to-output mapping.
Step 3: Platform Selection (Infrastructure Choice)
Where will this content run? YouTube, Instagram, TikTok, LinkedIn, a client's website, paid ad networks — each platform has different runtime constraints. Aspect ratios, duration limits, autoplay behavior, algorithm preferences, audience attention patterns. These are infrastructure constraints, and they shape the implementation.
Platform selection is not a creative decision. It is an infrastructure decision driven by where your target audience segment actually consumes content and what the platform's distribution algorithm rewards. Choosing the wrong platform is like deploying a latency-sensitive service on infrastructure optimized for throughput. The implementation might be flawless, but it will underperform because the environment does not match the workload.
Step 4: Content Format Choice (Implementation Pattern)
With the audience, emotional target, and platform locked, you select the format: talking head, documentary-style, testimonial, product demo, behind-the-scenes, narrative ad. This is the implementation pattern — the architectural approach that best satisfies the contract defined by the first three steps.
The key insight here is that format follows contract, not the other way around. Most videographers start with a format ("I will make a cinematic brand film") and then try to retrofit an audience, emotion, and platform onto it. That is implementation-first design. Merbis teaches contract-first design: the format is selected because it is the best implementation of the contract the first three steps defined.
Step 5: Distribution Planning (Deployment Strategy)
A single video asset can be deployed across multiple environments — primary platform, repurposed clips for secondary platforms, email embeds, website landing pages, paid amplification. Distribution planning is the deployment strategy: how many environments will this content run in, what adaptation is needed for each, and what is the rollout sequence?
This step is where the economics of the commission model start to make sense. If you are paid per project, distribution planning is extra work for no additional revenue. If you are paid on commission tied to the revenue the content generates, broader distribution directly increases your compensation. The deployment strategy and the pricing model reinforce each other.
Step 6: Measurement Criteria Definition (Observability)
This is the step that makes the entire pipeline revenue-coupled rather than delivery-coupled. Before production begins, you define what metrics will determine whether the video succeeded. Views, click-through rate, conversion rate, revenue attributed to the content, cost per acquisition — the measurement criteria are agreed upon with the client before a single frame is shot.
This is observability. You are instrumenting your deployment before you deploy. Without this step, you have no data layer connecting your output to business outcomes. With it, you have the feedback loop that makes the commission model viable and that makes every subsequent project more informed than the last.
This is one of 7 frameworks in Future of Filmmaking. The complete breakdown — every framework, every limitation — is available on Course To Action. Start free.
Where This Gets You — and Where It Stops
The Six-Step Video Strategy gives you the deployment pipeline. You can walk into a client meeting, run through these six steps, and produce a content plan that is structurally tied to measurable business outcomes. That alone separates you from the majority of videographers who pitch creative concepts without any revenue integration.
But the pipeline is not the complete system. The Six-Step Strategy tells you how to plan content that generates measurable value. It does not tell you how to price yourself into that value, how to run the initial client conversation that positions you as a revenue partner instead of a vendor, or how to psychologically frame the proposal so the client's decision process has minimal friction. Those are different subsystems, and without them the pipeline runs but the business architecture is incomplete.
The missing piece is this: a deployment pipeline without a service contract and a client integration protocol is just a better way to deliver commodity work. The pipeline needs to be coupled with a pricing model and a sales process that reflect the value it creates.
What System Are You Actually Running?
Before you evaluate whether this course is right for your situation, here is the question worth sitting with:
If you mapped your current video production business as a system diagram — inputs, processing, outputs, feedback loops, revenue flows — where does the architecture break down? Is it the quality of your processing? Or is it that you have no feedback loop between the value your output creates and the revenue you capture?
Most videographers who feel stuck are not stuck because of capability. They are stuck because of architecture.
The Rest of the System (By Name)
The Six-Step Video Strategy is one component. The complete system Merbis teaches across 40 lessons includes six other named frameworks:
- Blue Ocean Four Action Framework — the market repositioning strategy that moves you out of commodity competition entirely
- Upfront Fee + Commission Model — the pricing architecture that couples your revenue to client outcomes (Merbis claims 8.25x income versus retainer pricing)
- Five Core Emotions — the content psychology filter that determines what emotional state each piece of content targets
- NESP Rule — the four-parameter pre-production filter for evaluating content ideas before you invest production time
- Cognitive Ease — the proposal and conversation framework that reduces client decision friction without reducing the ask
- Seven-Step First Meeting — the structured discovery protocol for initial client calls that positions you as a business partner, not a vendor
Each framework addresses a different subsystem. Together they form a complete business architecture. The Six-Step Video Strategy is the deployment pipeline. The rest is everything else the system needs to run.
Start Free. Then Decide.
The full independent breakdown of all seven frameworks — every step, every limitation, every gap — is available free on Course To Action. No paywall on the breakdown itself.
If the frameworks fit your situation and you want the full 40-lesson implementation: the course is $365. On Course To Action, you can access it for $49 alongside 110+ other course breakdowns — no subscription, one-time purchase. Every breakdown includes an AI study tool and audio format.
The price comparison that matters is not $365 versus other courses. It is $365 versus the annual revenue you leave on the table by running a stateless service with no revenue endpoint.
Read the full breakdown on Course To Action — start free.
Discuss: If you freelance in any capacity — video, software, design, consulting — have you ever restructured your pricing from flat-fee to outcome-based? What broke, and what worked?
Top comments (1)
Great interesting read 👌 I’d never thought I’d see ‘deploy a microservice’ and ‘freelance videographer’ in the same sentence 🙃