jake/clawdbot-workspace
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
clawdbot-workspace/upwork-pipeline-design.md

7.0 KiB
Raw Blame History

Upwork Spec-First Pipeline — "Build It Before They Ask"

Overview

Automated system that scans Upwork 3-4x daily, identifies high-value jobs we can pre-fulfill, builds impressive proof-of-work, submits protected proposals, and delivers on hire.

Phase 1: SCAN (Automated, Cron-based)

Search Queries (rotate through these)

openclaw OR clawdbot OR "ai agent"
"mcp server" OR "model context protocol"
"ai automation" OR "ai assistant" setup
"discord bot" OR "telegram bot" OR "slack bot" AI
"web scraper" OR "data pipeline" automation
"landing page" react OR nextjs
"chrome extension" AI
"api integration" node OR typescript

Scan Schedule

  • 6 AM EST — catch overnight posts (international clients)
  • 12 PM EST — midday sweep
  • 6 PM EST — catch afternoon posts
  • 10 PM EST — late sweep for next-day early bird advantage

Scoring Algorithm (auto-rank each job)

Signal Points
Client $50K+ spent +30
Client $10K+ spent +15
Client 4.5+ rating +20
Payment verified +10
Less than 5 proposals +25
Less than 10 proposals +15
Posted < 2 hours ago +20
Posted < 6 hours ago +10
Budget $50+/hr or $1K+ fixed +25
Budget $30-50/hr or $500-1K fixed +10
We're a perfect skill match (Tier 1) +30
We're a strong match (Tier 2) +15
US/UK/CA/AU client +10
Code word in description (filters spam applicants) +15
Threshold: 80+ points = AUTO-BUILD
60-79 points = APPLY WITH STRONG LETTER
Below 60 = SKIP

Phase 2: BUILD (Spec Work — The Killer Differentiator)

What We Build Per Job Type

OpenClaw/Agent Setup Jobs

  • Complete SOUL.md + AGENTS.md + TOOLS.md config
  • 2-3 custom skills tailored to their use case
  • Cron job configs for their described workflows
  • Memory system scaffold
  • Delivery format: Screenshot of working agent chat + config files in private repo

MCP Server Jobs

  • Working server scaffold with 5-10 relevant tools
  • Zod-validated inputs, proper descriptions
  • README with architecture diagram
  • Delivery format: Screenshot of tool list + API test results

Web App / Landing Page Jobs

  • Working deployed prototype on our infrastructure
  • Responsive, dark mode, animations
  • Delivery format: Live URL (watermarked, "Built by MCPEngage — Demo") + screenshot

Bot / Automation Jobs

  • Working bot code with core functionality
  • Config file for their specific channels
  • Delivery format: Video recording of bot responding + code structure screenshot

Scraper / Data Jobs

  • Working scraper that pulls sample data
  • Formatted sample output (first 10 rows)
  • Delivery format: Sample data preview + architecture diagram

Build Time Targets

  • OpenClaw configs: 15-30 min (we know this cold)
  • MCP servers: 30-60 min (scaffold from templates)
  • Landing pages: 30-45 min
  • Bots: 20-40 min
  • Scrapers: 20-30 min

Phase 3: PROTECT (Show Don't Give)

Protection Strategies (by deliverable type)

Code Projects

  • Private GitHub repo — mentioned in proposal, access granted ONLY after contract starts
  • README with full feature list visible — they see WHAT it does
  • Architecture diagram attached — they see HOW it's built
  • Screenshot of passing tests — they see IT WORKS
  • They CANNOT clone, fork, or access the code pre-hire

Live Demos

  • Deployed on our infrastructure (Cloudflare Workers, Vercel, etc.)
  • Watermarked: "Demo — Built by MCPEngage for [Client Name]"
  • Time-limited: Demo URL expires after 7 days
  • Read-only: No export, no view-source that reveals proprietary logic
  • Rate-limited: Can't scrape or bulk-access

Data / Reports

  • Preview only: First 10 rows of 1000, blurred remaining
  • Watermarked PDF with "SAMPLE — Full report on contract"
  • Summary stats visible, raw data locked

Videos / Recordings

  • Screen recording of working product — 60-90 sec
  • Watermarked with our branding
  • No code visible in recording — only the UI/output
  • Uploaded as Upwork proposal attachment

The Pitch Template

Hi — I built this for you before applying.

[WHAT]: Brief description of what I built
[PROOF]: Screenshot / video / live demo link
[PROTECTION]: "Full source code + deployment transferred on contract start"

I specialize in [THEIR NEED] and have deployed [NUMBER] production instances.
Can start immediately. Happy to walk you through the demo on a call.

Phase 4: APPLY (Automated Proposal Submission)

Proposal Assembly

  1. Code word check — scan description for required keywords
  2. Rate selection — top 75% of their budget range (shows confidence, stays competitive)
  3. Cover letter — generated from template + job-specific details + spec work description
  4. Attachments — screenshots, architecture diagrams, sample outputs
  5. Submit — via browser tool automation

Connects Budget

  • Reserve 60+ Connects at all times
  • Auto-build jobs (80+ score): spend up to 24 Connects
  • Strong letter jobs (60-79): spend up to 16 Connects
  • Never go below 40 Connects reserve

Phase 5: DELIVER (Post-Hire Fulfillment)

On Contract Start

  1. Transfer private repo access to client
  2. Remove watermarks from demos
  3. Schedule kickoff call (if they want one)
  4. Set up milestone/hourly tracking

Delivery Standards

  • All code in a clean repo with README
  • Deployment instructions (step-by-step)
  • 1 week of post-delivery support included
  • Documentation for maintenance

Implementation Plan

Step 1: Cron Job (Scan)

  • Clawdbot cron job runs 4x daily
  • Searches Upwork via browser tool (logged-in session)
  • Scores and filters jobs
  • Posts top candidates to Discord (#upwork-pipeline or DM Jake)

Step 2: Decision Gate

  • Auto-build (80+ score): Buba starts building immediately, notifies Jake
  • Manual review (60-79): Posts to Jake for approval before applying
  • Skip (<60): Logged but no action

Step 3: Build + Apply

  • Sub-agent spawned for each build
  • Build completed → screenshots taken → proposal assembled → submitted
  • Jake notified with summary: "Applied to [JOB] at $XX/hr with [DELIVERABLE]"

Step 4: Monitor

  • Check proposal status daily
  • If client messages → notify Jake immediately
  • If interview requested → notify Jake + prep talking points

Revenue Targets

  • Week 1: Pipeline running, 5-10 applications/day
  • Week 2: First hires landing, $500-1K in contracts
  • Month 1: $2-5K/month steady from Upwork
  • Month 3: $5-10K/month with reputation + reviews building
  • Month 6: Top-rated profile, $10K+/month, premium rates

Tech Stack

  • Scanning: Clawdbot cron + browser tool
  • Building: Sub-agents (spawn for each build)
  • Hosting demos: Cloudflare Workers / Vercel / GitHub Pages
  • Repo management: GitHub (BusyBee3333 org, private repos)
  • Proposal submission: Browser tool (Upwork skill)
  • Notifications: Discord channel alerts
  • Tracking: Memory system (daily log of applications + outcomes)