Skip to main content
All resources
Process & workflows6 min readLast updated Sep 14, 2026

The 12 project context cards

Twelve kickoff cards that get the unsaid stuff on the table before a web or marketing project starts.

Most web and marketing projects don't fail on execution. They fail on the things nobody said out loud at kickoff: the assumption everyone quietly treated as fact, the budget holder who never came to a meeting, the content nobody has time to write.

Sit through enough kickoffs and the pattern holds. It's rarely the craft that sinks a project. It's the silence around it.

These 12 cards get all of that on the table early. Each one is a place to write down what we know, what we're assuming, and what could quietly blow up if nobody says it out loud.

You don't need another template. You need the awkward questions asked out loud, early, while they're still cheap.

How the system works

Every card answers the same five questions: what we know, what we're assuming, what we don't know, how risky that feels (low, medium or high), and who's going to check it. The last one matters most. If nobody owns the validation, that's your first red flag, and usually the most useful one in the deck.

You're not filling out all 12 cards before kickoff. Pre-fill what you know, walk the deck together in one 90-minute session, flag the unknowns, give each one an owner, then sequence the work by risk instead of by whatever everyone's most excited about.

The 12 context cards

1

Business model card

If you can't explain how the company actually makes money, nothing else on the cards matters much. Start here.

Capture
Revenue streams
Average deal size and lifetime value
Sales cycle length
Gross margin
Seasonality
Revenue targets for this project
Risk signals
"We just need more traffic"
Nobody can explain the conversion math
No revenue goal for this project
2

Audience reality card

Forget personas for a minute. What you want on this card is who actually buys, who talks them into it, and who can quietly kill the deal.

Capture
Who buys
Who influences the purchase
Who can block it
What triggers buying
What problem costs them money, time or status
Risk signals
"Everyone is our customer"
No customer data anywhere
Every assumption comes from the founder's gut
3

Offer and value proposition card

This is where projects get wobbly, and where the wobble usually stays hidden until launch.

Capture
Core offer
Proof points
Differentiation
Why now
Current conversion rate, if any
Risk signals
The offer is still being defined during design
No proof or credibility anywhere
Differentiation based on vibes
4

Success metrics card

If nobody agrees on what success looks like before you start, scope creep will happily decide for you.

Capture
Primary KPI
Supporting KPIs
What will NOT be measured
Time horizon for evaluation
Baseline data
Risk signals
"Brand awareness" is the whole goal
No baseline numbers
Nobody agreed on when we check the results
5

Assumptions and hypotheses card

Every project runs on beliefs dressed up as facts. This card makes them introduce themselves.

Capture
What we believe is true about users
What we believe is true about channels
What we believe is true about messaging
What must be true for this to work
Risk signals
No experiments planned
No budget for validation
"We just know"
6

Technical constraints card

Where agencies inherit other people's tech debt. Ask now, not in month two.

Capture
Current CMS and CRM
Integrations required
Hosting environment
Security and compliance needs
Internal tech skill level
API limitations
Risk signals
Legacy systems nobody understands
"Our developer set that up" (and that developer left in 2019)
No staging environment
7

Content readiness card

Content is what kills timelines, not the build. It's always "coming" right up until it isn't.

Capture
Who is writing the content
Brand guidelines status
Existing assets
Approval workflow
Whether legal review is needed
Risk signals
Founder writing copy "when they have time"
No content owner
A seven-person approval chain
8

Decision-making and power map card

Agencies love to pretend office politics isn't their problem. It is. Find out who actually decides before the deciding starts.

Capture
Budget holder
Final decision maker
Day-to-day contact
Who can veto
Internal tensions
Risk signals
"It's a committee"
The budget holder never comes to meetings
There's a hidden executive sponsor somewhere
9

Resource capacity card

Everyone says yes to everything and then quietly drowns. This card is where that gets named before it happens.

Capture
Client team availability
Agency team capacity
Competing initiatives
Vacation schedules
Hard launch deadlines, real versus symbolic
Risk signals
"ASAP" is the timeline
Client team mid-reorg
Agency over 85% utilization
10

Risk and dependency card

Write down everything that could break this project that lives outside your control, and what you'll do when it does.

Capture
Third-party vendors
Platform approvals
Legal sign-off
Data access
Sales team adoption
Market conditions
Risk signals
Dependencies outside project control
No mitigation plan
11

Change impact card

The site launches. Then what? If nothing changes in anyone's day to day, it's worth asking why you're doing it.

Capture
Sales process changes
Marketing workflow changes
Customer support impact
Training required
Internal resistance expected
Risk signals
"Nothing will change"
No training plan
No adoption owner
12

Financial reality card

Nobody wants to talk about money early, which is exactly why you talk about it early.

Capture
Project budget
Media budget
Ongoing maintenance cost
Internal time cost
Expected return timeline
Risk signals
No post-launch budget
No clarity on ongoing ownership

How to run the kickoff session

  1. Pre-fill every card with what you already know
  2. Walk the full deck together in one 90-minute working session
  3. Flag every "don't know" and every assumption still standing
  4. Give each one an owner who will actually check it
  5. Sequence the work by risk, not by excitement

If something is both uncertain and expensive to get wrong, it goes in an early sprint. If it's neither, it can wait.

Why standardize

When you run the same deck on every project, patterns start showing up fast. Project managers stop firefighting. Sales stops overselling. Scope creep drops, margins follow. And the quiet win is the real one: clients start trusting you more, because you're asking better questions than anyone else in the room.

Run it with a facilitator: A 90-minute session with a fresh pair of eyes surfaces what the team is too close to see. Book a chat and we'll pressure-test your cards together.

Rachel Ody

Written by

Rachel Ody

PM Operations Consultant & Coach

Rachel Ody is a systems strategist, operations consultant, and transformational leadership coach. For over twelve years, she has helped founder-led organizations fix the invisible systems that shape how people work.

More about Rachel

Newsletter

Get more like this in your inbox

Sharp opinions on operations, systems, and the psychology of how work gets done. No fluff. Unsubscribe anytime.

Dig deeper
Browse all resources

We use cookies to keep you logged in and make the site better. Read our Privacy policy.