SaaS Marketing Site Engineering: Why Most AI Founders Hire Wrong (2026 Playbook)

Most AI SaaS founders treat the marketing site as a brochure problem and hire it like one. They buy a Framer template, hand it to an agency, and end up six months later with a $60K site that still cannot ship a programmatic SEO page, render an ABM landing variant at the edge, or hold up under the WebGL hero everyone said they wanted. The marketing site in 2026 is a product-grade engineering artifact — programmatic content surfaces, edge-rendered personalization, MDX/Sanity content ops, A/B at the request boundary, lead routing into the product, motion budgets that interact with Core Web Vitals — and the right hire is a design-engineer, not a generic agency designer.

This article names the four staffing models AI founders actually choose between in 2026, prices them honestly, and walks through the failure pattern that breaks every founder-coded marketing site somewhere between $50K and $200K MRR.

Who this is for: Seed-to-Series-A AI SaaS founders, founding marketers, and engineering leads choosing between a design subscription, a boutique SaaS agency, an in-house marketing engineer, or a design-engineer studio for a marketing site rebuild. Stage: 0-24 months post-launch, 10-60 people, currently shipping on Framer/Webflow/founder-coded Next.js, planning a flagship rebuild in the next two quarters.

Key Takeaways

• The marketing site is now a product surface, not a brochure. Programmatic SEO, edge personalization, in-product embeds, real-time pricing, motion budgets — none of this lives in a Framer template, and none of it is a generic agency designer's job. The right hire is a design-engineer, and the wrong hire is whoever sells the cheapest monthly retainer.
• Four staffing models, four price points: $4K-$8K/mo (design subscription), $40K-$120K project (boutique SaaS agency), $160K-$280K all-in (in-house marketing engineer), $25K-$60K/mo (design-engineer studio / FDE model). Each model wins in a specific stage. Picking the wrong one is the single largest avoidable cost on the marketing site for the next two years.
• The founder-coded site breaks at $50K MRR. Pricing page needs three plans and an annual toggle, marketing wants weekly LPs for paid campaigns, sales wants ABM variants, eng will not prioritize it. The break is structural — no amount of "just one more Framer page" fixes it.
• The Linear/Vercel/Mercury/Stripe sites are not built by Framer designers. They are shipped by small design-engineering teams on Next.js + a structured CMS + Vercel edge + Motion + occasional WebGL. The stack is reproducible; the operating model is what makes them ship weekly instead of quarterly.
• The AI "55% faster" productivity figure means the right hire is 3× more leveraged, not that you need fewer hires. A marketing engineer who pairs with Cursor and Claude ships at the pace of a 2-3 person team from 2023. This rewires the build vs buy math entirely.
• WebGL on a marketing site is a budget question, not an aesthetic one. The right place to spend the bundle is the hero or one product-data viz; the wrong place is full-page Three.js everywhere. See our companion piece on WebGL & Three.js SEO for the trade-offs.

1. The Marketing Site Is a Product Now

1-1. What changed between 2022 and 2026

In 2022 the marketing site was a brochure: a hero, a features grid, a pricing page, a contact form. A WordPress theme or a Webflow template handled it. Marketing edited copy in a CMS; engineering never touched the repo. The site shipped quarterly because nobody needed it to ship faster.

By 2026 the same surface carries: programmatic SEO at scale (tens of thousands of pages targeting long-tail product-led queries), ABM landing pages personalized to the visitor's company and stage, real-time pricing and plan comparisons synced from billing, interactive product demos embedded in the hero, integration directory pages auto-generated from the product, edge-rendered A/B variants tested against actual revenue, lead enrichment and routing into the CRM in real time, motion and WebGL surfaces that have to coexist with sub-2.5s LCP, and a design system shared with the product UI. None of this is a Framer template. All of this is engineering work. The teams that ship it weekly look like product teams: a designer-engineer pair, a content surface owned by marketing, a deployment pipeline that ships on every commit.

1-2. Why the brochure-era hiring model fails

