Positioning & Messaging Framework — Product Marketing / Growth Manager Capstone — SkilsMVP

What you'll produce

A Positioning & Messaging Framework for Tempo: a single document that decides how Tempo wants to be perceived versus Toggl, Harvest, and "doing nothing," and turns that decision into the exact words every future asset will reuse. It contains a filled-in positioning statement (for / who / category / benefit / unlike / differentiator), a homepage-ready value proposition, a message hierarchy of three benefit-led pillars each backed by proof, and audience- and channel-tailored variations of the message. This is the strategic source of truth — your GTM launch plan (Deliverable 3), sales battlecard (Deliverable 4), and every ad, email, and landing page flow down from it. It proves the Topic 4 skills: positioning a product against real alternatives, leading with benefits over features, being clear before clever, and centering one genuine differentiator instead of sounding like everyone else. It is the deliverable that makes the rest of the portfolio sound like one company instead of six disconnected documents.

Instructions

Pull your differentiator forward from Deliverable 1. Open your Research Brief and copy out the one genuine differentiator your SWOT surfaced. For Tempo it must be defensible against both incumbents and the spreadsheet — something Toggl/Harvest structurally can't claim, not a generic "easy to use." Everything below has to ladder back to this single idea.
Write the positioning statement using the exact template. Fill in: For [target customer] who [problem], Tempo is a [category] that [key benefit]. Unlike [alternative], Tempo [differentiator]. Pick the category deliberately — the category is a strategic choice (is Tempo a "time tracker" or a "capacity-planning tool"?), because it sets the frame customers compare you in. Keep it to two sentences. This is an internal artifact; it does not need to be pretty, it needs to be true and sharp.
Distill the value proposition (the homepage headline + subhead). Compress the positioning into one punchy promise a visitor understands in five seconds: a headline (the benefit, in the customer's words) and a subhead (who it's for + the differentiator). Run the clarity test: if you swapped in a competitor's name, would the line still be true? If yes, it's too generic — rewrite until it could only describe Tempo.
Build the message hierarchy: three benefit-led pillars. Choose the three benefits that matter most to your ICP (not your three favorite features). Phrase each pillar as a customer outcome ("Stop guessing who's overbooked"), not a feature ("Capacity heatmap"). Under each pillar list 2–3 proof points — the specific features, numbers, or facts that make the claim believable. This is where features finally appear, in service of a benefit, never as a naked list.
Add a proof point to every claim. For each pillar, force yourself to answer "why should they believe this?" with something specific and credible — a metric, a capability only you have, a named integration, a customer-shaped fact. Replace any vague claim ("boost productivity") with a specific one ("see next week's overbooking before it happens").
Write audience and channel variations. The core story stays constant; the emphasis flexes. Write at least two audience variations (e.g., agency founder/owner vs. operations/account lead — they buy for different reasons) and two channel variations (e.g., a Google Search ad headline vs. a LinkedIn post opener vs. a cold-email subject line). Each variation is the same positioning, re-pointed — not a new strategy.
Run the four-pitfall audit before you submit. Re-read the whole document and kill: (a) lines that sound like everyone else, (b) feature-dumping, (c) internal jargon / company-centric "we" language, and (d) inconsistency where the pillars and the value prop tell different stories. Mark what you cut. The audit is part of the deliverable's value, not optional polish.

Worked example

(Product: Tempo — B2B time-tracking & capacity-planning SaaS for small creative agencies, 10–50 people. Differentiator carried from Deliverable 1's SWOT: Tempo doesn't just record hours after the fact — it forecasts who will be overbooked next week, which timesheet tools structurally don't do.)

Positioning statement

For small creative-agency owners and operations leads (10–50 people) who can track where last month's hours went but can't see next week's crunch coming until someone burns out or a deadline slips, Tempo is a capacity-planning tool that turns your team's time data into a forward-looking forecast of who's overbooked and where you have room to take on work. Unlike Toggl and Harvest — which are excellent timesheets that tell you what already happened — Tempo answers the question agencies actually lose sleep over: can we take this project on without breaking the team?

Category note (internal): we deliberately frame Tempo as a "capacity-planning tool," not a "time tracker." Competing as a time tracker is a fight against Toggl on price and features we'd lose; competing as the capacity-planning layer reframes Toggl/Harvest as inputs to Tempo rather than substitutes for it, and makes "doing nothing" (a spreadsheet) the real incumbent we beat.

Value proposition (homepage-ready)

Headline: Know who's overbooked next week — before the team does.
Subhead: Tempo turns your agency's time tracking into a live capacity forecast, so a 10–50-person studio can say yes to the right projects and stop running people into the ground.
Clarity test: Swap in "Toggl" — "Toggl turns your time tracking into a live capacity forecast" — and it's false. Good. The line can only describe Tempo.

Message hierarchy — three benefit-led pillars

Pillar 1 — See the crunch before it hits. Stop finding out you're overbooked the week it's already on fire.

Proof: AI capacity forecast flags overallocation up to 4 weeks out, per person and per project.
Proof: A red/amber/green capacity heatmap shows the whole studio at a glance — no spreadsheet rebuild every Monday.
Proof: Forecasts are built from the time data your team is already logging, so accuracy improves as you use it.

Pillar 2 — Say yes to the right work, with confidence. Quote new projects knowing whether you actually have the hours.

Proof: "Can we take this on?" scenario view models a new project against current commitments before you sign.
Proof: Surfaces who has genuine slack this month, so work goes to the right people instead of the loudest calendar.
Proof: Agencies in our beta cut "we overcommitted again" moments measurably — used as the launch case study, not a vague claim.

Pillar 3 — Built for how a small studio actually runs. Capacity planning you'll actually keep up — not another spreadsheet that goes stale, not a heavier tool to babysit.

Proof: One tool for both tracking and forecasting — the same time data your team already logs in Tempo flows straight into the plan, so there's no CSV export, no second system, no "rebuild the resourcing sheet every Monday" (the spreadsheet's fatal flaw from our research brief).
Proof: Set up in an afternoon and forecasting from day one — versus Harvest, where you stand up time-tracking and invoicing first and capacity is still only backward-looking reports.
Proof: Priced and scoped for 10–50-person agencies, like Toggl and Harvest are — this is not a heavyweight enterprise platform with a procurement cycle; it's the planning layer that finally makes the lightweight tooling you already trust look forward.

