Documentação / Pilot Status --- Branding Guide

Pilot Status --- Branding Guide

Entrar

Pilot Status --- Branding Guide

1. Brand Essence

Pilot Status is the control tower for message automation and delivery visibility (currently via WhatsApp). It transforms technical infrastructure into a structured aviation universe.

Core Metaphor: - Pilot Status = Control Tower / Airport Infrastructure - Project = Airline - WhatsApp Number = Aircraft - Message = Flight - Template = Flight Plan - Webhook = Radar - Logs = Black Box - TEST = Flight Simulator - PRODUCTION = Real Airspace


2. Brand Positioning

Pilot Status is not "just another messaging API".

It is: > Flight control infrastructure for mission‑critical notifications.

Target Audience: - Indie hackers - Solo founders - Node.js developers - Brazilian micro SaaS builders

Tone: - Technical - Confident - Minimal - Structured - Operational

Avoid: - Childish aviation jokes - Overly playful tone - Mixing metaphors (no rockets, ships, etc.)


3. Core Terminology Mapping

| Technical Feature | Branding Term |

|------------------|--------------| Project | Airline | | Multi-Projects | Multiple Airlines | | WhatsApp Number | Aircraft | | Platform Number | Shared Aircraft | | User Number | Private Aircraft | | Template | Flight Plan | | Send Message | Authorize Takeoff | | Queue | Runway Queue | | Sent | In Flight | | Delivered | Landed | | Read | Confirmed by Destination | | Failed | Flight Cancelled | | Logs | Black Box | | Webhook | Radar Endpoint | | TEST | Flight Simulator | | PRODUCTION | Real Airspace |


4. UX Copy Examples

Adding a Number

"Add a new aircraft to your airline."

Sending a Message

"Authorize takeoff for flight PS-4821."

Status Updates

  • 🟡 Awaiting Runway Clearance
  • 🔵 In Flight
  • 🟢 Landed Successfully
  • 🔴 Flight Cancelled

Webhook Configuration

"Configure your Radar Endpoint to receive incoming signals."

Environment Notice

"Your airline is currently operating in the Flight Simulator. Request authorization to enter Real Airspace."


5. Visual Identity

Design Direction

  • Dark cockpit aesthetic
  • High contrast
  • Operational dashboards
  • Clean grid layouts

Color System

Primary Background: #0B0F14 (Cockpit Black) Success: #22C55E (Landing Green) Info: #3B82F6 (Flight Blue) Warning: #F59E0B (Runway Amber) Error: #EF4444 (Alert Red)

UI Inspiration

  • Aviation dashboards
  • Control panels
  • Radar screens
  • Minimal flight instrumentation

6. Iconography

Icons should be: - Minimal - Line-based - Technical - Structured

Recommended motifs: - Control tower silhouette - Aircraft outline - Radar waves - Runway markers


7. Voice & Messaging Guidelines

Use operational language: - "Authorize" - "Monitor" - "Execute" - "Deploy" - "Validate" - "Confirm"

Avoid casual language: - "Hey there" - "Boom" - "Magic" - "Super easy haha"

The system should feel precise, not playful.


8. Product Narrative

Pilot Status is the airport. Your projects are airlines. Your numbers are aircraft. Your messages are flights. Your logs are black boxes. Your webhook is radar.

Nothing takes off without authorization. Nothing lands without monitoring.


9. Implementation Guidelines for AI Tools

When applying this branding:

  1. Replace technical nouns with aviation equivalents where appropriate.
  2. Keep API documentation technical --- branding applies mainly to UI and product copy.
  3. Preserve clarity over metaphor.
  4. Never sacrifice usability for storytelling.
  5. Keep terminology consistent across dashboard, landing page, and documentation.

10. Expansion Rules

If new features are added:

  • Analytics → Air Traffic Analytics
  • Rate Limits → Runway Capacity
  • Retry System → Autopilot Retry
  • Bulk Sending → Fleet Dispatch

All future features must remain consistent within the aviation ecosystem.


End of Branding Guide