Website build
A Gilbert carpentry website, built and not yet launched
A one-man carpentry business in Gilbert needed a site that looked like the work. This one is built and running, with a nine-page structure, a project enquiry system and an appointment calendar. It is not on a public domain yet, and this page says so rather than implying otherwise.
- Client
- Tim Ness — custom carpentry, Gilbert AZ
- Work
- Design, custom WordPress theme, enquiry and appointment systems
- Built
- Nine page templates, custom theme by AZ Web Corp
- Status
- Complete, not yet on a public domain
Tim Ness Carpentry
01 — The brief
A tradesman's site has one job: prove the work is good
For a custom carpentry business, the website is not a brochure — it is the portfolio. A homeowner deciding between three quotes is looking for evidence that the person turning up can actually do the work, and photographs of finished projects do more of that persuading than any amount of copy about craftsmanship.
The structure was built around that: the work first, the explanation second, the request for a quote always one click away.
02 — What was built
A real site, not a landing page
The build is a custom WordPress theme written for this business, with each section of the site given its own template rather than being squeezed into a page builder.
- Nine page templates, each written for its job: home, about, services, portfolio, process, service areas, FAQ, contact and a 404.
- A portfolio built to carry the work, since photographs of completed projects are the single most persuasive thing on the site.
- A project enquiry form that stores submissions in the WordPress dashboard under Project Inquiries, so nothing depends on an email arriving.
- A phone appointment system under Phone Appointments, with an availability calendar covering Monday to Friday, four Arizona-time request slots per day, bookable up to 90 days ahead.
- A service-areas page, because carpentry work is local and the searches that matter name the town.
- Accessibility and responsive behaviour treated as part of the build, not retrofitted.
03 — Why it is not live
The blockers are real and they are not technical
The site is finished and running locally. It is not on a public domain, and the reasons are worth stating because they are the normal reasons a good build sits waiting.
The photography is still concept imagery. For a carpentry business this is the highest-value asset on the whole site, and stock photography of somebody else's work would be worse than launching late.
The service wording and the address need confirming by the client before they are published as fact.
Outgoing email needs connecting, so enquiry notifications arrive reliably rather than depending on a host mail path that may or may not exist.
A privacy policy needs publishing, since the site collects enquiries and appointment requests — that means personal data, and it needs a policy that describes what actually happens to it.
04 — What is claimed here
A build record, not a results record
This page documents a build. There are no traffic figures, no ranking claims and no conversion numbers on it, because the site is not public and nothing has been measured.
When it launches and there is a reporting period worth comparing, this page will be updated with what actually moved. Until then the honest description is: the site is built, the systems work, and it is waiting on assets and sign-off.
Page templates
9 increase
Each written for its own job
Enquiry capture
Stored increase
Dashboard, not email-dependent
Booking window
90 days increase
Four slots per weekday
Public status
Not live no change
Photography, copy and sign-off outstanding
Technologies used
- WordPress
- Custom theme
- PHP
- CSS
- JavaScript
Want results you can check?
Tell us what you are trying to fix and we will tell you honestly whether we can measure it.