# AI Marketing OS — Delivery Kit (Internal)
*FounderVibe Advisory · How this service gets sold, scoped, delivered, and handed over*

---

## 1. Package definitions (what "done" means)

| | Starter €499 | Growth €990 | Full OS €1,500 |
|---|---|---|---|
| CMO agent w/ client context | ✓ | ✓ | ✓ |
| Workflows installed | 1 | 3 | 5 |
| Dashboard | – | ✓ | ✓ |
| SOP runbooks | basic | full | full + versioned |
| Training | 1×60 min | 2×60 min | 2×60 min |
| Support | – | – | 30 days async |
| Stack review | – | – | 1× quarterly incl. |
| **Target delivery time** | 3 days | 5 days | 7 days |
| **Target margin** | ~€400 | ~€750 | ~€1,100 |

**Scope guardrails (say no to):** custom software development, paid-ads management, ongoing content production, integrations into enterprise systems (Salesforce, HubSpot Enterprise), anything requiring us to hold client credentials permanently.

## 2. Scoping call script (20 min)

1. **Motion (5 min):** "Walk me through how a piece of marketing gets made today, from idea to published." Listen for the bottleneck.
2. **Stack (3 min):** What tools/AI do they already pay for? What died on the shelf?
3. **Bottleneck (5 min):** "If one marketing task ran itself next month, which one changes your revenue?" → this becomes Workflow #1.
4. **Fit filter (2 min):** team size ≤5? Own accounts OK? Someone willing to run runbooks? If any "no" → decline politely, point to the Playbook (€79) instead.
5. **Quote (5 min):** map to package, state fixed price, delivery window, next step (intake form + 50% deposit).

**Honest declines are marketing.** Every "you don't need this yet" builds the referral engine.

## 3. Client intake questionnaire (send after deposit)

**Business context**
1. One-paragraph description of the company and product
2. ICP: who buys, who uses, who decides?
3. Positioning statement / main promise (link Offer Canvas if they have one)
4. Product ladder & prices
5. Top 3 competitors and how you differ

**Voice & content**
6. 3 links to content that sounds like you (yours or others')
7. Words/phrases you always use; words you never use
8. Language(s) for output

**Operations**
9. Current channels, ranked by importance
10. The workflow you chose on the call — describe the manual version step by step
11. Who on the team will operate the system? Technical comfort 1–5?
12. Tools/accounts we'll connect (AI provider, site, analytics, email tool)

**Constraints**
13. Anything that must NOT be automated?
14. Compliance/privacy constraints (industry, region)?
15. Success in 30 days looks like: ___

## 4. Delivery SOP (day by day, Growth as default)

**Day 1 — Design**
- Verify intake, resolve gaps on a 15-min call if needed
- Select stack components for this client. **License check is mandatory:** confirm each repo's LICENSE allows commercial use in a service context; record repo URL + license + version in the Attribution Sheet. No license file = do not use.
- Draft workflow specs (input → steps → output → owner)

**Day 2 — Foundation**
- Set up client accounts/environment (their credentials, their machines/hosting)
- Install core agent framework + skills
- Build the **context layer**: `context/positioning.md`, `context/icp.md`, `context/voice.md`, `context/offers.md` from intake

**Days 3–4 — Workflows**
- Implement workflows one by one; test each against a real task from the client's backlog (ask for 3 real examples up front)
- Write one runbook per workflow: purpose, trigger, exact steps, expected output, failure modes, owner
- Growth/Full: connect dashboard; define the 3–5 metrics it must answer

**Day 5 — Hardening**
- End-to-end dry run of every workflow by someone who didn't build it (or the client operator, guided)
- Finalize Attribution Sheet and Handover Doc

**Days 6–7 — Handover**
- Training session(s): operator drives, we coach
- Deliver Handover Pack (see 5)
- Schedule 2-week check-in (15 min) — churn insurance and upsell moment

## 5. Handover Pack contents (client-facing)

1. **System map** — one page: layers, components, what talks to what
2. **Runbooks** — one per workflow
3. **Context files** — versioned, with editing instructions ("change your positioning here, everything downstream follows")
4. **Attribution Sheet** — every open-source component: name, repo link, license, version, why we chose it. *This transparency is a brand feature; never hide it.*
5. **30-day adoption plan** — week-by-week: W1 run everything supervised · W2 operator runs solo · W3 add volume · W4 review metrics, cut what's unused
6. **Support terms** — what's included, response times, maintenance sprint pricing

## 6. Upsell / cross-sell map

- Scoping call "not yet" → **Agent Stack Playbook** (€79)
- Starter after 30 days → Growth upgrade (pay difference + €100 setup)
- Growth/Full after 60 days → **Maintenance retainer** (€149–299/mo — feeds the Founders Club tier)
- Team wants to learn the method → **Build Your AI Team in a Day** workshop (€499)

## 7. Boilerplate: the honesty paragraph (use in proposals)

> Every component of your stack is open-source software, and your handover documentation lists each one with a link and license. What you're buying from us is selection, integration, configuration for your business, documentation, and training — not the software itself. When we're done, you own and control everything.

---
*Internal document — do not ship to clients. v1.0*