Customers may want the feature but reject SaaS delivery
A prospective receipt-printer user likes an HTTP API but cannot route business data through a third party.
The takeaway
Demand for a feature does not validate its delivery or pricing model.
The context
The commenter reports a real business use case but needs hosting within their own VPN and domain because of customer restrictions. They also question SaaS delivery when local hardware must still be installed. The feedback shows that adoption can be blocked by deployment boundaries rather than missing features.
Steps worth trying
Editorial suggestions, not promises made by the original author.
- 01
Before a demo, establish data flows, connectivity limits, and acceptable hosting locations.
- 02
Cost hosted, customer-hosted, and maintenance-service options separately and test willingness to pay.
Where this applies — and where it may not
One prospect’s feedback does not invalidate a SaaS market or prove that a self-hosted offering will sell.
From the discussion
“sending the data through a third party is a complete no-go for us”
@freedomben · View source
Show HN: Printercow – Turn any thermal printer into an API endpoint
@lionpixel · 150 points · 103 comments
Read the Hacker News threadSource: OpenIndex Hacker News dataset (ODC-By). Original content belongs to its authors. Summaries, translations, and suggested steps are AI-assisted editorial work. Read the sources; individual outcomes are not guarantees.