Templates are scaffolding, not the finished house
A template saves structure: opener, proof, plan, question, close. The client should see their project in line one and milestones that match their post. If you can swap only the client name and send, it is still spam — just organized spam.
Ten formats by job type
1. Web development (fixed or hourly)
Opener: restate outcome + stack constraint. Proof: one similar build with metric (launch date, performance, uptime). Plan: discovery → build → QA → handoff. Question: access, staging, or API constraints. Close: invite to a ten-minute scope call.
2. Shopify / e-commerce
Lead with revenue or conversion angle. Mention theme, apps, and data migration if relevant. Milestones: audit, implement, test checkout, monitor post-launch. Ask about SKU volume and payment stack.
3. UI/UX and product design
Reference users and flows, not “beautiful UI.” Offer audit of their current funnel or one screen critique. Deliverables: wireframes, design system tokens, handoff specs. Question: Figma access and decision-makers.
4. Copywriting and content
Show audience fluency in line one. Proof: niche samples or open rates if allowed. Plan: research → outline approval → draft → revisions. Question: brand voice references and approval chain.
5. Virtual assistant / operations
Emphasize systems: tools, time zones, turnaround SLAs. Proof: calendars managed, inboxes zeroed, SOPs built. Security note for credentials. Question: stack (Notion, Slack, etc.) and weekly rhythm.
6. Performance marketing (paid social / search)
Metric-first opener (CAC, ROAS, MER). Plan: audit → test plan → scale rules. Clarify ad account access and creative ownership. Avoid promising specific ROAS without data.
7. SEO and content strategy
Technical + content angles separated. Milestones: crawl audit, keyword map, content briefs, implementation. Question: CMS access and historical penalty context.
8. Video editing and motion
Reference pacing, platform (YouTube Shorts vs long form), and asset delivery format. Proof: links with similar tone. Question: raw footage location and revision rounds cap.
9. Customer support and success
Tone-matched to B2B vs consumer. Proof: CSAT, response time improvements. Plan: macros, help center, escalation paths. Question: channels and tooling integrations.
10. Data, automation, and integrations
Name systems (Zapier, Make, custom API). Risk section on data mapping and error handling. Milestones: discovery diagram → prototype → production hardening. Question: source-of-truth systems.
Workflow: generate angles, then pick one
Draft multiple variants from the same post, edit for voice, preview on the Upwork form, send the angle that sounds like you — not the one that sounds most “polished” but generic. Pair complex jobs with a structured landing page so the letter stays short and the scope stays clear.
Customization rules so templates do not sound fake
Swap client nouns, metrics, and deadlines every time. Keep your rhythm, not your sentences. One clarifying question proves you read the post. Templates fail when the opener could apply to a thousand jobs — pass the “replace client name” test and still sounds specific.