An example journey, shaped around your requirements.
A practical decision guide
Plan the work with clearer questions.
Written by Softglimmer Services. Use this guide to prepare a brief and compare options against your actual requirements.
Start with the job the website must do
A business website can be a simple introduction, a detailed service catalogue, a project portfolio or an operational sales channel. Those jobs require different content, design and testing. Before comparing prices, write down the primary audience, their decision and the action that should follow. A clinic enquiry site and a multi-category store should not share the same estimate merely because both have a homepage.
Prepare a page inventory and mark which pages need a distinct layout. Ten pages built from two carefully designed templates may be less involved than five pages with different interactive journeys. Explain whether the team must write copy, organise old material, create illustrations or work with final approved content. These responsibilities belong in the proposal.
Separate design work from functionality
A quotation should explain how the visual direction is developed, how many key layouts are reviewed and how revisions are handled. It should also describe the functional work. Contact forms, product variants, customer accounts, document uploads, payment flows and CRM connections are separate requirements, even when the final interface looks simple.
For each feature, describe the starting event, the expected result and any exception. For example, an enquiry should be stored, routed to the correct team and acknowledged appropriately. Ask what happens when the notification fails. This turns an attractive feature list into a testable scope and makes competing proposals easier to compare.
Include content, migration and quality checks
Replacing an existing website adds work beyond building the new screens. Someone must inventory useful URLs, preserve approved content, identify redirects, transfer media and check forms and analytics. If organic traffic already matters, request a migration plan before changing the page structure.
Quality checks should cover realistic desktop and phone widths, keyboard access, readable text, image loading and the critical conversion path. Clarify which browsers are included and how launch issues are handled. Avoid assuming that a line called SEO includes ongoing content strategy, search monitoring or a guaranteed ranking. Ask for the specific deliverables.
The build fee is one part of ownership. Record hosting, domain renewal, platform subscriptions, extensions, licensed assets, support and future content work separately. Third-party services may have their own usage charges. Ask which accounts will be owned by your business and which costs are billed by the supplier.
Maintenance should describe responsibilities and response expectations. Updating content, repairing a broken integration and developing a new feature are different activities. A clear handover should include access, publishing guidance and a way to recover from a bad change. Compare the first year and a normal ongoing year using the same assumptions.
Compare like-for-like proposals
Create a short comparison with columns for page templates, content, features, integrations, migration, quality checks, ownership and support. Mark each line included, optional or excluded. Ask suppliers to explain ambiguous items before selecting the lowest headline price.
Softglimmer scopes work around the actual requirements rather than publishing a universal price for every business. Bring an existing website or a rough page plan, the systems you use and the content you already have. We can then discuss a focused first release and identify what should wait. A useful budget protects the essential visitor journey and gives later improvements a clear place.
Before you decide
Common questions.
Can I get an estimate before writing all the content?
Yes. A page inventory and examples can support an initial estimate. The proposal should state its assumptions about copy, media, revisions and functionality.
Does a higher price guarantee better search rankings?
No. Compare the quality and scope of the work. Rankings depend on many factors, and a website build alone cannot guarantee a position.
What should I send for a useful quotation?
Your objective, existing URL, expected pages, examples you like, required features, integrations and intended launch date.
Connected services
Build the right combination.
Start with the primary need, then connect the supporting work where it is useful.
