What does a successful DIY voice-agent project involve?
Build one bounded service, not a general-purpose artificial receptionist.
Section 02 of 11 / Understand the work
Plan the people, integrations and tests a working agent needs.

A proposed ten-week path from baseline to an expansion decision. Each stage has an exit condition.
The following six-to-ten-week schedule assumes one bounded inbound workflow, one main operational integration and available internal decision-makers. It is an illustrative project plan, not an observed typical duration.
Build one bounded service, not a general-purpose artificial receptionist.
Choose the least complex route that can satisfy the workflow and its controls.
The minimum team is an operations owner, an integration owner and a risk approver, with named frontline fallback.
Plan around evidence gates, not a promised launch date.
Measure recoverable work, not ringing events.
Write the rules before writing the prompt.
Review the actual workflow, data path and jurisdictions—not a generic claim that the platform is compliant.
Use a test number and sandbox tools before touching the public line.
Put a controlled transaction service between the agent and the operational system.
Define handoff success as an accepted transfer to the intended destination—not invocation of a transfer tool.
Test business outcomes, audio behaviour, transactions and recovery separately.
Release limited traffic when the responsible team is available, then expand on evidence.
Price the whole operating service, not just the connected minute.
Treat the agent as a maintained service with versioned releases and accountable incident response.
The handover pack should allow someone other than the builder to understand, operate and stop the service.