A Webflow project at Digitalmakers runs in six steps: brief and strategy, design in Figma, build in Webflow, content and SEO, testing, and launch with handover. A typical B2B site takes [__] weeks. The biggest factor in that timeline is usually how quickly content and feedback come in.
- Six steps: brief, Figma design, Webflow build, content and SEO, testing, launch.
- A design system in Figma becomes a component library in Webflow.
- Your team learns to edit text, add CMS items and build pages.
- Late content, crowded feedback rounds and reopened decisions slow projects down most.
At a glance
- 1. Brief and strategy: goals, audience, sitemap, content plan. Takes about [__] week(s). What we need from you: a kick-off with the decision makers.
- 2. Design in Figma: key pages, then the design system. Takes about [__] weeks. What we need from you: two feedback rounds.
- 3. Build in Webflow: components, CMS, interactions. Takes about [__] weeks. What we need from you: content for the CMS.
- 4. Content and SEO: copy in place, metadata, redirects. Takes about [__] week(s). What we need from you: final copy and approvals.
- 5. Testing: speed, accessibility, devices, forms. Takes about [__] days. What we need from you: a test round on your side.
- 6. Launch and handover: go live, training, first checks. Takes about [__] days. What we need from you: domain access.
1. Brief and strategy
We start with what the site needs to do, not with what it should look like. Who visits, what do they need to believe, and what should they do next? The result is a sitemap, a content plan and agreement on how we'll measure success.
2. Design in Figma
Robin designs the key pages first, usually the homepage, a service page and a case. Once those are approved, the rest follows from a design system: colours, type, spacing and components such as cards, quotes and forms. That system is what makes the site easy to extend later.
3. Build in Webflow
The design system becomes a component library in Webflow. Pages are built from those components, so your team can later make new pages without breaking anything. CMS collections get set up for content that repeats, such as cases, articles or vacancies. Motion and interactions are built with GSAP; custom scripts live in Slater.
4. Content and SEO
Copy goes in, together with titles, meta descriptions, alt texts and structured data. If you're moving from an old site, the redirect map is completed here. See WordPress to Webflow without losing SEO.
5. Testing
We test on phones, tablets and wide screens, check page speed, run an accessibility check and send every form to its destination. You get a test link for your own round.
6. Launch and handover
We connect the domain together, submit the sitemap to Google and Bing and watch the first days closely. In a handover session your team learns to edit text, add CMS items and build new pages from components.
What slows projects down
In our experience, three things: content that arrives late, feedback rounds with too many people, and decisions that get reopened after approval. Name one decision maker on your side and the timeline holds.