The brochure-era model — a designer in Figma, a Webflow developer, a marketing person editing CMS copy — produces a site that ships once and then ossifies. Three months post-launch, the founder wants the pricing page redone for the Series A pitch, marketing wants programmatic SEO turned on, sales wants ABM variants for the top-50 enterprise accounts, and the same Webflow developer is now a $4K/mo bottleneck for every change. The cost is not the hourly rate; the cost is the velocity loss. The pricing page that should ship in a day ships in three weeks because nobody on the team can engineer it.

This is the single most expensive thing most AI founders are getting wrong in 2026. The right framing is captured in the SaaS founder kickoff guide and the Forward Deployed Engineer Studio article: the marketing site is a customer-facing product surface, and product surfaces require engineering operating models.

2. What Breaks at $50K MRR

The pattern is consistent across every AI SaaS we have seen between $50K and $200K MRR. The site is fine at launch — founder-coded on Next.js, or Framer for the non-technical founder. Six months in, the cracks open.

The pricing page. The original site has one plan, $99/month, billed monthly. The Series A pitch needs three plans, annual toggle, enterprise contact form, comparison table, FAQ block, and feature parity matrix. A Framer page cannot hold the comparison logic; a founder-coded React page works but takes the founder a weekend they do not have.

The campaign LP cycle. Paid acquisition is finally working. Marketing wants to ship one LP per week against the top three keywords. The Framer site supports it slowly (each LP is a manual duplicate). The Next.js founder-coded site does not support it at all (the founder has not built an LP factory abstraction). Marketing falls back to Webflow on a subdomain — the brand splits, analytics splits, lead routing splits.

Programmatic SEO. Marketing reads the playbook and wants to ship 10,000 pages targeting "{competitor} alternative" and "{integration} + {use case}." Framer cannot do it. The founder-coded site can, in theory, but it requires a content schema, an MDX or Sanity pipeline, ISR or static generation tuned, and an internal linking strategy. Three weeks of engineering work nobody has.

ABM variants. Sales wants the homepage hero to address the prospect's industry by name when they land from a tailored email. Edge middleware can do it in 50 lines on Vercel; it requires someone who knows what middleware.ts is, has used edge config or KV before, and understands the analytics implication. Not a Framer skill, not a founder's weekend skill.

Product embeds and live data. The hero should show the actual product, not a screenshot. The pricing should reflect the actual plans, not hard-coded numbers. The integrations directory should regenerate when a new integration ships. All three require the marketing site and the product to share a data contract.

This is the break. It is structural. The founder-coded site cannot grow into it without an embedded engineer; the Framer template cannot grow into it at all. The remaining decision is which staffing model to hire into the gap.

3. The Four Staffing Models, Compared

3-1. Design subscription ($4K-$8K/mo)

The Superhi / Designjoy / Awesomic model. Unlimited design requests, one designer at a time, 48-hour turnaround, cancel anytime. Sells well to early founders because it feels low-risk.

What you actually get. A designer who can ship Figma files and Webflow/Framer pages competently. No engineering depth, no edge middleware, no CMS architecture, no design system thinking beyond the single deliverable in front of them. The pod composition is one person at a time, often offshore, frequently rotated. The deliverable is a file, not a deployed surface.

When it wins. Pre-PMF, fewer than 100 paying customers, the site is still a brochure, marketing is the founder, and nothing on the site is load-bearing for revenue yet. The subscription is a placeholder until the product is ready to invest in real surface.

When it fails. Post-PMF, post-Series-A, anywhere the site needs to ship programmatic SEO, ABM variants, edge personalization, or product embeds. The model is structurally incapable of producing those — it is a Figma-and-Framer service, priced for what it is.

3-2. Boutique SaaS agency ($40K-$120K project)

The traditional SaaS web agency: 6-12 person studio, runs an RFP, scopes a 12-16 week project, delivers a Webflow or Next.js site, hands off, optionally sells a retainer for ongoing changes.

What you actually get. A well-designed site at a fixed cost with a fixed timeline. Brand polish, motion, a real design system delivered. The handoff problem is the killer — the agency knows the site, you do not, and three months post-launch the changes start to cost $200/hr against a retainer the agency would rather close.

