How Do I Organise Your Website Services to Guide Each Inquiry?
By Adrian Butnaru · Independent developer · Blanes (Girona), working remotely across Spain.
Published: · Last technical review:
To organise your website's services and guide each inquiry, I group the offering according to the visitor's problem—operations with a PWA, lead generation, or PHP maintenance—assign a clear page to each service, and link to the form preserving your explicit choice without blocking open questions.
Criteria: start with what your visitor needs to solve
To prepare the architecture, I would suggest writing down the inquiries you want to receive in the words of those making them. «I want to organise records», «I need a website to present my service», and «my existing application is failing» are editorial examples, not client testimonials. Afterwards, I would review whether they correspond to distinct services or to different ways of explaining the same project. I would not create a new page for every synonym.
On buangh, I distinguish operational web applications and PWAs, lead generation websites, and PHP maintenance or evolution. That separation stems from my published offering. It does not mean your business must copy those categories: I suggest identifying your own requirements and comparing them against what you actually offer. A service page should help recognise its scope, not force the visitor to interpret your internal organisation.
A table to avoid mixing destinations
| Need in my published offering | Planned editorial destination |
|---|---|
| Digitise workflows and records | Web applications and PWAs |
| Present services and receive inquiries | Lead generation websites |
| Maintain or evolve existing PHP | PHP maintenance |
The table explains the focus of my services; it does not calculate what you should commission. If you have a PHP tool and want to alter its operations, I would not take for granted that you need both maintenance and a new application at the same time. I would propose clarifying whether we are discussing the same tool. The choice must emerge from your context, not from a sales journey multiplying selected services.
What context I would preserve in the inquiry
When designing the journey between service pages and contact, I plan to preserve the service you explicitly select and the page you are inquiring from, always allowing you to change that selection in the form before submitting. Before applying this to your website, I would suggest agreeing on what data the person chooses, what is retained, and how they can correct it if they arrived from a page that does not describe their requirement.
Proposed editorial framework, neither a screenshot nor an implemented feature:
- Need: describe what the visitor wants to resolve.
- Service: explain the scope and offer an alternative if it does not fit.
- Explicit choice: allow selecting or changing the service.
- Inquiry with context: retain only the agreed context, without automatically attaching answers.
The article you arrive from helps contextualise the reading; it does not authorise inferring that you wish to hire that service. Nor would I use your answers to a self-assessment as content automatically attached to the contact form. I maintain that separation so that an informational reading or a prior self-assessment never transmits data without your express decision.
As a preparation sheet, I would note down the visible service name, a brief explanation, the link destination, and the information that would make the inquiry useful. I would propose reviewing the same sheet for anyone unsure of their choice. «I do not know yet» deserves an understandable pathway, not a blockage or an invented sales category. The contact form on buangh.com includes this service selector.
Proof of my own and the limits of that proof
I present aguacomplet.es as a website of my own designed and developed by me. I also present complet.digital as a website of my own that I developed. Those projects are examples of my work, not external clients or testimonials of improved lead capture. My website offering includes a landing page or website with a form, email confirmation, sequence, SEO, and configured analytics.
The homepage screenshot of complet.digital shows a website of my own developed by me with a distinct focus; the structure of pages and forms for your website is defined in writing according to your services. I would not use a homepage screenshot as proof of form implementation or its follow-up tracking.
When dividing the website further is NOT right for you
In web architecture terms, it is advisable to group the offering in a single view when options address the same problem and require the same preliminary clarifications. Separating them can be an editorial alternative, but I would not sell it as superior by default. The trade-off is reviewing whether each page contributes a distinct explanation or merely repeats the same offering under another title.
If requirements are different, I would propose separate destinations and links that allow comparing them. The trade-off is having to maintain consistent scope and contact details for each service. I would not promise more inquiries simply by adding pages. Nor would I turn navigation into a mandatory questionnaire: to explain your case, you should be able to state what you need even if you do not know the technical name of the service.
What I would leave out of the initial proposal
I would not include technical labels that your visitor does not need in order to choose, form fields whose utility you cannot explain, or automated decisions based solely on the page read. Nor would I present the editorial origin as proof of purchasing intent. I would propose distinguishing what you declare from what the site records as context, and reviewing both with concrete copy before programming.
How I would work on it with you
In my published process, I start with a written diagnosis and agree on deliverables, quote, and timeframe before development. Afterwards, I provide functional progress updates for you to test. Applied to this architecture, I would suggest first reviewing the requirements map and then a sample navigation path through to the inquiry. I do not claim that a rigid template exists for all sectors.
To prepare that review, note down what business inquiries you need to capture, what journey the form should follow, and whether it coexists with an already running PHP/MySQL application. I would propose bringing an example inquiry without personal data and checking together where it should arrive, what information would be useful to retain, and what does not need to be asked.
Review also the path for anyone picking the wrong service
I suggest writing an inquiry that arrives from a page different from the actual need. Could you change your choice without starting over? Would the form copy allow you to explain your case? Would editorial context be preserved as guidance or interpreted as a purchase? These are acceptance criteria to agree upon, not demonstrated features. Reviewing them alongside the primary journey ensures the document accommodates doubts and shifts in intent, rather than designing solely for those who already know the correct label in advance.
Frequently asked questions
What destination corresponds to each requirement?
In my offering, organising workflows points to web applications/PWAs, capturing inquiries to lead generation websites, and maintaining an existing PHP tool to maintenance. I do not transfer that classification automatically to your business. I suggest describing the requirement before choosing a destination and retaining the ability to explain it when no label fits clearly.
What context should the form preserve?
In an inquiry-oriented architecture, the form should retain the service you explicitly select and the page you arrive from, while always allowing you to change that option or choose another general inquiry. Answers from a prior self-assessment must not be sent automatically without your decision.