1. What Is MatchUp?
At its simplest, MatchUp presents people with two choices and asks them to choose. What happens around that simple interaction depends on the business objective.
Sometimes it is entertainment. Sometimes it is discovery. Sometimes it helps a potential customer understand services, clarify preferences, or make a decision.
The business objective should determine the design, language, call to action, and overall experience.
2. Emerging MatchUp Categories
Preference MatchUp
Primarily fun and engaging. The visitor chooses favorites.
Language: Play It Now · Pick Your Favorite
Discovery MatchUp
Helps visitors discover their tastes or preferences without emphasizing winning.
Language: Find Your Style · See What You Prefer
Decision MatchUp
Helps someone compare meaningful alternatives, services, or options. Useful rather than game-like.
Language: Compare Your Options · Find What Fits
Insight MatchUp
Uses simple choices to reveal needs, priorities, or opportunities. Closest to a lightweight interactive consultation.
Language: Discover What Matters · See Your Priorities
These categories are emerging, not locked. Future client implementations should refine the framework.
3. The Consulting Principle
Do not sell every customer the same MatchUp. Determine which MatchUp experience best accomplishes that customer's business objective.
- What do we want the visitor to do?
- Is this entertainment, discovery, decision-making, or insight?
- What should happen after the final MatchUp?
- Is there a natural lead opportunity?
- What vocabulary fits this business?
- What makes the experience worth completing?
4. Language Follows the MatchUp Type
Game vocabulary should not automatically carry from one client to another. Words such as play, round, score, winner can work beautifully for a Preference MatchUp but feel gimmicky in professional services.
Discovery and decision experiences may instead use explore, compare, preferences, priorities, results, next step and similar language.
The MatchUp structure can remain familiar while the vocabulary changes to fit the customer's business.
5. First Product Lesson — D&L
D&L showed that MatchUp works beyond MatchUp Studio's consumer games and revealed that the same fundamental interface can serve a very different business purpose.
“Play It Now” works for D&L because choosing between kitchens naturally feels playful. That does not mean the same language belongs on a bank, dental practice, or professional-service MatchUp.
This became the first documented example of consulting determining the MatchUp type.
6. Content Versioning & Rotation System
Every client MatchUp should maintain a Content Registry so future versions can be created without accidental duplication and past content can be intentionally reused when appropriate.
Two Levels of Tracking
Content Set identifies the complete group of MatchUps deployed together for a client. Example: D&L Content Set 01.
Content ID identifies each individual comparison inside a set. Example: DL-KITCHEN-001.
Deployment Date
The registry records the date the content set actually goes live for the customer, not the date it was created. This provides a reliable history of what the customer was running and when.
The Registry Lists the Actual Content
Do not record only an ID or a Used/Unused flag. The actual comparison should be visible so anyone can immediately understand what has already appeared without opening old files.
| Content ID | Actual MatchUp | Deployed | Status |
|---|---|---|---|
| DL-KITCHEN-001 | White Cabinets vs. Natural Wood | 9/16/26 | Used |
| DL-KITCHEN-002 | Quartz vs. Granite | 9/16/26 | Used |
| DL-KITCHEN-003 | Island vs. Peninsula | — | Available |
Standard Statuses
Available → content exists and has not been deployed. Scheduled / Active → selected for the current deployment. Used → previously deployed. Retired → should not be used again.
Next-Version Workflow
When creating the next client version, check the client's registry, exclude previously used content unless reuse is intentional, select the next appropriate items, assign the new Content Set number, and record the deployment date when it goes live.
Important: Software/build version and content version are separate. A MatchUp can run the same software version while moving from Content Set 01 to Content Set 02.
7. Resources & Client Examples
This section will become the hub for supporting MatchUp material: working examples, client collateral, launch instructions, design standards, lessons learned, and future product experiments.
D&L Construction
Kitchen MatchUp pilot, Facebook collateral, launch process, and product lessons.
Client page to be added.
Mann Family Dental
Next client implementation and an opportunity to test a less game-like MatchUp category.
Client page to be added.
Launch Process
Repeatable steps learned from creating, branding, deploying, linking, and promoting MatchUps.
Process page to be added.
Ideas & Experiments
Concepts worth testing before they become official product standards.
Living section.