Delivery hub
Nine offers, one build-and-launch runbook.
Every offer below moves through the same five-phase framework, with its own build plan and a working demo of what the client experiences.
Standard delivery framework
PHASE 1
Scoping & Inputs
Confirm niche, access, guarantee framing. Lock inputs per offer.
PHASE 2
Build
Pod builds the offer — automation, creative, content, or advisory work.
PHASE 3
QA & Demo
Live test run + recorded walkthrough before touching the client's live list or account.
PHASE 4
Client Launch
Point of Contact presents the demo, confirms go-live.
PHASE 5
Iterate & Handover
Pod monitors and iterates through the month-4 handover point.
OFFER 01
AI Growth Engine
Stop chasing leads and start dominating the market.
Acquisity (cold email engine)
Auto-booked discovery call
Discovery → Growth plan → Close scripts
CRM logging
Delivery Plan
Technical Build
Scoping
Confirm niche, ICP, and mailbox/domain setup for cold send on Acquisity
Build
Load target list, configure sequences and personalization inside Acquisity, connect calendar routing
Booking logic
When a prospect replies, the AI SDR reads intent, proposes times, and books the meeting directly onto the client's own calendar — it lands as a "Discovery Call," not a generic lead notification
QA
Send a small test batch, confirm deliverability (SPF/DKIM/DMARC) and that a real reply books correctly before full volume
Launch
Ramp full cold-send volume; discovery calls begin landing on the client's calendar automatically
Inputs needed from client
- Confirmed niche + target list source
- Sending domain(s) for warm-up / deliverability
- Approved discovery + close script language
- Calendar connected + write access for auto-booking
Build this once — Offer 07 (AI SDR) runs on the same Acquisity engine. Build the sequence infrastructure once per client, then set a different volume/goal per offer.
Workflow components
Trigger
New list loaded / sequence scheduled
→
Personalize
Merge fields per contact (name, company, niche detail)
→
Send
Cold email touch, staggered over the sequence
→
Detect reply
Positive reply branches into booking
→
Book
Event created on client's calendar
→
Log + notify
CRM updated, Slack alerted
Build this as a workflow in Acquisity's own Workflow Builder, or in n8n if the sequence needs to reach outside what Acquisity's builder covers (e.g. a CRM Acquisity doesn't natively support). Same six components either way — pick whichever your team already has the strongest muscle with.
| Access | What you need |
|---|---|
| Acquisity | Workspace access, sequence builder, reply-detection settings |
| Sending domain(s) | DNS access for SPF/DKIM/DMARC; 2–3 warm-up domains separate from primary |
| Target list | Cleaned list matching ICP, or enrichment source access |
| Calendar | Write access so the AI SDR can create events directly |
1. Deliverability foundation
- Publish SPF, DKIM, and DMARC records for every sending domain before any send goes out.
- Warm up each domain on a ramping schedule (low volume first 1–2 weeks, increasing gradually).
Template — DNS records (example)
TXT @ "v=spf1 include:_spf.acquisity.com ~all"
TXT acq._domainkey "v=DKIM1; k=rsa; p=<public key from Acquisity>"
TXT _dmarc "v=DMARC1; p=quarantine; rua=mailto:dmarc@{{client_domain}}"
2. List & sequencing
- Load the target list, mapped to ICP fields the sequence personalizes against.
- Build a 3-touch sequence: Day 0 specific opener → Day 3–4 proof point → Day 7–8 direct ask.
3. Reply handling → auto-booking
- Configure reply-detection so a positive reply triggers booking, not just a human notification.
- Connect the calendar so booking creates the event directly as "Discovery Call" with prospect context.
- Route the same reply event to CRM (log) and Slack (notify).
QA checklist
- Send a test batch (10–20 contacts), confirm inbox placement not just "sent" status.
- Send yourself a test reply, confirm it books correctly with the right details.
Full demo — reply → auto-booked discovery call
OFFER 02
Reactivation
Bring your dead lead list back to life.
n8n orchestration
HubSpot
Vapi + Claude Sonnet 5
SendGrid
Twilio (A2P 10DLC)
Slack
Delivery Plan
Technical Build
Scoping
Connect CRM, define dormancy window (>90 days) and scoring weights
Build
Configure channel router, voice / email / SMS templates, CRM activity logging
QA
Live batch test — 8 leads → 3 AI calls, 3 emails, 2 SMS, all logged
Launch
Daily 9:00 AM batch run against the full dormant list
Backstop
Claim + call hot leads within 15 minutes of the Slack alert
Inputs needed from client
- CRM access + export of dormant/cold leads
- Registered caller ID / SMS number (A2P 10DLC)
- Slack channel equivalent to #sales-hot-leads
Workflow components
Trigger
Daily schedule, 9:00 AM
→
Fetch
Dormant leads pulled from CRM
→
Score + route
0–100 score, branch by channel
→
Act
Voice / Email / SMS touch fires
→
Log
Activity written back to CRM
→
Notify
Slack alert on high-intent reply
This build uses n8n as the orchestration layer since it needs to reach HubSpot, Vapi, SendGrid, and Twilio in one flow. If the client's stack is fully inside Acquisity, the same six components can be built in Acquisity's own Workflow Builder instead — the shape doesn't change, only where it's hosted.
| Access | What you need |
|---|---|
| HubSpot | Private app token — contacts (read/write), deals (read), timeline events (write) |
| n8n | Workspace with credentials for HubSpot, Vapi, SendGrid, Twilio, Slack |
| Vapi | Account, phone number, assistant configured with Claude Sonnet 5 |
| SendGrid | Account with sending domain authenticated (SPF/DKIM) |
| Twilio | A2P 10DLC campaign registered, phone number |
1. Extract & score
- Schedule node: trigger daily at 9:00 AM.
- HubSpot node: search contacts where last activity > 90 days AND has an associated deal.
- Code node: score 0–100 — weight deal value × 0.6 + recency × 0.4.
2. Channel routing
- Switch node on score: ≥ 60 → Voice, 30–59 → Email, < 30 or SMS preference → SMS.
3. Multi-channel outreach
- Voice — HTTP Request to Vapi's call API with dynamic variables (deal value, dormancy days) in the system prompt.
- Email — Claude drafts a short personalized email; SendGrid sends it.
- SMS — Twilio sends a short, human-sounding text.
Template — Vapi system prompt (voice branch)
You are Sarah, calling on behalf of {{company_name}}.
Context: {{contact_name}} discussed a ${{deal_value}} project {{dormancy_days}} days ago
that went quiet. Do not read a script — reference the specific context above.
Goal: confirm whether it's still relevant and book a 10-minute catch-up if so.
If they say no or ask to be removed, thank them and end the call — do not push.
4. Log & notify
- HubSpot node: write a timeline event for whichever channel fired.
- IF node: on reply/high-intent signal, post to Slack with an AI summary + CRM deep link.
QA checklist
- Run one batch against 5–10 test leads before the full dormant list.
- Confirm all three channels log correctly to HubSpot.
- Have a teammate reply as a fake prospect to confirm the reply-handling path end to end.
Full demo — the real delivered asset, all 4 channels
Video posters shown above — click either to open the full source image; click "Watch recorded video" for the .mp4.
OFFER 03
Looking to Exit
Lift profit and valuation.
Unit-economics audit
EBITDA improvement plan
Valuation benchmarking
Delivery Plan
Method
Scoping
Collect financials, org structure, current valuation assumptions
Build
Run unit-economics + EBITDA audit, draft improvement plan
QA
Internal review of assumptions and recommendations
Launch
Present findings and improvement roadmap to the client
Inputs needed from client
- Recent financial statements / P&L
- Cap table or ownership structure
- Target sale timeline and desired multiple
1. Unit-economics pass
Contribution margin = Revenue − Variable costs (per job/unit/client)
CAC = Total sales + marketing spend ÷ new customers acquired
LTV = (Avg. monthly revenue × Gross margin %) ÷ monthly churn rate
Payback period = CAC ÷ (Avg. monthly revenue × Gross margin %)
2. EBITDA bridge
| Lever | Current | Target |
|---|---|---|
| Pricing | e.g. avg. job $420 | e.g. $460 (+9.5%) |
| Cost of delivery | e.g. 62% COGS | e.g. 56% COGS |
| Overhead | e.g. 18% of revenue | e.g. 15% of revenue |
3. Valuation benchmarking
- Pull comparable EV/EBITDA multiples for the client's sector and size band from real transaction data.
- Never present a multiple without a real comp — flag as a range with a stated source instead.
4. Exit-readiness report structure
- Executive summary → current-state financials → EBITDA bridge → valuation range → 90-day action plan.
QA
- Second reviewer sanity-checks EBITDA assumptions before the client sees them.
Full demo — what the deliverable looks like
OFFER 04
Fractional Sales
Lift close rate by 20% in 30 days.
Acquisity Sales Call Analyser
VA training & enablement
Objection-handling playbook
Weekly pipeline review
Delivery Plan
Method
Scoping
Audit current pipeline, call recordings, close-rate baseline
Build
Connect the Sales Call Analyser, build the objection-handling playbook + close script for the client's offer
Train
Teach the client's VA to run the playbook and read the Analyser's scorecards — this is the actual deliverable, not a one-off handoff doc
Co-pilot
Sit in on 2–3 live calls with the client's VA, coaching in real time against the Analyser's feedback
Launch
Client's VA runs closing calls independently; Analyser keeps scoring every call; track lift against baseline
Inputs needed from client
- Baseline close-rate and pipeline data
- Call recordings routed through Acquisity (or the Sales Call Analyser connected to the existing recording tool)
- Their VA's time for training sessions and the first few co-piloted calls
This is a training engagement, not a staffing one — the client already has a VA. The deliverable is teaching that VA to run the playbook and read the Analyser's output themselves, so the skill stays in-house once the engagement ends.
1. Connect the Analyser
- Route the client's call recordings into Acquisity's Sales Call Analyser (native if calls already run through Acquisity; connected via integration otherwise).
- Confirm it's tagging objections into the taxonomy below and scoring talk-time / sentiment per call.
2. Objection taxonomy (what the Analyser tags)
- Price — "too expensive," "need to check budget"
- Timing — "not right now," "check back next quarter"
- Authority — "need to run this by my partner"
- Trust — unfamiliarity with the company
- Competitor — actively comparing an alternative
3. Build the playbook, then teach it
- Pull the Analyser's most frequent objection tags across the client's last 10–15 calls.
- Build the objection-handling playbook and close script directly from those patterns, not a generic template.
- Run training sessions with the client's VA: walk the playbook, role-play the top objections, show them how to read their own Analyser scorecard.
- Co-pilot 2–3 live calls, coaching in real time, before stepping back fully.
4. Weekly tracking (pulled from the Analyser)
| Week | Close rate | Avg. Analyser score |
|---|---|---|
| Baseline | 18% | — |
| Week 1–4 | track weekly | talk-ratio + sentiment trend |
QA
- Confirm the Analyser is tagging objections accurately on a sample of calls before building the playbook around it.
- Confirm the client's VA can read their own scorecard unassisted before calling training complete.
- Confirm baseline close-rate is calculated the same way before/after so the +20% comparison is real.
Full demo — the Sales Call Analyser in action
OFFER 05
DFY SEO
Pull in free, qualified leads on autopilot by ranking #1 on Google.
Ahrefs (keyword + competitor research)
Technical audit
Content build-out
Authority building
Delivery Plan
Technical Build
Scoping
Technical audit + keyword/competitor research in Ahrefs for the chosen niche
Build
Fix technical issues, publish initial content set, begin authority-building
QA
Confirm indexing and rank-tracking dashboard report correctly
Ongoing
Monthly content + authority cadence; report rank and traffic movement from Ahrefs + Search Console
Inputs needed from client
- Website / CMS access
- Google Search Console + Analytics access
- Target niche/service pages to prioritize
Ahrefs runs the research side — keyword volume/difficulty, competitor gap analysis, and backlink tracking all come from Ahrefs; Search Console stays the source of truth for actual indexing and click-through data.
1. Keyword & competitor research (Ahrefs)
- Pull keyword volume + difficulty (KD) for the niche's service + location combinations.
- Run a competitor content gap report — what's ranking for competitors that this site doesn't have yet.
- Prioritize by volume ÷ difficulty, not volume alone — low-competition terms compound faster early on.
2. Technical audit — specific checks
- Every priority page returns 200, is in the sitemap, isn't accidentally no-indexed.
- Core Web Vitals: LCP under 2.5s, CLS under 0.1, INP under 200ms.
- Meta titles under 60 chars, meta descriptions under 155 chars, one H1 per page.
- Schema markup: LocalBusiness + Service at minimum; FAQPage where relevant.
3. Content brief template
| Target keyword | "emergency plumber [city]" |
| Search intent | Local, high-urgency, transactional |
| Word count | 900–1,200 |
| Required sections | Overview, service area, pricing signal, trust signals, CTA |
4. Authority building
- NAP consistency across the top 20 local directories before anything else.
- Track backlink growth in Ahrefs; steady monthly citation/backlink cadence, not a single burst.
QA
- Confirm indexing within 1–2 weeks of publishing.
- Set expectations at 90–180 days — don't imply a 30-day result.
Full demo — Ahrefs research → rank tracker
OFFER 06
Creative Ad Agency
30 high-converting Meta ads in 30 days.
Hook/angle matrix
UGC production
Meta Ads Manager testing
Delivery Plan
Technical Build
Scoping
Pull performance baseline, define hook/angle matrix
Build
Produce first batch of statics + UGC scripts/edits
QA
Review creative for brand/compliance before spend
Launch
Roll out 30 variations across the 30-day window in batches
Inputs needed from client
- Brand assets / guidelines
- Live Meta ad account access
- Existing UGC or customer testimonials
1. Hook/angle matrix
| Angle | Format | Example hook |
|---|---|---|
| Pain point | Static | "Still chasing quotes by hand?" |
| Before/after | UGC clip | Job transformation, 15–30s |
| Testimonial | UGC clip | Owner or customer, unscripted |
| Urgency | Static | "Booked out 3 weeks — here's why" |
2. Copy formula
- Hook (pattern interrupt) → Problem → Agitate → Solution → CTA — same structure per piece so the test isolates the hook.
3. Test budget math
- Spend 2–3× target CPL per creative before judging it — e.g. $30 target CPL needs $60–90 spend, or 50+ clicks / 3–5 leads, before comparing.
QA
- Every piece checked against brand + ad-platform policy before going live.
- No creative killed before it reaches the minimum spend/lead threshold above.
Full demo — what the creative testing board looks like
OFFER 07
AI SDR
Book 30 qualified calls in 30 days.
Acquisity (email SDR)
List sourcing / enrichment
Calendar booking
CRM + Slack hand-off
Delivery Plan
Technical Build
Scoping
Define ICP, sourcing method, and packaging vs. the Growth Engine offer
Build
Configure Acquisity sequences for the standalone 30-call target, connect calendar + CRM
QA
Test batch send against a list segment before full volume
Launch
Run full cadence toward the 30-calls-in-30-days target
Inputs needed from client
- ICP definition
- Source list or enrichment access
- Calendar link for booking
- Sign-off on how this is positioned vs. Offer 01
Same engine as Offer 01 — build the Acquisity sequence infrastructure once per client; this offer just tracks a standalone 30-call target instead of feeding the full close pipeline.
1. Packaging split
- Track and report against the 30-calls-in-30-days target as a standalone metric, independent of the close-call pipeline used for Offer 01.
2. Build
- Reuse the Offer 01 sequence infrastructure (deliverability, sequencing, reply→booking) — see Offer 01's Technical Build tab for the full steps and DNS/sequence templates.
- Point the calendar + CRM connections at this client's booking target instead of the growth-engine funnel.
QA checklist
- Send a small test batch and confirm deliverability before full volume.
- Confirm CRM logging and Slack notification both fire on a real reply.
Full demo — Acquisity booking flow
OFFER 08
AI Receptionist
Never miss another call again.
Vapi + Claude Sonnet 5
Call routing
Booking logic
CRM logging
Delivery Plan
Technical Build
Scoping
Map current call volume, common inbound intents, booking flow
Build
Configure voice agent, routing, qualification and booking logic
QA
Test call scenarios end-to-end (answer → qualify → book → log)
Launch
Cut over the business line to the AI receptionist
Inputs needed from client
- Business phone number / porting or forwarding access
- Common inbound scenarios/FAQs
- Booking calendar to connect
Workflow components
Trigger
Inbound call answered by Vapi
→
Qualify
Service type, urgency, service area
→
Check availability
Function call to the calendar
→
Book
Confirms slot back to the caller
→
Log
Call outcome written to CRM
The webhook + CRM-logging step is typically built in n8n since it just needs to catch Vapi's call-ended event and write one record — this is also a fine candidate for Acquisity's Workflow Builder if the CRM it needs to reach is one Acquisity already connects to.
| Access | What you need |
|---|---|
| Business number | Porting to Vapi, or call-forwarding from the existing number |
| Vapi | Assistant configured for inbound with qualification + booking script |
| Calendar | API/webhook access so the assistant can book directly |
Build steps
- Map the 5–10 most common inbound scenarios before writing the script — this is the input the prompt is built from.
- Configure the Vapi assistant: greeting, qualifying questions, function-calling step that checks calendar availability.
- Connect a webhook from Vapi (call-ended event) into n8n (or Acquisity's Workflow Builder) → CRM to log every call, qualified or not.
Template — Vapi system prompt (inbound)
You are the receptionist for {{business_name}}. Answer warmly, in one sentence,
then ask what they need help with.
Qualify: service type, urgency (same-day vs. routine), and service area.
If urgent and in area: check calendar availability, offer next 2 open slots,
confirm the booking back to the caller.
If outside scope: say so plainly and offer to take a message.
QA checklist
- Call the line with 3–4 scenarios (routine, emergency, out-of-scope) and confirm each is handled appropriately.
- Confirm a booked call appears on the calendar with correct details.
Full demo — what an inbound call looks like
OFFER 09
AI Agents
10 custom AI agents built for your business.
n8n / equivalent orchestration
Claude for reasoning/drafting
Per-workflow integrations
Delivery Plan
Technical Build
Scoping
Map workflows, select the 10 highest-value agents to build
Build
Build agents in priority order, reusing shared components
QA
Test each agent against real scenarios before handover
Launch
Walkthrough + handover docs as each agent goes live
Inputs needed from client
- Full workflow map / priority list of the 10 agents
- System access per integration (CRM, inbox, Slack, etc.)
- Named approver as agents ship
Workflow components (the shared pattern every agent reuses)
Trigger
Event, schedule, or message
→
Fetch / score
Pull the relevant record(s)
→
Personalize
Claude drafts / decides the action
→
Act
Send, update, or create something
→
Log + notify
Record it, alert a human if needed
Build each agent in either n8n or Acquisity's Workflow Builder — same six components regardless. Acquisity's builder is the faster path when the agent only needs to touch tools Acquisity already connects to; reach for n8n when it needs to bridge something Acquisity doesn't (a bespoke internal tool, for example).
1. Workflow-mapping session
- Walk the client through day-to-day operations by function: sales, ops, support, back-office.
- For each recurring task: capture trigger, current manual steps, tools touched, time spent.
- Prioritize by time saved × frequency, weighted down for anything needing slow-to-grant access.
Template — interview questions
"Walk me through what happens the moment a new lead/ticket/invoice comes in."
"What do you do by hand today that you wish just... happened?"
"Which of these would you trust an AI to do without checking its work first?"
"What's the cost of this going wrong once?"
2. Build in priority order
- Reuse the shared pattern (trigger → fetch/score → personalize via Claude → act → log → notify) per agent.
- Build shared components once — CRM connectors, Slack notifier, prompt scaffolding — reuse across agents.
QA checklist
- Each agent tested against 3–5 real scenarios from the client's own data before calling it done.
- A named approver signs off on each agent before it acts on real data.
Full demo — build board, 10 agents
Illustrative build board — actual 10 agents depend on the client's workflow-mapping session.