Sales Enablement Kit & Content Piece

Worked example

(Product: Tempo — B2B time-tracking + capacity planning for 10–50-person creative agencies. Differentiator carried from Deliverables 1–2: Tempo is the only tracker built around agency capacity, not just billable hours — it tells you who's overbooked before the work slips, and the new AI forecast predicts it weeks out. Pillars: 1) See overload before it burns your team, 2) Capacity planning a non-finance owner can actually run, 3) Set up in an afternoon, not a quarter.)

Artifact A — Competitive Battlecard

vs. Toggl Track

• Where Toggl wins: Cheapest entry point ($9/user/mo), huge integration library, strong standalone stopwatch UX, well-known brand. Don't fight on raw price or integration count.
• Where Tempo wins: Toggl tracks past hours; Tempo plans future capacity. Toggl shows you a team logged 1,900 hours last month; Tempo shows you that Maya is booked to 140% next week and the client deck will slip — before it does. (Pillar 1.) Toggl's forecasting is a reporting add-on; Tempo's AI capacity forecast is the core product.
• Landmines to set (ask the prospect): "When you look at Toggl, can you see who's overbooked next week, or only how many hours were logged last week?" · "How far in advance does it warn you a project is going to slip?" · "Who on your team actually opens the reports — and do they trust the numbers enough to move work around?"
• Trap to avoid: Don't claim Tempo has more integrations or is cheaper — it isn't. Win on forward-looking capacity, not on the feature count.

vs. Harvest

• Where Harvest wins: Mature invoicing and expense tracking, trusted billing brand, deep QuickBooks/Xero ties. If the buyer's #1 pain is invoicing, acknowledge Harvest is strong there.
• Where Tempo wins: Harvest is a billing tool that happens to track time; Tempo is a capacity tool that happens to track time. Harvest answers "what do we invoice?" Tempo answers "can we even take this next project without burning the team?" (Pillars 1 & 2.) Harvest's capacity view is a static schedule grid; Tempo forecasts overload weeks out and an owner — not a finance lead — can run it in an afternoon (Pillar 3).
• Landmines to set: "Does Harvest tell you you're about to over-commit, or only bill for it after the fact?" · "How long did Harvest take to roll out, and who had to own it?" · "If a new project comes in Friday, can you tell by Monday whether you have the capacity?"
• Trap to avoid: Don't position against Harvest on invoicing — you'll lose. Move the conversation to capacity and overload, where Harvest is weak.

Objection handling (Objection → Reframe → Proof)

Note on the proofs below: every proof point is a logic/cost argument or a verifiable product fact — the kind a rep can defend live — not a pilot statistic. We're pre-launch, so we have no real retention or pilot numbers to cite, and inventing one would teach the rep to lie. Where an illustrative number would go, this card leaves a labeled placeholder instead of a fake fact (see the cost-math note on objection 1). This is the data-honesty rule from Instruction 3 in practice.

• "You're more expensive than Toggl." → "You're right that our per-seat price is higher — because we're not the same tool. Toggl tells you what already happened; we stop the $8k project from slipping and the senior designer from quitting. One missed deadline costs more than a year of the price difference." → Proof (cost math, not a stat): at $12/seat for a 12-person team that's ~$144/mo over Toggl's ~$108 — call it ~$430/year of difference; a single blown $8k project, or one senior hire you have to re-recruit, dwarfs that. The rep can do this arithmetic on the call with the prospect's own numbers — no claimed statistic required. (If/when we have pilot data, add it here labeled (illustrative — replace with real pilot data before this card ships) until it's measured — never present an unmeasured number as fact.)
• "We already use Harvest for everything." → "Most agencies we talk to want to keep their invoicing tool. Tempo isn't a billing replacement — it's the capacity layer Harvest doesn't have. You can run both; the time data even flows out to your billing." → Proof (verifiable product fact): Tempo exports to CSV/QuickBooks, so the rep can demo the export live and the prospect can see their own Harvest workflow stays intact — no need to cite how many customers "still invoice in Harvest," a number we couldn't back up anyway.
• "How do I know I can trust the AI forecast?" → "Fair — a forecast you don't trust is wallpaper. It doesn't make decisions; it flags risk and shows its work: which people, which projects, which weeks. You decide what to move." → Proof (verifiable product fact): every forecast links to the underlying bookings the rep can open on the call, so the prospect sees the math, not a black box. (Avoid quoting an "accuracy %" we haven't measured — let the visible bookings be the proof.)
• "Switching trackers means re-onboarding the whole team — not worth the disruption." → "That's the fear that keeps agencies stuck on a tool nobody likes. Tempo imports your existing Toggl/Harvest time data, and tracking works the same way your team already tracks. The new part is the capacity view owners see — your team's day barely changes." → Proof (verifiable product fact): CSV import from Toggl/Harvest is built in and the rep can show the import flow in the demo (Pillar 3) — the claim is checkable, not a "median setup is X" stat we can't yet support.

Artifact B — One-Page Product Summary

Tempo — See overload before it burns your team. The time tracker built for creative agencies that plan by people, not just hours.

Who it's for: Owners and ops leads at 10–50-person creative agencies (design, branding, digital, content studios) who juggle people across multiple client projects and keep getting surprised by overload. Who it's NOT for: Solo freelancers, agencies that only need invoicing, or 200+ person shops needing enterprise resource management.

Why agencies choose Tempo

(Same data-honesty rule as the battlecard: the proofs below are product capabilities, not pilot stats. Any number that looks like a measured outcome — "caught ~2/month," "median go-live is one afternoon" — is marked (illustrative) because we haven't measured it yet, and would be replaced with a real figure before this one-pager ships to prospects. Don't let a placeholder go out reading like a fact.)

1. See overload before it burns your team. Tempo flags who's booked past 100% — weeks ahead, not after the deadline slips. Proof: the AI capacity forecast warns 2–3 weeks out, and every flag links to the bookings behind it so you can see why. (illustrative target: agencies catch ~2 over-commitments/month before they hurt — replace with real pilot data before shipping)
2. Capacity planning an owner can actually run. No finance background needed — a visual board shows who's free, who's drowning, and what one moved deadline would fix. Proof: the whole weekly review runs from one board, no spreadsheet or finance lead required. (illustrative target: under 15 minutes — replace with measured data before shipping)
3. Set up in an afternoon, not a quarter. Import your existing Toggl or Harvest data; your team tracks the way they already do. Proof: CSV import from Toggl/Harvest is built in, so there's no manual re-entry. (illustrative target: median go-live in one afternoon — replace with measured onboarding data before shipping)

Tempo vs. the alternatives

	Tempo	Toggl	Harvest	Spreadsheet
Tracks hours	Yes	Yes	Yes	Manual
Forecasts overload weeks out	Yes (AI)	No	No	No
Owner can run it (no finance)	Yes	Partial	Partial	No
Setup time	An afternoon	Fast	Weeks	"Free" but endless

Pricing: $12/user/mo (annual) · AI capacity forecasting included · 14-day free trial · no card required. Next step: Start your team's free trial at tempo.app/start — import your Toggl/Harvest data and see your first capacity forecast the same day.

Artifact C — SEO Content Piece ("help, don't sell")

• Target search query (literal): "how to tell if my agency is overbooked"
• Search intent: Informational, problem-aware. The owner feels the chaos but isn't shopping for software yet — top of funnel.
• Primary keyword: agency overbooked / agency capacity warning signs
• Meta description: Five honest signs your creative agency is overbooked — and a 10-minute check to see how close to the edge your team really is.
• Title (= the searcher's question): How to Tell If Your Agency Is Overbooked (5 Warning Signs + a 10-Minute Check)

The post (draft, ~700 words):

Most agency owners don't find out they're overbooked until something breaks — a missed deadline, a great designer who quietly starts job-hunting, a client who stops replying. By then the damage is done. The good news: overload almost always sends warning signs weeks earlier. Here's how to read them, plus a 10-minute check you can run today without any new software.

1. Deadlines are slipping by "just a day or two" — often. One late deliverable is a fluke. A pattern of small slips is your team absorbing more than it can hold. Look back over the last month: how many deadlines moved, even slightly? Three or more is a flashing light.

2. Your best people are the busiest — every single week. Work flows to whoever delivers, so your strongest designers and leads quietly get overloaded first. If the same two names are always "slammed," you're one resignation away from a crisis.

3. You say yes to new work without checking capacity. Be honest: when the last project came in, did you look at who actually had room — or did you assume it would "fit somehow"? Saying yes on hope is the single most common cause of agency burnout.

4. Nobody can answer "who's free next week?" in under a minute. If figuring out real availability means pinging people on Slack or rebuilding a spreadsheet, you don't have a capacity view — you have a guess. And guesses are optimistic right up until they're wrong.

5. Overtime is creeping up and nobody decided it should. A few late nights around a launch is normal. Late nights as the default mean the schedule is over capacity and the team is silently paying for it.

The 10-minute capacity check (do this today):

1. List every person who does billable work.
2. For each, write their realistic weekly capacity in hours (not 40 — account for meetings and admin; 30 is often honest).
3. Add up the hours they're already committed to across all live projects next week.
4. Divide committed hours by capacity. Anyone over 100% is overbooked now. Anyone at 85–100% has zero room for the next "quick favor."
5. Circle anyone over 100%. That's your at-risk list — the deadlines most likely to slip and the people most likely to burn out.

If more than a couple of names are over 100%, you're not having a bad week — you're structurally overbooked, and it will keep happening until you change how you say yes to work.

Making this a habit instead of a fire drill. The check above works, but doing it by hand every Monday gets old fast — and a spreadsheet can't warn you about next month. This is exactly the problem we built Tempo to solve: it pulls your team's real bookings into one capacity view and uses an AI forecast to flag who'll be overbooked weeks before it happens, so "are we overbooked?" stops being a question you answer after the damage is done. If the 10-minute check showed you more red than you expected, see your own agency's capacity forecast free for 14 days. Either way — run the check. Knowing where the edge is, is how you stop falling off it.

Voice-consistency note: the phrase "see overload before it burns your team" anchors the one-pager headline, Pillar 1 on the battlecard, and the blog's closing pitch — one benefit, one set of words, three artifacts.