When it wins. Flagship rebuild tied to a fundraise, Series A or later, the brand is in the wrong shape and needs a full reset, budget is real ($60K+), and there is a separate post-launch plan (in-house engineer, ongoing retainer, or design-engineer studio). Our agency vetting checklist and the premium website cost budget guide are the right tools for shortlisting these.

When it fails. Pre-PMF (too expensive), or post-launch when iteration speed matters more than initial polish. The model is a stage-gate project model; it does not produce a site that ships weekly.

3-3. In-house marketing engineer ($160K-$280K all-in)

A full-time hire: senior frontend engineer with brand sensibility, hired specifically to own the marketing site. Title varies — "marketing engineer," "design engineer," "growth engineer."

What you actually get. Eventually, the right answer for most Series-B+ companies: someone in the repo every day, shipping LPs in hours, owning the design system, integrating with the CRM and the product. Linear's marketing surface, Vercel's marketing surface, and Mercury's marketing surface are all built this way.

When it wins. Series B+, marketing site is core to the GTM motion, founder is no longer the bottleneck for hiring, and there is six months of runway to ramp a hire to full productivity. The economics work above ~$5M ARR.

When it fails. Before Series B. Hiring takes 4-6 months. Ramping takes another 3. The role is rare — the design-engineer skill set is one of the hardest in tech to hire for, and the candidates who exist mostly already work at Linear, Vercel, or Mercury. Most pre-Series-B attempts to hire this role fail and end up with either a frontend engineer who cannot do brand or a designer who cannot ship code. The in-house vs agency vs freelance comparison covers the full trade-off matrix.

3-4. Design-engineer studio / FDE model ($25K-$60K/mo)

A small pod (2-4 people) embedded in your repo, on your Linear, for 8-24 weeks. Includes a design-engineer, a brand designer, a strategist, and optionally a copywriter. Ships into your codebase, not into a vendor wall.

What you actually get. The output of an in-house marketing engineering team without the 6-month hiring lead time and without the $250K loaded annual cost. The pod ships LPs daily, builds the design system, sets up programmatic SEO, builds the ABM pipeline, and handles the WebGL hero — all into your repo, with your team in the room. At the end of the engagement, the work is owned by you (no proprietary CMS, no agency lock-in), and the design system is set up for whoever inherits it.

When it wins. Post-PMF, Series Seed through Series B, the founder-coded site has broken at $50K MRR, and there is no in-house marketing engineer yet. This is the modal AI startup in 2026. The model mirrors the Forward Deployed Engineer Studio on the engineering side and the Forward Deployed Designer on the brand side — combined for the marketing site surface specifically.

When it fails. Pre-PMF (budget should go elsewhere), Series C+ with an existing in-house team (the model adds nothing the team cannot do), or when the founder wants a "vendor" rather than a partner (the embedded model requires daily collaboration).

3-5. Side-by-side comparison

The two rows that matter most: ships into your repo and time-to-start. The design subscription fails the first. The in-house hire fails the second. The boutique agency fails inconsistently on both depending on the studio. The design-engineer studio is the only model that solves both at the engagement size a Series Seed through Series B AI startup can absorb.

4. The Linear / Vercel / Mercury Stack

The reference sites founders cite (Linear, Vercel, Mercury, Stripe) are not built on magic. They are built on a small, reproducible stack with a specific operating model. The stack is the easy part. The operating model is the hard part.

4-1. The reproducible stack

