IN SHORT
Urgent help or a contract?Give each its own entrance.
A homeowner needs your actual availability; a business manager needs to understand the file and follow-up. We plan those as different website journeys, with verifiable certificates and a clear report structure. The illustrated logbook is not software or a real customer record.
A wasps’ nest and a business inspection ask different questions.
The residential route puts species, service area and calling first. The business route explains the contract, reporting and the client’s own responsibilities. Separate pages should give their own answer; search phrases in the diagram are examples, not measured demand or conversion results.
Show fields and update rhythm, not a customer’s file.
Explain what is recorded at reporting, inspection, treatment and aftercare: dates, technician, findings, actions and follow-up. Use anonymised examples without pretending they are a delivered portal. A login belongs in the header only if you already have a real customer system to link to.
Promise the agreed follow-up, not pests gone forever.
State the number of checks, return arrangements and what happens when the cause is structural. Keep prevention contracts separate from one-off treatment and list exclusions. The site explains the service you actually deliver, without inventing treatment results or an unconditional guarantee.
A monthly website built around the two enquiry routes.
Intake, a draft design and a page flowchart define the two entrances, reporting explanation and useful species pages, including work you do not perform and referrals. A complete website costs €75 per month and a webshop €150 per month, excluding VAT. Both have an initial fixed term of 24 months and can be cancelled monthly after that, without a new fixed term. There is no upfront build fee. Domain and email are paid by the client. Agree seasonal content updates and maintenance in advance. Any customer portal or reporting integration needs its own scope agreement.
What this presentation does and does not do
This describes a proposed website brief. No form, booking or integration runs here; the existing contact route remains available.
- Functionality verified in this layer
- No
- New form in this layer
- No
- Original route retained
- Yes
The next step