Choose a Foundation website when the problem is understanding
If customers mainly need services, menus, hours, directions, proof, and a clear contact or booking path, a focused information site may solve the problem.
Choose a connected website when the problem is coordination
If customers must move between the website and booking, forms, newsletters, catalogs, analytics, a POS, or another existing system, the work includes integration boundaries and failure states.
Consider a custom tool when the problem is workflow
If staff need roles, queues, statuses, approvals, business-specific calculations, or a tailored data view, the job is closer to an operational application.
A quick diagnostic
| Question | Likely direction |
|---|---|
| Do people mainly need to learn and contact? | Foundation website |
| Must the site connect supported third-party tools? | Connected website |
| Are there roles, permissions, queues, or custom states? | Custom tool |
| Will customer or regulated data be stored? | Higher-risk discovery before commitment |
| Is the workflow still vague? | Map it before choosing technology |
Start with the smallest honest system
A direct link to an existing booking tool may be better than a new booking platform. A well-structured spreadsheet may prove a workflow before a dashboard. Custom code is justified when the observed problem and ownership model support it—not because it sounds impressive.