pricing-proposal-builderlisted

Build a client-ready pricing proposal, monetization recommendation, or sales-comp plan the f13i way — recommendation-led, every number defended with a framework, CEO pressure-tested, then logged to the deal file. ALWAYS use this skill when Farhan is building a pricing proposal, pricing model, packaging recommendation, monetization plan, discount structure, or sales compensation / commission plan for a client (e.g. "build the Vectra proposal", "put together a pricing model for Cloudline", "draft a comp plan for Munch", "help me with Paywell pricing", "AirPLAi pricing handoff"). Also trigger when he's iterating on numbers from a prior session, defending pricing decisions, or prepping a proposal to send. This is his core billable deliverable — reach for it whenever a client pricing artifact is being created or revised.
f13i/pricing-proposal-builder · ★ 0 · DevOps & Infrastructure · score 67

Install: claude install-skill f13i/pricing-proposal-builder

# Pricing Proposal Builder This is Farhan's highest-value repeated work: turning a discovery call into a defensible pricing or comp recommendation a client's CEO can act on. He's done it for Vectra, Cloudline, Paywell, Forgeworks, AirPLAi, Munch, Cordia, Volt and more — each time from scratch, each time re-deriving the same principles by hand. This skill encodes the f13i method so every proposal starts at his standard instead of at zero. The point is not to spit out numbers. Farhan's whole differentiation, in his own words from past sessions: **"more important than numbers, we deliver frameworks for how to think and then let the CEO make the decision."** A proposal that just asserts "$80K base, 22% commission" is worthless to him. A proposal that shows *why* each number falls out of a defensible framework — and hands the CEO the levers — is the product. ## Before you build: load the context A grounded proposal beats a generic one every time. Pull what exists before drafting: 1. **The deal file.** Client deals live in his Obsidian vault under `30-deals/<client>/` (e.g. `30-deals/vectra/index.md`). Read the index for meeting context, prior pricing decisions, current status, and stakeholder map. Use the `obsidian` tools. 2. **The discovery call.** The relevant Granola transcript holds the real constraints — current ARR, ACV, customer count, who the decision maker is, what "fire" the client flagged. Pull it via the Granola tools if not already summarized in the deal file. 3.