Begin with the job the website must do.
A small brochure site, a portfolio with editable case studies and a store connected to inventory are different projects. Write down the customer journey and the essential actions first. This avoids comparing a basic build with a proposal that includes research, content, integrations and launch support.
What changes the build cost?
Unique templates often matter more than raw page count. Ten pages using one established template differ from ten individually designed experiences. Content migration, bespoke interactions, complex forms and external systems also affect effort.
- Number and complexity of page templates
- Copywriting, photography and asset preparation
- CMS, ecommerce and third-party integrations
- Accessibility, testing and migration requirements
- Training, documentation and support scope
Separate launch costs from running costs.
Hosting, domain renewal, platform subscriptions and maintenance continue after launch. Ask which accounts you own, which fees go to third parties and what ongoing support includes. A low initial quote can omit work your business will still need.
Make proposals comparable.
Ask for a list of deliverables, revision stages, content responsibilities and acceptance criteria. Confirm whether redirects, metadata, analytics configuration and mobile testing are included. Agree how changes outside the scope are estimated before the project starts.
Prepare a brief that produces a useful quote.
Share your existing website, the service you want to promote, examples of work, essential integrations and intended launch timing. You can include a budget you are comfortable discussing without needing a final specification. Buildron will use that context to define a suitable scope; no fixed packages are published here.
Written by Buildron. Project requirements vary; use this guide to prepare a brief, then agree the details for your business.