hiring

What this skill does

# Hiring Technical Help

The most expensive developer is the cheap one who breaks things. This skill helps you decide when to hire vs. use AI tools, find and vet contractors, and manage the founder-developer relationship — even if you can't evaluate code yourself.

**This skill is for hiring and managing technical people.** For writing specs contractors can build from, use **plan**. For trying AI tools before hiring, use **build**. For legal contracts and IP protection, use **legal**.

## Core Principles

- Hire for the problem, not the role. Define what you need done before you look for who can do it.
- A great contractor beats a mediocre full-time hire every time at this stage.
- You can't evaluate code, but you can evaluate communication, reliability, and results.
- The most expensive developer is the cheap one who breaks things. Budget for quality.
- AI tools have moved the line. Many things that used to require hiring now don't.

## When to Hire vs. When to Use AI Tools

### You Do NOT Need to Hire If:

- You need a landing page → Use Lovable, Framer, or Webflow
- You need a CRUD app (create, read, update, delete data) → Use Claude Code, Lovable, or Replit
- You need to integrate Stripe → Tell AI to do it (see payments)
- You need basic auth → AI tools handle this well
- You need UI polish → AI + design system handles 80% of this
- You need simple bug fixes → Describe the bug to Claude Code

### You DO Need to Hire When:

- **Complex integrations** — Connecting to enterprise APIs with poor documentation
- **Performance at scale** — Your app is slow under load and AI-generated fixes aren't working
- **Data migrations** — Moving from one database or architecture to another
- **Security audit** — You need someone to verify your AI-generated code is secure
- **Native mobile apps** — AI tools are weaker here (improving, but still)
- **Infrastructure you don't understand** — Something is broken in production and you can't debug it
- **Ongoing maintenance** — You're spending more time fixing than building

### Decision Framework

```
Do I need to hire?
1. Can I describe the task clearly enough for an AI tool? → Try AI first
2. Did AI fail or produce something that doesn't work? → Try a different AI prompt
3. Still stuck after 2-3 serious attempts? → Time to hire
4. Is this a one-time task or ongoing? → One-time = contractor. Ongoing = consider part-time.
```

**Tell AI:**
```
I'm trying to decide if I need to hire a developer. Here's what I need done:
[describe the task]

I've tried: [what AI tools you used, what happened]

Help me decide: can this be solved with a better prompt or approach,
or do I genuinely need a human developer? If I need to hire,
what type (freelance contractor, part-time dev, agency)?
```

---

## Types of Technical Help

| Type | Cost | Best For | Where to Find |
|------|------|----------|---------------|
| **Freelance contractor** | $50-150/hr | One-time tasks, specific features, bug fixes | Upwork, Toptal, referrals |
| **Part-time developer** | $2-6K/mo | Ongoing development, 10-20 hrs/week | Indie communities, referrals |
| **Fractional CTO** | $3-8K/mo | Architecture decisions, code review, hiring other devs | Toptal, referrals, FounderPath |
| **Dev agency** | $5-20K/project | Full builds, redesigns | Clutch.co, referrals |
| **Technical co-founder** | Equity | Building the company together, long-term | Co-founder matching, network |

**For most solo bootstrapped founders: Start with a freelance contractor.**

---

## Finding Good Developers

### Where to Look (Ranked by Quality)

1. **Personal referrals** — Ask other founders: "Who built your product?" Best source by far.
2. **Indie communities** — Indie Hackers, r/forhire, Twitter/X developer community. Developers here understand SaaS.
3. **Toptal** — Pre-vetted, expensive ($80-150+/hr), but high quality and low risk.
4. **Upwork** — Huge pool, variable quality. You need to vet carefully. More on this below.
5. **Arc.dev, Gun.io, Lemon.io** — Curated freelancer platforms. Mid-range pricing.
6. **Agency** — Good for well-defined projects. Expensive. You lose the direct relationship.

### Red Flags When Evaluating

- **No portfolio or GitHub** — They should be able to show you work they've done
- **Can't explain things simply** — If they use jargon to answer simple questions, they'll be hard to work with
- **"I can build anything"** — Specialists outperform generalists. Look for experience with your stack
- **No questions about your project** — Good developers ask questions before estimating
- **Price way below market** — $15-25/hr for a "senior developer" means they're either lying about experience or in a situation where communication overhead will eat the savings
- **Won't do a small paid trial** — The best test is a real task (see below)

### Green Flags

- They've built SaaS products before (not just websites or WordPress)
- They ask clarifying questions about requirements
- They push back on bad ideas ("You don't need that. Here's a simpler approach.")
- They communicate proactively ("Here's my progress. I'm blocked on X.")
- They have experience with your stack (React, Next.js, Supabase, whatever you're using)
- They can show you something they built that works and looks good

---

## The Paid Trial: Best Hiring Strategy

Never hire based on interviews alone. Do a paid trial.

### How It Works

1. Pick a real but self-contained task from your backlog (a bug fix, a small feature, an integration)
2. Write a clear brief (see Writing a Job Brief below)
3. Pay them their normal rate for 5-10 hours of work
4. Evaluate the result

### What You're Evaluating

- **Communication** — Did they ask clarifying questions? Did they update you on progress?
- **Speed** — How long did it take relative to their estimate?
- **Quality** — Does it work? Does it look right? Did they test it?
- **Independence** — Did they figure things out on their own or need constant hand-holding?
- **Code quality** — You can't read code, but you can: (a) ask Claude Code to review it, (b) ask another developer to glance at it, (c) check if it works without bugs

**Tell AI:**
```
Review this code from a contractor I'm evaluating. Check for:
- Obvious bugs or issues
- Security problems
- Code quality and readability
- Whether it follows the existing codebase patterns
[paste code or point to files]
```

---

## Writing a Job Brief

A good brief gets good candidates. A vague brief gets time-wasters.

### Template

```
# [Task Name]

## What I Need
[2-3 sentences describing the outcome you want. Focus on WHAT, not HOW.]

## Current Setup
- App built with: [framework, e.g., Next.js + Supabase]
- Hosted on: [e.g., Vercel]
- Repo: [GitHub link — you'll share after NDA/agreement]

## Specific Requirements
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]

## What "Done" Looks Like
- [Acceptance criteria 1]
- [Acceptance criteria 2]
- [Acceptance criteria 3]

## Timeline
[When do you need this done?]

## Budget
[Your budget range, or "Tell me your estimate based on this brief"]

## To Apply
Tell me:
1. Have you built something similar before? Show me.
2. How would you approach this?
3. What's your estimated time and cost?
4. What questions do you have?
```

**Tell AI:**
```
Help me write a job brief for a freelance developer. I need:
[describe the task in plain English]
My app is built with [stack]. Format it as a clear brief that
a contractor can estimate from.
```

---

## Managing Contractors

### Communication Cadence

- **Short tasks (< 1 week):** Async updates. Ask for a progress update halfway through.
- **Ongoing work:** Weekly 15-minute sync call + daily async updates in Slack/email.
- **Complex projects:** Start with a kickoff call. Weekly demos of work-in-progress.

### Tools

| Purpose | Tool |
|---------|------|
| Communication | Slack (channel for the project) or email |
| Task tracking | Linear, GitHub Issues, or even a shared doc |
| Code access | GitHub (add them as a collaborator with limit