percona / percona/percona-messaging
Expand motions: use-case coverage for growth situations
Open
@brianamarie is already working on this.
Since Sep 1, 2026.
Area: Cross-product
Content & messaging
MISSING TIMELINE
Needs: product or GTM
Roadmap: soon
- Dominant language
- Python
- Stars
- 3
- Forks
- 1
- Avg merge
- 15m
- Merged PRs (30d)
- 2
Description
Why
CS already runs a set of expand/growth discovery motions in business reviews and renewals. Messaging should mirror those situations as use cases, not invent a parallel expand program. (CS co-review not required if we stay on this list.)
Situations to check for coverage
- More servers under coverage
- Additional technologies / BUs (MySQL, MongoDB, MariaDB, PostgreSQL, Valkey)
- Professional Services attach on existing MS / Support (roadmap, expertise, or people-power gaps; health / performance assessments)
- EOL Support or PS to upgrade
- Support → Managed Services / ExpertOps
- Advanced → Premium (SLAs, contacts, Level 2 tech, screen-sharing)
- Service add-ons (contacts, Level 2 tech such as operators, ProxySQL)
Done when
- Gap check each situation: covered vs missing in services / Support / ExpertOps / consulting / engine copy
- Add or extend use-case copy (buyer situation, discovery cue, CTA) without inventing new play names
Out of scope
CS process redesign, external “expand program” narrative, niche extension kits as a separate program.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.