Vamo Design Voice
03

Voice

Write like the changelog, everywhere.

The eight rules

Eight rules bind every surface that carries copy: the app, agent output, PDFs, decks, and the book itself. Each rule below pairs a violation with its rewrite.

01 No em dashes
DON'T

"GitHub activity — commits, reviews, releases — drives every result."

DO

GitHub activity drives every result: commits, reviews, releases.

02 No "not X, it's Y" contrast constructions
DON'T

"It's not another job board, it's a search engine for real work."

DO

Vamo is a search engine for developers, built on GitHub activity.

03 No branded aphorisms or slogans
DON'T

"Vamo: where signal meets talent."

DO

Vamo searches developers by their public GitHub activity.

04 Don't write about the reader
DON'T

"You're a smart recruiter, so you already know résumés only tell half the story."

DO

Rank results by commit history. Open a profile to see the evidence.

05 No throat-clearing
DON'T

"In today's fast-moving hiring landscape, speed matters. That's why we built..."

DO

Search runs on GitHub activity. Results return in seconds.

06 No infomercial claims. Real numbers, named customers
DON'T

"Sourcing that used to take all day now takes minutes."

DO

'3 hrs now takes 20 min.' Rich Moss, Candidate Labs

07 Never disparage the prior experience
DON'T

"Stop wasting hours in spreadsheets and clunky legacy sourcing tools."

DO

Import your existing lists. Sequences keep running unchanged.

08 · Candidates read this copy too

Describe personalization at the capability level. Never walk through outreach mechanics (variable tokens, message assembly, cadence) in enough detail to make a received email feel canned. The same rule binds hero art and screenshots.

DO · capability level
Cam Whiteside cam@vamo.app Initial

Your query engine work

Hi Ada, The note references their query engine work: your vectorized join executor caught our eye, and the role centers on exactly that kind of storage-layer performance. Worth a short call?
Cam Vamo
via work email
DON'T · mechanics exposed, the violation
Cam Whiteside cam@vamo.app Initial

Loved your work on {repo_name}

Hi {first_name}, I saw your work on {repo_name} and was impressed by {recent_commit}. We insert the repo name here so every email feels hand-written. Worth a short call?
Cam Vamo
No email found

Plain, direct, matter-of-fact. Source: recruiter-bot docs/changelog-authoring.md.