# 07 · Modules

Four modules, each a phase in the recruitment process, each carrying one signal color.

**Process line**: Blueprint. Scout. Reach. Meet.
**Outcome line**: We match. You hire.

## 01 · Blueprint · Direction

| | |
|---|---|
| Color | Blueprint Blue `#2E61E1` |
| Position in mark | Top-left |
| Role | Direction |
| What it does | Turns intake into search specs and company DNA |
| Outcome | Vacancy to brief in under 15 minutes |
| Module page | Page 44 of master PDF |

Use cases:
- Intake interview parsing (audio → structured brief)
- Criteria templating from past hires
- Company-DNA fingerprint (culture, working style, tech stack)
- Search spec generation

## 02 · Scout · Intelligence

| | |
|---|---|
| Color | Scout Purple `#7D3CED` |
| Position in mark | Top-right |
| Role | Intelligence |
| What it does | Sources, verifies, ranks across 130+ data sources |
| Outcome | 130+ sources, three-layer scoring |
| Module page | Page 45 of master PDF |

Use cases:
- Multi-source candidate sourcing (LinkedIn, GitHub, niche DBs)
- Three-layer scoring (skills match, fit match, motivation match)
- Verification across data points
- Real-time pipeline ranking

## 03 · Reach · Activity

| | |
|---|---|
| Color | Reach Magenta `#BF27D2` |
| Position in mark | Bottom-left |
| Role | Activity |
| What it does | Multichannel outreach in the client's voice |
| Outcome | Outreach within hours, response classification, adaptive follow-up |
| Module page | Page 46 of master PDF |

Use cases:
- Email + LinkedIn + WhatsApp sequenced outreach
- Voice cloning (client tone, not generic)
- Response classifier (Positive / Not now / Declined / Red flag / No action)
- Adaptive follow-up cadence per channel

## 04 · Meet · Human

| | |
|---|---|
| Color | Meet Pink `#EB77FF` |
| Position in mark | Bottom-right |
| Role | Human |
| What it does | Books the conversation, hands over to the recruiter |
| Outcome | Calendar booked, brief auto-shared |
| Module page | Page 47 of master PDF |

Use cases:
- Calendar scheduling (no Calendly needed)
- Brief auto-share to candidate
- Recruiter handover summary
- Pipeline tracking through to hire decision

## Loop

The four modules form a **loop**, not a funnel. Output of Meet becomes new criteria for Blueprint:

```
Blueprint → Scout → Reach → Meet
    ↑                          │
    └──────────────────────────┘
```

Hire decisions feed back into the model: what worked, what didn't, refine search specs for next cycle.

## When to use which module name

- In product UI: always use the module name when referring to that surface ("Open in Blueprint", "View in Scout")
- In sales decks: use module names + role ("Blueprint, our direction module")
- In marketing copy: process line ("Blueprint. Scout. Reach. Meet.") followed by outcome ("We match. You hire.")
- Never translate module names. Never abbreviate ("BP" → no, "Blueprint" → yes)

## Module color usage rules

- Each module surface uses its own color for accents and action elements
- Modules can be visually neighbored (Blueprint + Scout in a single hero) but signal colors should not overlap proximally without dark/white spacing
- Capsule decoration in marketing assets should follow color order: Blueprint top-left → Scout top-right → Reach bottom-left → Meet bottom-right