Avery

One clarification for people arriving from a chat product: this was API list pricing. If you use the model through a subscription rather than by key, none of these numbers are the ones you are billed on, and your allowance did not necessarily change on 30 July. Different page, different rules.

Launching next month so I have been reading about exactly this, and the prep list I ended up with is short.

Complete every identity and business detail on the account weeks early rather than at the minimum needed to accept a payment. Put a real product page, a refund policy and a contact address on the site before launch, because those are the first things anyone reviewing looks for. Run a handful of genuine small transactions in the weeks before so the account has a history that is not a vertical line. Set the statement descriptor to the product name. Have the bank account verified in advance and in the same name as the business.

None of it guarantees you skip a review, but it turns a review into a two email conversation instead of a document hunt during your one busy week.

Doing exactly this right now, 25 a day, second week in. Two surprises. First, putting the company's actual name and one specific detail in the opening line more than doubled my replies compared to the version where I described my product first - every guide says this and I didn't believe it until I split it fifty-fifty by hand. Second, sending from a hosted mailbox on my own domain has been fine, but I had to add the DMARC record myself because the setup wizard didn't, and I only noticed because I checked with a lookup tool. Took ten minutes.

Get the arithmetic straight first, because it is less bad than it feels. The dispute fee is refunded if you win, so the swing between winning and losing on a twenty nine dollar charge is the charge plus the fee, roughly forty five dollars either way, against your hour.

What actually decides these on digital goods: evidence that the person had access and used it. Signup timestamp with IP, login history with dates, the record of them accepting terms, usage logs showing the specific things they did, the receipt email and any support correspondence. Screenshot of the refund policy as displayed at checkout. If you have all of that, unrecognised transaction disputes are winnable a fair proportion of the time.

But the fix for unrecognised is upstream, not in the response form. Most of them are genuinely somebody not recognising a line on a statement. Put the product name in the statement descriptor rather than your company name, put it in the receipt subject line, and email before every renewal. That removes more disputes than any amount of evidence gathering.

Keep a text file of exact quotes. Not paraphrases. When you paraphrase you translate into your words, and your words are the ones that do not rank and do not resonate.

Tore a test sheet both ways and my grain runs across the spine. Well, that explains the entire first book.

I didn't. I'd assumed that was decorative. Adding it to the next one.

Corollary I'd add: usage-based also needs the usage to correlate with the value they get, not just with your cost. If your expensive customer is expensive because your PDF renderer is inefficient, charging them for it is charging them for your bug.

Something that helped me more than any headline formula: write the sentence a happy customer would use to describe you to a colleague, out loud, in the pub. Mine came out as "it chases the people who owe you photos so you do not have to". I put almost exactly that on the page and my five second test answers went from "file sharing?" to people repeating the sentence back to me.

The formulas produce headlines that sound like software. The pub sentence produces headlines that sound like a person.

Do at least two prototypes. Everyone's first coptic looks like a disaster and it's much less painful when it cost 20p.

Do it, but understand what you now owe.

That $7,480 is deferred revenue. It is on your balance sheet as a liability until you have delivered the months. If you spend it in Q1 and three people ask for prorated refunds in month 4, you are paying that out of Q2 cash. It is not free money, it is a loan from your customers repaid in service.

Practical guardrails that cost nothing:

• a written refund policy before you sell the first one. Prorated, not full, is normal and defensible.
• do not count annual cash as MRR. Divide by 12 or you will lie to yourself about growth.
• keep a mental reserve of maybe 20% of annual cash for the refunds that will happen.

Chargebacks on annual are also nastier than monthly. A $374 chargeback is a real hit and the dispute process is unpleasant. Send a receipt with a clear descriptor so people recognise the line on their statement.

If you do reback, photograph the spine first, including the lettering, from straight on. If the original spine piece is salvageable at all it gets laid back down on the new leather afterwards and you'll want the reference.

Write the migration runbook before diligence, not after. Buyers pay more for a deal they can already see landing, and the exercise will also tell you which parts of your own billing you never really understood.

Do not register early to be safe. That is advice from people who sell registration services.

A registration is not a one time act of tidiness, it is a permanent filing obligation. You will file returns in that state forever, including zero returns, sometimes monthly, and each one is a deadline you can miss and be penalised for. Registering in fourteen states at eleven hundred a month would be the single worst use of your evenings available to you.

Track, do not register. Know your numbers by state. Act when a number gets close to a threshold.