pm-business-model

Reverse-engineer pricing, packaging, and go-to-market signals into a BUSINESS-MODEL.md document.

42|2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/nmrtn/nanopm --skill pm-business-model-nmrtn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-business-model
Source: https://github.com/nmrtn/nanopm/tree/main/pm-business-model
Command: npx skills add https://github.com/nmrtn/nanopm --skill pm-business-model-nmrtn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams articulate and align a company’s monetization approach by analyzing code signals, pricing data, and interviews, then generates a concrete BUSINESS-MODEL.md to guide strategy and execution.

Core Features & Use Cases

  • Reverse-engineers pricing, packaging, and go-to-market signals from codebases and public pages to draft a coherent model.
  • Supports refining an existing BUSINESS-MODEL.md by comparing new evidence against prior versions.
  • Produces a clear, shareable document that captures model type, revenue streams, pricing & packaging, GTM motion, unit economics signals, and the riskiest assumption.

Quick Start

Run this skill in a repository with pricing signals or pricing data to generate or refine BUSINESS-MODEL.md.

Frequently Asked Questions about pm-business-model

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reverse-engineer a business model from a codebase?

Reverse-engineer a business model by analyzing code signals, pricing pages, and prior artifacts to infer monetization type, revenue streams, GTM motion, and unit economics. This process drafts a structured BUSINESS-MODEL.md file capturing your strategy.

Can I infer pricing and packaging strategy from code and public pages?

Yes, you can infer pricing and packaging strategy by extracting monetization signals from codebases and public pricing pages. This generates a structured business model document detailing revenue streams and go-to-market motion.

What is the best way to document a company's monetization approach?

The best way to document a monetization approach is to generate a BUSINESS-MODEL.md file. This document captures model type, revenue streams, pricing, GTM motion, and unit economics, labeling each claim as evidenced or assumed.

Does this business model analysis require interview data?

Interview data is required to clearly label each business model claim as evidenced or assumed and flag validation gaps. Code signals and pricing page data alone are insufficient for a complete monetization articulation.

How do I refine an existing BUSINESS-MODEL.md file?

Refine an existing BUSINESS-MODEL.md by comparing new evidence against prior versions. This validates current pricing and packaging assumptions while updating the riskiest assumption and go-to-market motion documentation.

What are the limitations of inferring revenue streams from code signals?

A limitation of inferring revenue streams from code signals is that claims without direct evidence must be labeled as assumed and flagged for validation. Monetization signals often require correlation with pricing page data to confirm accuracy.