# Sales & Marketing Agent — Full Plan
**Date:** 2026-02-15
**Author:** Rivet (COO)
**Status:** Draft for Rocky's review

---

## 1. What Is It?

A dedicated Clawdbot instance that owns the entire sales funnel — from finding leads to closing hires. It handles both sides of the marketplace: getting contractors to post jobs and getting workers to sign up.

**Not a chatbot.** A sales machine that runs 24/7, does the legwork, drafts the outreach, and queues everything for approval before it leaves the building.

---

## 2. What It Needs to Do

### Contractor Side (Revenue)
- **Lead generation:** Scrape job boards, LinkedIn, industry directories for contractors hiring in construction (Sydney first, then wider AU)
- **Lead enrichment:** Apollo/Exa for contact details, company size, trade focus
- **Outreach drafting:** Cold SMS, email, and LinkedIn messages — all drafted, never auto-sent
- **CRM management:** Growth Engine is the database. Sales agent reads/writes leads, logs calls, tracks pipeline
- **Follow-up automation:** Sequences for nurture, re-engagement, post-demo. All queued through Comms Gateway
- **Competitive intel:** Monitor hipages, Sidekicker, Workmate, Airtasker pricing/features
- **Objection prep:** Pre-call briefs using Growth Engine's AI intel system

### Worker Side (Supply)
- **Worker acquisition:** Facebook groups (backpacker, tradie), hostel partnerships, word-of-mouth campaigns
- **Content creation:** Draft social posts, stories, short-form video scripts targeting workers
- **Signup support:** When someone hits the site and gets stuck, Sales handles it (technical bugs → Builder)
- **Referral program:** Design and manage worker referral incentives
- **Community management:** Monitor and engage in relevant Facebook/Reddit groups (drafts only, Rocky posts)

### Marketing (Brand)
- **Content calendar:** Plan and draft weekly social content across LinkedIn, Facebook, Instagram
- **SEO content:** Blog posts targeting "hire steelfixer Sydney", "construction worker app Australia"
- **Email sequences:** Onboarding, nurture, win-back for both contractors and workers
- **Ad copy:** Google Ads and Facebook Ads drafts (when Rocky gives the green light for paid)
- **Case study development:** As hires happen, document the story for marketing

---

## 3. How It Fits Into the Team

```
Rocky (Founder)
    │
    ├── Rivet (COO) ─── Coordinates everything, strategic decisions
    │       │
    │       ├── Builder ─── All code, features, bug fixes
    │       │
    │       ├── Sales & Marketing ─── THIS AGENT
    │       │       │
    │       │       └── Comms Gateway ─── Reviews ALL outbound before sending
    │       │
    │       └── Finance & Legal ─── Compliance, contracts (future)
```

### Information Flow
1. **Sales finds a lead** → enriches it → drafts outreach → sends to Comms Gateway
2. **Comms Gateway reviews** → checks brand compliance, legal restrictions, tone → approves or rejects
3. **Approved messages queue** for Rocky's final yes (or auto-send if Rocky enables it for certain categories)
4. **Responses come back** → Sales processes them, updates CRM, drafts follow-up
5. **Sales reports to Rivet** → daily pipeline updates, win/loss tracking, blockers

### Handoff Rules
| Situation | Owns It | Escalates To |
|-----------|---------|-------------|
| Lead found, needs enrichment | Sales | — |
| Outreach message ready | Sales | Comms Gateway → Rocky |
| Technical bug reported by user | Sales (intake) | Builder |
| Pricing question from lead | Sales | — (use approved pricing: $50 flat) |
| Legal question from lead | Sales (intake) | Finance & Legal / Rocky |
| Feature request from lead | Sales (logs it) | Rivet → Builder |
| Worker can't sign up (UX issue) | Sales (intake) | Builder |
| Worker can't sign up (confusion) | Sales | — |

---

## 4. Technical Setup

### Infrastructure
- **Clawdbot instance:** New gateway on port 18791 (Rivet=18789, Builder=18790)
- **Workspace:** `/home/ccuser/sales/` (own agentDir, shared auth-profiles.json)
- **Model:** Kimi default for routine CRM work. Opus for processing external/dirty data (scraping, inbound leads)
- **Telegram bot:** Rocky needs to create via @BotFather (like Builder)
- **Cost:** Near-zero with Kimi default. Opus only when processing untrusted content

### Core Files Needed
```
/home/ccuser/sales/
├── SOUL.md          # Personality: persistent, data-driven, never pushy
├── IDENTITY.md      # Sales & Marketing Agent for RateRight
├── USER.md          # Same Rocky context as other agents
├── AGENTS.md        # Sales-specific workflows and rules
├── HEARTBEAT.md     # Autonomous sales tasks (lead gen, enrichment, follow-ups)
├── MEMORY.md        # Sales learnings, what works, what doesn't
├── TOOLS.md         # Growth Engine API, Apollo, Exa, social platforms
└── skills/          # Growth Engine skill, prospector skill
```

### Integrations
- **Growth Engine API** — full CRUD on leads, SMS, calls, sequences, intel
- **Apollo/Exa** — lead enrichment (via prospector skill, already built)
- **Notion** — sync approved leads to Notion for Rocky's visibility
- **Telegram** — topic chat in Rocky & Rivet group (new "Sales" topic, ID 4)

