Finance
business-model-preferences - Claude MCP Skill
Pricing philosophy and business model constraints. Auto-invoke when: evaluating pricing, checkout flows, subscription logic, tier structures.
SEO Guide: Enhance your AI agent with the business-model-preferences tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to pricing philosophy and business model constraints. auto-invoke when: evaluating pricing, checkout fl... Download and configure this skill to unlock new capabilities for your AI workflow.
Documentation
SKILL.md# Business Model Preferences
These are organizational preferences. Apply them when designing or reviewing any billing integration.
## Philosophy
Keep it simple. Complexity in pricing confuses customers and creates engineering debt.
## Pricing Model
**Single tier or nothing.** Either:
- Free and open source (no billing)
- One price point with full access
No multiple tiers. No Basic/Pro/Enterprise. No feature gating. No usage-based pricing.
If annual pricing exists, it's simply "2 months free" — same features, discounted rate.
## Free Trial, Not Free Tier
Offer a trial (14 days standard). After trial: pay or lose access.
No freemium. No "free forever with limits." Trial is the only free path.
## Credit Card Upfront
**Require payment method at trial signup.** This is the standard SaaS pattern:
1. User enters credit card during signup
2. Trial starts immediately (no charge)
3. If user cancels before trial ends → no charge
4. If trial ends without cancellation → automatic charge, subscription begins
**Why upfront:**
- Higher conversion (commitment at signup)
- Qualified leads (real intent to pay)
- Smoother UX (no second checkout flow)
- Less support burden (no "how do I upgrade?" questions)
**Stripe implementation:**
```typescript
await stripe.checkout.sessions.create({
mode: 'subscription',
payment_method_collection: 'always', // Require card
subscription_data: {
trial_period_days: 14, // Or use trial_end for specific date
},
});
```
**UX messaging:**
- "Start your 14-day free trial"
- "You won't be charged until [date]"
- "Cancel anytime during trial"
## Trial Completion on Upgrade
When a user upgrades mid-trial, honor the remaining trial days.
Pass `trial_end` to Stripe with the remaining time. User finishes their trial, THEN billing starts. Never charge immediately on mid-trial upgrade — that's confusing and feels like a bait-and-switch.
## Simplicity Tests
When reviewing pricing or checkout:
- Can you explain the pricing in one sentence?
- Is there only one "upgrade" button?
- Does the pricing page have comparison tables? (It shouldn't.)
- Would upgrading mid-trial surprise a user with an immediate charge? (It shouldn't.)
## Application
Reference these preferences when:
- Designing new Stripe integrations
- Reviewing checkout flows
- Auditing subscription logic
- Evaluating pricing page designsSignals
Information
- Repository
- phrazzld/claude-config
- Author
- phrazzld
- Last Sync
- 3/2/2026
- Repo Updated
- 3/1/2026
- Created
- 1/23/2026
Reviews (0)
No reviews yet. Be the first to review this skill!
Related Skills
firecrawl-build-search
Integrate Firecrawl `/search` into product code and agent workflows. Use when an app needs discovery before extraction, when the feature starts with a query instead of a URL, or when the system should search the web and optionally hydrate result content.
firecrawl-build-onboarding
Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
firecrawl-build
Integrate Firecrawl into application code whenever a product, agent, or workflow needs web data inside the app — web search, live search results, page scraping, structured extraction, or browser interaction. Use when building any feature that needs data from the web in code, even if the user does not mention Firecrawl explicitly and only describes wanting web data, website content, search, scraping, or interaction in an application. Trigger for Firecrawl requests, "fire girl" shorthand, and generic app-level web-data needs that should map to `/scrape`, `/search`, or `/interact`. Do not use this skill for one-off terminal-only web tasks during the current session; use `firecrawl/cli` for those.
firecrawl-build-interact
Integrate Firecrawl `/interact` into product code for dynamic pages and browser actions after scraping. Use when a feature needs clicks, form fills, pagination, authentication-aware flows, or other multi-step interactions that plain `/scrape` cannot complete.
Related Guides
Mastering Python and TypeScript Development with the Claude Skill Guide
Learn how to use the python typescript guide Claude skill. Complete guide with installation instructions and examples.
Mastering VSCode Extension Development with Claude: A Complete Guide to the TypeScript Extension Dev Skill
Learn how to use the vscode extension dev typescript Claude skill. Complete guide with installation instructions and examples.
Next.js SEO Dev: The Essential Claude Skill for Documented React Development
Learn how to use the nextjs seo dev Claude skill. Complete guide with installation instructions and examples.