hiring-contractors · v1.0.0 · 2026-06-10 · sha256 928480318dcf76e6

hiring-contractors v1.0.0A

Immutable. This exact content is served forever at /api/v1/blob/928480318dcf76e6.

---
name: hiring-contractors
description: >-
  Hire and manage contractors for SaaS startups — where to find them, how to
  structure engagements, IP assignment, rates by role, and management practices
  that produce quality work without full-time overhead. Use when hiring freelance
  developers, designers, writers, or any contract talent. Triggers on: "hire
  contractor", "freelance developer", "contract work", "outsource development",
  "find a designer", "contract vs employee", or any contractor hiring request.
license: MIT
compatibility: Claude Code, Cursor, Codex, Hermes, Windsurf, OpenCode, Gemini CLI, Copilot, Zed, VS Code, Goose
metadata:
  version: "1.0.0"
  author: LeadMagic
  category: founder-led
  tags: [hiring, contractors, freelance, outsourcing, startup]
  frameworks:
    - "Freelance Talent Management"
    - "Upwork Enterprise Patterns"
    - "Paul Graham — Do Things That Do Not Scale"
  related_skills: [hiring-agencies, sales-team-building, building-saas, solo-founder-gtm]
---

# Hiring Contractors

## Overview

Contractors give you talent without full-time commitment. Done right, they
accelerate product development at a fraction of the cost of a bad full-time
hire. Done wrong, you pay for code you don't own and work you can't use.

This skill covers sourcing, structuring engagements, IP protection, rate
negotiation, and management practices that make contractor relationships
productive rather than painful.

## Frameworks Referenced

This skill is grounded in public frameworks and source material relevant to the task:

- **Freelance Talent Management.** Use the relevant method or published guidance where it improves the requested deliverable; do not cite it as decoration.
- **Upwork Enterprise Patterns.** Use the relevant method or published guidance where it improves the requested deliverable; do not cite it as decoration.
- **Paul Graham — Do Things That Do Not Scale.** Use the relevant method or published guidance where it improves the requested deliverable; do not cite it as decoration.

## When to Use

- "Hire a freelance developer"
- "Find a contractor for my SaaS"
- "Contract vs full-time employee"
- "How much should I pay a contractor?"
- "Where to find freelance talent"
- "Structure a contractor agreement"
- "Manage remote contractors"

## Step-by-Step Process

### Phase 1: When to Use Contractors

**Good for:**
- Building MVP or prototype (no long-term commitment needed)
- Specialized work (DevOps, security audit, complex integration)
- Capacity overflow (you have more work than your team can handle)
- Testing a role before hiring full-time
- Work with clear deliverables and end dates

**Not good for:**
- Core product development you'll need to maintain long-term
- Roles requiring deep domain knowledge of your business
- Ongoing customer-facing work
- Anything without a clear scope

### Phase 2: Where to Find Them

| Source | Best For | Quality | Cost |
|---|---|---|---|
| Upwork | General freelance, quick hires | Variable | $30-150/hr |
| Toptal | Top-tier developers, designers | High, vetted | $80-200/hr |
| Gun.io | Senior engineers | High | $100-200/hr |
| LinkedIn / Network | Referrals, warm intros | Highest | Negotiable |
| Twitter/X | Niche specialists, indie devs | Variable | Negotiable |
| Arc.dev | Remote developers | High | $60-120/hr |

### Phase 3: Rate Benchmarks (2026)

| Role | Junior | Mid | Senior |
|---|---|---|---|
| Full-stack developer | $40-75/hr | $75-125/hr | $125-200/hr |
| Frontend developer | $35-65/hr | $65-100/hr | $100-150/hr |
| Designer (UI/UX) | $40-70/hr | $70-120/hr | $120-180/hr |
| DevOps / SRE | $60-100/hr | $100-150/hr | $150-250/hr |
| Content writer | $30-60/hr | $60-100/hr | $100-150/hr |
| Data analyst | $50-80/hr | $80-130/hr | $130-200/hr |

Rates vary by geography, experience, and demand. Top-tier contractors often
cost more per hour than equivalent full-time employees — but you pay only for
hours worked, with zero benefits, equipment, or severance costs.

### Phase 4: Engagement Structure

**The Contract (minimum requirements):**
1. Scope of work — specific deliverables, not vague descriptions
2. Timeline — start date, milestones, completion date
3. Payment terms — hourly or fixed-price, payment schedule
4. IP assignment — contractor assigns all work product to your company. THIS
   IS NON-NEGOTIABLE. Missing IP assignment can kill an acquisition later.
5. Confidentiality — they don't share your business details
6. Termination — either party can end with X days notice

**Platforms that handle this:** Upwork (built-in contracts), Deel (global
compliance, payments), Gusto (US contractors).

### Phase 5: Management Practices

- **Start with a paid test.** A small, paid project before a large engagement.
  ~$500-2,000 to validate quality, communication, and reliability.
- **Clear deliverables, not hourly tracking.** "Build the onboarding flow as
  specified in this Figma file" beats "work 40 hours on onboarding."
- **Async communication over meetings.** Contractors are paid by the hour.
  Every meeting costs money. Use Loom, written specs, and async check-ins.
- **Code review everything.** Don't merge contractor code without review.
  This isn't about trust — it's about maintainability.
- **Documentation as a deliverable.** If they build it, they document it.
  Otherwise you own code you can't maintain.

## Output Format

Contractor engagement plan with: role spec, sourcing strategy, rate range,
contract template highlights, test project scope, and management cadence.


## Quality Check

Before delivering, verify:
- [ ] All required sections are complete
- [ ] Output matches the user's stated need
- [ ] Named frameworks are cited for key recommendations
- [ ] No vague claims — every recommendation has a specific action
- [ ] Deliverable is ready for operational use, not just conceptual

## Common Pitfalls

1. **No IP assignment clause.** The most expensive mistake. Without it, the
   contractor owns the work. Fix this in the contract before work begins.

2. **Vague scope.** "Improve the app" is not a scope. "Add single sign-on via
   Google OAuth with these 5 specific requirements" is.

3. **Hiring the cheapest option.** A $15/hr contractor who takes 4x as long
   and produces unmaintainable code costs more than a $100/hr contractor who
   ships correctly the first time.

4. **No code review.** Contractor code without review becomes technical debt
   your team can't touch. Review everything before merge.

5. **Treating contractors like employees.** They have other clients. They don't
   attend your standups unless you're paying for that time. Set clear
   expectations and respect boundaries.

## Execution Artifacts

- `references/framework-notes.md` — Named frameworks and reference tables
- `templates/output-template.md` — Deliverable shell for agent output
- `scripts/check-output.py` — Lightweight deliverable validator

## Related Skills

- **hiring-agencies**: When to use agencies instead of individual contractors
- **building-saas**: SaaS development and architecture
- **solo-founder-gtm**: Building with limited resources