creatify.ai: one site, one designer





Design
- Page design and layout
- Visual system and gradients
- Covers and illustrations
Build
- Framer, end to end
- CMS templates
- Eight languages
Growth
- Conversion copy
- A/B testing
- SEO page families
The job
There's no single project. The site is the project.
Every launch, pricing change, new feature and campaign ends up as a page, and every page goes through me, from the first layout to the moment it's live.
That's around 640 pages in English, mirrored into Spanish, Portuguese, French, German, Japanese, Indonesian and Chinese. More than 5,000 live URLs in total, for a site that gets 500k+ visitors a month.
A system, not a pile of pages
One look across hundreds of pages.
The only way one person keeps this many pages consistent is with a system. Every page shares the same pieces: the floating nav, a big gradient hero, the black button with the pixel arrow, the "AI generated" tags on every example ad.
What changes is color. The core platform lives in deep blue and violet, Studio in warm orange, use cases in sunset gradients. Each product feels like its own place while still clearly being Creatify.
Templates that scale
One template, many pages.
Most of the site is built from page families: one template, many pages. A comparison page against HeyGen and one against Fliki share the same layout and the same cover style; only the content changes. Reviews, use cases, features and tools work the same way.
That's what keeps new pages quick to ship, and it's a big part of how the site gets found in search.
Pages that sell
Design and copy, working together.
The site's job is to turn visitors into users, so design and copy can't be separated. I write and rewrite a lot of the copy myself and run A/B tests to see what actually moves people.
Pricing is a good example: three products (Platform, Studio and the API) sharing one page without getting confusing.
Explaining a service
Some pages need more than screenshots.
Some pages need more than screenshots. Studio is a done-for-you service, so its page tells a short story in three illustrations: set a budget, build the pilot together, approve it and launch.
Running it
It never ships once. It keeps shipping.
The work never really ships; it keeps shipping. Model launches like Aurora, campaigns, new features every few weeks, all landing on a site that has to stay fast, consistent and available in eight languages.
Owning the Framer setup end to end means there's no handoff between design and build: what I design is what goes live.








