TrackingTime — Brand Voice & Positioning Guidelines

Status: Canonical. Supersedes prior positioning material in the knowledge base where they conflict. Language of this document: English. Language for public surfaces: English international. Spanish remains for internal sales/CS enablement that already lives in that language. Out of scope: Visual system (colors, typography, logos, layout). Defined separately.

---

1. Positioning — one sentence

TrackingTime is the operational back office for agencies and professional services — one workspace where time tracking, retainers, time off with policies, approvals, payroll, expenses, and client reporting live together. Not a timer with things bolted on.

Internal reference line: "We are the system where an agency runs its day — not the app that reminds it to start a timer."

---

2. Category thesis

We move deliberately from the "time tracker" frame to the "operational back office" frame.

The time tracker category is already claimed by Toggl (UX), Clockify (free), and Timely (AI). Competing there is fighting on their ground. "Operational back office for agencies" is new territory we win by construction — we have all seven pieces, the competitors do not.

In all public surfaces: lead with the back-office frame. The time-tracking cluster remains valid for SEO discovery only — it is not the primary commercial category.

---

3. Audience

Primary ICP

Agencies of 5–50 people. Creative, digital, consulting, marketing.

Secondary

Consultancies and professional services — legal, accounting, architecture.

Tertiary

Microsoft 365 teams that need tracking inside their stack.

Who we are deliberately not

---

4. Two defensible differentiators

Everything else is hygiene. These two are the only things no competitor has well. They appear on every public surface with a "No workarounds" tag.

Real retainers

Pace tracking, rollover, burn alerts, rates by person or task. Toggl, Harvest, Timely, and Clockify do not have these as a complete product.

Time off with configurable policies

Multi-country, accrual rules, unlimited types, approval workflows. Internal framing: Not a calendar widget — a policy engine.

---

5. Anti-positioning

Four things we do not do, and we communicate actively:

Summary line on any material: "No surveillance. No pricing puzzles."

---

6. Wedges

Wedges are contact points with specific segments, not master positioning.

---

7. Voice

7.1 Base tone

Operational calm. Competent without shouting. Editorial, not startup. Professional without being corporate. Friendly without being playful.

Useful analogies: The Economist before TechCrunch. Basecamp before Linear. A product built by people who understand your operation — not a pitch deck.

7.2 Register

Clear international English. No SaaS jargon when a common word works the same. No hollow superlatives ("best-in-class", "world-class", "industry-leading"). No hype.

We prefer:

7.3 Recurring language decisions

Use:

Avoid:

7.4 Copy rules

7.5 Competitor treatment

We do not name competitors on the homepage or in primary marketing copy. We frame them by category ("another time tracker") or by contrast ("real retainers, not fake budgets").

On comparison and alternatives pages we are honest about the rival's strengths. This is both an ethical principle and an SEO strategy — AI Overviews penalize biased comparisons.

When we address surveillance-style tools (Hubstaff, Time Doctor), we do it with positioning, not contempt. We are the option for teams that do not want surveillance. Contempt signals insecurity. Clarity about our place signals confidence.

---

8. Message architecture

Every public surface — home, landing, email, deck — follows this hierarchy:

  1. Who we are for (agencies and professional services).
  2. What we are (one workspace / back office).
  3. What we cover (time, retainers, time off, approvals, payroll, client reporting).
  4. What makes us unique (real retainers + time off with policies).
  5. What we reject (no surveillance, no pricing puzzles).
  6. Where we live (Microsoft, Jira, Asana, 60+ tools).
  7. How we charge (plans tied to stages).

Not every surface needs all seven levels. No surface inverts the order.

---

9. Surface application

Homepage. Lead with the back-office frame. Use all seven levels of the message architecture. Microsoft 365 is a featured section. Pricing appears as clarity proof, not detail. Competitors are never named.

Landing pages. Can emphasize a single wedge (Microsoft 365, EU compliance, a specific segment). The back-office frame still applies. The two defensible differentiators still carry the "No workarounds" tag when referenced.

Comparison / alternatives pages. Competitors can be named. We lead with what the rival does well and position ourselves by contrast — never by dismissal.

Email / outbound. Same register as landing. No hype superlatives. Specific pain language is welcome. Keep lists to three or four.

Sales decks. Can carry more depth and internal language, but cannot invert the message hierarchy or dilute anti-positioning.

Product UI copy. Same tone. Prefer concrete verbs. Never adopt surveillance-adjacent language.

---

10. The five ten-second pitches

Any team member should be able to deliver these without thinking.

All five are true, specific, and none is defensive.

---

11. Language policy

---

12. Pricing communication

---

13. PM-positioning rule

A recurring trap — handle carefully.

---

14. Quality check — how to review a draft

Before any piece of public copy ships, it should pass this check:

Any "yes" on the first, fourth, fifth, sixth, or seventh — rewrite.

---

15. Proof points — approved for public use

These claims are validated and cleared for homepage, landing pages, emails, and decks. Use them in the register of §7 — no superlatives attached.

Adoption

Third-party validation

Testimonials on file (already cleared by appearing on homepage)

New testimonials must come from a verifiable source (G2, Capterra, nachonacho, or a direct customer agreement) and name role or company function. Anonymous quotes are not used.

Claim hygiene

---

16. Pending items (to resolve, not to invent)

⚠️ Nota operativa: estos ítems están sin resolver intencionalmente. Si necesitás determinar algo sobre cualquiera de estas secciones para producir contenido o tomar decisiones de positioning, consultá primero. No asumir, no inventar.

---

17. Source hierarchy

When this document and any other material disagree, this document wins for voice, tone, positioning frame, and anti-positioning.

Supporting material remains valid for product detail:

Where the older knowledge-base calls TrackingTime a "time tracking platform" or frames Project Management as a commercial category, this document supersedes it.