Pages and content
A few service pages need a different scope from a large catalogue. Existing copy, photography and brand assets also affect how much preparation is needed.
Small websites and complex software projects need different amounts of work. I'll look at your requirements and provide a written quote explaining what's included.
For businesses needing a professional new site or redesign. Pricing depends on pages, functionality, content and integrations.
Request an accurate quote ↗Scoped individually to reflect the features, database, security, testing, integrations and support required.
Discuss requirements ↗Managed hosting, backups, maintenance and support can be packaged with clear monthly or annual terms.
Explore hosting ↗The most useful starting point is what your business needs the project to do. These four areas help turn an idea into a scope that can be quoted.
A few service pages need a different scope from a large catalogue. Existing copy, photography and brand assets also affect how much preparation is needed.
Bookings, payments, accounts and online ordering introduce workflows that need to be designed, connected and tested.
Moving content or records, connecting software and keeping an existing service running can add work beyond the visible screens.
Hosting, licences, updates, backups and content changes need their own allowances. Ask which costs are recurring and which are optional.
A useful proposal makes it clear what you receive, what you need to supply and what happens after launch.
Use the checklist when comparing options, including proposals from other providers.
Read the website quote checklist ↗Clear answers to help you prepare, even if this is your first website or software project.
Start with the outcome you need, who will use the site or system, and one example of how it should work. The Project Builder helps organise that information. A reliable quote still needs an agreed scope; a questionnaire submission is not a fixed-price offer.
Bring a rough page list, your existing website address if you have one, any available logo and content, and the main action visitors should take. Mention bookings, payments or connections to other software early. It is fine to mark uncertain items as “not sure”.
A useful first step is to separate what the business needs at launch from what can wait. Staging can make sense when the first release works independently. Dependencies, later changes and the cost of each stage should be discussed before choosing that approach.
That depends on the agreed proposal. Ask for hosting, domain renewals, software licences, payment-provider fees and ongoing support to be identified separately, including who pays each provider. Do not assume an initial development price covers these costs.
Describe the change and ask how it affects the agreed scope, price and delivery plan before proceeding. A proposal should explain the process for reviewing and approving additional work.
Timing depends on the scope, content readiness, integrations and review availability. Bring any real deadline to the first discussion so the necessary work can be assessed against it. A delivery date needs to be agreed for the specific project.
You can review your answers and download a summary before submitting. No technical vocabulary required.
Choose Quick Quote in the Project Builder to describe the service you need, your main goal and how to contact you.
Start a short enquiry ↗The Detailed Builder adds questions about existing systems, features, budget, timing and priorities.
Build a detailed brief ↗It can be a simple website or something quite specific to your business. Start with the basics and I'll help work out the details.