Questions before commissioning website or software work

Can we start with a problem rather than a specification?

Yes. Describe who is trying to do something, what happens now and what you want to become possible. An organiser unable to explain an uncertain group size, a packer missing part of a delivery address or a team unable to distinguish completed work from a proposed return visit are useful starting examples.

A link to the current system and a sample with private details removed can help. The first discussion establishes what is known and what requires investigation; it does not require you to choose the implementation.

Do you work from New Zealand?

Faith Forge Labs is based in the United States and serves New Zealand organisations remotely. Agree meeting overlap, feedback routes and any support requirements before work begins. A project requiring attendance at a physical site needs that responsibility identified explicitly.

Check the relevant dates when arranging meetings. New Zealand and US clock changes mean that one fixed offset should not be carried through the year without verification.

Can we retain our existing software?

Often the useful project is a change around software the organisation already relies on. We examine the supported capabilities, access, condition and dependencies before proposing repair, configuration, integration or replacement.

For example, a booking provider may already support the required staff review, while the public page fails to explain the request properly. Conversely, clearer copy will not give a provider a field or permission it does not have. The assessment needs to distinguish those limitations.

Do you build separate service pages and improve the enquiry journey?

Yes, within an agreed website scope. We identify the different questions visitors need answered, the approved facts behind each offer and the information staff need next. Existing useful pages and saved links form part of the review.

A separate page should help with a distinct decision. A remote service available broadly does not need interchangeable pages for every town. A visit service may need genuine coverage and preparation information supplied by the business.

Can you support English and te reo Māori content?

The project can plan the required language journeys and their technical publishing needs. Your organisation supplies suitable language and cultural review, agreed for the work. Review should cover the finished task, including navigation, messages, captions or documents that a person actually uses.

The presence of translated content does not establish that project discussions, customer support or specialist advice are delivered in that language. Agree those responsibilities separately and make the public offer accurate.

Is a booking request the same as a confirmed place?

Only if the actual business process establishes that commitment. An initial request may contain alternatives or an approximate party size. Staff may need to assess capacity, clarify details and offer an arrangement before the customer can confirm.

We design the wording and states around the approved rule. A submitted form, a saved request and an accepted payment can establish different facts. The selected provider and the business's terms need to support the journey described to the customer.

What would you check in an online shop?

The scope can follow a selected product from its information page through ordering and staff fulfilment. We consider the accepted destination, delivery decisions, merchant-approved terms and the records the packing team receives.

For rural delivery, use the actual carrier's supported requirements and approved address information. Do not assume that an address suggestion proves service availability for every product. Payment-provider support, tax decisions and consumer information require their own confirmation by the merchant and appropriate advisers.

Can a customer portal separate different organisations?

That is a requirement to design and verify, not an automatic consequence of adding sign-in. A person may have an authorised relationship with more than one customer. Their available records and actions should follow the selected membership and the approved permissions.

We assess the specific tasks, provider capabilities and access model before recommending a portal. Use invented records while investigating those boundaries. Arrangements for personal information and suppliers need review before live records are introduced.

Can an app work without a connection?

Some tasks can be designed for local preparation or recording, depending on the device and technology. The scope must state which information is available, what is saved locally and what has reached the office. Pending changes need a defined treatment when the office record has also changed.

Test the intended equipment and actual task. A general statement about reception cannot establish that an app will work throughout a particular route. An installed application also brings distribution and maintenance responsibilities that a responsive website may not need.

How are cost and timing established?

Through the selected deliverables, current system condition, access, content, external dependencies, testing and handover. Where an important uncertainty would undermine an estimate, an initial assessment can establish a firmer basis.

A written scope should identify third-party charges and specialist responsibilities rather than implying they are included. New requirements discovered during a project need a decision about scope and priority. See scope and budget.

What happens after handover?

The agreed handover explains the operating tasks and ownership needed for the delivered system. Continuing support has its own scope, reporting arrangements and coverage. If a problem prevents work, the report should identify the failed task and relevant evidence rather than only saying the website is down.

We do not infer continuous emergency cover from a maintenance page. Discuss the consequence of an interruption and the people who can act during your working day.

What should stay out of an initial enquiry?

Passwords, payment details and private customer records. Explain the situation with anonymised or invented examples. If more sensitive material becomes necessary, agree an appropriate authorised review method first.

The contact page provides the enquiry form and email route. The site information page explains how this website handles enquiries and measurement.