07 - Studio
Studio
In short: Studio is where your reusable templates live, for both landing pages and emails. Build one, and every page made from it inherits the same structure and rules.
Most of the docs so far have been about building one page. Studio is about building the mold those pages come from. Dial in a template once, and you stop making the same choices over and over.
We will keep using Aerix Sport as the example.
Studio is not the page editor
In short: The page editor changes one page. Studio changes the template that many pages are built from.
These two are easy to mix up, so here is the difference:
What it changes | When you use it | |
|---|---|---|
Page editor | One single page | Tweaking a page you already generated |
Studio | A reusable template | Setting the structure and rules for many future pages |
A change in the page editor affects that page only. A change in Studio affects every new page built from that template.
Build a template from a description
In short: Describe the layout you want in plain language. The AI builds the template for you.
You do not lay out a template by hand. You pick a landing-page type, then describe the structure you want in words. Flunnel builds a template that matches.
Example: "An advertorial for Aerix Sport that opens with a player's frustration, then a coach's explanation, then the racket, then proof, then the offer."
Refine it by talking to it
In short: Adjust the template in plain language, and Flunnel updates the structure.
Once a template exists, you change it the same way you built it: conversationally. Tell it what you want different and it rebuilds.
Examples:
"Add an FAQ section near the end."
"Lead with the expert credential."
"Move the proof above the offer."
Quick tip: Refine the template once, properly, instead of fixing the same thing on every page. That is the whole point of Studio.
What a template carries
In short: A template holds its own structure, its own writing rules, and your brand tokens.
Each template stores three things, so the pages it produces stay consistent:
It carries | Meaning |
|---|---|
Its own structure | The layout and section order |
Its own writing instruction | How the copy in it should be written |
Brand tokens | Reusable values like product name, proof bank, and claim guardrails |
Because the tokens and rules live in the template, every page built from it inherits them. Set your Aerix proof bank and claim guardrails once in the template, and every Aerix page made from it follows the same rules automatically.
Templates for pages and emails
In short: Studio holds both landing-page templates and email templates.
Reusable templates are not just for pages. Your email templates live in Studio too, so your follow-up flows stay as consistent as your pages.
Logos and color schemes
In short: Flunnel can generate logos and color schemes from your brand colors automatically.
You do not have to build every visual asset yourself. From your brand colors, Flunnel can generate logos and color schemes for your templates to use.
When to use Studio
Reach for Studio when you find yourself repeating work:
You keep making the same structural change to every page.
You want every page in a brand to follow the same proof and compliance rules.
You are setting up a brand for the first time and want a house style before you scale.
Build the template once, then generate page after page from it, each one on brand and on the rules without extra effort.
Back to Editing Your Page · Continue to Email Flows
Share:
