messaging-please
messaging-please builds the chain that connects why your company exists to what you say to each person in a buying decision.
What it does
Most messaging problems look like a writing problem, but they usually are not. The company has something to say. What it lacks is an architecture: who hears which version of it, why, and how each version connects back to the same root.
messaging-please builds that architecture. It works from one principle: messaging is a chain, not a menu. Purpose anchors positioning, positioning anchors your core claim, and that claim gets translated, not watered down, for each person in a deal. Break one link and the damage shows up further down, usually in sales.
How it works
messaging-please works in four phases:
- Discover: it establishes the foundation, your purpose, mission, vision, ideal customer, and a positioning statement. Everything else hangs off this.
- Architect: it maps the people in a buying decision, the buyer, the user, the champion, the person who can block it, and builds a tailored version of the message for each. The buyer cares about return; the user cares about their workflow. Both hear the truth; each hears a different version of it. That is precision, not inconsistency.
- Bridge: it turns the architecture into a go-to-market narrative, connecting it to your sales motion, product story, and pricing.
- Maintain: it keeps the whole thing current as the company changes, surfacing what has drifted.
Who it's for
- Founders and early teams who have plenty to say but no structure for saying it consistently
- B2B companies where the buyer is not the user, and several people have to agree before anything moves
- Companies at an inflection point, a new market, product, or customer, rebuilding messaging from the foundation up
Using it without writing code
You do not need to be a developer to use messaging-please, and you do not need to be comfortable with GitHub. The framework is a set of plain-language instructions that an AI assistant reads and works from. Your part is the conversation.
The quickest way in is the "Open in Claude" button on this page. It hands Claude a short brief on messaging-please and leaves room for you to describe your own situation, so you can talk through the fit before committing to anything.
To run the framework itself, you open the repository with Claude Code, Anthropic's assistant that works directly with files, and tell it what you need in ordinary sentences, like "help me get clear on our positioning." It handles setup the first time and walks you through the rest. If any of that feels unfamiliar, it is a good thing to bring to a first conversation.
See it on GitHub
The full framework, its step-by-step skills, and worked examples are all in the open repository: