You do not need to know the name of the solution, and you do not need to have every piece already. Choose the question you recognise: below it are the concrete situations it leads to.
01 / This is where you enter
Something is not working
The site is there, the tools are too. One step breaks.
Enquiries arrive and are lost between one step and the next: few useful questions, customers who do not find you, contacts with no follow-up, work done by hand every day. That is where you start, not from a category.
Does the visitor understand what you offer, and find a clear next step? Start from the journey: message, service pages, form and confirmation. If the tracking is reliable, it shows where people stop.
Are you missing relevant visits, or clear information about what you offer? Check the first scan, your pages and the questions your customers ask. For a local business the consistency of locations and contacts matters too; for AI answers you need verifiable information.
Does every contact have an owner and a next action? Rebuild how enquiries arrive, how they are assigned and how they are answered. Connect the CRM only after you have defined what happens to a normal, an incomplete or a duplicate enquiry.
Which repetitive step has a recognisable input and a recognisable result? Choose one frequent, bounded activity. Define rules, exceptions and an owner; consider AI to interpret information when a simple rule is not enough.
The site is missing, or the booking flow, or the CRM.
Here the question is not what to connect but what to build. You start from the journey that has to work, not from the tool: a site with its content, a booking or enquiry flow, the tool that holds your contacts. You decide the order, and what already exists gets connected.
These are the pages that describe how each piece is designed and put into production, with the evidence that makes it verifiable. One of the three is enough.
The situations listed here are the ones this site describes in detail, and each one leads to a capability: they are not a choice you have to make at the door, they are the body of the page. The second door has no list: where a piece is missing, it is built. If neither of them seems like yours, describing it in the brief is the right way to begin.
Check first
Look at the structure.
The audit reads the titles, metadata, hierarchy and basic signals of any public URL. It is free: no account, no payment, no form. It is a technical starting point, to be read together with your content.
Focus the first intervention on the point that blocks the journey. In the brief you can describe the dependencies and say what you want to take on afterwards.
For those who want their web presence at its best.
Businesses, professionals, projects: the service is for anyone who has a web presence — a site, searches, contacts, manual work around all of it — and wants it to work well. The three situations below are recognisable examples, described in the pages of this site: they are not the boundary of what we do. If yours is not among them, describe it in the brief: the starting point is the problem, not the sector. None of the three assumes that you already have every piece: where a piece is missing, it is produced.
A catalogue with orders and availability, a shop that has to hold the checkout: Ecommerce. A complex offer that has to become understandable before the first consultation: Professional services. Ads on several channels and visits that have to be assigned: Real estate. Availability, evidence and appointments: Automotive. A hypothesis to test before building: Startup. These are pages already written here, not a list of clients and not a boundary: they describe contexts, not the limits of the service.