Field Product Manager · New York

How I would run one Blue pilot in the field.

“Discovery is easy. Coordination is hard. Commitments are harder still.”

The problem you are building around

This is not a note about an engineering seat. It is one page showing how I find the real problem, size the number that moves, and prove it cheaply. That is the muscle a field pilot actually runs on.


A field-discovery teardown

Residential home services, from first call to a booked pilot.

The vertical is a deliberate composite, drawn from a real small-business pattern. The point is not HVAC. It is the method, and every number below is a hypothesis to be tested in the pilot, not a claim.

01 The business

A six-technician HVAC company in North Jersey.

Owner-operated. Roughly forty inbound leads a week from calls, web forms, and Google Business Profile. Peak demand lands on the hottest and coldest days, exactly when the office cannot pick up every call.

02 The request · surface

“I want an AI receptionist that answers the phone.”

03 The problem underneath · discovery

He is not short on calls. He is losing the calls he already gets.

On peak days and after hours, a large share of inbound leads hit voicemail, and a homeowner with no heat calls the next company on the list. The bottleneck is speed-to-lead, not headcount. An AI receptionist is the request. Recovered revenue from unanswered demand is the job.

04 Signal or one-off

I would not build off one owner's complaint. I would call three more shops in the same trade and ask two questions: what percent of inbound never gets answered live, and what is a booked job worth. If the answer clusters across shops, it is a market pattern worth a product bet. If it is one disorganized owner, it is a services fix, not a product.

05 The one number that moves
Inbound leads~40 / week · ~173 / month
Assume unanswered or slow follow-up (~30%)~52 lost / month
Recover with instant response (~20%)~10 saved / month
Convert to a paid visit (~60% × ~$500)~$3,000 / month
Recovered revenue, before replacement upsells~$3,000 / mo
A $8k system replacement now and then sits on top as upside. Every figure here is a hypothesis to test, not a promise.
06 The workflow · discovery to deployment

An agentic intake agent that answers every inbound lead in under a minute, around the clock.

  1. Answers the call or web form, qualifies problem type, urgency, service area, homeowner versus renter.
  2. Books directly into the dispatch calendar and sends a confirmation plus a reminder.
  3. Escalates true emergencies, no heat or a gas smell, to the on-call technician immediately.
  4. Follows up on quoted-but-unbooked leads over the next forty-eight hours.
  5. Sends the owner a nightly digest: leads in, booked, missed, revenue attributed.
07 Where engineering and I meet
Working with your engineers I build agentic systems myself, so I can scope the integrations, APIs, and data flows with your engineers and own the tradeoffs: phone and SIP overflow, the scheduling API (ServiceTitan, Housecall Pro, Jobber), the web and Google Business Profile webhooks, two-way calendar sync. I do not need to write it. I need to scope it, sequence it, and translate it both ways, to the engineers building it and to an owner who just wants three more booked jobs.
08 The pilot as a testable experiment

Three weeks. Low cost. Reversible.

Week 0 · baseline

Measure current live-answer rate, median speed-to-lead, and booked rate.

Weeks 1 to 3 · treatment

Route after-hours and overflow only to the agent.

Primary metric

Incremental booked appointments and revenue attributed to recovered leads.

Guardrail

Escalation accuracy and homeowner satisfaction, so we do not book junk.

Kill it if

Incremental booked revenue does not clear cost, or the owner spends time cleaning up mistakes.

Scale it if

Net-positive and trusted enough to hand over all hours. Then add the follow-up agent and the next trade that showed the pattern.

09 Why this is the job, not a demo

The owner never sees a model. He sees three more booked jobs this month and a nightly text that reconciles to his bank deposits. That is the only proof that matters to a small business, and it is what turns a pilot into a paying, sticky customer.


The part that generalizes

How I run pilots.

Swap the vertical and the one-number math changes. The method does not.

01

Find the real problem

The stated request is a symptom. The job is the thing underneath it that actually moves money.

02

Size the one number

Name the single metric the business already tracks, and make the whole pilot rise or fall on it.

03

Prove it cheap

The smallest reversible experiment that could show the effect, with an honest kill line drawn before starting.

04

Ship evidence they can check

Results the owner can reconcile against real bank deposits. That is what earns trust.


The vertical is interchangeable. The method is not.

Point me at a vertical Blue cares about and I will run this on it. That is the field work, and it is the part I actually enjoy.