Upwork Project Delivery

# SOP — Upwork Project Delivery

**Tag**: Track 1 — Fast Cash
**Timeline**: Varies by project (typically 3-14 days)
**Owner**: Devin (Delivery Ops) · Rick (Revenue) for proposals and client comms

---

## Purpose

Upwork is the fast-cash track. It generates revenue while the DFW pipeline builds, creates portfolio pieces, and produces testimonials that transfer to local credibility. Every Upwork project should produce: revenue, a review, and a reusable skill.

---

## Phase 0: Prospecting & Proposals

### Lead Source
- Rick's automated cron jobs surface relevant Upwork jobs nightly (11pm lead research)
- Clayton manually browses for high-fit projects
- Upwork invitations to bid

### Qualification (BANT Quick Filter)
Before writing a proposal, confirm:
- **Budget**: $500+ (skip low-budget jobs)
- **Authority**: Client has decision-making power (check profile: payment verified, prior hires)
- **Need**: Clear automation/lead-gen need we can solve
- **Timeline**: Reasonable (not "need this in 2 hours")

### Proposal Writing
1. **Rick** drafts proposal using this structure:
   - **Hook**: Reference something specific from their job post (show you read it)
   - **Proof**: Relevant experience or similar project completed
   - **Plan**: 3-5 bullet summary of what you'll do and deliver
   - **Timeline**: Specific estimate (e.g., "5 business days")
   - **CTA**: "Happy to jump on a quick call to discuss scope"
2. Keep proposals under 200 words. No jargon. No "Dear Sir/Madam."
3. If possible, attach a skateboard demo (a quick screenshot or video showing a working version of what they need)
4. **Rick** submits proposal and logs in HubSpot → "Upwork — Proposed"

### Deliverables
- Proposal submitted
- HubSpot deal created

---

## Phase 1: Scoping & Contract

### Steps
1. Client responds → **Rick** moves deal to "Upwork — In Discussion"
2. **Rick** conducts scoping conversation (Upwork messages or call):
   - Clarify exact deliverables
   - Confirm tools/platforms involved
   - Identify any access requirements
   - Agree on milestone structure (see below)
3. **Rick** sends scope summary in Upwork message:
   - "Here's what I'll deliver: [list]. Here's the timeline: [X days]. Here's the cost: [$X]."
4. Client accepts → Rick creates Upwork contract (fixed-price preferred)

### Milestone Structure (Fixed-Price)
For projects $1,000+, split into milestones:
- **Milestone 1 (30%)**: Discovery + scope confirmation
- **Milestone 2 (50%)**: Build + internal testing complete
- **Milestone 3 (20%)**: Client review + final delivery

For projects under $1,000: single milestone is fine.

### Deliverables
- Scope confirmed in writing (Upwork messages)
- Contract created with milestone structure
- HubSpot deal → "Upwork — Contracted"

---

## Phase 2: Build & Delivery

### Steps
1. **Devin** receives handoff from Rick with:
   - Scope summary
   - Client access credentials (if needed)
   - Timeline commitment
2. **Devin** builds the deliverable:
   - Follow the technical build process from the relevant package SOP (starter/standard)
   - Document everything as you build (client will need handoff docs)
3. **Devin** tests end-to-end:
   - All integrations fire correctly
   - Edge cases handled (empty fields, API failures, duplicates)
   - Output matches what was promised in scope
4. **Devin** submits milestone for review (Milestone 2) with:
   - Summary of what was built
   - Screenshots or video walkthrough
   - Any questions for the client

### Platform Rules
- **ALL communication through Upwork messages.** Do not move to personal email/Slack until after the project closes. Upwork monitors for off-platform communication and will flag accounts.
- **Submit milestones promptly.** Do not let funded milestones sit unsubmitted.
- **Respond within 24 hours** to all client messages.

### Deliverables
- Working deliverable (tested)
- Milestone submitted with documentation

---

## Phase 3: Client Review & Revisions

### Steps
1. Client reviews submitted milestone
2. If revision requested:
   - **Devin** addresses within 48 hours
   - Resubmit milestone with revision notes
   - Maximum 2 revision rounds within original scope
3. If revision is scope expansion (not in original agreement):
   - **Rick** communicates: "That's a great idea — it's outside the current scope but I can add it as an additional milestone for $X"
   - Do NOT do free scope expansion
4. Client approves milestone → funds released

### Deliverables
- Revisions completed (if requested)
- Milestone approved and paid

---

## Phase 4: Handoff & Close

### Steps
1. **Devin** delivers final package:
   - All files, credentials, access
   - Handoff documentation (how it works, how to maintain it)
   - 15-min walkthrough call (for projects $1,000+)
2. **Rick** submits final milestone
3. After final payment received:
   - **Rick** sends review request via Upwork messaging:
     - "Thanks for working together! If you're happy with the result, I'd really appreciate a review — it helps a lot."
   - Send within 24 hours of project close
4. **Rick** leaves a review for the client (builds goodwill)
5. **Rick** updates HubSpot → "Upwork — Closed Won"
6. **Rick** sends off-platform follow-up (email, only AFTER project closes on Upwork):
   - "If you ever need anything else or know someone who does, I'm always here."
   - Include link to LeadsPanther site for retainer info

### Deliverables
- Final deliverable handed off
- All milestones paid
- Review requested (and left for client)
- HubSpot deal closed
- Off-platform follow-up sent

---

## Post-Project: Skill Extraction

### Steps
1. **Devin** evaluates: is any part of this build reusable?
2. If yes:
   - Extract the reusable core into a deployable skill
   - Document the skill (inputs, outputs, configuration)
   - Add to skill library
3. Log in workspace memory:
   - Project type, client industry, deliverable, tools used, revenue, time spent
   - This data feeds future scoping and pricing

### Deliverables
- Reusable skill extracted (if applicable)
- Project logged in memory

---

## QA Checklist

- [ ] Proposal under 200 words, references specific job post details
- [ ] Scope confirmed in writing before contract creation
- [ ] Milestones structured correctly (30/50/20 for $1K+)
- [ ] All communication on Upwork platform until project closes
- [ ] Deliverable tested end-to-end before submission
- [ ] Documentation included with delivery
- [ ] Review requested within 24 hours of close
- [ ] Review left for client
- [ ] HubSpot deal updated at each stage
- [ ] Skill extraction evaluated

---

## Agent Responsibilities

| Agent | Role |
|-------|------|
| Rick | Prospecting, proposals, scoping calls, contract creation, client comms, review collection, upsell |
| Devin | Build, testing, documentation, handoff, skill extraction |
| Alfred | Monitors project timelines, escalates if milestones are late |

---

## Anti-Patterns (Do NOT)

- Do NOT communicate off-platform before the project closes on Upwork.
- Do NOT accept projects under $500 (time vs. revenue doesn't work).
- Do NOT skip the review request. Every project must produce a review.
- Do NOT do free scope expansion. New scope = new milestone = new payment.
- Do NOT let milestones sit unsubmitted for more than 24 hours after completion.