PUZINSKI / HOME SERVICES HANDOFF CHECKLIST
Fictional planning example. Not a client system, operational instruction, or performance claim.

BUSINESS SITUATION
A fictional home-services company receives requests through one website form.
The first release concerns an inquiry, not a confirmed job or accepted estimate.

FIRST-RELEASE BRIEF
Source: one existing website form.
Destination: the business's existing CRM, subject to access and API review.
Required context: service requested, service area, contact preference, description.
Assignment: one agreed service-area rule with a named fallback owner.
Next action: one internal notification or approved follow-up, as scoped.
Source of truth: the agreed CRM inquiry record.

ACCEPTANCE QUESTIONS
1. Does a complete fictional request create or update the expected record?
2. Can the assigned person see the context and next action?
3. Does a missing service area reach the fallback owner?
4. Does a repeated submission follow the agreed duplicate rule?
5. Is a failed connection visible, with a documented way to continue manually?
6. Does retrying avoid unintended duplicate records or messages?

BEFORE EXPANDING
Separate estimates sent, estimates accepted, and booked jobs in reporting.
Define the status event that stops a reminder.
Confirm the business's approved messaging channels and audience permissions.
Agree on maintenance, running costs, and process ownership.

NOT INCLUDED BY ASSUMPTION
Additional sources, phone-provider integrations, multiple assignment rules,
estimate sequences, migrations, new CRM implementation, or emergency support.
The written proposal defines what is actually included.

Explore scopes: https://puzinski.com/packages/
Contact: https://puzinski.com/contact/