Why every Next.js quote sounds like a different planet

Vendors are not lying when numbers swing from five figures to seven for “a Next.js app.” They are answering different questions. A five-page marketing site with a headless CMS is not the same problem as a multi-tenant B2B SaaS with SSO, audit trails, and a billing engine — even if both say React on the tin.

We scope in three passes: discovery (what we are building), technical architecture (how it stays maintainable), and delivery model (who owns product decisions week to week). Skip discovery and you get either a padded hourly estimate or a fixed bid that turns into change-order hell.

If your brief is “just like Vercel’s marketing site,” say what you mean: static-first, aggressive caching, zero custom auth, and a CMS your marketing team can actually use. That is a different animal than “just like Notion.”

Ballpark tiers (CAD, fixed-bid friendly ranges)

These are all-in build budgets for a competent agency — design, frontend, API layer, QA, project management, and a proper handoff. They assume you already know what you are selling; strategy workshops are extra.

Treat the wide bands as “complexity tax”: integrations, compliance, legacy data migration, and executive stakeholders who discover new requirements every Tuesday move you to the high end.

Where the money goes (line items as % of total)

Once discovery locks scope, we translate scope into buckets. Percentages move — if you are importing ten years of messy CRM data, backend and migration swell; if you are obsessed with marketing conversion, UX and frontend swell.

Hidden costs honest vendors put in the appendix

These are the ones that blow up “cheap” quotes: WCAG-oriented fixes after the fact, structured data and OG hygiene for SEO, i18n when the CEO announces Canada + UK launch in the same quarter, CMS modeling when marketing wants “just one more flexible block,” and a real permissions matrix when “admin” turns into five roles and legal wants read-only observers.

We bake baseline SEO and analytics into proposals; some shops treat Search Console and sitemap generation as a phase-two upsell. That is how you launch something pretty that nobody finds.

• Accessibility remediation after launch costs more than building accessible components from week two.
• Customer-facing exports (CSV/PDF) with sane defaults — lawyers care, engineers underestimate.
• Observability: Sentry, structured logs, uptime checks — without them you are guessing in production.

Hourly vs fixed bid — how we actually work

Hourly is honest when nobody knows what they want yet. Fixed bid works once acceptance criteria exist — ideally written down after a paid discovery slice. We have eaten budget on unclear specs; now we insist on a discovery milestone before we commit the rest.

Blended rates for “Toronto PM + Dhaka engineering” land roughly $55–$85 CAD/hour all-in for senior-heavy teams at our shop — versus Toronto-only shops at roughly $140–$220 for comparable seniority. The gap is not magic; it is timezone orchestration and overhead you actually want (daily standups that do not require someone awake at 3 a.m.).

When we steer you away from Next.js

If you need a five-page brochure for $4k, WordPress or a static builder wins — fight me. If your core product is a giant pivot grid with sub-second updates across fifty thousand rows, we might keep Next for marketing but put the app shell elsewhere.

Pick the boring stack for the job; pick Next when you care about SEO + modern React + deployment ergonomics for the customer-facing surface.

Frequently asked questions