Key Takeaways
- Start from the buyer’s task, not the format. The task decides site, app, or both.
- Start with one format when you can. “Both” needs two scope sheets, not one bigger one.
- Included / excluded and a named sign-off turn a build request into a Final Product you can accept.
- Screens (UI and UX) sit inside the job. They are scoped lines, not a second pitch.
Decision table: site, app, or both
Read across. The column that matches most rows is your starting format.
| Question | Points to a website | Points to an app | Points to both |
|---|---|---|---|
| What must the buyer do? | Find you, understand the offer, enquire or book | Use a tool or service repeatedly after they sign up | Discover you on the web, then use a service day to day |
| How often do they come back? | Occasionally, when deciding | Often, as part of a routine | Both patterns exist, with different people or stages |
| Must people find it through search? | Yes, it needs public, crawlable pages | No, users arrive already knowing you | Public pages for discovery, the app for use |
| Do users need accounts or saved data? | No, or only a simple form | Yes, the job depends on it | Only inside the app part |
| Does it need phone features (camera, location, notifications, offline)? | No | Yes, and the job fails without them | Only for the app part |
| Who updates the content? | Your team, often, without a developer | Mostly the product itself, through data | Your team owns the site; the product owns the app |
| What does “done” mean first? | Pages live, forms working, tracking in place | One core flow working end to end for real users | Each part has its own done, signed separately |
If you cannot answer a row, that row is your first scope question, not a reason to build both.
One-page scope sheet
Fill one sheet per format. Empty lines mean there is no scope yet.
- Job in one sentence: What must be true when we stop? (Not “a modern website.”)
- Format: Site, app, or one part of “both”, taken from the table above.
- Primary user and task: Who uses it, and the one task they must complete.
- Pages or screens in scope: List them by name. Anything unlisted is not in scope.
- Content and data: Who supplies copy, images, and data, and by when.
- Integrations: Forms, booking, payments, CRM, analytics. Name each one or write “none.”
- Included: Design (UI and UX), build, launch, handover, and training. List only what you will pay for.
- Excluded: Other formats, marketing campaigns, a brand rewrite, unrelated internal workflows.
- Done looks like: What ships, where it lives, who accepts it, and when the job closes.
- Owners: One named person on your side and one on the supplier side who can change scope and accept “done.”
Why build requests go wrong
A build request usually fails before the first screen, because nobody chose the format against the buyer’s task. Teams ask for an app because a competitor has one, or for “both” because it sounds complete. The result is two half-scoped products and no clear done. That is the same naming problem we mapped in AI-native work vs common buyer pains: the pain shows up as a delivery problem, but it starts as a missing scope.
Start with the table. If the job is to be found, understood, and contacted, it is usually a site. If the job is repeated use with accounts and data, it is usually an app. Treat either as a Websites & Apps Development job with one scope sheet per format.
Screens are part of that job. Layout, flows, and how a form behaves are UI & UX Design lines on the same scope sheet, decided before build, not redesigned after launch.
If the real goal is more enquiries through ads or search, the site is only one line of that job. Write a Digital Marketing brief for the channel and KPI (see Brief a digital marketing job before you spend). If the real goal is to change one internal workflow, such as intake or reporting, that belongs under AI Integrations & Solutions, not inside a website rebuild.
Tools speed up the build. They don't set the scope.
The habit is the one in What an AI-native agency is, and how Voyuma works: people own the scope, the job is named, and then it ships as a Final Product. A page builder, a template, or a code tool can speed production inside a written perimeter. None of them decides the format or signs off done.
When you are weighing a freelancer, a tool, or a firm, the deciding question is still who owns the scope. See AI-native agency vs freelancers and tool stacks. Fill the table and the sheet before you choose the shape of help.
How Voyuma runs that model
We specialize in four services: Digital Marketing, Websites & Apps Development, UI & UX Design, and AI Integrations & Solutions. For a site or app, the path is the same on every job. We name the format, scope included and excluded, design the screens inside that scope, and ship to production. A named person owns the scope and the sign-off. Scoped, then shipped.