A website quote is only as useful as the brief behind it. Colours, a logo and a reference site explain the look. The things that set the scope are elsewhere: pages, content editing, forms, integrations, ownership and support after launch. If you are looking for custom website development, this is the brief I would want to receive for a Next.js site, with a worked example you can adapt.
First decide: website or application
Start with what visitors need to do. Reading service pages and sending an enquiry is a marketing website. Managing records, making bookings, processing transactions or following business rules adds application work.
A login is a useful clue, but it is not the only test. A public booking tool or calculator can still need application logic. A customer account with invoices and private documents adds permissions, data storage and more testing than a contact form.
Name these features separately in the brief. A website with an invoice portal is two connected pieces of work. Sometimes the portal can be a link to a tool you already use. If most of the project involves accounts and workflows, the MVP development service explains how I scope that work.
The example brief, section by section
This is an illustrative example, not a client project. Harbour Accounts is a two-office accountancy practice replacing its old website.
1. Goal and primary action. "Explain our bookkeeping, payroll and tax services, and help suitable visitors book a call." The primary action is booking a call; the secondary action is sending a message. That gives the homepage a purpose beyond looking newer. Search visibility can be a goal, but rankings should not be promised as a development deliverable.
2. Pages, with the job of each. Home; four service pages; about and team; pricing; resources; contact; privacy; terms. That is eleven initial pages, plus individual articles later. Mark what already exists, who supplies new copy and which old URLs need redirects. A service page using an existing layout is different work from a page with its own interactive tool.
3. Content and who edits it. List what staff need to change without a developer: team members, opening hours, prices and articles. Those items need an agreed editing route, such as a content management system. Markdown files may suit a technical owner, but are not automatically a convenient staff interface. Confirm who writes the initial content and when it will be ready.
4. Responsive behaviour and accessibility. Include phone and desktop use, keyboard navigation, readable text, labelled forms and useful error messages. For Harbour Accounts, tap-to-call and a usable booking form matter on mobile. Downloadable guides should remain accessible there too. Identify any device-specific requirements rather than assuming a desktop feature can simply disappear on a phone.
5. Lead forms and routing. Specify fields, destination, visitor confirmation and spam handling. Does a submission go to an inbox, a CRM or both? What happens if delivery fails? Agree which successful actions to measure, such as completed enquiries or bookings. A visit to the contact page alone is not a lead.
6. Integrations. List the booking tool, CRM, newsletter platform, analytics and any payment or e-commerce connection. Say which accounts already exist and who administers them. A hosted checkout link for a deposit is a smaller job than building a shop with inventory, shipping and order management. Keep those scopes separate.
7. Ownership and deployment. Agree ownership of the custom code and content in writing, including any third-party licences. Put the repository, hosting and domain accounts under your control, with developer access granted separately. Ask for a staging link, a deployment procedure and a record of the services the site depends on.
8. Maintenance. Define launch support, future content changes, dependency updates and how problems are reported. A hand-coded website still needs upkeep. Decide whether staff handle content, a developer handles changes as requested, or you want an ongoing support arrangement. Keep service subscriptions separate from the development quote.
The scope ladder: from landing page to SaaS
These are different kinds of projects I can discuss and scope, not a claim that every type below is a completed client engagement.
- Landing page: one main offer and action, with the content needed to support it. Navigation depends on the campaign. See business website, landing page or both for that decision.
- Business or service website: service pages, company information, enquiry forms and perhaps articles. The Clinical Stack product site is a relevant example of explaining a product and helping visitors take the next step.
- Portfolio website: work items, case studies and contact options. This portfolio is built in Next.js.
- Content or blog website: articles, categories, an editing workflow and feeds where needed. Reasy's public site includes rental articles in three languages.
- Directory: listings, search and filters. Submissions, moderation or paid listings introduce application workflows.
- Property or rental platform: listings, owner accounts, enquiries and potentially availability or payments. Reasy is related rental-marketplace experience, delivered as a mobile app with a public website and web admin.
- Marketplace website: two sides of a transaction, with their own accounts, rules and administration. Describe each side's journey separately.
- Customer-facing SaaS: accounts, billing, permissions and working product screens. Clinical Stack is a delivered example. Its public marketing pages are only one part of the product.
When an existing tool is enough
A small information site with a contact form may be well served by an existing website builder. If your only immediate requirement is appointment booking, a hosted scheduling page may cover the first release. The comparison should include editing, subscriptions, support and future requirements, not only the build price.
A Next.js website can make sense when you need custom interactions, close integration with a product, a particular content architecture or control over the code. Multilingual content and performance goals belong in that discussion, but Next.js does not automatically make a website fast or improve its rankings. Those outcomes depend on implementation and content.
Two relevant projects and my contribution
Clinical Stack is a scheduling product for clinics that I migrated from Bubble to Next.js and Supabase. Its public site explains the products, shows demo videos, lists pricing and provides about, contact and privacy pages. It is an example of marketing pages supporting a working application, rather than being the whole deliverable.
Reasy is a rental-matching product with a public website in English, Hebrew and Russian. The Hebrew version includes a right-to-left layout. The site carries about, articles and contact pages, alongside the app and administration work. My contribution included the multilingual implementation. I am citing it for that work, not claiming that its website uses Next.js or that I owned the visual design.
What I need to quote your site
Send the goal, your current website if you have one, the essential workflow and your desired timeline. Include the content staff need to edit and any systems the site must connect to. I can then propose a page list, identify application features and explain a sensible first release.
Use the contact page to share your brief, or see business website development for the service details.