CMS architecture
Component libraries
Figma to Webflow
Editor handover
CMS architecture
Component libraries
Figma to Webflow
Editor handover
SaaS websites
SaaS sites your team can edit
Changing a headline should not be a ticket. We build SaaS marketing sites as a system — tokens, components, collections — so your team ships landing pages and blog posts on their own, and the number of things only a developer can do gets small enough to list.
The usual state of things
One headline, three weeks
Almost every SaaS site we are asked to look at has the same three problems, and they are all the same problem: the site was built as pages instead of as a system.
One long custom page
Nothing on it is reusable. Nobody will touch it, because the last person who tried broke the spacing on mobile and it took two days to find.
An orphaned blog
It is on a different platform, or a template nobody has opened since launch. Your best content is the worst-looking page you own.
Nine different navs
Every campaign landing page was duplicated from the last one. Change a nav link and you change it nine times, and you will miss two.
What we build instead
Three layers, in
that order
The order matters more than any individual decision in it. Build the pages first and you get a site nobody can maintain; build the system first and the pages take care of themselves.
01
Tokens
Colour, type scale and spacing live as Webflow variables rather than as values typed into each element. Change one and every page follows. This is the layer that turns a rebrand into an afternoon.
Brand colour
Type scale
Spacing
Radii
02
Components
The page shapes your marketing site actually repeats, built once and reused everywhere. Edit the component and every instance updates — which is the difference between a site that can be maintained and one that gets quietly abandoned.
Hero
Feature row
Logo wall
Pricing table
FAQ
CTA band
Nav
Footer
03
Collections
Everything that will be published more than once becomes structured content rather than a pasted page. Your team fills fields; the template does the design. Nobody chooses a font size to publish a blog post.
Blog
Case studies
Integrations
Changelog
Jobs
Authors
The honest version
What your team
can do
Every agency says “fully editable”. Almost nobody publishes the other column. Here is both, and the right-hand one is the list we are trying to keep short.
Your team, on their own
No developer, no ticket, no us
✓Publish a blog post, a case study, a changelog entry or a job opening
✓Add a customer logo, an integration or a pricing tier
✓Swap any headline, image or button on any page
✓Assemble a new campaign landing page from existing components
✓Change a nav or footer link once and have it change everywhere
✓Roll a page back to an earlier version without asking anyone
Still needs a developer
Us, or whoever you have in house
XA section type that does not exist in the component library yet
XAnything that changes CMS structure — a new collection, a new field
XIntegrations that need code: a product tour embed, a pricing calculator
XDesign system changes — a new type scale, a new spacing rhythm
The right-hand column is the honest measure of the build. If six months after launch your team is still sending us tickets to change copy, the architecture was wrong and we would rather hear about it than keep invoicing for it.
Two builds, both live
Two SaaS sites,
both live
Both shipped in 2026, both still live, both open in a new tab from here. No traffic graphs and no percentage uplifts — we do not have access to their analytics and would not publish it if we did.
Amplify
2026
AI-powered content creation and creator discovery platform, designed to help brands create content and connect with creators through intelligent signals.
amplify.clubSemactic
2026
SEO and GEO platform helping brands and agencies improve AI Search visibility, turn search insights into actionable priorities, and measure the impact of their optimizations.
semactic.comHow it runs
The four steps
No week numbers here, because the honest answer depends on how many page types you have. You get a date with the quote, and the date is a commitment rather than an estimate.
01
We agree the component list before anything is designed
An hour on a call with whatever you have — the current site, the Figma file, or a list of pages on a whiteboard. The output is the component library, written down. Every argument about scope happens here, where it is cheap.
02
The system gets built before the pages do
Tokens, then components, then collection structure. It looks like slow progress and it is not — once the system exists, pages assemble in hours instead of days.
03
Pages get assembled, on a staging URL you can open any time
No weekly reveal. There is a link, it is current, and you are welcome to look at it at two in the morning and send notes.
04
Handover is a thing that actually happens
Editor accounts for your team, a recorded walkthrough of the component library, and the collection structure documented in writing. Not a Slack message saying it is live.
Questions
Fair questions
01
Can you just build our Figma file?
02
Can we keep the blog on WordPress?
03
What about our product docs?
04
And a rebrand?
05
What are the limits?
06
Do you do the ongoing work?
FIGMA IN, SCOPE OUT
Send us the Figma file
Or the site you have now, or a list of the pages you wish you had. You get a scope, a price and a date back the Within 1 business day.