The RMBC method: how Research, Mechanism, Brief and Copy structure a VSL project
RMBC is the copywriting process taught by direct-response copywriter Stefan Georgi: Research, Mechanism, Brief, Copy. This guide explains the idea at a high level, why separating thinking from writing produces better VSLs, and gives you an original research doc and brief template to run the process yourself.
On this page
- What is the RMBC method, and who created it?
- Why separate research and briefing from writing?
- R: what to research for a VSL
- M: finding the mechanism
- B: writing the VSL brief
- C: writing the VSL from the brief
- A condensed RMBC run on a fictional VSL
- Common mistakes when using RMBC
- How to apply this to your VSL tomorrow
- Frequently asked questions
The RMBC method is a four-step copywriting process taught by Stefan Georgi: Research the market, find the Mechanism, write a Brief, then write the Copy. The idea behind it is to do the thinking before the writing. Research, the mechanism and a written brief each get their own step, so by the time you write the VSL, every major decision has already been made.
What is the RMBC method, and who created it?
Stefan Georgi is a direct-response copywriter and marketer who created the RMBC Method, which he describes as a systematic approach to writing better sales copy, more consistently, in less time (Stefan Georgi). On his site, RMBC is spelled out as Research, Mechanism, Brief and Copy (The RMBC Method). He teaches it as a paid course, and the newer version, RMBC II, builds much of the process around AI tools and covers assets from VSLs to advertorials, landing pages, upsells and emails (RMBC II).
At a high level, the four steps as he presents them:
What RMBC stands for
The four steps at a high level, as Georgi presents them
- ResearchLearn who the customer is, what problems they face, what they want, and what they like and dislike about the options they've tried.
- MechanismExplain why the prospect's past attempts failed and why this offer works where they didn't.
- BriefOrganize the research and the mechanism into answers you can reuse when you write.
- CopyWrite the sales message from a structured outline, once the earlier steps are done.
Everything below is our own interpretation, with our own templates, written for VSL projects. For the full method, go to the source.
Why separate research and briefing from writing?
Writing a VSL is two jobs: deciding what to say and saying it well. Doing both at once is slow, because every paragraph reopens questions you haven't settled. Who exactly is this for? Why does the problem persist? What proof do we have? Which objection comes first? The draft turns into research written in full sentences.
Separating the jobs fixes three things:
- Reviews get faster. A two-page brief can be approved, challenged or redirected in one meeting. A 3,000-word script is hard to review until it's finished, and by then changes are expensive.
- Rewrites get cheaper. Changing the mechanism in a brief takes an hour. Changing it after the VSL is filmed can mean a re-shoot.
- AI help gets safer. A model given your research and brief can draft variations of leads, transitions and bullets. A model asked to "write a VSL for my product" tends to fill the gaps with invented claims.
The cost math, with invented numbers: say a finished 20-minute VSL takes two days of filming and three days of editing. If a reviewer rejects the mechanism after the edit, you lose a week. If the same objection comes up at the brief stage, you lose an afternoon. Over a year of testing, that difference decides how many ideas you can put in front of traffic.
The same objection, raised early or late
Invented numbers from the example above: two days of filming and three days of editing
R: what to research for a VSL
Research has one goal: to understand the viewer's situation better than they could describe it themselves, in their own words. A practical research doc has these sections (our template, not Georgi's):
| Section | What goes in it | Where to find it |
|---|---|---|
| The viewer | Who they are, their situation, what a bad day with the problem looks like | Interviews, support tickets, sales calls |
| Their words | Exact phrases for the problem and the outcome they want | Reviews of competing products, forums, comments |
| Failed attempts | What they've tried and why each one disappointed | Reviews, forums, refund reasons |
| Objections | Why they might not buy, in their words | Sales calls, pre-sale questions, ad comments |
| Awareness and sophistication | How much they know, how many similar claims they've heard | Ad libraries, competitor VSLs, search queries |
| The product's truth | How it actually works, what it can't do, the evidence you hold | Product team, documentation, studies you can cite |
| Competitor claims | Promises and mechanisms already in the market | Ad libraries, competitor pages |
Two rules make the doc useful. Quote real customers word for word, because those phrases often become your best lines. And keep a source next to every fact, so the copy step never has to guess what's provable. For the awareness row, see the five levels of awareness; for the sophistication row, see market sophistication.
M: finding the mechanism
The mechanism is the explanation that makes the offer believable: why the problem exists or persists (the problem mechanism) and why this solution works where others failed (the solution mechanism). In crowded markets, where every competitor makes the same promise, a credible mechanism is often what earns a skeptical viewer's attention. For how to find and name one, see unique mechanism.
The test of a mechanism has three questions. Is it true? Can you show it? Does it explain the viewer's failed attempts? If any answer is no, keep researching. A mechanism invented to sound scientific is a liability, because it's a claim like any other: the FTC's guidance says advertisers need proof for their claims before the ad runs (FTC Advertising FAQs). This isn't legal advice.
A short fictional example, for SoilCycle, a countertop food-waste appliance:
SoilCycle's mechanism (fictional)
Problem mechanism
Composting in an apartment fails because a closed indoor bin stays too wet and gets too little air, so it smells long before anything breaks down.
Solution mechanism
SoilCycle heats, dries and grinds scraps overnight, so nothing wet is left to smell, and a carbon filter handles the rest.
That last line is where the mechanism step earns its keep. It forces the true claim onto paper before anyone gets creative.
B: writing the VSL brief
The brief is where research and mechanism turn into decisions. It should be short enough to read in ten minutes and specific enough that two different writers would produce recognizably similar VSLs from it. Here's a brief template you can copy (our own):
A VSL brief template
Tick each section as you fill it in; the ticks stay in this browser
0 of 11 done
Get the brief approved before anyone writes a line of script. Disagreements are cheap at this stage and expensive later.
C: writing the VSL from the brief
With a solid brief, the copy step is mostly assembly and craft. Turn the brief into a beat sheet (lead, problem, story, mechanism, proof, offer, guarantee, close), then write each beat for the ear. The VSL script guide covers the beat sheet and runtime math in detail.
Habits that make the copy step go well:
- Write the body first and the lead last. You can only write a lead that lands cleanly once you know exactly what it lands in.
- Pull lines from the research doc. Customer phrases are often the strongest lines in the script.
- Draft fast, then table-read. Read the script aloud to someone who fits the viewer profile, and mark every place they frown, ask a question or drift.
- Check every claim against the brief. If a line makes a claim the brief doesn't support, cut it or go back to research.
- Use AI inside the brief, not instead of it. Ask for ten versions of a transition or five leads built on the brief's mechanism, and never let it add facts. See writing a VSL with AI.
A condensed RMBC run on a fictional VSL
Here's what the four steps look like end to end for SoilCycle.
Research (sample findings, invented for the example): reviewers of indoor compost bins complain about smell and fruit flies; people who quit composting say they gave up in winter or after the first bad smell; apartment renters say they have no outdoor space.
Mechanism: closed indoor bins stay wet and airless, so they smell; heating, drying and grinding overnight leaves nothing wet, and a carbon filter handles odors. Honest limit: the output is dried food waste, not compost.
Brief (excerpt): Big idea: you can keep food scraps out of the trash without living with a smelly bin. Viewer: apartment renters who tried a bin and quit. Promise: no smell on the counter, scraps reduced overnight. Lead options: a problem-solution lead about the bin that made the kitchen smell, and a story lead about a renter whose neighbor complained.
Copy (first lines of the problem-solution lead): "If you've ever kept a compost bin in an apartment, you know the moment it starts to smell. You didn't do it wrong. A closed bin indoors is simply too wet and too airless. Here's what happens when you take the water out of the equation."
Notice what each step contributed. Research supplied the smell and the winter quitters. The mechanism supplied the "why" and the honest limit. The brief locked the promise to what the product does. The copy step only had to make it sound like a person talking.
Common mistakes when using RMBC
Here they are, grouped by the step where each one happens:
Where RMBC goes wrong, step by step
1Research
What happens: Research collects the market's words, problems, failed solutions and objections.
What goes wrong:
- Skipping research because you "know the market". Your memory of the market is a hypothesis. The research doc is evidence.
Read more: The 5 Levels of Awareness: Schwartz's Map for VSLs
2Mechanism
What happens: The mechanism explains why past attempts failed and why this offer works.
What goes wrong:
- Inventing a mechanism. A mechanism you can't prove is a claim you can't make.
Read more: Unique Mechanism: What It Is and How to Find Yours
3Brief
What happens: The brief turns research and mechanism into decisions, so the copy step is execution, not discovery.
What goes wrong:
- Treating the brief as paperwork. A vague brief produces a script that is vague in exactly the same places.
- Writing before the brief is approved. The most expensive feedback is the feedback that arrives after filming.
- Ignoring the traffic. The same product needs a different lead for cold viewers and for retargeted buyers.
Read more: Big Idea Copywriting: Find the One Idea That Sells
4Copy
What happens: With a solid brief, the copy step is mostly assembly and craft.
What goes wrong:
- Dumping research into the script. Research is for deciding. Viewers need the conclusions, not your notes.
How to apply this to your VSL tomorrow
- Open a blank research doc with the seven sections above and fill in what you already know, marking each item with a source or the word "assumption".
- Collect 30 real customer phrases about the problem from reviews, forums or support tickets.
- Write your problem mechanism and solution mechanism in two sentences each, and list the evidence for each.
- Fill in the brief template, including compliance notes and two lead options.
- Get the brief approved by whoever signs off on the VSL before anyone writes a line of script.
- Turn the brief into a beat sheet, write the body first, and write the lead last.
- After launch, treat the sections where viewers leave as new research for the next brief. In RevvyScales, the second-by-second retention chart marks the pitch, so you can see which beat lost viewers (reading your analytics).
Frequently asked questions
What does RMBC stand for?
RMBC stands for Research, Mechanism, Brief and Copy, the four steps of the copywriting process taught by Stefan Georgi. You research the market and the customer, work out the mechanism that explains why past solutions failed and why this one works, organize everything into a brief, and only then write the sales copy.
Who created the RMBC method?
Stefan Georgi, a direct-response copywriter and marketer, created the RMBC Method and teaches it as a paid course. He describes it as a systematic approach to writing better sales copy, more consistently, in less time. The newer version, RMBC II, builds much of the process around AI tools. This guide only describes the public idea at a high level.
Is the RMBC method only for video sales letters?
No. RMBC is a process for sales copy in general, and Georgi's newer course applies it to VSLs, advertorials, landing pages, upsells and email sequences. It suits VSLs especially well, because a long video is expensive to change after filming, so settling the research, mechanism and brief first saves the most rework.
How long should the research step take?
There is no fixed number of hours. Research is done when you can fill every section of your brief with sourced answers and real customer phrases, and when you can explain the viewer's failed attempts in their own words. If you're guessing at any brief section, that's the section to research further before you write.
Can I use AI with the RMBC method?
Yes, and Georgi's own newer course leans on AI tools. AI is useful for summarizing large amounts of research, suggesting mechanism angles to investigate and drafting variations of leads or transitions from a finished brief. Humans still need to verify every fact, own the claims and check compliance, because a model will fill gaps with plausible inventions.
What is the difference between a mechanism and a big idea?
The mechanism is the explanation: why the problem persists and why this solution works. The big idea is the frame for the whole message, the single concept that makes the VSL interesting and memorable. A strong VSL usually has both. The big idea earns attention, and the mechanism makes the promise believable.
