A recent update to WASEVERIN Image Converter introduced a public Pricing page.
The image converter remains free, and payments are not enabled yet. The page currently explains what users can access today and previews a possible Pro plan for future features.
This raises a useful product question:
Should a SaaS product publish pricing before its payment system is ready?
The answer can be yes, as long as the difference between current and planned functionality is clear.
Pricing and payment are different features
A Pricing page communicates the product structure:
- What is available for free
- What may be included in a paid plan
- How much that plan may cost
- Whether the plan can currently be purchased
A payment system has a different responsibility. It handles checkout, payment confirmation, subscription status and access to paid features.
Separating these two areas allows a product to define its plans before introducing payment complexity.
Be clear about what is available
The most important requirement is transparency.
For WASEVERIN Image Converter, the current Free plan includes:
- Browser-based image conversion
- No image uploads
- No account requirement
- No watermark
The planned Pro option is displayed at $4.99 USD per month or $39 USD per year, but it is clearly marked as unavailable for purchase.
This avoids creating a checkout experience for features that are not ready.
Users should be able to understand the difference between available now and planned for later without reading additional documentation.
Keep the free workflow independent
The core conversion workflow remains unchanged:
- Choose an image
- Select an output format
- Convert it locally
- Download the result
This workflow should not depend on a payment provider or subscription service.
If payment support is added later, temporary billing failures should not prevent users from accessing the existing free converter.
Keeping the free workflow independent also makes future payment development easier to test and release separately.
Prepare without pretending
A Pricing page can prepare a product for future monetization without pretending that payment functionality already exists.
It provides an opportunity to validate:
- Whether the Free and Pro distinction is understandable
- Whether the planned price feels reasonable
- Which features users expect from a paid plan
- Whether users show interest before payment development begins
This feedback can be more useful than building a complete billing system based only on assumptions.
Final result
Publishing pricing before payments can work when the page is honest and the existing product remains unaffected.
The current update defines the Free plan, previews the planned Pro direction and keeps image conversion available without payment or registration.
Explore the Pricing page:
https://image.waseverin.com/pricing/
Would you publish pricing before integrating payments, or launch both at the same time?
Top comments (1)
Publish first, with one addition: what decides whether it works is not only whether the page is honest, it is whether the number survives contact with your cost to serve.
An unshipped feature you can quietly delay. A published price you have to walk back, and you walk it back in front of the people who showed up earliest. That is expensive in a way the page does not look like it is.
So before it goes live, price a deliberately heavy user rather than the median one. Anything with per-unit cost underneath it (model calls, storage, egress) can convert beautifully at a number that sits below your marginal cost on the top few percent of accounts, and you do not find that out until those accounts exist. If you are not confident yet, one line saying introductory pricing may change is much cheaper than a repricing email six months in.
The other thing I would add to your setup: capture intent at the point of interest, not just the pageview. Email plus which plan they clicked. Otherwise you get the demand signal without knowing who wanted what, and that plan-level breakdown is most of the value of shipping the page early.