For small teams and agencies
Win clients and deliver the work — from one studio site.
Use LayoutPages for service positioning, selected work, forms, private client pages, multilingual admin access, API keys, and webhooks without stitching tools together.
Launch checklist
What your first session should produce
Client pages included
Multilingual admin
API keys and webhooks
Practical workflow
Built around the few moves that get a real site live.
Frame the offer
Use the starter sections to clarify services, proof, and the kinds of clients the studio serves.
Add delivery surfaces
Create private client pages, multilingual admin paths, form workflows, API keys, and webhooks for real operations.
Watch upgrade pressure
Studio gives the capacity and workflow headroom that active client pipelines need.
Recommended starter
Start with the studio template and the developer setup path.
This keeps signup, onboarding, and lifecycle follow-up aligned with the same segment data now reported in the growth dashboard.
Template guidance
What to customize before you send the link.
The template examples are mock sites, so this page focuses on the practical launch work: what to replace, what to keep, and when the paid plan starts to matter.
Can a studio start without a team plan?
Yes. Start with the public offer and selected work, then move to Studio when client pages, teammates, multilingual access, API keys, or webhooks become part of delivery.
What should the first studio template include?
Lead with services, one proof-heavy case study, a contact path, and the first private client page if delivery review is part of the workflow.
Recommended plan path
Start free, then upgrade when the site starts doing work.
For studio sites, the first paid step is usually studio: Studio is the practical plan when client pages, integrations, and teammate access become part of delivery.
Best for first publish
Free
Start from a template example, launch on a hosted subdomain, and replace starter content before you pay.
When this plan makes sense
Use Free until the site has your real homepage, at least one real content item, and a shareable contact path.
No credit card required.
Upgrade happens inside your admin whenever you need it.
Best for public launch
Core
Make the site fully yours when you are ready to send prospects to it.
When this plan makes sense
Upgrade to Core when the site is ready for your own domain, clean branding, and regular publishing.
$90/year total, save $18. Most serious solo sites should land here.
Upgrade happens inside your admin whenever you need it.
Best for client delivery
Studio
Add collaboration, private client workflows, and automation once the site is part of operations.
When this plan makes sense
Upgrade to Studio when client pages, teammates, forms, API keys, or webhooks become part of delivery.
$290/year total, save $58. For client work, teams, and automation-heavy setups.
Upgrade happens inside your admin whenever you need it.
Best for shops running multiple sites
Agency
Run client sites at scale: white-label admin, bulk seats, fair-use headroom, and reseller-friendly terms.
When this plan makes sense
Choose Agency when you are operating a roster of client sites and need bulk seats, white-label, and contract flexibility.
$1990/year total, save $398. Custom contracts and white-label terms available.
We'll reply within one business day.
Related paths
More pages for this use case.
Template
Studio Services Website Template
Launch a studio services site with client pages, forms, case proof, API keys, webhooks, and CMS editing.
Guide
Moving from a website builder to a CMS-backed site
Migration does not need to be a risky cutover. Start by extracting public signals and rebuilding a better first draft.
Guide
What a lightweight client portal should include
Client portals work when they stay focused: one private page, clear deliverables, and an obvious next action.
Comparison
Compare LayoutPages with other tools
See when LayoutPages fits better than a general website builder or plugin-heavy CMS.
Next step
Start a studio site from the closest template.
For a studio workspace, prioritize services, one proof-heavy case study, client pages, multilingual admin access, and automation checks.