Recommendation

Go with Next.js plus a headless CMS that supports visual editing and a component-based page builder. Your developers build a library of React blocks, and marketing assembles and edits pages from those blocks with live preview. This gets marketing independence without handing them a free-form canvas, and it keeps engineering in their own stack.

For a team your size, I'd pick one of these two:

• Sanity: very flexible content modeling, strong developer experience, and a Presentation tool for click-to-edit visual previews. It's the best choice if your devs want control and you expect the content model to grow (blog, case studies, changelog).
• Storyblok: the most "visual builder" feel out of the box, so marketers get comfortable faster. It's a little more opinionated. Choose it if marketing autonomy matters more than modeling flexibility.

Contentful works too, but it's pricier and clunkier for page building at your stage.

When to choose something else

• Builder.io or Plasmic give marketing true drag-and-drop on top of your React components. They're powerful, but layouts tend to drift off-brand without discipline, and you add a vendor dependency to rendering.
• Webflow or Framer are honestly the fastest path if developer time is the real constraint. The trade-off is that your devs lose React, and sharing components or styles with the product gets harder.

If your devs can commit roughly one to two people for six weeks, stay with headless and Next.js. If they can't, use Framer and revisit after the raise.

The most important scoping decision

Separate the site launch from the announcement. Ship the new site in week 6, then make announcement day just a content publish: the news post, an updated About page, and a homepage banner. Use your CMS's drafts and scheduled publishing to stage the embargoed content ahead of time. Launching a new site and a funding announcement on the same morning is how you end up debugging DNS during your press cycle.

Pages to include at launch

• Home
• Product or platform overview, plus one to three solution or use-case pages at most
• Pricing, or a "Talk to sales" page if pricing isn't public
• Customers, with two or three case studies or at least strong logos and quotes
• About, covering mission, team, and investors (staged for the announcement)
• Blog, with the funding announcement post ready in draft
• Careers, linking out to your ATS (Ashby, Greenhouse, Lever) rather than building job pages, since a raise drives applicants
• Demo or contact page with a form routed into your CRM
• Security or trust page, which matters for B2B data buyers, plus privacy, terms, and a 404 page

Block library (about 12 to 15 components)

• Hero variants, logo strip, feature grid, split image and text, and stats band
• Testimonial or quote, case study card, CTA band, and FAQ accordion
• Pricing table, team grid, rich text, and video or embed

Keep the blocks constrained: limited color and layout options, sensible defaults, and required alt text. Guardrails are what keep the site on-brand once marketing owns it.

Non-negotiables

• Per-page SEO fields, OG images, sitemap, and canonical URLs
• A redirect map from the old site's URLs, managed in the CMS so marketing can add more later
• Draft preview and scheduled publishing
• Analytics (PostHog, GA4, or your own product, if dogfooding makes sense), a consent banner, and form-to-CRM integration (HubSpot or similar)
• Good Core Web Vitals, basic accessibility, and hosting on Vercel or Netlify with preview deploys

Cut for now

• Localization, personalization, and A/B testing
• A filterable resource center or gated content library
• Docs migration, interactive product demos, and heavy animation
• Elaborate integrations page

Suggested timeline

• Week 1: information architecture, page list, content model, and design direction. Start copywriting immediately, because content is usually the real bottleneck, not code.
• Weeks 2–3: build the block library, configure the CMS, and set up preview.
• Weeks 4–5: assemble pages in the CMS, with marketing doing the building so they learn the tool. Wire up forms and analytics.
• Week 6: content QA, redirects, SEO checks, performance and accessibility pass, then launch.
• Week 7: fix issues and stage the embargoed announcement content.
• Week 8: announce, with buffer to spare.

Main risks to watch

• Design or copy arriving late. Lock messaging by week 3, even if the Series A specifics stay in draft.
• Over-building the block library. Add a new block only when a page actually needs one.
• Unclear ownership after launch. Name one marketing owner for the CMS and one engineer for the block library.