• Framework. Next.js 15 (App Router) on Vercel, or Astro for content-heavy sites. Both ship sub-100ms TTFB at the edge and both support server components / islands for performance budgets.
• CMS / content layer. Sanity, Contentlayer, or MDX in the repo. The choice depends on who edits the content — Sanity for marketing-edited content (Linear, Vercel use similar), MDX in the repo for engineer-edited content. Never Webflow as the source of truth if the site is in Next.js — the dual-source-of-truth pattern is the single most common cause of marketing-site rot.
• Design system. Tailwind v4 + a small set of in-repo components, or a structured token system feeding both the marketing site and the product UI. Linear and Mercury both share tokens between marketing and product.
• Motion. Motion (formerly Framer Motion) for component animations; GSAP for scroll-driven sequences; Lottie for icon-scale motion.
• 3D / WebGL. Three.js or React Three Fiber for the hero or product viz, behind an IntersectionObserver lazy load and a mobile fallback image. See our WebGL & Three.js SEO guide for the performance contract.
• Personalization / experimentation. Vercel Edge Middleware, edge config or KV for variant assignment, Statsig or PostHog for measurement.
• Lead capture. Inngest or Vercel Cron for enrichment, Clearbit or RB2B for identification, the CRM (HubSpot/Salesforce/Attio) as the source of truth.

The stack is public. Anyone can copy it. What is not public is the operating model: who commits to the repo, who reviews PRs, who owns the design tokens, who decides when to ship a WebGL hero, who triages the marketing backlog. That is the work the four staffing models in section 3 differ on.

4-2. What the stack costs

For a Series-A AI SaaS shipping on this stack: Vercel Pro ($20/seat/month) + Sanity ($99-$949/month depending on traffic) + Statsig/PostHog ($0-$2K/month) + the design system (free, owned by you). Tooling cost is rounding error. The cost is the team that runs it. This is the custom web app budget guide point applied to the marketing site specifically.

5. The Marketing-Engineer Job Spec

For founders considering the in-house hire route in section 3-3, the job spec below is the one that has actually worked in 2026. It is not the spec for a generic frontend engineer.

Title: Marketing Engineer (or Design Engineer)

Reports to: Head of Marketing (dotted line to Head of Engineering)

Comp band 2026: $160K-$220K base + 0.1-0.4% equity, $200K-$280K loaded total

Must have:

• Shipped a production marketing site on Next.js or Astro in the last 18 months
• Demonstrably good visual taste — a portfolio that shows brand sensibility, not just engineering
• Comfortable in Figma at the design-system level (modifying tokens, building components, not pixel-pushing)
• Comfortable owning the deployment pipeline (preview deploys, edge middleware, ISR)
• Has shipped at least one of: programmatic SEO at scale, edge-rendered personalization, motion-heavy hero with passing Core Web Vitals

Nice to have:

• WebGL/Three.js production experience (rare and 30K+ on the comp band)
• Brand-side writing ability (rarer still, worth the same premium)
• Has worked at Linear, Vercel, Mercury, Stripe, Ramp, or similar (the candidate pool is mostly here)

What this role does not do:

• Product engineering (separate role)
• Generic design work outside the marketing surface (separate hire)
• Performance marketing or paid acquisition (separate hire)
• Brand strategy at the company level (founder + brand designer, not this role)

Interview signals. Ask the candidate to take a public marketing site (Linear, Vercel, Mercury) and rebuild the hero in 90 minutes. The strong candidates ship working code + reasonable motion + a non-broken mobile layout in that window. The weak candidates ship a static screenshot. The signal is unambiguous.

6. Programmatic SEO, ABM, and the Things Framer Cannot Do

Three engineering capabilities separate a real marketing surface from a brochure. Founders consistently underestimate how much of the GTM motion depends on them.

6-1. Programmatic SEO

The pattern: generate thousands of pages targeting long-tail queries from a structured data set. Example sets: integrations ("Notion + Slack integration"), comparisons ("{competitor} alternative"), use cases ("AI agent for {industry}"), templates ("{document type} template"). Each page is a deterministic function of the data plus a shared template.

Framer does not support this. Webflow CMS supports up to a few thousand items but ships poor LCP and brittle internal linking. Next.js + a content source (Sanity, Contentlayer, a JSON file in the repo) is the only path that scales to tens of thousands of pages with good Core Web Vitals.

The traffic compounds: AI search and traditional SEO both reward the long tail in 2026, and the first AI startups to ship 10K+ pages in their category are capturing the inbound. The lead quality is high because the queries are commercial-intent. The work is two weeks of design-engineer time once the data is structured.