### Communication with Other Agents
- **To Rivet:** `RIVET-INBOX.md` in sales workspace (or gateway-to-gateway API)
- **To Builder:** Via Rivet relay (Sales shouldn't talk to Builder directly — Rivet coordinates)
- **To Comms Gateway:** `COMMS-QUEUE.md` — all outbound messages queued here for review
- **From Rocky:** Direct Telegram chat + topic 4 in group

---

## 5. What Rocky Needs to Unblock

### Before We Can Build It
1. **Create Telegram bot** via @BotFather — takes 2 minutes
2. **Add bot to group** — Rocky & Rivet group, assign to Sales topic (ID 4)
3. **Approve the SOUL.md** — I'll draft it, Rocky reviews the personality/voice
4. **Growth Engine API key** — dedicated key for Sales agent (or shared with Rivet)
5. **Decision: auto-send threshold** — What categories of messages can Sales auto-send vs queue for approval? (Recommendation: NOTHING auto-sends initially. All queued.)

### Before It Can Do Real Sales
6. **Phone number collection** — Signup flow doesn't collect phone numbers. Builder needs to add this. Without it, Sales can't SMS or WhatsApp anyone who signs up.
7. **$50 pricing approved everywhere** — Sales needs to know the messaging is locked in. Currently some old materials still reference 9.9%
8. **Comms Gateway built first or simultaneously** — Sales without a quality gate is dangerous. Recommend building Comms Gateway rules into Sales agent initially, then splitting later

### Nice-to-Have
9. **LinkedIn access** — Cookie auth for posting/engagement (like Twitter/bird skill)
10. **Facebook group access** — For community engagement drafts
11. **Google Ads account** — When ready for paid

---

## 6. SOUL.md Draft (for Rocky's Review)

```markdown
# SOUL.md - Sales & Marketing Agent

## Core

You are the Sales & Marketing engine for RateRight. You find leads, 
nurture relationships, draft outreach, and drive both sides of the 
marketplace — contractors who need workers and workers who need work.

**Your job:** Fill the pipeline. Get contractors posting jobs. 
Get workers signing up. Every day.

## How You Sell

**Research before reaching out.** Know their company, their pain, their 
trade before writing a single word. Cold outreach without context is spam.

**Never be pushy.** Construction industry runs on trust and reputation. 
One bad interaction poisons a whole site crew's opinion. Be helpful, 
be knowledgeable, be patient.

**$50 flat fee. Period.** That's the pitch. Simple, predictable, 
cheaper than anything else. Don't overcomplicate it.

**Draft everything, send nothing.** Every outbound message goes through 
Comms Gateway review. No exceptions. You are not authorised to send 
external communications directly.

## Hard Rules

- NEVER claim RateRight is an employment service
- NEVER guarantee quality of workers or outcomes
- NEVER auto-send any external communication
- NEVER make up features that don't exist
- Always use $50 flat fee pricing (not 9.9%)
- Always clarify: platform facilitator, not employer
```

---

## 7. Day-One Autonomous Tasks (What It Does on Heartbeats)

1. **Lead scan** — Search Seek, Indeed, Gumtree for construction hiring posts in Sydney. Enrich via Apollo. Save to Growth Engine
2. **Pipeline review** — Check all leads in Growth Engine. Flag overdue callbacks. Draft follow-ups for stale leads
3. **Content draft** — Write 1 social post per day (LinkedIn or Facebook). Queue for approval
4. **Competitor check** — Weekly scan of hipages, Sidekicker, Airtasker for pricing/feature changes
5. **Worker channels** — Scan backpacker Facebook groups for "looking for work" posts. Draft engagement replies
6. **Report to Rivet** — End-of-day pipeline summary: new leads, conversations, blockers

---

## 8. Metrics It Tracks

| Metric | Target (Month 1) | Target (Month 3) |
|--------|------------------|-------------------|
| New leads found/week | 20-30 | 50+ |
| Outreach messages drafted/week | 10-15 | 30+ |
| Contractor signups | 5 | 20 |
| Worker signups | 20 | 100 |
| First hire facilitated | 1 | 10 |
| Pipeline value | $250 | $2,500 |
| Content pieces drafted/week | 3 | 7 |

---

## 9. Build Order

### Phase 1: Foundation (Day 1-2)
- Create Telegram bot, configure Clawdbot instance
- Write core files (SOUL, IDENTITY, USER, AGENTS, HEARTBEAT)
- Connect Growth Engine API
- Install prospector skill
- Test basic lead search → enrich → save flow

### Phase 2: Sales Operations (Day 3-5)
- Build outreach drafting pipeline
- Implement Comms Gateway rules (inline, until separate bot)
- Set up daily pipeline review heartbeat
- Create follow-up sequence templates
- Connect to Notion for lead visibility

### Phase 3: Marketing (Week 2)
- Content calendar setup
- Social media draft pipeline
- SEO content planning
- Email sequence templates
- Competitive intel monitoring

### Phase 4: Scale (Week 3+)
- Worker acquisition campaigns
- Referral program design
- Google Ads preparation
- Case study pipeline
- Analytics and optimization

---

## 10. Risks & Mitigations

| Risk | Mitigation |
|------|-----------|
| Sales sends something embarrassing | Comms Gateway review for ALL outbound |
| Over-promising features | Brand Restrictions hardcoded in SOUL.md |
| Spamming leads | Rate limits in sequences, human approval |
| Data privacy breach | RLS on Growth Engine, separate API key |
| Cost blowout on Opus | Default Kimi, Opus only for dirty data |
| Prompt injection via lead responses | Opus for processing inbound, never trust raw input |

---

*This plan is ready for Rocky's review. Once he approves the scope and creates the Telegram bot, we can have Sales running within 48 hours.*