Choose the job before the platform

What must your visitors be able to do?

Start with the action a customer needs to take. A site that explains a service and invites an enquiry has a different job from a shop, booking system or customer portal. Map the functions first, then choose the right build.

A decision in four routes

Follow the action through.

The label on a website matters less than the work it has to perform. Follow the customer's next step to see what must exist behind the page.

Visitor needs toWebsite must supportBuild decision
01Ask a questionClear services, proof and an enquiry routeBusiness website
02Choose a timeAvailability, confirmations and changesBooking scope
03Buy onlineCheckout, stock, fulfilment and returnsCommerce platform
04Sign in and use a serviceAccounts, data and access rulesSoftware project

These are different requirements, not a ladder of quality. More functions create more operational work as well as more screens.

Make the boundary visible

Choose the smallest build that does the job.

A customer might read about a service before booking or buying. Decide whether the website itself must handle the transaction, or whether an existing specialist service already does that work.

01 / Explain and enquire

Make the decision easier.

Use service pages, real evidence, practical answers and a contact route when a person needs a conversation before buying. This is the core job of UpOnUp's standard business website.

02 / Schedule

Define the booking journey.

A link to an existing booking service and an on-site booking system are different tasks. Clarify who controls availability, reminders, payments and cancellations before agreeing the build.

03 / Sell

Plan the operation behind checkout.

Taking an occasional payment through an existing service differs from running a product catalogue and cart. Stock, delivery, taxes, returns and customer support all need owners.

04 / Give account access

Scope the software, not just the screens.

Logins, personal data, permissions or custom workflows make this an application. They need a separate product and technical plan.

UpOnUp's standard build covers planning, writing, original design and development for an agreed enquiry-led website of up to 30 pages. Ecommerce, bespoke software, large catalogues and complex integrations are outside that scope. Read the service terms before ordering.

A private working sheet

Turn your answers into a useful brief.

Choose the closest answer for each function. The mapper runs in your browser and sends nothing to UpOnUp. You can copy the result and use it with any provider.

01 / Main actionWhat must most visitors do?

02 / Required functionsWhat else must the site handle?

This is a planning aid, not a quote or an automatic technical assessment.

Keep planning

Set the scope before anyone starts building.

Once you know the main action and required functions, decide which pages earn a place, who supplies the facts, and how an existing domain or site will be handled.

Message the team