When the Payment Provider Says No: Resetting Holdie as a Free Beta

The previous article ended with Holdie fully equipped for paid subscriptions: Lemon Squeezy integrated, trial logic wired up, webhooks firing. It was ready to charge people. Then Lemon Squeezy stepped in.

The Rejection

Lemon Squeezy flagged Holdie as high-risk. Their concern was crypto. Holdie lets users track any asset they own, including cryptocurrency, and that was enough to trip their review process. The fact that Holdie has no transactional capability whatsoever, no buying, no selling, no wallets, no exchange connections, just a field where you can type in a value and save it, did not seem to move them.

I explained this clearly. Holdie is a net worth tracker. It is closer to a spreadsheet than a crypto platform. The review process was not really interested in nuance, and the live subscription path stayed blocked.

It was frustrating, but in hindsight it forced a useful pause. The subscription infrastructure was in place before I had a single paying user. Lemon Squeezy blocking activation meant I had to stop and ask a more honest question: was the product actually ready for people to pay for it?

The Doubt

The honest answer was: probably not yet. Building the product had been absorbing enough that I had not spent much time thinking about whether it was genuinely useful to people who were not me. I knew what I wanted it to do. I did not have strong evidence that strangers would find it valuable enough to hand over money.

That is a reasonable thing to figure out before locking in a pricing model. The Lemon Squeezy situation just made it impossible to avoid the question any longer.

Going Beta

The decision was to open Holdie as a free beta. All paid logic is commented out for now. Anyone who signs up gets full access. The goal is to get real people using it, watch where they get stuck, and find out what is missing before committing to a pricing structure.

This also meant shifting the focus from shipping features to sharpening what was already there. A few things that had been slightly rough got proper attention: the snapshot history chart got time range filtering so you can zoom into the last month or last quarter rather than looking at everything at once. Small things, but the kind that matter when you are trying to make a good first impression on someone who does not already know how the product works.

The Feedback Path

The other obvious gap was having no way for users to tell me what was wrong or what they wanted. A feedback button now sits on the dashboard. It is a simple floating button that opens a small form: a text field, an optional email, and a send button. Submissions save to a database table and arrive in my inbox.

That is the entire feature. No voting mechanisms, no categorisation, no public roadmap. Just a direct line between a user and me. At this stage that is the right level of sophistication. The goal is to hear from people, not to manage a feedback product.

What Comes Next

The payment provider question is not resolved, just deferred. Lemon Squeezy may not be the right fit, and there are alternatives worth exploring once there is a clearer picture of what users actually need. Going straight to a full Stripe integration is still on the table if the compliance overhead turns out to be manageable.

For now the focus is on the beta. If you track your finances and want to give Holdie a try, it is free at holdie.io. The feedback button is right there on the dashboard.