Next.js Agency for SaaS: 8 Questions to Ask in 2026

Why is choosing a Next.js agency for SaaS harder in 2026?

Choosing a Next.js agency for SaaS in 2026 means separating engineering studios from template resellers, and the difference shows up in five places: rendering strategy, hosting independence, performance evidence, AI-search readiness, and ownership terms.

Next.js itself is no longer a differentiator. The framework runs on 3.2% of all websites as of August 2026 (W3Techs), and Next.js 16, released in October 2025, made Turbopack the stable default bundler with production builds two to five times faster. Nearly every web vendor now claims Next.js expertise, and that claim is cheap.

What separates senior shops is judgment: which pages should be static, which deserve server rendering, where the site actually lives, and what you own when the project ends. The eight questions below force that judgment to the surface. Ask all of them before signing anything.

Which rendering strategy should a SaaS marketing site use?

The right answer is per-route: static generation for public marketing pages, incremental regeneration for content that changes between releases, and server rendering only where content must differ per user.

The economics are simple. Static HTML served from a CDN responds in tens of milliseconds and costs almost nothing per request. Server-side rendering buys freshness and personalization but adds per-request latency and ongoing compute. In practice, a B2B marketing site is nearly all static pages, a handful of incrementally regenerated ones — blog, pricing, changelog — and zero or a single page that genuinely needs a server.

Listen for reasoning, not slogans. An agency that answers 'SSR for everything' is selling compute you do not need. One that answers 'everything is static' without addressing how your CMS pushes updates has not thought about your workflow. The senior answer names the pages in each category and explains why.

• Green flag: a page-by-page rendering map tied to how often content changes.
• Red flag: a single global rendering mode defended with buzzwords.

Do we need Vercel to run Next.js in production?

No. Next.js is a framework, not a hosting product — a static or hybrid Next.js site can run on any CDN or edge network, including Cloudflare, and often should.

Vercel created Next.js and its platform conveniences are real, but tying your marketing site to one vendor's runtime is a negotiating position you do not want. The test is architectural: if the build output is portable HTML plus edge functions, you can change hosts in a day. If the site depends on proprietary runtime features, leaving means rebuilding.

Ask where the site will deploy, who owns the hosting account, and what happens if you want to move. A senior shop answers all three without hesitation, because portability is cheap to deliver and expensive to retrofit.

• Green flag: deployment to infrastructure in your name, with build configuration in your repository.
• Red flag: hosting bundled inside the agency's account with no export path.

What Core Web Vitals evidence should a Next.js agency show?

Ask for field data from live client sites, not Lighthouse screenshots from a staging server.

Google's thresholds are specific — LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1 — and Core Web Vitals are part of Google's page-experience ranking signals (Google Search Central). Performance is also a revenue variable: in an A/B test published as a web.dev case study in 2024, Rakuten 24's Core Web Vitals-optimized landing page converted 33.13% better and generated 53.37% more revenue per visitor than the original.

So the question is evidence. Any agency can promise speed; a senior one shows Chrome UX Report or Search Console numbers for a site it shipped, and explains which decisions — rendering mode, image handling, script budgets — produced them.

• Green flag: field metrics on live client URLs, with the tradeoffs explained.
• Red flag: lab-only scores, or measurements taken on a developer's own machine.

Will the site be visible to AI answer engines?

Only if your content appears in the initial HTML response. Most AI crawlers — OpenAI's GPTBot and OAI-SearchBot, ClaudeBot, PerplexityBot — fetch pages without executing JavaScript and give up quickly on slow responses (AI Crawlability, 2026).

That makes the rendering decision from question one an AI-visibility decision too. A client-side-rendered marketing site is effectively invisible to most answer engines, because the text never exists in what the bot fetches. A static or server-rendered page hands over its full content on the first request.

Beyond rendering, ask how the agency handles robots.txt — AI bots need explicit allowance, separate from Googlebot — structured data, and freshness signals. Answer engines favor pages with visible, machine-readable update dates. A static-first architecture gets this right almost by default; retrofitting it later rarely works as well.

• Content present in the initial HTML response, not injected by JavaScript.
• robots.txt explicitly allowing GPTBot, OAI-SearchBot, ClaudeBot, and PerplexityBot.
• Valid structured data plus visible, machine-readable publish and update dates.

How much does a Next.js agency project cost in 2026?

Market pricing for a specialized-agency marketing site typically runs $15,000 to $40,000 with a four-to-eight-week timeline, at agency rates of roughly $150 to $350 per hour (Social Animal, 2026).

Use those bands as a plausibility filter. A quote far below the floor has to recover the margin somewhere: junior developers, reused templates, skipped QA, or open-ended hourly billing that drifts. A quote far above the ceiling should come with a named senior team and a scope that justifies it.

The structural question matters more than the hourly rate: who actually does the work, the people in the sales call or someone else? Small senior teams with modern tooling routinely out-deliver large junior teams at a lower total cost, but only if staffing is named in the contract rather than promised verbally.

• Green flag: named senior staff, fixed milestones, written scope.
• Red flag: a vague quote with the team 'assigned after kickoff.'

Who owns the code when the project ends?

You should — all of it: repository, IP, hosting accounts, CMS, analytics, and every credential. Anything less is a rental, not an asset.

This is where cheap quotes become expensive. Agency lock-in usually hides in the contract rather than the code: hosting inside the agency's account, CMS licenses in their name, or IP assignment that vests only after 'full payment of ongoing retainers.' Read the ownership clauses before evaluating the portfolio.

Pair ownership with scope discipline. Fixed milestones with written scope protect your budget; open-ended time-and-materials transfers estimation risk to you. The handoff question reveals an agency's model instantly — shops that plan to keep you through dependency will hedge, while shops that expect you to stay because the work is good will hand over everything.

• Code, IP, and all accounts transfer to you at handoff, in writing.
• Fixed milestones and written scope, not open-ended billing.

How this applies at Kiwi

Kiwi is a boutique studio built around the senior answer to every question above. We take on two to three new builds per month, staff every project with senior engineers only — no junior hand-offs — and every enquiry is reviewed by a senior within 24 hours. Kickoff typically happens within five business days of agreement, and each project runs on fixed milestones with written scope, so the budget is decided before work starts rather than discovered during it.

Our default architecture for B2B marketing sites is a Next.js 15 static export served from Cloudflare's edge: portable, HTML-first output that loads fast, deploys anywhere, and can be read by AI crawlers without executing a line of JavaScript. At handoff you own 100% of the code and IP. Our audits are evidence-led — we report what the data shows and never guarantee rankings. If you are choosing between agencies, bring us the same eight questions and compare the answers.