6-2. ABM landing variants at the edge

The pattern: a sales rep emails a prospect at Acme Corp with a tailored URL. The prospect lands on the homepage. Edge middleware reads the URL parameter, looks up Acme Corp's industry, swaps the hero copy, and serves the page in 50ms. The prospect sees "AI agents for healthcare" instead of "AI agents for everyone." Conversion lifts 2-4x for the targeted accounts.

This requires: edge middleware, an edge KV store of account data, a hero component with a swappable copy block, and a clean fallback for non-targeted traffic. Vercel ships all of it; the implementation is one week.

6-3. Product embeds and live data

The pattern: the hero shows the actual product (not a screenshot), the pricing reflects the actual plans (not hard-coded numbers), the integrations directory regenerates when a new integration ships. The marketing site and the product share a data contract.

This requires: a shared component library between marketing and product, a feature flag system, and a deploy pipeline that triggers both repos. Hard to set up the first time; trivial to maintain after. Linear and Mercury both do this; the result is a marketing site that feels alive.

None of this is exotic engineering. All of it is invisible to a Framer-trained designer. This is the single largest reason the staffing-model choice matters.

7. Where WebGL Pays Off — and Where It Wastes Budget

Founders see Linear's homepage and want a WebGL hero. Sometimes they should have one; usually they should not.

Where WebGL pays off. A single product-data visualization or a one-screen hero that demonstrates something a screenshot cannot. Examples that work: a real-time scrollytelling sequence showing the product's value (Stripe-style), an interactive product topology (Vercel's edge map), a Gaussian splat of a physical product (e-commerce, hardware). One WebGL surface, lazy-loaded, with a passing LCP — this is the right spend.

Where WebGL wastes budget. Full-page Three.js scenes, animated 3D logos, particles-on-every-page. The pattern fails on mobile (Three.js bundles add 200KB+ minified), it tanks Core Web Vitals, and the conversion lift is rarely measurable against the engineering cost. If the conversion data does not exist, the right move is to skip it.

The decision is captured in the WebGL & Three.js SEO guide: WebGL has to defer the bundle, move shader compile to a Web Worker via OffscreenCanvas, ship a mobile image fallback, and survive Core Web Vitals. None of this is a Framer designer's job, and none of it is even a typical agency Next.js developer's job — it is design-engineering territory.

For the question of when AI website builders (v0, Lovable, Bolt) are enough versus when custom is required, our AI website vs custom design piece covers the trade-offs.

8. AI Productivity Realism: The 55% Number

The 2026 hiring discourse cites a 55% productivity gain from AI coding assistants. Some recruiting guides interpret this as "you need 30-40% fewer developers." This is the wrong read for marketing engineering specifically.

The right read: a marketing engineer who pairs with Cursor and Claude ships at 2-3× the velocity of the same engineer in 2023. They are not replacing a team of three; they are doing the work of a team of three. The shape of the role changes — more time spent on judgment, less on boilerplate — and the comp expectation rises accordingly. The best marketing engineers in 2026 are not cheaper than they were in 2023; they are 50% more expensive and 3× more leveraged.

For the design-engineer studio model (section 3-4), the same multiplier applies. A 2-person pod in 2026 ships what a 4-person pod shipped in 2023, at roughly the same dollar cost — because the comp scaled but the headcount did not. The total throughput per engagement is the variable; the model captures the gain rather than passing it through as a discount.

The implication for build vs buy: the agency price points have not moved much, but the output per engagement has. A $90K design-engineer studio engagement in 2026 ships a Linear-quality marketing site in 8-10 weeks, where the same engagement in 2023 would have shipped a non-Linear-quality site in 14 weeks. This is the math founders are missing when they compare 2023 RFP responses to 2026 ones.

9. Decision Tree: Pick Your Model in Five Questions

Five questions, answered honestly, will pick the right model 90% of the time.

1. Are you pre-PMF (fewer than 20 paying customers)? If yes, spend the budget on customer interviews and a Framer template. None of the engineering capabilities in this article matter yet. Revisit the decision at $30K MRR.

