Skip to content

COPYWRITING_GUIDE.md

Latest commit

 

History

History
74 lines (53 loc) · 2.64 KB

COPYWRITING_GUIDE.md

File metadata and controls

74 lines (53 loc) · 2.64 KB
Raw

TalentTrust Copywriting Guide

Overview

This guide ensures all user-facing copy is clear, consistent, and non-technical. We avoid implying guarantees unless they're accurate and use language that resonates with both freelancers and clients.

Tone & Voice

  • Clear: Use simple, direct language
  • Reassuring: Focus on security and trust without overclaiming
  • Helpful: Explain features in terms of user benefits
  • Respectful: Acknowledge the value of both freelancers' and clients' time

Key Terms Glossary

Escrow

User-friendly definition: Money held safely until work is completed and approved.

Why this matters: End users don't need to understand financial or technical mechanisms. They need to know their money is safe.

Usage guidelines:

  • ✓ "Your money is held in escrow until you approve the work"
  • ✗ "Escrowed funds are managed by smart contracts"

Milestone

User-friendly definition: A project checkpoint where payment is held until you approve the work.

Why this matters: Helps users understand that they can break projects into stages with built-in checkpoints for quality assurance.

Usage guidelines:

  • ✓ "Complete each milestone and get paid when you approve it"
  • ✗ "Deploy milestone smart contracts to the blockchain"

Release

User-friendly definition: When approved work is finished, the payment goes to the freelancer.

Why this matters: Clear action word that describes the outcome users care about - getting paid or paying for completed work.

Usage guidelines:

  • ✓ "Release payment once you're happy with the work"
  • ✗ "Execute transfer of escrowed funds"

Copy Examples

Success Scenarios

  • ✓ "Your money is protected at every step"
  • ✓ "Get paid when your work is approved"
  • ✓ "Breaks projects into manageable stages with built-in quality checks"

Avoid

  • ✗ "Instant payments" (we can't guarantee this)
  • ✗ "Always secure" (no system is 100% secure)
  • ✗ "Eliminated middlemen" (we ARE a service provider)
  • ✗ "Blockchain powered" (technical jargon users don't understand)

Consistency Rules

  1. Address users directly - Use "you" language
  2. Focus on benefits - What problem does this solve?
  3. Be specific - Avoid vague marketing language
  4. Avoid technical terms - Explain in user terms instead
  5. No guarantees - Use "helps protect", "works to ensure", etc., not absolute claims

Audit Checklist

Before launching new copy:

  • Does it avoid technical jargon?
  • Does it speak to user benefits?
  • Is it consistent with other copy?
  • Does it avoid false guarantees?
  • Would a non-technical user understand it?