Audience variations (same positioning, re-pointed)

Agency founder / owner (buys to protect margin and the team): "You win the pitch, then realize the team's already maxed. Tempo shows you next week's capacity before you commit — so you say yes to the profitable projects and stop quietly burning out your best people."
Operations / resourcing lead (buys to stop the Monday fire-drill): "Rebuilding the resourcing spreadsheet every Monday, then watching it go stale by Wednesday? Tempo keeps a live capacity view your whole studio shares, and warns you who's about to be overbooked while there's still time to move work."

Channel variations (same message, re-fit to the medium)

Google Search ad (intent: "resource planning for agencies"): Headline — Capacity Planning Built for Agencies · See Who's Overbooked Next Week. Description — Turn your time tracking into a live forecast. Spot the crunch 4 weeks out. Set up in an afternoon.
LinkedIn post opener (founder audience, scroll-stopping): "Most agencies don't lose money on the projects they say no to. They lose it on the ones they said yes to while the team was already underwater."
Cold-email subject line: Will your team be overbooked in 3 weeks?
Homepage hero (consistency check): reuses the exact value-prop headline above — same words, no drift.

Four-pitfall audit (what I cut and why)

Sounded like everyone else: cut an early headline "The all-in-one platform for modern agencies" — it could describe any of 50 SaaS tools. Replaced with the overbooking-specific line.
Feature-dumping: an early draft listed nine features (timers, invoicing, reports, Slack integration…). Cut to three pillars; features now appear only as proof under a benefit.
Internal jargon / "we" language: replaced "we leverage proprietary ML allocation algorithms" with "see who's overbooked next week" — the customer's words, the customer's outcome.
Inconsistency: an earlier subhead said "the simplest time tracker for freelancers," which contradicts both the audience (10–50-person agencies, not freelancers) and the category (capacity planning, not time tracking). Rewritten to match the positioning statement exactly.

Rubric

The app's AI scores the learner's submission against these criteria and gives feedback. Levels: Needs work (1) / Solid (2) / Excellent (3). Passing = every criterion at Solid or above.

Positioning statement (template fully + sharply filled) — 1: missing slots or generic filler · 2: all six slots (for/who/category/benefit/unlike/differentiator) present and coherent · 3: a deliberate category choice and a differentiator Toggl/Harvest structurally can't claim, true in every word.
Value proposition (clear-before-clever, customer-led) — 1: vague, feature-y, or could describe a competitor · 2: a clear benefit headline + who-it's-for subhead · 3: passes the swap test — could only describe this product — and a visitor gets it in five seconds.
Message hierarchy: benefit-led pillars with proof — 1: a feature list or three features relabeled · 2: three customer-outcome pillars, each with at least one proof point · 3: the three benefits that actually matter to the ICP, each backed by specific, credible proof (metrics/unique capability/customer fact), not adjectives.
One genuine differentiator, centered throughout — 1: no clear differentiator or a generic "easy to use" · 2: a real differentiator that the pillars support · 3: one defensible differentiator threaded consistently from statement → value prop → every pillar and variation.
Audience & channel variations (consistent, not contradictory) — 1: missing, or each variation invents a new strategy · 2: ≥2 audience and ≥2 channel variations, same core story · 3: emphasis genuinely re-pointed per audience/channel while positioning stays identical, with a visible consistency check.
Pitfall audit & coherence with Deliverable 1 — 1: reads generic or disconnected from the research brief · 2: avoids the four pitfalls and reuses the brief's differentiator · 3: an explicit audit (what was cut and why) and a clean line of descent from the ICP/SWOT into the framework other deliverables can build on.