HH / CASE 001
NovaNest Pro

NovaNestPro.

A personal AI operator for independent service professionals—designed to understand the business, preserve control, and move real customer work forward.

Role
Founder / product / build
Setting
Thumbtack + home services
Interface
Telegram control surface
Status
Active product development

I was on a ladder.
The next lead was already leaving.

I was doing camera-installation work in Los Angeles. A new paid lead could arrive while I was driving, carrying equipment, or inside a customer’s property. Reply too late and the opportunity was gone; reply too quickly without the right context and the quote could be wrong.

The problem was larger than sending a message. The system needed to know service area, job type, price rules, availability, risk, conversation state, and what required a human decision. That became NovaNest.

The product is the operating loop.
AI is one component.

NovaNest turns each lead into visible business state. The model can interpret and draft; rules, approvals, follow-up, and outcomes remain inspectable.

Fig. 02 — NovaNest operating loopHuman-control boundary marked in orange
PAID LEADDETAILS + MEDIA QUALIFYRULES + CONTEXT REPLYDRAFT / SEND FOLLOW-UPSTATE + TIMING OUTCOMERECORDED APPROVE / EDIT / SKIP NO RESPONSE / DECLINE
IntakeLead details and photos become structured context
RulesPrice, service area, availability, and risk
ControlOwner can approve, edit, skip, or automate
StateReply, follow-up, booking, and outcome stay distinct

The hard part was deciding
what the AI must not hide.

01Business state before chat

A fluent reply is not the product. The system must know whether a lead is qualified, quoted, waiting, booked, cancelled, completed, or unresolved.

02Control is a working mode

Approve, edit, skip, and automatic behavior are explicit choices. Sensitive price or scheduling decisions can stay with the owner.

03Failure paths are first-class

No response, incomplete details, out-of-area work, cancellations, and follow-up timing are designed into the loop.

04Outcome is not revenue

A lead, reply, booking, completed job, collected payment, and product revenue are separate facts. The system and this case study do not collapse them.

Observed, not inflated.
The boundary matters.

The figures below describe an early founder-account trial and a separately recorded external-professional trial. They are product evidence—not claims of current revenue, completed jobs, or scaled traction.

Early founder-account trial

Six real leads.
Two bookings.
One without approval.

Recorded booking value
$190
First autonomous booking
Not represented as collected revenue

The signal was simple: a system designed around business rules and explicit state could move a real conversation to a booking without the founder approving that message. The next work is proving repeatability, reliability, and customer value over time.

Visit NovaNest Pro ↗
6Real leads in documented early founder trial
2Booking records in the same trial
1External professional trial recorded separately

Need this kind of ownership
on another system?

Start with the operational problem. The useful conversation begins before the technology choice.