Product and business
The decisions a founder or product lead makes about a BSV product: how it earns, what it charges, what it measures, how it grows, who holds the money, and how much to say about the network.
When a payment costs a fraction of a penny, needs no account and settles the moment the recipient's wallet accepts it, a product can charge for different things and grow in different ways. It also has decisions to make that a card-based product does not: who holds the money, what to do when a payment cannot be taken back, and how much of the network users should see.
This section is for founders and product people making those decisions. It covers product and business only. Where a decision has legal or regulatory consequences, the page says so once; that part needs advice for your jurisdiction.
Start from your question
"How will this make money?" Read Business models: pay per use, metering, allowances, tipping, credit to try, and what each one asks of the user.
"What should it cost, and in what currency?" Read Pricing: pricing in local currency and settling in satoshis, showing the price before the action, free tiers, and refunds when every payment is final.
"How do I know it is working?" Read Measuring a product: a first payment as activation, connection and allowance metrics, recovery readiness, and measuring without tracking people on a public ledger.
"How do I get users without buying them?" Read Growth that pays: referral payouts that arrive instantly, paying for contributions, and the fraud that follows any reward.
"Should we hold our users' money?" Read Custody as a product decision: the user's own wallet, the product holding funds, and the arrangements in between, as onboarding, support and recovery trade-offs.
"Do we mention BSV at all?" Read Talking about BSV: where your product sits on the expression scale, when to name the network, and the copy that loses people.
What this section assumes
It assumes you have already decided to build and want to know what the product should do. It does not argue for the network. It gives no market sizes or conversion rates, because none have been published for BSV products that this guide can stand behind. Where a page is reasoning rather than reporting, it says so in an open question.
The design detail behind each decision lives in the Patterns section. These pages link to it rather than repeat it. Three reference designs show these decisions applied to a reading app, a web app and an agent.
Related
- Why design for BSV: the constraints that shape every product here
- Getting to know your users: what motivates people and what stops them
- User personas: five people to test a business decision against
- Research: finding out whether anybody wants the product
- Pay-per-use reader: pricing, allowances and refunds in one worked product
Written from: the pages listed here.