# The Homework List We Send Before Any AI Build Begins

*Nikhai Jaysen · November 9, 2026*

> Before any voice AI agent or chatbot build starts, an AI automation agency needs five things from you. Here's the list, and what slips when one is missing.

Source: https://www.spaceblanket.ai/blog/client-handover-checklist-ai-automation-build

The contract is signed and the kickoff call is booked, but the build doesn't actually start until five specific things land in our inbox. Here's what we ask every client for before writing a single line of an agent's logic, and what slips when one of them is late.

The contract is signed, the kickoff call is booked, and most clients assume the clock starts when our engineers start building. It doesn't. The clock starts the moment we ask for five things, and any **AI automation agency** worth hiring will ask for some version of the same list, because the agent you eventually launch is only as good as what it was trained on. We've watched two-week builds stretch into six because one of these five items sat in someone's inbox for a week.

## What We Ask For, and Why Each One Matters

None of this is paperwork for its own sake. Each item changes a real decision in how the agent gets built.

- **Real call recordings or chat transcripts.** Not a script of how customers are supposed to talk, the actual recordings of how they do. A [voice AI agent](/services/voice-ai-agents) trained on real interruptions, slang, and half-finished questions sounds like it belongs on the call. One trained on an idealized script sounds like it's reading from a card, and callers notice within the first ten seconds.

- **Read access to the CRM or calendar the agent will feed.** Where a qualified lead lands, and how fast, is a scoping decision, not an afterthought to wire up after launch. We've written about [why we run the CRM integration conversation before the build starts](/blog/voice-ai-crm-integration-before-you-build), and it's usually the single biggest unknown on a timeline.

- **The internal version of your FAQ or pricing document.** The one support actually uses, with the exceptions and caveats still in it, not the cleaned-up marketing page. An [AI chatbot](/services/ai-chatbots) or WhatsApp flow answers questions the same way your best support rep does only if it was trained on what your best support rep actually knows.

- **One named approver.** A single person who can sign off on tone, copy, and escalation rules within a day. Committees are where launches die quietly: the agent is ready, and it sits unlaunched for two weeks waiting for four people to agree on one sentence.

- **A decision on the phone number, made early.** Porting a number or registering a new one for outbound takes longer than most of the actual build. We go into this in more detail in [the phone number problem nobody mentions before a voice AI agent goes live](/blog/voice-ai-phone-number-setup-before-launch), but the short version is: decide this in week one, not week three.

## What Happens When One of These Is Missing

Nothing dramatic. The build doesn't stop, it just stalls at exactly the point that depends on the missing piece. We can write the conversation logic without CRM access, but we can't test what happens after a lead qualifies, so that work sits half-finished until the login arrives. The cost isn't abstract: research on inbound sales leads has repeatedly found that [response speed in the first hour is the strongest predictor of whether a lead converts at all](https://hbr.org/2011/03/the-short-life-of-online-sales-leads), and every week a build is delayed is a week that advantage sits on the table instead of in production.

We flag the delay the moment we see it, in writing, with the specific item we're waiting on. But the calendar slips from the client side, not ours, and it's almost always the same five things. If you want the earlier half of this process, we've also written about [how we scope a voice AI agent before any code exists](/blog/how-we-scope-voice-ai-saas-inbound), which is the conversation that determines which of these five items matters most for your build specifically.

Every week one of these five sits unanswered is a week added to your launch date, not ours. [Talk to our team](/contact) before you sign anything, and we'll tell you exactly what we'd need from you on day one, for your specific build.

## How to Prepare for an AI Automation Build: the steps
1. **Pull real conversations, not scripts.** Export actual call recordings or chat transcripts, the messy ones, not an idealized version of how customers are supposed to talk.
2. **Grant CRM or calendar access.** Give read access to the system where qualified leads should land, so routing can be scoped before the agent goes live.
3. **Hand over the internal FAQ or pricing document.** Share the version support actually uses, including the caveats and exceptions left off the public-facing page.
4. **Name one approver.** Assign a single person who can sign off on copy, tone, and escalation rules within a day, not a week.
5. **Decide on the phone number early.** Settle whether the agent uses a new number or an existing one, since porting and spam registration take longer than the build itself.

## Frequently Asked Questions

### What does an AI automation agency need from a client before building starts?

Five things, consistently: real call recordings or chat transcripts, read access to the CRM or calendar the agent will write into, the internal version of the FAQ or pricing document, one named approver for copy and escalation rules, and an early decision on the phone number. Missing any one of these is the most common reason a two-week build slips.

### Why do you need real call recordings instead of a script?

A script shows how a company wants customers to talk. Real recordings show how they actually talk: the interruptions, the slang, the way someone describes a problem before they know the right words for it. A voice AI agent trained on the second version sounds like it belongs on the call, not like it is reading from a card.

### Why does CRM access matter before the agent is even built?

Where a qualified lead lands, and how fast, determines whether it gets worked. If CRM access is sorted out after launch, the first few weeks of calls either go nowhere or get logged by hand. Settling this on day one means the agent is routing real leads into a real pipeline from its first live call.

### What happens if a client is slow to hand over one of these five things?

The build doesn't stall evenly, it stalls at the one missing piece. A two-week build can quietly become six weeks because an approver was on leave or a CRM login request sat unanswered. We flag the delay in writing as soon as we see it, but the calendar slips from the client side, not ours.

## Related Service

### [Voice AI Agents](/services/voice-ai-agents)

Handle inbound calls, qualify prospects, and follow up with leads, using natural-sounding AI voice agents that never miss a call.

## Related Reading

### [The Quiet Stretch Between Kickoff and Launch Is the Busiest Part of the Build](/blog/kickoff-to-launch-ai-build-timeline)

The two weeks between kickoff and launch look quiet from the outside, but they're the busiest part of building a voice AI agent, chatbot, or WhatsApp automation. Here's what an AI automation agency is actually doing in that window, and what slows it down.

### [The 60 Seconds After a Voice AI Call Ends](/blog/voice-ai-call-ends-post-call-pipeline)

A voice AI agent's real value often isn't the call itself, it's the pipeline that runs the moment it ends: transcript, disposition, CRM write, and whatever follow-up fires automatically. Here's what that pipeline actually looks like, and where it quietly breaks if nobody's watching.

### [The CRM Integration Conversation Every Voice AI Build Should Start With](/blog/voice-ai-crm-integration-before-you-build)

Most voice AI builds treat the CRM integration as a technical afterthought, something to wire up once the agent itself is working. We run that conversation first, because the answer to where a call's data lands changes how the agent should be scoped.

## Related
- [All articles](https://www.spaceblanket.ai/blog)
- [Voice AI Agents](https://www.spaceblanket.ai/services/voice-ai-agents)
- [All AI automation services](https://www.spaceblanket.ai/services)
- [Contact](https://www.spaceblanket.ai/contact)