2. Is the marketing site currently breaking on a specific shipped need (programmatic SEO, ABM variants, pricing page, weekly LPs)? If yes, you need engineering capacity now. Skip the design subscription. Choose between agency project, in-house hire, or studio based on questions 3-5.

3. Do you have 4-6 months of runway to hire and ramp a marketing engineer? If yes and you are Series B+, hire in-house. If no or pre-Series-B, choose between agency project and studio based on questions 4-5.

4. Is there a flagship rebrand or rebuild tied to a specific event (fundraise, launch, repositioning) in the next quarter? If yes, agency project is correct — fixed scope, fixed timeline, designed for the event. The evaluate web agency checklist and the series-A website refresh framework cover this case in detail.

5. Do you need ongoing capacity (weekly LPs, programmatic SEO, ABM, product embeds, motion experiments) and you cannot wait 4-6 months for an in-house ramp? If yes, design-engineer studio is correct. The model is built for this gap.

The 10% of cases that fall outside the tree usually involve a designer or design-engineer co-founder who is already shipping — in which case skip everything in this article and let them ship. The model is wrong when the gap is not real.

10. About Utsubo

Utsubo is a creative web studio that runs design-engineer studio engagements for AI-adjacent SaaS startups. We embed a small pod (design-engineer, brand designer, strategist, optional copywriter) into the client's marketing-site repo for 8-24 weeks, working in the client's codebase, Figma, and Linear rather than handing off across a vendor wall.

We work mostly with seed-to-Series-B AI startups (10-60 employees) whose founder-coded marketing site has broken at $50K MRR and who need engineering capacity now without a four-to-six-month in-house hiring ramp. We ship into Next.js, Astro, and the standard 2026 marketing stack (Sanity, Vercel edge, Motion, Three.js where it pays off). We are vendor-neutral by structure on frameworks and CMS — we do not pull licensing revenue from any tool we recommend.

We say no when a freelance designer alone, a Framer template, or a permanent in-house hire is the right answer. If you do not need us, we will tell you and point at who you do need.

11. Let's Talk

Building an AI SaaS and looking for the engineering capacity to ship programmatic SEO, ABM variants, a real pricing page, or a Linear-quality marketing surface — without waiting six months to hire it in-house?

If you are exploring a design-engineer studio engagement, let's discuss your project:

• The product, the stage, and the specific shipped needs blocked today
• The current state of the marketing site stack and team
• Whether we are the right team — and if not, who is

Book a project discussion

Prefer email? Contact us at: contact@utsubo.co

12. Pre-Hire Checklist

Ten questions before signing with anyone — us included.

1. You can describe the specific marketing-site capability gap in one sentence. "We cannot ship LPs faster than once a month" is a brief. "The site feels old" is not.
2. You have at least one shipped need in the next two quarters that requires engineering (not design). Programmatic SEO, ABM, edge personalization, billing-synced pricing, product embeds. If none of these are on the roadmap, you are choosing the wrong model.
3. You know which of the four staffing models matches your stage and runway. Walk the five-question decision tree in section 9 before booking calls.
4. You can absorb the cost of the chosen model in this quarter without forcing a payment plan over 12 months. If the cashflow does not exist, the engagement is too big for the current stage.
5. You can give the pod (or hire) in-repo access, a Figma seat, and a Linear seat. Embedded means embedded. If access takes four weeks of security review, the engagement starts in week five and ends short.
6. The marketing site is owned by someone — Head of Marketing, founder, or a founding marketer. If nobody owns it, the engagement has no decision-maker and stalls in week two.
7. You have realistic conversion benchmarks. Per the Landy 2026 benchmark report, the median landing page converts at 6.6% and the top decile at 15-20%. If your current conversion is 0.5% and you expect 15% from a redesign, expectations are misaligned.
8. You are not pre-PMF. Fewer than 20 paying customers and unclear product shape — the budget belongs in customer interviews, not marketing site engineering.
9. You have a measurable success metric for the engagement. "Better-looking site" is not measurable. "Trial-to-paid conversion from organic up 30% in 90 days" is. Pick one or two.
10. You want one team accountable for the whole marketing-site surface, not three vendors handing off. The single-throat-to-choke argument from the Forward Deployed Engineer Studio article applies equally here.

