Written Scope: AI Sales and Marketing Automation
Sample
- Prepared for
- A 150-person oilfield equipment rental and repair company in north Houston (fictional)
- Their team
- CEO, VP of sales, 8 field reps, 3 inside reps, and a Salesforce admin. The board meets monthly.
- Lead
- Joe Zeng
- Version
- 1, approved by both sides before work starts
1. The Goal
Why It's Here
We can't promise how fast your reps call back. Each phase has its own finish line, and the board page shows what the build produced.
Clean Salesforce data, an owner on every inquiry within minutes, field visits logged without typing, and one page each month the board can check, with pipeline value and a weighted forecast built from your own stage weights.
What we're working toward: a first contact on every inbound inquiry within 1 business hour, and every field visit logged the same day, by the end of Phase 3. These are targets. We commit to the work in each phase, and the report shows what it produced.
2. Before Anyone Gets Access
Why It's Here
Least access, named logins, and a sandbox first mean a mistake gets caught before it touches a live customer record.
- An NDA is signed on request, before anyone sees your data.
- Your Salesforce admin creates one integration user for the workflows, with only the objects and fields they need. No Modify All Data, no data export, and no admin rights.
- People on our side get their own named logins, never a shared one.
- Every change is built and tested in a sandbox first, and your admin approves the move to production.
3. The Phases
Why It's Here
Phases keep risk small. Each one is approved before the next starts, so you never wait months to see working results.
- Phase 1, Weeks 1 to 3: Cleanup
- Opportunity stages rewritten to match how you win rentals and repairs, each with a forecast weight your VP of sales sets. Duplicate and matching rules for accounts and contacts. Required fields for lead source, equipment line, region, and amount.
- Phase 2, Weeks 4 to 6: Routing
- Salesforce Flows that give every inbound inquiry an owner by territory and equipment line, a task due within 1 business hour, and a named backup when the owner is out.
- Phase 3, Weeks 7 to 10: Visit notes
- A rep records a short voice note after a visit. AI turns it into a logged visit on the right account, with next steps as tasks. The rep reads it and confirms it before it saves.
- Phase 4, Weeks 11 to 12: Board page
- One page a month built from saved Salesforce reports: pipeline value created, won, and open by source, a weighted forecast from your stage weights, opportunities created, speed to first contact, visits logged, and rep hours saved.
- Phase 5, Weeks 13 to 14: ERP sync
- Equipment availability from your rental and repair ERP shown on each open rental opportunity, read only, so a rep sees what's in the yard before promising it. Built by the Salesforce developer named below, from Joe's written spec.
Each phase starts only after you approve the one before it. Weeks count from the kickoff call.
4. What Counts as Done
Why It's Here
Each phase has a written finish line that your admin can test before the next phase starts.
Phase 1 is done when
- Every open opportunity sits in a stage from the new list, with an amount.
- Duplicate rules block new duplicate accounts, tested on 10 real records.
- Every new lead has a source, an equipment line, and a region.
Phase 2 is done when
- Routing has been tested on 20 real inquiries, and each one reached the right rep with a task.
- A backup owner gets the inquiry when the first owner is marked out.
Phase 3 is done when
- Each of the 8 field reps has logged 5 real visits by voice and confirmed each one.
- Voice recordings are deleted once a visit is confirmed, and only the text stays in Salesforce.
Phase 4 is done when
- Every number on the board page opens to the saved Salesforce report behind it.
- The weighted forecast matches open pipeline times the stage weights your VP of sales signed off.
Phase 5 is done when
- Every open rental opportunity shows current availability from your ERP, checked against the ERP on 20 real records.
- The sync reads from your ERP and writes nothing back to it, confirmed by your admin.
5. Who Does What
Why It's Here
Your admin approves every change to Salesforce, and your reps keep every customer conversation. We build and test first.
Who does each part of the work: your team or Apex Local Task Your team Apex Local Talk to customers Your team: Your reps Apex Local: Never Confirm every visit note Your team: The rep who made the visit Apex Local: Builds the voice note workflow Approve changes to Salesforce Your team: Your Salesforce admin Apex Local: Builds and tests them in a sandbox Stages, weights, required fields, and routing rules Your team: Your VP of sales signs off Apex Local: Writes them and builds them Custom code and the ERP sync Your team: Your admin approves the release Apex Local: Writes the spec and reviews the developer's work Board page Your team: Your CEO presents it Apex Local: Builds it and checks every number Joe Zeng leads every phase. Custom code and the Phase 5 ERP sync go to a Salesforce developer: [Name], named in your scope before that work starts. Joe writes the spec and reviews the work before it reaches you.
Backup: [Name], a specialist Joe works with, named in your scope before work starts, keeps sandbox testing and the board page on schedule if Joe is out.
6. Tools
Why It's Here
The AI model is named here before you sign, and your admin approves it before it reads a single visit note.
- Salesforce
- Your CRM, already in place. Stages, Flows, duplicate rules, and the board page reports all live in your org.
- Integration user
- One Salesforce user for the workflows, with the least access they need, set by your admin.
- Voice notes
- Reps record from their phones, in the Salesforce mobile app or a short form we set up. We confirm which in Week 1.
- AI model
- A transcription and drafting model from OpenAI, Anthropic, or Google, named here before you sign, with what its terms say about training on your data. Your admin approves it before Phase 3 starts.
- n8n
- Runs the steps Salesforce Flows don't cover, such as passing a voice note to the model. In your company's account.
- Your ERP
- Your rental and repair system. In Phase 5 the sync reads equipment availability through a test login first, then a read-only login your admin approves.
Before each phase, we check the current integration lists, your ERP's too, and write here how each piece connects. A piece that won't connect gets a named workaround before the phase starts.
7. Sending Rules
Why It's Here
Your sending reputation and customer trust stay intact. Nothing reaches a customer unless a person on your team approves it.
- This project sends nothing to customers. No new sending domains, and no outreach sequences.
- Nothing is sent without a person's approval. If a later phase drafts emails, a rep approves and sends each one from their own inbox.
- Routing alerts and tasks go to your own people only.
8. Accounts and Data
Why It's Here
Your customer data and every build stay in your org. If the work stops, your admin can run everything from the notes.
- Every account is in your company's name: Salesforce, the integration user, n8n, the AI model account, and the ERP logins. Your admin holds the admin logins.
- Voice recordings are deleted once the rep confirms the visit. Only the confirmed text stays, in Salesforce.
- Customer records stay in Salesforce and your ERP. We work inside them and don't copy customer records into our own systems. Our record of the project, the scope, specs, and board pages, is kept up to 3 years after our last contact.
- We remove our access within 2 business days of the work ending or your request, whichever comes first, and hand over every Flow and workflow with a one-page note on how it runs. Ask in writing, and your data leaves our own systems within 30 days.
9. What a Person Approves
Why It's Here
AI drafts each visit note, and the rep who made the visit checks and confirms it. Nothing saves on its own.
- Every visit note: the rep confirms it before it saves.
- Every change to Salesforce: your admin approves the move from sandbox to production.
- Stages, forecast weights, required fields, and routing rules: your VP of sales signs off.
- The board page: your CEO sees it before the board does.
- Joe reviews the summary of every confirmed visit note during Phase 3, and keeps reviewing them each week after it, flagging any error to the rep who made the visit.
10. Not in This Scope
Why It's Here
This project is about clean data and speed, so outreach of any kind needs a written change first.
Outreach sequences, new sending domains, marketing emails, ad campaigns, and replacing your ERP. The Phase 5 sync only reads from your ERP. The rest each need a written change first, through the change rule below.
11. Changes
Why It's Here
Every new Flow is written, approved, and built in the sandbox first, so the build matches the scope line for line.
Either side can ask for a change, such as a new routing rule or another number on the board page. It's written here with its date, your admin or VP of sales approves it, and it's built in the sandbox before anything changes in production.
12. How Billing Works
Why It's Here
This is a project in five phases, so each phase is scoped and approved on its own.
Projects are a fixed price per phase. Monthly work is billed monthly. Any software you pay for is listed in your scope.
13. Terms
Why It's Here
You can stop between any two phases and keep what's built, so the project has to prove itself at each step.
- One project in five phases, each approved before the next starts.
- You can stop between phases with 7 days' written notice, and Apex Local gives 30 days' written notice before stopping between them.
- You keep everything built up to that point.
- We check the build with you 30 days after Phase 5 goes live.
