Brand Site in Framer — 10+ Pages, CMS, Built in a Week by Andrii BobrovskyiBrand Site in Framer — 10+ Pages, CMS, Built in a Week by Andrii Bobrovskyi
Brand Site in Framer — 10+ Pages, CMS, Built in a WeekAndrii Bobrovskyi
Cover image for Brand Site in Framer — 10+ Pages, CMS, Built in a Week
The full site an agency would quote six weeks for. Ten to twelve pages, multiple CMS collections, custom code where the canvas isn't enough — live on a real URL in seven days.
Who this is for
Companies whose site has to carry the whole brand, not just capture a lead. Studios, agencies, production houses, networks, multi-service businesses. If you have five services that each deserve their own page and a body of work that needs to stay current, this is the one.
Studios: send the Figma, I build it; your name stays on the work if you want.
What makes this different from a bigger version of a landing page
Structure comes first. Multiple CMS collections mean your team publishes without a designer — a new case study, a new event, a new team member is a form, not a ticket. My EPIC CLANS concept runs on seven collections for exactly this reason: servers, events, rules and rankings are all entries, so whoever runs the site updates it without opening the canvas.
Code where it's needed. Framer's canvas has limits. On my builds, header interactions inside a layout template didn't fire on the published site, and a form whose questions branch on earlier answers is cleaner as code than as a stack of variants. I write those as React components. That's the difference between a site that demos well and one that works after handover.
Real breakpoints, every page. 1200, 810 and 390 laid out deliberately. Ten pages at three widths is thirty layouts, and none of them get auto-scaled.
The process
Day 0 — you send Figma, a prototype, or whatever you have. Everything runs in writing, in Contra chat and Figma comments, so no calls are needed. My portfolio includes full sites built from a React prototype and from PNG mockups plus a business card.
Days 1–4 — structure and all pages. The repetitive setup (page scaffolds, CMS entry) is scripted through Framer's Server API; layouts are checked by hand. You watch it appear on a live URL as it goes; no hidden progress.
Days 5–6 — CMS collections built and populated, code components, responsive pass.
Day 7 — SEO, forms, handover walkthrough, project transferred to you.
Honest scope note
I don't design logos from scratch, do art direction, write your copy unless you add it, shoot photos or video, or build backends and CRM integrations. Those are separate line items and I'll say so before we start, not in week two.
FAQs

Starting at$3,800
Duration7 days
Tags
CMS
Framer
React
Web Designer
Web Developer
Service provided by
Andrii Bobrovskyi proHamburg, Germany
2
Followers
Brand Site in Framer — 10+ Pages, CMS, Built in a WeekAndrii Bobrovskyi
Starting at$3,800
Duration7 days
Tags
CMS
Framer
React
Web Designer
Web Developer
Cover image for Brand Site in Framer — 10+ Pages, CMS, Built in a Week
The full site an agency would quote six weeks for. Ten to twelve pages, multiple CMS collections, custom code where the canvas isn't enough — live on a real URL in seven days.
Who this is for
Companies whose site has to carry the whole brand, not just capture a lead. Studios, agencies, production houses, networks, multi-service businesses. If you have five services that each deserve their own page and a body of work that needs to stay current, this is the one.
Studios: send the Figma, I build it; your name stays on the work if you want.
What makes this different from a bigger version of a landing page
Structure comes first. Multiple CMS collections mean your team publishes without a designer — a new case study, a new event, a new team member is a form, not a ticket. My EPIC CLANS concept runs on seven collections for exactly this reason: servers, events, rules and rankings are all entries, so whoever runs the site updates it without opening the canvas.
Code where it's needed. Framer's canvas has limits. On my builds, header interactions inside a layout template didn't fire on the published site, and a form whose questions branch on earlier answers is cleaner as code than as a stack of variants. I write those as React components. That's the difference between a site that demos well and one that works after handover.
Real breakpoints, every page. 1200, 810 and 390 laid out deliberately. Ten pages at three widths is thirty layouts, and none of them get auto-scaled.
The process
Day 0 — you send Figma, a prototype, or whatever you have. Everything runs in writing, in Contra chat and Figma comments, so no calls are needed. My portfolio includes full sites built from a React prototype and from PNG mockups plus a business card.
Days 1–4 — structure and all pages. The repetitive setup (page scaffolds, CMS entry) is scripted through Framer's Server API; layouts are checked by hand. You watch it appear on a live URL as it goes; no hidden progress.
Days 5–6 — CMS collections built and populated, code components, responsive pass.
Day 7 — SEO, forms, handover walkthrough, project transferred to you.
Honest scope note
I don't design logos from scratch, do art direction, write your copy unless you add it, shoot photos or video, or build backends and CRM integrations. Those are separate line items and I'll say so before we start, not in week two.
FAQs

$3,800