How much should a website cost? An honest answer

Asking what a website costs without surfaces, integrations, and ownership rules is like asking what a building costs without floor plans. A five-page marketing site and a logged-in product shell are different products with different risk profiles.

mxstermind Studio quotes after discovery because established buyers need milestone maps, escrow options, and engineering proof — not a SKU in a cart. This article explains what moves price so you can self-qualify before /apply.

A website purchase is usually four bundled problems: positioning clarity, visual system, front-end engineering, and instrumentation for conversion. Cheap quotes often solve only one while hiding the others behind change orders.

Maintenance matters. Who updates copy? Who owns the repo? Who patches dependencies when Next.js ships security fixes? Studio handoff includes documentation so your team can operate — or we scope retainers when you want us to stay.

See /services for how brand, web, and growth lanes split. See /developers/tech-stack for how we reason about Next.js, export, and edge hosting on Cloudflare.

Focused marketing sites with approved copy, limited motion, and no auth commonly land mid four figures to low five figures USD after discovery — when timeline and revision rounds are bounded.

Combined brand system plus marketing site plus performance budget often starts mid five figures because strategy, design, and engineering run in parallel with sign-off gates.

Product surfaces with authentication, dashboards, API integration, or Web3 wallet flows scale higher. Public examples include /portfolio/crypto-trading-platform and /portfolio/sui-blockchain — complexity is visible in scope, not adjectives.

Enterprise procurement with compliance, multi-locale, and role-based CMS scales again. Those projects are quoted per milestone with explicit assumptions — not guessed in a blog footer.

Custom motion systems and scroll storytelling add review cycles. WebGL and heavy shaders add performance work most buyers only notice when Lighthouse scores tank.

Multi-role CMS, internationalization, and real-time data each add specialists. Web3 flows add wallet testing matrices and copy for failure states — see /developers/blockchain.

Rush timelines without scope cuts multiply cost. Emergency squads are possible — see our SUI case study post — but only with frozen requirements and executive sign-off in Discord.

Unbounded revisions destroy margin and quality. Studio quotes include defined revision rounds; extras are change orders with updated dates.

Frozen sitemap and approved long copy from your team reduce design iteration. Template-adjacent structure with custom tokens costs less than net-new interaction design — but must still match brand standards on /portfolio.

Single stakeholder sign-off beats committee reviews spread over six weeks. Escrow-friendly milestones do not add cost — they add clarity.

Bringing analytics access, Figma files, and API documentation upfront shortens discovery billed time.

Unlimited revisions, unlimited pages, or unlimited anything — someone pays eventually, usually you through delay. Hourly billing without cap on discovery — you fund learning on their side. No mention of who owns IP on final payment.

No live portfolio URLs matching the stack they propose. mxstermind publishes case studies with tags and timelines precisely so technical buyers can verify before deposit.

No escrow or milestone structure for five-figure work — risk is asymmetric. Our /ethics-standards page states financial rules publicly.

Intake happens on Discord or Telegram via /apply. You share link, outcome, budget range, timeline, escrow preference. We respond with fit and capacity — same day when slots exist.

Discovery produces a written brief: deliverables, milestones, price, assumptions. Sign-off before pixels. Execution updates weekly in-thread.

If scope is smaller than Studio minimums, we say so. Honesty saves both sides weeks.

Drain.cx demonstrates Figma-to-production with motion and FAQ structure. Cascade Markets demonstrates Web3 landing discipline. CarSpotLive demonstrates mobile delivery on the App Store.

Read /portfolio entries and link them in your intake. Quotes get sharper when we know which proof line matches your outcome.

Copywriting, legal review, translation, accessibility audit, SEO migration redirects, analytics implementation, email domain warmup, status page, on-call after launch. Each is a line item or an explicit exclusion.

mxstermind lists exclusions in the brief so you do not discover them at invoice time.

Greenfield is predictable when scope is frozen. Brownfield requires audit time — tech debt, test coverage, deploy pipeline. Audit may be Milestone 0 with separate fee.

Share repo access early if you want accuracy. NDA templates are fine before access.

Hosting on Cloudflare or Vercel is often modest compared to human maintenance. Budget for dependency updates, especially Next.js security releases.

Studio can train your team or stay on retainer — both are scoped, not implied free support forever.

If scope, timeline, and budget cannot all be true, we say which to relax. Pretending all three fit breeds failure. Honest agencies lose deals — and keep reputations.

Vendor onboarding, insurance, and security questionnaires add calendar time — not always cost. Mention them in intake so milestones do not assume day-one kickoff while legal reviews for three weeks.

Reference /ethics-standards in your vendor portal. Public rules speed security reviews that ask about data handling and delivery channels.

Website cost is a function of scope, risk, timeline, and who maintains after launch. mxstermind quotes after discovery with milestone maps — not shopping-cart pricing.

Send sitemap, integrations, budget range, and proof links on /apply. Compare /portfolio cases before you compare dollar figures.