GUIDE · PLATFORM
Why we build where we build
We default to Framer for startup marketing sites because it collapses design and build into one act and lets non-developers publish. We use Webflow for relational content, keep WordPress when it is already working well, and go custom only when the site needs application behaviour rather than more pages.
THE DEFAULT
Framer, for most startup marketing sites.
Not because it is fashionable, and not because it is the most capable tool in the comparison — it is not. Because of one specific property: designing and building are the same act in it. There is no file that gets handed to someone who rebuilds it, which removes the phase where a design quietly becomes 80% of itself, and it is most of the reason a site can go live seven days after we start.
The second reason matters more six months later. Your marketing person can publish a page in it without learning a layout model and without breaking mobile. A site nobody on your team can safely edit is a site that stops being current, and the cost of that shows up slowly enough that nobody blames the platform.
THE THREE QUESTIONS
We ask these in order, and stop at the first one that decides it.
Who edits this after launch? If the answer is a marketer or a founder, that narrows it immediately. If the answer is a developer who already owns your stack, the calculation changes and staying where they are is usually right.
Does the content have structure? A blog with authors, categories and related posts, or case studies that reference services that reference industries, is relational content, and Webflow handles it better than Framer does. A site with twenty flat pages is not relational content no matter how it is organised in the sitemap.
Does the site need to do something? Log people in, calculate a result, read from your database, generate pages from a dataset. That is application behaviour, and it belongs in your codebase rather than in a builder — usually alongside a builder rather than replacing it.
WHAT WE WILL NOT DO
Sell you a migration you do not need. If your WordPress site is maintained, fast and publishing fine, moving it costs a week, risks your URLs and buys you a preference.
Pretend the platform is the reason the site works. It is not. The argument the page makes is the reason, and a good argument converts on any of these while a bad one converts on none of them.
Or leave you renting your own website. You own the project, the domain and the account at the end, on every platform we work in. If the handoff leaves you unable to change your own headline without calling us, we built the wrong thing.
QUESTIONS
Do you only build in Framer?
No. Framer is the default because it fits most startup marketing sites, but we build in Webflow when the content is structured or you already run it, and we work alongside your engineers on a custom stack when the site genuinely needs one.
What if we already have a platform we like?
Then we usually stay on it. Migrating a working site costs a week and risks the URLs, and neither of those is worth a preference. We will say plainly when a move is worth it and when it is not.
Who owns the project after launch?
You do — the project file, the domain and the account. The point of building somewhere your own team can edit is that you are not dependent on us afterwards, and that only holds if you own it outright.