Website Enquiry Journeys for Small Businesses in Australia: Questions to Ask Before Signing a Contract

A website enquiry journey begins when someone tries to understand your service and ends when your team receives enough information to respond. Before signing a website contract, make sure the proposed work covers that whole journey. A redesigned page will not solve an enquiry form that loses submissions or sends them to an inbox nobody monitors.

Use this checklist to turn a proposal into clear questions for the provider. The aim is to agree on working behaviour, responsibilities and evidence of completion. Contract wording, intellectual property and privacy obligations may need professional advice specific to your business.

Check the customer’s task

  • Which customer is the enquiry page intended to help?
  • What should that person understand before contacting you?
  • Which action should they take, and what alternatives are available?
  • What information does your team genuinely need to give a first response?

Business.gov.au’s website setup guide recommends defining goals and organising pages around customers’ tasks. Apply that principle to a specific enquiry, such as asking whether you service a location. Ask the supplier to show the path from the relevant service page to the form and its confirmation message.

Clarify whether writing the page content is included. A design proposal may assume your business supplies finished text, photographs and service descriptions. Establish who checks those details and who approves them before the site is launched.

Check how a submission reaches your team

Ask where form information is stored, where notifications go and how failed delivery is detected. An email notification and a securely stored submission are different things. Confirm whether either is included, how access works and how long records remain available.

Agree who tests the receiving inbox and any connected customer management system. A successful message on the customer’s screen does not prove the business received the enquiry. The acceptance check should include retrieving the submitted test information at the destination your staff will actually use.

Check collection and privacy decisions

  • Why is each field needed, and can some be optional?
  • Could customers upload sensitive documents unnecessarily?
  • Which providers receive or store the information?
  • Who can view, export and remove submissions?
  • What privacy information must the customer see at collection?

Do not assume the same legal obligations apply to every small business. The OAIC’s small-business guidance explains that some small businesses are covered by the Privacy Act despite their size. Assess your circumstances and any other relevant obligations before approving how the form collects and handles information.

Keep testing data fictional and clearly marked. Do not send real customer files to demonstrate an upload feature. If a third-party tool is proposed, ask about its data handling and ongoing costs before agreeing that it forms part of the enquiry journey.

Check access and error handling

Ask how the provider will test the page on a phone and with keyboard navigation. Request clear field labels, understandable error messages and a way to recover without entering everything again. A form should tell customers which information needs attention instead of simply refusing to submit.

Discuss what happens when an attachment is too large, a required field is missing or a connection fails. Include an alternative contact option where appropriate. Avoid a success message that promises an immediate reply unless your business can reliably provide one.

Check ownership and control

Ask who controls the domain registration, hosting, content management system and connected form accounts. Establish which business representative receives administrative access and how access will be transferred if the relationship ends. Record the account responsibilities without placing passwords in the public contract or project notes.

IP Australia’s guidance on ownership highlights the need for contracts to specify rights in material created by contractors. Ask which parts are assigned, licensed or dependent on third-party services. Paying an invoice should not be assumed to give you every right needed to modify or move the website.

Include a handover exercise in the proposal: a nominated staff member changes a contact detail, retrieves a test enquiry and identifies where to request support. This exposes missing permissions or undocumented steps while the supplier is still available. Ask for instructions that match the delivered system, rather than a generic manual covering features your contract does not include.

Check scope, completion and ongoing charges

  • List the pages, forms and integrations included in the quoted work.
  • Record content responsibilities and the number of review rounds.
  • Agree on test submissions and the evidence needed for acceptance.
  • Identify hosting, plugin, form-service and support renewals.
  • Document support response arrangements and the exit process.

Keep optional enhancements separate from the core enquiry function. If the supplier recommends analytics or automated follow-up, ask what decision it supports and whether it adds data or maintenance responsibilities. A simpler journey may be easier for your team to operate well.

Before signing, summarise the agreed result in ordinary language: a customer can find the service, submit an appropriate enquiry, understand what happens next and reach a monitored destination. If the proposal cannot explain how that result will be tested, resolve the uncertainty before treating the design as complete.