# Whisper — what to ask Chad, and why it is Chad and not Larry

*For Ken. Written 2026-08-17. There is a copy-and-paste message at the bottom.*

**The short version:** we do not need Larry White to start. **Chad can answer most
of this himself, today, with four screenshots** — and those screenshots tell us
whether this is an afternoon's work or a fortnight's, before anybody books a call.

---

## Where this stands

Chad wants to introduce you to **Larry White at Whisper Computer Solutions** —
inspection software, Texas-only report, *"tons of home inspectors have him."* The
job is to make our booking pre-fill the inspection report: client name, property
address, age of the home, the rest.

**We already hold nearly all of it.** Every booking captures, in a structured
record: client name, phone, email · property address, square feet, year built,
foundation, occupancy, utilities on, pool/spa, MLS number · access notes and
lockbox code · the package, the add-ons, the price · the referring agent. That is
a report header already.

**What is missing is entirely on Whisper's side**, and it is one question: *does
Whisper accept data in, and how.*

---

## Why ask Chad first

Because the two things that decide the whole job are visible **inside Chad's own
Whisper account**, and he can photograph them in five minutes:

1. **The "new job" screen.** The fields Whisper asks for when he creates a job
   are, by definition, the fields we would have to fill. That is the mapping,
   without a single conversation.
2. **The settings / integrations page.** If there is an API key, a webhook URL or
   an import button on it, the answer to the hard question is already yes and we
   can be specific with Larry instead of general.

If those two show a way in, the call with Larry becomes *"here is what we want to
send, is this the right endpoint"* — fifteen minutes. If they show nothing, we
know before we spend anybody's time that this needs him to build something, and
that is a different conversation with a different timescale.

⚠️ **And one thing only Chad can tell us:** whether he is retyping the same job
into two systems today. If he is, that is the actual product — the time saved is
the pitch, and it is worth knowing how much of it there is before we build it.

---

## Copy and paste to Chad

> Hey Chad — quick one on Whisper, and it'll save Larry's time as much as ours.
>
> Before we set up the call with him, could you send me four screenshots from
> your own Whisper account?
>
> 1. **The screen where you create a new job** — the one with all the blank
>    fields you fill in. I want to see exactly what it asks for.
> 2. **Your settings or integrations page** — whatever Whisper calls it. I'm
>    looking for anything that mentions an API, a key, a webhook, or importing.
> 3. **The top of a finished report** — just the header with the property and
>    client details, nothing confidential below it.
> 4. **The job list / dashboard**, so I can see how a job moves through.
>
> And three questions, whenever you get a minute:
>
> - **When you book a job today, do you type the details into Whisper as well as
>   into ISN?** If so, roughly how long does that take you per job?
> - **Does anything pre-fill for you today**, from ISN or anywhere else?
> - **Is Larry the right person for the technical side**, or does he have someone
>   who handles that?
>
> That's it. If the screenshots show a way in, the call with Larry will be short
> and specific rather than us both feeling our way through it.

---

## Then, and only then — what to ask Larry

Unchanged from what I sent earlier, in this order:

1. Do you have an API or a webhook that creates a job, or pre-fills a report,
   from outside Whisper?
2. If not, do you support a file import — CSV or otherwise — for a new job?
3. What are the required fields, and what do you call them?
4. Is it per-inspector credentials, or one integration key for a company?

⚠️ **Question 4 is the one that decides whether this scales.** Per-inspector
credentials means every client we onboard has to go and get their own from
Larry — that is a step in the White Glove setup and it belongs on the checklist.
One company key means we wire it once.

---

## What I would tell Ken

**Nothing is blocked and nothing is being built yet.** The next move costs Chad
five minutes and costs us nothing. Ask him for the screenshots before the
introduction, not after — the call with Larry is worth far more when we already
know what his software looks like from the inside.

You also asked whether to put the same question to **ISN and Spectora** — *"does
ISN pre-fill my inspection report, and how."* Worth doing, and it tells us the
shape Whisper has most likely copied. **But they are not the same job:** ISN and
Spectora are a scheduler pre-filling their *own* report writer. We would be a
scheduler pre-filling **somebody else's**, which is the harder version and depends
entirely on what Larry exposes.

*Estimate, honestly: I cannot give you one until those screenshots exist. Anything
I said now would be invented.*