Before you start
A coding or chat assistant and a fictional service brief with verified or explicitly sample details.
Why this lesson exists
This lab adapts the “Turn a Local Service Into a Trust-First Website” project write-up into a practice build. The time is an estimated first session, not a promise to finish a production system. Use the public repository as a reference when available; the exercise can be built with original sample content.
Do the exercise
Define the practice version
List what is included, what is excluded, the service area and the next step. Keep sample testimonials and invented credentials out.
Build step 1
List every service and define what is included.
Build step 2
Publish starting prices with honest qualifiers.
Build step 3
Photograph the process, not only the finished result.
Build step 4
Build a short quote form with the minimum useful fields.
Build step 5
Add real phone, email, hours, licenses, and service areas.
Build step 6
Test every claim and placeholder before launch.
Run the experiment
Trace every factual claim to the brief. Use a phone preview to find contact details, inspect price qualifiers and test the quote or contact destination.
A prompt to adapt
Replace the bracketed parts with your own practice details.
Work in a disposable practice project. Explain any setup requirements before changing files. Build one small step at a time and show how I can check it. Audit this local-service website for trust. Flag unsupported claims, fake-looking statistics, unclear prices, weak service boundaries, missing contact information, and anything that could mislead a customer. Return fixes ranked by risk. Turn these technician notes into a plain-English service page. Explain the problem, inspection, work performed, what is included, starting price, safety limitations, and when the customer should call a specialist. My first-version boundary: List what is included, what is excluded, the service area and the next step. Keep sample testimonials and invented credentials out.
Run this experiment
Trace every factual claim to the brief. Use a phone preview to find contact details, inspect price qualifiers and test the quote or contact destination.
Check your result
Use evidence from your output. A confident explanation from the AI is not enough.
- Service scope and exclusions are explicit.
- Claims are verified or removed.
- The contact route works on a phone.
If it isn’t working
If a form has no delivery backend, label it as a prototype or replace it with a working contact link. A success animation is not proof a message was delivered.
Optional. Progress stays in this browser.
Where this came from
Public project repository ↗. The practice lesson is an adaptation, not a verbatim transcript. About the sources.
Prepared September 2026. Tools and interfaces change; use current official setup instructions. Session lengths are estimates.