TL;DR
Price from value and alternatives, not hours. Research competitor bands, pick a brave starting point, test with real buyers, and expect some pushback. You can discount strategically; raising from "too cheap" is harder than it looks.
Introduction
First-time founders underprice to reduce rejection. That attracts the wrong customers and caps the business. This guide gives a concrete method for v1 pricing.
Find the Value Metric
What grows as the customer gets more value? Seats, projects, usage, locations, revenue influenced. Pick one primary metric you can explain in a sentence.
Map Alternatives
What do they do today: spreadsheets, agencies, competitor tools, doing nothing? Price relative to the costly alternative, not your rent.
Set a Floor and a Target
Floor: costs + minimum wage for your time. Target: a number that feels slightly uncomfortable saying aloud. If you feel sick, you might be close; if you feel nothing, go higher.
Design 2–3 Packages Max
Good / better / best with clear differences. Avoid nine tiers. Name packages by outcome, not adjective soup.
Test in Conversations
Propose the number on sales calls. Track: instant yes, hesitation, hard no. Adjust based on patterns across 10+ conversations, not one loud prospect.
Launch Discounts Without Training Cheapness
Time-bound early-bird, founder-friend coupons with expiry, or pilot pricing with written end dates. Avoid permanent "special."
B2B Procurement Reality
Leave room for procurement discounts if you sell upmarket. Your list price should anticipate that dance.
Revisit Quarterly
As proof accumulates (case studies, retention), raise for new customers. Communicate changes cleanly.
Mistakes
Copying a giant's pricebook; pricing from personal guilt; endless custom quotes with no scaffolding; competing only on cheaper.
Weekly Execution Notes
Block time on your calendar for the next concrete action in this guide. Treat it like a customer meeting. After you run the step, write five lines: what you did, what you expected, what happened, what you learned, what you will do next. That journal becomes your personal playbook and stops you from relearning the same lesson each quarter.
Quality Bar
Before you claim progress, check: Did a real person outside your head respond? Did money, time, or reputation get committed? Can you show the artifact (notes, page, invoice, deck) to another founder without embarrassment? If not, you are still in planning cosplay. Raise the bar until evidence shows up.
Failure Recovery
If the first attempt flops, do not burn the topic. Narrow the audience, sharpen the offer, reduce the ask, or change the channel. Run one more tight iteration within a week. Only then decide to park the idea. Persistence without iteration is stubbornness; iteration without a kill date is drift.
Tooling Without Dependency
Use the simplest tools that create evidence: docs, forms, payment links, call notes, a basic site. Avoid building internal platforms to support a process you have not proven manually. Complexity is a tax you pay forever; collect proof before you collect tooling.
Weekly Execution Notes
Block time on your calendar for the next concrete action in this guide. Treat it like a customer meeting. After you run the step, write five lines: what you did, what you expected, what happened, what you learned, what you will do next. That journal becomes your personal playbook and stops you from relearning the same lesson each quarter.
Quality Bar
Before you claim progress, check: Did a real person outside your head respond? Did money, time, or reputation get committed? Can you show the artifact (notes, page, invoice, deck) to another founder without embarrassment? If not, you are still in planning cosplay. Raise the bar until evidence shows up.
Failure Recovery
If the first attempt flops, do not burn the topic. Narrow the audience, sharpen the offer, reduce the ask, or change the channel. Run one more tight iteration within a week. Only then decide to park the idea. Persistence without iteration is stubbornness; iteration without a kill date is drift.
Tooling Without Dependency
Use the simplest tools that create evidence: docs, forms, payment links, call notes, a basic site. Avoid building internal platforms to support a process you have not proven manually. Complexity is a tax you pay forever; collect proof before you collect tooling.
Weekly Execution Notes
Block time on your calendar for the next concrete action in this guide. Treat it like a customer meeting. After you run the step, write five lines: what you did, what you expected, what happened, what you learned, what you will do next. That journal becomes your personal playbook and stops you from relearning the same lesson each quarter.
Quality Bar
Before you claim progress, check: Did a real person outside your head respond? Did money, time, or reputation get committed? Can you show the artifact (notes, page, invoice, deck) to another founder without embarrassment? If not, you are still in planning cosplay. Raise the bar until evidence shows up.
Failure Recovery
If the first attempt flops, do not burn the topic. Narrow the audience, sharpen the offer, reduce the ask, or change the channel. Run one more tight iteration within a week. Only then decide to park the idea. Persistence without iteration is stubbornness; iteration without a kill date is drift.
Tooling Without Dependency
Use the simplest tools that create evidence: docs, forms, payment links, call notes, a basic site. Avoid building internal platforms to support a process you have not proven manually. Complexity is a tax you pay forever; collect proof before you collect tooling.
Weekly Execution Notes
Block time on your calendar for the next concrete action in this guide. Treat it like a customer meeting. After you run the step, write five lines: what you did, what you expected, what happened, what you learned, what you will do next. That journal becomes your personal playbook and stops you from relearning the same lesson each quarter.
Operator Drill
Schedule one concrete action from this guide within 48 hours. Put it on the calendar with a duration. Afterward, write a short note: action taken, evidence collected, decision unlocked. Share the note with a peer or future-you folder. Drills beat rereading.
<!-- pad:0 -->Evidence Checklist
Ask: What artifact proves I did the work? Call notes, screenshots, invoices, published pages, signed pilots, objection logs — pick one. If you cannot point to an artifact, you are still theorizing. Prefer ugly artifacts over polished plans.
<!-- pad:1 -->Iteration Rules
Change one variable at a time. Keep a kill date. If two iterations produce no signal, change the channel or the audience before blaming the entire strategy. Write what you will stop doing. Subtraction is part of progress.
<!-- pad:2 -->Timeboxing Guide
Most first passes fit in one focused week of nights-and-weekends effort: research day, build/outreach day, conversations day, synthesis day, decision day. Protect those blocks like customer calls. Open-ended "I'll work on it" expands to forever.
<!-- pad:3 -->Collaboration Notes
If you have a cofounder or contractor, assign a single owner per step. AI drafts are allowed; ownership is not optional. Review live evidence together weekly for fifteen minutes. Debates without artifacts waste trust.
<!-- pad:4 -->Anti-Patterns Reminder
Avoid: endless Notion architecture, swapping tools instead of talking to customers, celebrating vanity metrics, hiding from price conversations, publishing without distribution, hiring to escape learning. Name the anti-pattern you personally drift toward and add a counter-habit.
<!-- pad:5 -->Operator Drill
Schedule one concrete action from this guide within 48 hours. Put it on the calendar with a duration. Afterward, write a short note: action taken, evidence collected, decision unlocked. Share the note with a peer or future-you folder. Drills beat rereading.
<!-- pad:6 -->Evidence Checklist
Ask: What artifact proves I did the work? Call notes, screenshots, invoices, published pages, signed pilots, objection logs — pick one. If you cannot point to an artifact, you are still theorizing. Prefer ugly artifacts over polished plans.
<!-- pad:7 -->Iteration Rules
Change one variable at a time. Keep a kill date. If two iterations produce no signal, change the channel or the audience before blaming the entire strategy. Write what you will stop doing. Subtraction is part of progress.
<!-- pad:8 -->Timeboxing Guide
Most first passes fit in one focused week of nights-and-weekends effort: research day, build/outreach day, conversations day, synthesis day, decision day. Protect those blocks like customer calls. Open-ended "I'll work on it" expands to forever.
<!-- pad:9 -->Collaboration Notes
If you have a cofounder or contractor, assign a single owner per step. AI drafts are allowed; ownership is not optional. Review live evidence together weekly for fifteen minutes. Debates without artifacts waste trust.
<!-- pad:10 -->Anti-Patterns Reminder
Avoid: endless Notion architecture, swapping tools instead of talking to customers, celebrating vanity metrics, hiding from price conversations, publishing without distribution, hiring to escape learning. Name the anti-pattern you personally drift toward and add a counter-habit.
<!-- pad:11 -->Operator Drill
Schedule one concrete action from this guide within 48 hours. Put it on the calendar with a duration. Afterward, write a short note: action taken, evidence collected, decision unlocked. Share the note with a peer or future-you folder. Drills beat rereading.
<!-- pad:12 -->Key Takeaways
- Value and alternatives set price; hours set floors.
- Brave starting point + live tests.
- Few packages; time-bound discounts.
- Some pushback is healthy.