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.
Choose the job before the platform
What type of website does your business need?
What should someone be able to do when they reach your website? They might need to understand a service and ask a question, or they might need to book, pay or sign in. Work that out first, because it makes a real difference to what needs building.
A decision in four routes
Follow the action through.
Picture someone using the site from start to finish. If they choose a time, something needs to check availability and confirm the booking. If they buy a product, someone needs to handle the order. Following that action through tells you what the website and the business need to support.
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
A straightforward enquiry website may be exactly what the business needs. Extra functions are useful when customers need them, but they also bring work to manage after launch.
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.
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.
Use the booking handover guide to turn those decisions into a brief and a set of launch checks.
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.
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 25 pages. Ecommerce, bespoke software, large catalogues and complex integrations are outside that scope. Read the service terms before ordering.
Launching a venture? Our startup website scope separates the public marketing website from product software and features that require visitors to sign in.
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.
Your working result
Requirements to take forward
Next step
Keep planning
Set the scope before anyone starts building.
Once you know what visitors need to do, you can plan the pages that help them get there. Agree who will supply the business details and, if you already have a website, what needs to happen to its content and domain.