Key takeaways
- A competent Next.js development agency should tell you up front whether your pages will be statically generated, server-rendered or a mix, and why that choice suits your content.
- Ask who owns the hosting account, the domain and the CMS login before work starts. After launch is too late, and you should never be locked out of your own site.
- A fixed scope and fixed price, in writing and agreed before work begins, is a basic professional standard. It is not a premium feature.
- Ask for a live Next.js site you can open in a browser, not a mockup or a slide, and check its performance yourself.
- Meant answers all 11 questions directly: a fixed price after a free 30-minute call, a senior team only, hosting and accounts owned by the client, and work in English, Arabic or Greek.
Why the Wrong Next.js Development Agency Costs More Than the Build
Picking a Next.js development agency is a software decision. It is not a design decision. The framework is flexible, so two agencies can quote for the "same" site and deliver very different things. One builds pages that load as finished HTML from the edge. The other renders everything on every request, runs up a hosting bill and slows down under traffic.
The invoice is the cheap part. The real cost of a bad choice turns up later. It looks like a site your team can't edit, a hosting account in someone else's name, or a rebuild eighteen months on because nobody planned for a second language. A pitch built on adjectives can hide all of this, and a slick portfolio reel can too.
When you are hiring a web agency, the remedy is to ask technical questions and listen for specific answers. You don't need to be a developer to do it. You only need to notice whether the person across the table names the tool, the account and the price, or changes the subject. This is how we run bespoke Next.js website design and development at Meant, and it is the standard to hold any agency to.
The 11 Questions to Ask Before You Sign
Take this Next.js agency checklist into the sales call. Each question has a short note on why it matters. The table after the list sets out what a good answer and a worrying answer sound like.
1. Will the site be statically generated, server-rendered, or both?
Static pages are built once and served instantly. Server-rendered pages are built for each visitor. Most good sites use a mix. A marketing page is usually static, while a logged-in dashboard is rendered on the server. The agency should explain the split page by page.
2. Which CMS will we use, and can we edit content without a developer?
If every new case study or price change needs a ticket, you are paying a developer to do data entry. Ask to see the editing screen, not just hear the product name.
3. Where will the site be hosted, and who owns the account?
The hosting account, the domain registrar and the code repository should be in your company's name, with the agency added as a user. Whoever owns the account owns the site.
4. What happens to our page speed and layout stability at launch?
Three things matter most to a visitor: how fast the main content appears, how quickly the page responds to input, and how much the layout jumps while it loads. Ask whether good scores on mobile are part of the acceptance criteria, not an afterthought you discover once the site is live.
5. Is the scope and price fixed in writing before work starts?
This is the core of a fixed scope web build. You should know the total before you commit, and you should know what counts as a change.
6. Who actually writes the code: your team or a subcontractor?
Many agencies sell the work and pass the build to freelancers. That is legal. It is also worth knowing, because the people on the sales call may never touch your project.
7. How do you handle bilingual or multi-language builds?
A second language changes routing, metadata, typography and, for Arabic, the direction of the entire layout. It needs planning on day one. Adding it after launch costs far more.
8. What's your plan for SEO and structured data from day one?
Ask about page titles and descriptions, sitemaps, redirects from your old URLs, and structured data (machine-readable labels that tell search engines what a page is about). A migration without redirects throws away the rankings you already have.
9. Can you show a live Next.js site, not a mockup?
A Figma file proves someone can design. A live URL proves they can ship. Open it on your phone and judge the speed yourself.
10. What happens if we want to leave or switch agencies later?
The answer should be dull: you already own the repository, the accounts and the content, so you hand a new team the keys. Exit fees or "proprietary" frameworks are a warning.
11. Who do we call after launch, and what does support cost?
Get a name, a channel and a price. Support that is "included" with no terms written down usually means support that is slow.
| Question | Strong answer sounds like | Worrying answer sounds like |
|---|---|---|
| 1. Rendering | "Marketing pages static, account area server-rendered, blog revalidated when you publish." | "Next.js handles all that automatically." |
| 2. CMS | A demo of the editing screen | "Just send us the changes." |
| 3. Hosting | "Your account, your card, we're added as users." | "We host it for you on our account." |
| 4. Speed and stability | Mobile targets written into acceptance criteria | "It'll be fast." |
| 5. Scope and price | A written scope with a single total | An hourly rate and an estimate range |
| 6. Who codes | Named people on the call | "Our development partners." |
| 7. Languages | Routing, layout direction and metadata per language | "We'll add a translation plugin." |
| 8. SEO | Redirect map, sitemap, structured data at launch | "SEO is a separate service." |
| 9. Live work | URLs you can open now | Slides and screenshots |
| 10. Leaving | "You already own everything." | Exit fees or a proprietary setup |
| 11. Support | Named contact and written terms | "We're always around." |
Answers That Should Worry You
The checklist works best as a filter. Good agencies answer quickly and specifically. Weaker ones get vague at the same few points.
Vague answers about rendering strategy
"Next.js is fast by default" isn't an answer. The framework gives you options. It doesn't make the choice for you. If an agency can't say which pages are static and which are rendered per request, it hasn't designed the architecture yet, or it builds every project the same way regardless of content. Either way, you'll find out in production.
No answer on who owns hosting and the CMS
Some agencies keep hosting on their own account and bill it back with a margin. That can be convenient, until you want to leave and find your domain, your deployments and your content database all sit behind someone else's login. If ownership isn't clear in writing before kickoff, assume it isn't yours.
Scope that grows after the kickoff call
A proposal that says "approximately" a lot, or lists deliverables without listing pages, templates and integrations, leaves room for the price to move. Then the kickoff call turns into a discovery phase, which turns into a revised estimate. A proper scope is detailed enough that both sides can point to it when they disagree.
What a Strong Answer Actually Looks Like
Good answers are easiest to judge against real, live work. Two of our projects show what questions 2 and 9 should get you.
CMS control without calling a developer
Lava Space is a UAE interior design and fit-out company that works with government entities, hospitality brands and corporate headquarters across the Gulf. We built a minimal, monochrome Next.js site where the spaces take centre stage. Underneath it sits Lava Space's bespoke CMS, which lets the studio upload and organise projects, galleries, categories and client logos without ever calling a developer. That is the answer to question 2. The editing tool fits the business's content, and nobody has to file a ticket to publish a new project. It is live at lavaspace.ae, so you can test it against question 9 as well.
Full-stack build and AI layer on top of a brand
Grumpus began as a 2023 meme coin with a homepage to match. We rebranded it end to end, covering the logo, the brand architecture and the move from paulgrumpus.com to grumpus.io. Then we engineered the ecosystem around it. Grumpus's full-stack rebuild and AI layer covers web development, hosting and frontend management. It also includes a Telegram character with conversation memory, live football predictions with shareable match cards, community polls and full-time reactions. The relevant point for your checklist is that the build, the hosting and the AI layer came from the same team, which is what question 6 is really asking you to check.
What Fixed Scope and Fixed Price Actually Mean
"Fixed price" only protects you if the scope it is fixed against is written down properly. One without the other is a guess.
What a written scope should list
A usable scope document names, at minimum:
- Every page and page template, with the rendering approach for each
- The CMS, and which content types your team will be able to edit
- Integrations: forms, CRM, payments, analytics, booking, WhatsApp or email flows
- Languages, and whether right-to-left layout is included
- SEO work at launch: redirects, sitemap, metadata, structured data
- Performance targets and how they will be measured
- Who owns which accounts, and when access is handed over
- What counts as a change request, and how changes are priced
- The total price and the payment milestones
At Meant, every build starts with a free 30-minute call. We then send a fixed price for a written scope before any work begins. Projects start at $2,000. There is no hourly billing, and the first call costs nothing.
Why hourly billing on a web build is a risk
Hourly billing makes sense for open-ended work such as consulting or ongoing support. A website build has a defined end state, so it can be scoped. When an agency bills a build by the hour, the risk of its own estimating moves onto you. Slow work earns it more and efficient work earns it less, which sets up the wrong incentive. If an agency can't price a build it has scoped, it hasn't really scoped it.
Running the Project Once You've Hired Someone
Hiring a web agency is the start. Whether the project runs well depends on communication more than code.
Working across time zones
Most of our clients work with us remotely, and we schedule calls in your time zone rather than ours. Ask any agency how decisions get made between calls, where files and feedback live, and who signs off each stage. If you want the detail, here is how a remote project actually runs across time zones.
Bilingual and multi-language delivery
We work in English, Arabic and Greek. For bilingual English and Arabic builds, that means more than translated strings. Each language gets its own URLs, a layout that mirrors properly from right to left, Arabic typography chosen to sit well beside the Latin type, and translated metadata so search engines index both versions. Ask any Next.js development agency whether a native speaker reviews the second language before launch. Machine translation on a premium brand reads as machine translation.
Frequently asked questions
What is the difference between static generation and server-side rendering in Next.js?
Static generation builds a page into HTML once, at build time, and serves the same file to every visitor, so it is very fast. Server-side rendering builds the page fresh on each request, which suits personalised or constantly changing content. Next.js also lets static pages be regenerated on a schedule or when you publish. Most well-built sites mix all three.
How much does a Next.js website typically cost?
It depends on the number of templates, the CMS, integrations and languages, which is why a written scope matters more than a ballpark. At Meant, projects start at $2,000, and every build gets a fixed price in writing after a free 30-minute call. Be cautious of any quote given before anyone has asked what the site needs to do.
Can a Next.js site be built bilingually in English and Arabic?
Yes. Next.js supports language-based routing, so each language gets its own URLs and metadata. Arabic also needs a right-to-left layout and suitable typography, and both should be planned from the start. We build bilingual English and Arabic sites as standard.
Is Next.js better than WordPress for a growing business?
For a simple blog, WordPress is often enough. Next.js suits businesses that need fast performance, custom design, integrations with other systems, or a site that behaves like a product. With a headless CMS, your team still edits content without touching code.
How long does a typical Next.js build take from kickoff to launch?
It depends on scope: a focused landing page and a multi-language site with integrations are very different jobs. A good agency puts the timeline and milestones in the written scope alongside the price. If an agency won't commit to dates, treat that the same way you would treat an open-ended estimate.
If you want straight answers to all 11 of these questions, book the free 30-minute call with Meant. You'll leave with a clear scope, and a fixed price will follow in writing.
