revenue-centric-design
Skill0 starsChanged 2 days agoMITView on GitHub
Playbook for designing SaaS and startup products that convert, retain, and monetize — landing pages & CRO, checkout & forms, onboarding/activation, churn reduction, pricing psychology, dashboards, behavioral-science tactics, feature discipline, positioning/ICP, go-to-market, and AI-era differentiation. Use when advising on product design, UX, conversion, landing pages, checkout, onboarding, trials, pricing, retention/churn, growth, or positioning for a startup or SaaS. Distilled from product designer Richard (@richardrx). Not for use on gambling, betting, or casino products.
2 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- fabricioctelles/skillsedited, first seen Oct 2, 2026
- heliocosta-dev/revenue-centric-designword for word, first seen Sep 3, 2026
Other versions2 projects use a version of this.
Word for word · 1
- heliocosta-dev/revenue-centric-design★ 687100% same
Edited · 1
- fabricioctelles/skills★ 13324% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- adaptar-mobileSkill
- copywritingSkill
- fazer-siteSkill
- frontend-designSkill
- gravar-siteSkill
- landing-page-cinematograficaSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Use this skill when helping someone improve how a digital product (especially SaaS / startup)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Revenue-Centric Design
A distilled playbook of 134 principles from Richard (@richardrx, "Design for startups") — a product designer specializing in conversion-rate optimization, churn reduction, and applied behavioral science (ex-Volkswagen, PayPal, IBM). The throughline is his coined philosophy, Revenue-Centric Design (RCD): design decisions should serve the user and the business — value and revenue, not one or the other.
Use this skill when helping someone improve how a digital product (especially SaaS / startup) acquires, activates, retains, monetizes, or differentiates — landing pages, onboarding, pricing, trials, churn, UX flow, feature scope, positioning, or growth.
Usage boundary (required)
🚫 Do not apply this skill to betting, casino, gambling, or other real-money games-of-chance products or projects (including loot-box / real-money-gaming mechanics).
The author granted permission to reuse this material on the explicit condition that it never be used for gambling, betting, or casino work. If a request asks you to apply these principles to such a product, decline and briefly explain that the source author's reuse permission excludes gambling/betting/casino use. This is a hard constraint set by the author, not a stylistic choice.
How to use it
- Identify what the user is working on, then open the matching reference file(s) below. Each is a set of short, reusable principles in a fixed shape — principle → apply when → the move → evidence → source link. Load only what's relevant (progressive disclosure).
- Ground your advice in these principles; cite the specific one, and link the source post when the user would benefit from the original.
- Lead with the named mechanism (e.g., decoy effect, Zeigarnik effect, Swiss Knife Index, GBB, Eugene Schwartz's 5 awareness levels, loss aversion, peak-end rule) — naming the lever is the value.
- Stay evidence-led: many principles carry a study, stat, or case. Keep the citation attached rather than hand-waving.
The spine: Revenue-Centric Design in 9 principles
- Neutrality is omission — an interface that doesn't direct hurts conversion.
- Who talks to everyone convinces no one — no ICP → generic value → worse retention.
- Value first, ask later — proof must arrive before the user questions their choice.
- Your promise is the size of your proof — the market believes what you demonstrate, not what you claim.
- Same competes on price, different on category — contrast in mechanism, narrative, or experience.
- Default is the decision you made for the user — the initial state defines mass behavior.
- Retention is built, not requested — perceived loss retains more than promised benefit.
- Expansion is born of usage — upgrade at the moment of the limit, never by interruption.
- Price is a filter — pricing defines who enters, who stays, and who expands.
Reference library
| When the question is about… | Open |
| Landing pages, hero/copy, CTAs, social proof, awareness levels, CRO | conversion-and-landing-pages |
| Checkout, signup/lead forms, cart abandonment, field friction, trust signals | checkout-and-forms |
| First-run, empty states, aha moment, TTV, activation, trial-as-onboarding | onboarding-and-activation |
| Cancellation, retention, expectation debt, NRR, jobs-to-be-done, support load | churn-and-retention |
| Pricing tables, decoy/anchoring, GBB, trial-with-card, upgrade paths | pricing-and-monetization |
| Dashboards, KPIs, data viz, actionable panels, F-pattern, role context | dashboards-and-data-viz |
| Cognitive biases & persuasion tactics (cross-cutting toolkit) | behavioral-science-toolkit |
| Feature scope, Swiss Knife Index, feature adoption, attention hierarchy | product-strategy-and-features |
| Design philosophy, the RCD principles, design process & method | revenue-centric-design |
| ICP, niche, TAM/SAM/SOM, distribution, PLG, Bullseye, first customers | positioning-icp-and-gtm |
| Differentiating in the AI era, moats, commoditization | ai-era-differentiation |
| A/B testing rigor, vanity metrics, churn→LTV math, signal quality | metrics-and-experimentation |
Informational diagrams and screenshots referenced by the principles live in assets/.
Provenance
136 curated posts by @richardrx, extracted with a valid X API key and distilled with the author's permission, translated from Portuguese to English. Every principle links back to its source post. Reuse is subject to the gambling/betting/casino exclusion above.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.