Walker Home Pros: from request to report

How a request on the Walker Home Pros website becomes a booked, confirmed home inspection, and how the report reaches the client.

Client
Walker Home Pros, a home inspection business in the Sacramento area, run by Matt Walker
What we built
The website and its request form, and Walker Inspector, a phone app for booking, inspecting and sending reports
Also in the project
Logo, favicon and a print kit

Homeowners and buyers ask for an inspection on the website. Matt books the job in his phone app, the customer confirms online, and Matt inspects the house and sends the report from the same app. Both tools run on the business’s own WordPress website, so there’s nothing to download from an app store.

Below, one sample customer goes from the request through booking and confirmation. A finished sample inspection then shows the report.

How it works

The screenshots come from a private demo copy of the site and app. The customers, agents, email addresses, phone numbers and addresses in them are made up, and the inspection photos are drawings. A test mailbox caught every email, so none were sent.

Step 1: A homeowner asks for an inspection

Who: the buyer or homeowner, on the Walker Home Pros website.

  • They tap Request an inspection. A short form opens over the page in two steps: the property first, then their name, email and phone.
  • The form says plainly that sending it doesn’t book an appointment. Matt confirms the details himself.
  • They see “Request received” without leaving the page.

What happens automatically

  • The website saves the request first, privately, so it isn’t lost if an email fails.
  • Then it emails Matt the details.
  • A spam check screens each request. A doubtful one is still saved and marked for Matt to check.
Request an inspection form on a phone, step 1 of 2, filled in: service, county, property type, approximate size, address and a message about the property.
Step 1 of the form: county, property type, approximate size, address and a message for Matt. Demo copy, so the form shows a test-mode note. Names and addresses are made up.
Step 2 of the request form on a phone: name, email, phone and a consent checkbox, with a note under the submit button that the request does not book an appointment.
Step 2: contact details and consent. The note under the button says the request doesn’t book an appointment. Demo data. Names and addresses are made up.

Step 2: Matt sees the new request

Who: Matt, on his phone or computer.

  • Matt signs in to Walker Inspector. It runs in the phone’s browser, and he adds it to his iPhone Home Screen like any other app. “Remember Me” keeps his phone signed in for 30 days.
  • New requests appear on the app’s Requests tab with a count, and on the Home screen under Website requests.
  • Each card shows the property, size, contact details and the customer’s message, with two buttons: Schedule and Start inspection.
  • The same requests are also listed in WordPress.
The inspection app's Requests tab on a phone. New website requests show the address, county, property type, size, contact details and the customer's message, each with Schedule and Start inspection buttons.
New website requests on the app’s Requests tab, each ready to schedule. Demo data. Names and addresses are made up.

Step 3: Matt books the appointment

Who: Matt, in the app.

  • He taps Schedule on the request. The appointment form fills itself in from the request: name, email, phone, address, county, property type and size.
  • The app suggests a length based on the home’s size, and copies the customer’s message into Matt’s private notes.
  • Matt picks the date and time. He can add the buyer’s agent and a note for the email. If the time overlaps another job, the app warns him.
  • He taps Save & send confirmation.

What happens automatically

  • The buyer gets a “Please confirm your home inspection” email with a Confirm appointment button. The agent gets it too if Matt ticks “Send to the agent too”.
  • The appointment shows Waiting for customer.
  • A history on the appointment records each step with the time.
New appointment form on a phone, already filled in from the request: date, start time, length, customer name, email and phone, address, county, property type and size.
The appointment form, filled in from the request. Matt sets the date and time. Demo data. Names and addresses are made up.
The saved appointment on a phone, marked Waiting for customer, with Call, Text, Directions and Start inspection buttons and a message saying the confirmation was sent to the buyer and the agent.
Saved and sent. The appointment shows Waiting for customer, and a message confirms the email went to the buyer and the agent. Demo data. Names and addresses are made up.

Step 4: The customer confirms

Who: the buyer or their agent. Either one can confirm.

  • The email shows the time, address, inspector and Matt’s note, with a Confirm appointment button.
  • The button opens a private page for that appointment. It asks who is confirming, who will let the inspector in, whether the utilities will be on, whether they’ll attend, and anything else Matt should know.
  • The page asks people not to type lockbox or gate codes. They share those with Matt by phone.
  • After confirming, they see “You’re all set”, with links to add the appointment to Apple, Outlook or Google Calendar.
  • If the time doesn’t work, they tap “This time doesn’t work for me” and suggest better times. Matt gets an email, and his Reschedule button sends a new time to confirm.

What happens automatically

  • The buyer and agent get a “You’re all set” email with the calendar links.
  • Matt gets a short email with who confirmed and their answers.
  • The appointment changes to Confirmed.
The customer's confirmation page on a phone: who is confirming, who will let the inspector in, whether the utilities will be on, whether they plan to attend, a notes box that asks people not to enter lockbox or gate codes, a Confirm appointment button and a link for when the time does not work.
The questions on the customer’s confirmation page, answered, with Confirm appointment and the link for a time that doesn’t work. Demo data. Names and addresses are made up.
The short email the owner gets after a customer confirms: who confirmed, the time and address, who will let the inspector in, whether the utilities are on, whether they will attend, and their notes.
The short email Matt gets once the customer confirms, with their answers. Demo data, caught by a test mailbox. Names and addresses are made up.

Step 5: The job is on Matt’s schedule

Who: Matt, in the app.

  • The confirmed appointment shows the customer’s answers at the top, with buttons to Call, Text, get Directions and Start inspection.
  • The Schedule tab has a month calendar, the selected day’s jobs and a Coming up list, each with its status.
  • Each job has an Assigned to button, so Matt can hand a job to another inspector on his team.

What happens automatically

  • The day before a confirmed inspection, the customer gets a reminder email.
  • An inspector gets an email when a job is assigned to them, moved or cancelled.
  • Inspectors on the team see only their own jobs. They can fill out reports, and Matt sends them.
The confirmed appointment in the app, marked Confirmed and assigned to the owner, with Call, Text, Directions and Start inspection buttons and the customer's answers about access, utilities, attending and notes.
The confirmed appointment, with the customer’s answers at the top. Demo data. Names and addresses are made up.
The app's Schedule tab on a phone: a month calendar with dots on booked days, the day's two confirmed inspections, and a Coming up list with one appointment waiting for the customer and one confirmed.
The Schedule tab: the month, the day’s jobs and what’s coming up, each with its status. Demo data. Names and addresses are made up.

Step 6: Matt inspects the house on his phone

Who: Matt, at the house.

  • From the appointment, he taps Start inspection. The report starts with the customer, agent, address and time filled in.
  • Conditions on the day, such as who attended and the weather, are quick taps.
  • The report follows Matt’s own template, with 10 sections from Roofing to Appliances. Each item gets one tap: IN (inspected), NI (not inspected), NP (not present) or RR (repair or replace). “Mark all as IN” handles the routine items.
  • Matt picks from his standard comments or types his own. “Save as my comment” keeps new wording for next time.
  • He adds photos from the camera or photo library, then draws arrows, boxes and circles to point out the problem.

What happens automatically

  • Every tap is saved on the phone and uploaded in the background. A check mark at the top shows when everything is saved.
  • With no signal, the work waits on the phone and uploads later.
  • The phone shrinks each photo before saving it.
One inspection item on a phone, marked RR for repair or replace, with a standard comment about the water heater's seismic straps, a photo marked up with arrows and a box, Camera and Add photos buttons, and Save as my comment.
One item marked RR (repair or replace), with a standard comment and a photo Matt marked up with arrows and a box. Demo data. The photos are drawings.

Step 7: Matt reviews and sends the report

Who: Matt, when the report is done, often the same day.

  • Review & send shows how many items are marked, how many need repair, and how many photos there are.
  • It warns about anything missing, such as unmarked items, no client email or no cover photo.
  • Matt can preview the web report and the PDF. He chooses who gets it (the client, the agent, a copy to himself), adds a note if he likes, and taps Send report.

What happens automatically

  • Each person gets an email with a link to the report and a link to the PDF.
  • The app records when the report was sent and to whom.
  • The report link starts working when Matt sends it. The link is long and hard to guess, and search engines are told not to list it.
  • An inspector on the team taps Submit for review instead, and Matt gets an email.
Review and send screen on a phone: 62 of 62 items marked, 5 for repair or replace, 5 photos, Preview report and Preview PDF buttons, checkboxes for the client, the agent and a copy to the inspector, a note box and a Send report button.
Review & send: every item marked, the repair and photo counts, and who will get the report. Demo data. Names and addresses are made up.

Step 8: The client reads the report

Who: the client and their agent, on a phone or computer.

  • The web report has the cover photo, the inspection details, and a section for each part of the house with Matt’s comments and marked-up photos.
  • At the end, a Summary gathers every item marked Repair or Replace in one place.
  • The PDF is the same report as a branded, page-numbered file. The website builds it on its own server.
A section of the client's web report: the electrical system table with each item marked IN, NI, NP or RR, two rows highlighted for repair, and a comment with a marked-up photo of the electrical panel.
A section of the web report on a computer: the item table, Matt’s comment and the marked-up photo. Demo report. The photos are drawings.

What we built

  • A custom WordPress theme, with pages the owner can edit in the normal editor.
  • A request form that saves every request in WordPress before it sends the email, with spam protection.
  • Service-area pages for the towns it serves, and a booking page for the booking link on its Google listing.
  • Walker Inspector, a phone app that runs in the browser and can be added to the home screen, with website requests and appointments in the same place.
  • Booking with a customer confirmation page, calendar links and reminder emails.
  • Home inspection reports with photos and markup, sent to the client as a web page and a PDF.
  • Logo, favicon, and a print kit with the logo in each color and a business card design.

Results

These come from the website. We list results only where we measured them.

  • Homepage on a phone with a slow network: main content about 2.6 s, down from 5.7 s. Page size 571 KB, down from 1,033 KB.
  • Accessibility: axe, an automated accessibility checker, found one issue before our speed and accessibility work and 0 after, including with the request form open.

Other case study: JPG Insurance, AI chat with live agents
All our work

Tell us what you're working on.

A website chat, a network you're unsure about, or a task that eats your week.

Book a call

Book a call

Let's set up a call

Two quick steps: what you need, then how to reach you.

Fields marked with an asterisk are required.

Please don't send passwords or access details through this form. We'll ask for what we need over a secure channel.

This site is protected by reCAPTCHA and the Google Privacy Policy (opens in a new tab) and Terms of Service (opens in a new tab) apply.

Sending this doesn't start any work. We'll reply to set up a call.