FAQs

What is a design-engineer studio? A design-engineer studio is a small pod (2-4 people) that combines a senior design-engineer, a brand designer, a strategist, and optionally a copywriter, embedded in a client's marketing-site repo for 8-24 weeks. The pod ships code and design into the client's codebase rather than handing off Figma files or a Webflow site across a vendor wall. The model is sized for AI SaaS startups between Series Seed and Series B that need engineering capacity on the marketing site immediately, without a 4-6 month in-house hiring ramp. Cost lands at $25K-$60K/month total, or $150K-$360K for a typical 6-month engagement.

How is a design-engineer studio different from a SaaS web design agency? Three structural differences. First, the studio ships into the client's repo and Linear rather than into a separate vendor-owned site or a handoff. Second, the engagement is ongoing (8-24 weeks) rather than a fixed-scope project, which means the pod ships LPs weekly rather than delivering one site once. Third, the pod includes a design-engineer (someone who can ship Next.js, edge middleware, programmatic SEO, and motion) rather than a designer-plus-Webflow-developer pair. Agencies are stronger for one-off flagship rebuilds; studios are stronger for ongoing marketing-site engineering capacity.

When should an AI SaaS hire a full-time marketing engineer instead of a studio? At Series B+, with $5M+ ARR, where the marketing site is core to the GTM motion and there is six months of runway to hire and ramp the role. The candidate pool is small (most strong marketing engineers already work at Linear, Vercel, Mercury, Stripe, or similar), the hiring lead time is 4-6 months, and the ramp is another 3 months. Below Series B, the in-house route loses on time-to-shipped-code and on hiring odds. Above Series B, it is usually the right answer.

How much does a SaaS marketing site cost to build in 2026? Tier ranges: design subscription $24K-$48K over 6 months, boutique SaaS agency project $40K-$120K (often plus a retainer), in-house marketing engineer $200K-$280K loaded annually, design-engineer studio $150K-$360K over 6 months. The right answer depends on what you actually need shipped, not on which number sounds cheapest. The cheap option (design subscription) cannot ship programmatic SEO, ABM, or a real pricing page — which means it is not actually cheap if any of those are on the roadmap.

Is Framer enough for a SaaS marketing site? For pre-PMF startups with fewer than 100 paying customers and a brochure-shaped marketing surface, yes. For anything beyond that — programmatic SEO at scale, ABM variants, edge personalization, billing-synced pricing, product embeds, motion-heavy hero — no. The Framer ceiling is structural, not a matter of skill. The right time to migrate off Framer is when the first shipped need on the roadmap requires capability Framer does not have.

How long should a flagship marketing-site rebuild take in 2026? A design-engineer studio model ships a Linear-quality flagship rebuild in 8-12 weeks. A boutique agency project takes 12-16 weeks. An in-house team takes 6-9 months including hiring. The 2026 productivity gains from AI coding assistants have compressed the studio timeline more than the agency timeline, because the studio model captures the productivity gain while the fixed-scope agency model passes some through as faster delivery and some through as wider scope.

Where does WebGL belong on a SaaS marketing site? On the hero, on one product-data visualization, or on a single scrollytelling sequence — and only when there is a measurable conversion thesis behind it. Full-page Three.js on every section is a budget waste: it tanks mobile performance, hurts Core Web Vitals, and rarely lifts conversion measurably. The right WebGL spend is one surface, lazy-loaded, with a mobile image fallback. The implementation requires a design-engineer who has shipped production WebGL before — not a Framer designer and not a typical agency Next.js developer.

Should the marketing site live in the product monorepo? Usually no, but with shared design tokens and a shared component library. Separate repos for the marketing site and the product, with the design system as a published package consumed by both. This gives the marketing site faster CI, independent deployments, and a different release cadence (daily or weekly for marketing, slower and more controlled for product). The pattern is what Linear, Vercel, and Mercury all converged on.