BUILDING THE
PROGRAMS THAT
FEED THE
PRODUCT

Some of the highest-leverage design work never touches a Figma file: the customer program feeding steady signal into the roadmap, the framework deciding who to invest in next, the relationships turning at-risk accounts into advocates. This is the program I founded and ran end to end, and the strategy behind it.

Role
Lead Product Designer, program founder
Discipline
Program design, customer advocacy, events, prioritization
Context
Enterprise B2B SaaS platform
Threads in this study
04
THREAD 01 / 04
Founding the program
1
Program founded and architected end to end
5+
Founding-cohort industries: travel, food, fintech, retail, tech
7
Touchpoint types a year, kickoff to live channel
The problem

The team needed a trusted line to power users: a place to recruit research participants, pressure-test direction, and build loyalty with the accounts that mattered most. None existed; feedback was ad hoc, and the most valuable customers had no relationship with the people building the product.

What I did

I founded a customer advisory community and designed the whole program: member criteria weighted toward power users and high churn-risk accounts, a hand-selected founding cohort spanning travel, food, fintech, retail, and tech, and a year-long cadence of an in-person kickoff, monthly virtual sessions, quarterly events and newsletters, semi-annual surprise events, and a dedicated channel. Running every detail myself, down to sourcing branded swag and untangling vendor logistics when a contractor underdelivered, mattered because the trust the program runs on is built in the details.

Frame it as a community and a thought-leadership circle. The trust is the whole point. Program positioning principle
CANDIDATE MEMBER VERTICAL HAND-SELECTED WEIGHTED TO POWER USERS AND CHURN-RISK ACCOUNTS EVERY CANDIDATE ACCOUNT MEMBER CRITERIA THE FOUNDING COHORT THE FOUNDING COHORT FIVE VERTICALS, ONE STANDING PROGRAM ADVISORY PROGRAM A TRUSTED LINE TO POWER USERS TRAVEL FOOD FINTECH RETAIL TECH IN-PERSON KICKOFF MONTHLY SESSIONS QUARTERLY EVENTS NEWSLETTERS A YEAR-LONG CADENCE, PLANNED FROM DAY ONE
Fig. A hand-selected cohort across five verticals, with a year-long cadence from day one
THREAD 02 / 04
Multi-region expansion
3
Global regions sequenced: Europe, North America, Asia-Pacific
4
Weighted factors in the city-scoring model driving expansion order
1
Repeatable nomination and outreach process for partner teams
The problem

The founding cohort proved the model in one region. Scaling globally meant choosing where to invest next without spreading thin, through partner teams wary of anything resembling a sales push into their accounts.

What I did

I built a scoring model ranking expansion cities by churn risk, account size, renewal timing, and growth potential, then sequenced the rollout across Europe, North America, and Asia-Pacific, so investment followed evidence, not enthusiasm. A repeatable nomination and outreach process, region-specific plans, and internal positioning as a customer community brought the teams who owned those relationships along instead of pushing back.

The scoring model decides where we go next. It keeps the program honest under pressure. Expansion framework principle
LIVE NEXT COMING SOON PARTNER NOMINATION SEQUENCED BY SCORE CHURN RISK, ACCOUNT SIZE, RENEWAL TIMING, GROWTH POTENTIAL EUROPE THE FOUNDING REGION NORTH AMERICA SECOND BY SCORE ASIA-PACIFIC THIRD BY SCORE SCORE NOMINATED BY PARTNER TEAMS NOMINATED BY PARTNER TEAMS POSITIONED AS A CUSTOMER COMMUNITY, NOT A SALES PUSH REGION-SPECIFIC PLANS EARNED WARY PARTNER TEAMS OVER
Fig. Expansion sequenced across three regions by score, through partner-team nomination
THREAD 03 / 04
Program to roadmap
8
Distinct roadmap influences traced to the founding cohort's input
1
Standing recruitment pool feeding concurrent studies on demand
7
Days until the channel became self-sustaining peer support
The problem

A community only earns its keep if it changes the product. Every advisory program risks becoming a nice-to-have where members feel heard, nothing moves the roadmap, and trust quietly erodes.

What I did

I wired the program into the product process as a standing recruitment pool for studies and a fast channel to pressure-test direction. The cohort's input traced to concrete roadmap influences, from dynamic landing pages to an attribution tool to bulk creation enhancements. Within the first week the channel became self-sustaining, members answering each other's product questions, deepening engagement without adding support load.

Member input has to show up in what ships. Otherwise the whole program is just theater. Program-to-product principle
MEMBER INPUT SHIPPED INFLUENCE THE CHANNEL SELF-SUSTAINING WITHIN THE FIRST WEEK MEMBERS ANSWERING EACH OTHER IN WEEK ONE A STANDING POOL FOR STUDIES, A FAST CHANNEL TO PRESSURE-TEST DIRECTION SYNTHESIZE TRACED TO THE ROADMAP INPUT TO SHIPPED INFLUENCE, NOT A NICE-TO-HAVE DYNAMIC LANDING PAGES AN ATTRIBUTION TOOL BULK CREATION ENHANCEMENTS EVERY INFLUENCE TRACES BACK TO A MEMBER
Fig. Community input traced to shipped roadmap influence
THREAD 04 / 04
At-risk to advocate
100%
Founding-cohort retention, the only loss caused by a layoff
1
At-risk account turned internal advocate against a competitor
1
Proof of concept leadership cites as flagship retention story
The problem

The accounts most worth investing in were often the most at risk: large customers weighing competitors mid-contract, with no strong reason to stay. The real test was whether sustained, genuine engagement could turn someone evaluating alternatives into an internal defender of the product.

What I did

I treated the founding cohort as the proof of concept and invested directly in the relationships. Retention held across the full cohort; the one departure came from a layoff, not a decision to leave. The clearest signal: a member mid-evaluation of a direct competitor fought internally to keep their company on the platform, the exact at-risk-to-advocate arc the program was built to create.

A member fighting to keep their company on the platform, with a competitor's pitch on the table, is the whole thesis proven. Advocacy outcome, founding cohort
AT RISK ADVOCATE TOUCHPOINT AT RISK THE ACCOUNTS MOST WORTH INVESTING IN A LARGE ACCOUNT MID-CONTRACT EVALUATING A DIRECT COMPETITOR NO STRONG REASON TO STAY SUSTAINED, GENUINE ENGAGEMENT THE FOUNDING COHORT AS PROOF OF CONCEPT KICKOFF MONTHLY SESSIONS EVENTS A DIRECT LINE THE INTERNAL ADVOCATE FOUGHT TO KEEP THEIR COMPANY ON THE PLATFORM RETENTION HELD ACROSS THE FULL COHORT THE ONE DEPARTURE WAS A LAYOFF, NOT A DECISION TO LEAVE
Fig. An at-risk account turned internal advocate through sustained engagement
A-7 / CASE STUDY
← ALL CASE STUDIES