---
creationDate: 2026-04-21
type: person
relationship: contractor
company: Independent (freelance designer)
status: active
last_interaction: 2026-04-18
next_step: Review V2 mockups Friday
priority: medium
person_relationship_type: "contractor"
person_is_public_figure: false
person_journal_mention_count: 0
person_priority: "medium"
example: true
---

> **Example card.** Contractors need extra structure so tasks you delegate are crystal clear. The "MVD pattern" below (Source / Location / Shape / Channel) is the four fields that turn a vague task into something a contractor can execute without pinging you back. Replace with a real person when you set up your vault, or delete this file.

# Sam Patel (example)

*Freelance brand and product designer. 8 hours/week, project-based.*

**Role:** Brand systems, landing pages, light product UI
**Based:** Lisbon (UTC+0)
**How we met:** Referral from a previous colleague, January 2026.

## Contact
- Email: (placeholder)
- WhatsApp: (placeholder — async-first, voice notes welcome)
- Portfolio: (placeholder URL)

## How we work together
- Async-first. Loom + WhatsApp voice notes for context. Live calls only when stuck.
- Weekly kickoff Monday morning, weekly check-out Friday afternoon.
- Invoice monthly, paid net-15.

## Active projects
- Landing page V2 for the consulting practice (in flight, due late April)
- Brand kit refresh for Q3 (scoped, not started)

## Task delegation pattern (MVD: Minimum Viable Delegation)

Every task delegated to a contractor needs four fields explicit. This is the difference between a task they can ship and a task they have to ping you about.

| Field | What goes here | Example |
|---|---|---|
| **Source** | Where the input lives | Loom recording at <link>, or Figma file at <link>, or a written brief at <link> |
| **Location** | Where the output goes | New Figma frame, or a Google Doc named X, or pushed to GitHub branch Y |
| **Shape** | What "done" looks like | "3 hero variants, 1500x900px, copy lockable, ready for client review" |
| **Channel** | How they report back | "WhatsApp voice note when shipped, link in the channel" |

Tasks missing any of the four fields get sent back for enrichment before the contractor sees them. Codify the pattern by adding a personal rule in your CLAUDE.md once you have a few contractors.

## How this card auto-populates

Same as the maintainer card — journal mentions, meeting notes, and floor co-occurrence populate the frontmatter fields automatically as you use the system. Run `/second-brain-mapping` to refresh.
