Disclosure: this article contains affiliate links. If you buy through them we may earn a commission at no additional cost to you. Our recommendations are based on the evidence recorded alongside this article, and prices were verified on the date shown.

What changed and why it matters

An Ask HN thread posted by user xtiansimon puts one specific, checkable question in front of anyone evaluating SaaS right now: can you ask a salesperson to mock up the solution with your own data before you sign, instead of taking their word for it? The thread is titled "Ask HN: Is Mockup Data a thing you can ask from SaaS Salesperson?" and runs on the original Ask HN thread.

The question isn't abstract. It comes from a real buyer scenario the poster describes directly: an accounting client signed on to a first point-of-sale (POS) system and ended up, in the poster's words, desperately unhappy with the results. That client is now vetting a third POS system within a seven-month span, after the poster says the promised solutions turned out ineffective and the API integration to the client's ERP was insufficient.

The detail

Strip away the POS specifics and the question generalizes to any SaaS purchase: sales conversations run on promises, demos, and slide decks, not on your actual data flowing through the actual system. The poster's question is whether a vendor will build a working mockup, using data that resembles what you'll really process, before money changes hands.

That matters because the two failures the poster names, an ineffective promised solution and insufficient ERP API integration, are exactly the kind of gaps a standard sales process can leave undiscovered until after signing: whether the tool can actually pull from your ERP, handle your record volume, or survive the edge cases your business generates every day. Two failed POS systems in one client relationship, per the poster's account on Hacker News, is the cost of finding that out after signing rather than before.

The thread doesn't report what any vendor said in response to the mockup-data request, and it doesn't name which POS vendors were involved. What it does establish, reliably, is the pattern: a buyer burned twice is now trying to build a pre-purchase check into the sales process itself, rather than relying on promises alone.

What it means for you

If you're evaluating any SaaS tool, the practical takeaway from this thread isn't about point-of-sale software specifically; it's about how you structure the evaluation before you commit budget and migration time. Asking a vendor to demonstrate the product against something closer to your real data and your real integration points, before signing, is the same instinct as insisting on a working preview instead of a slide deck.

That instinct applies directly to developer tools, where the gap between a sales pitch and a working environment is often the difference between a smooth rollout and a repeat of the POS story above. If you're comparing platforms in this category, our developer-tools buying guide walks through the criteria worth checking before you sign, not after.

Vercel sells into exactly this category, and if you're building the kind of evaluation checklist the Ask HN thread is pushing toward, you can [see current pricing at Vercel](See current pricing at the merchant) as one input into that comparison, alongside whatever mockup or trial access you can get directly from a vendor.

The deciding question, either way, stays the same as the one raised in the thread: does the vendor let you verify the fit before you commit, or only after?

Best for: buyers who've been burned once and want a pre-purchase check built into the sales process, not just promises.

Skip it if: you're buying a tool with a short, low-cost trial period where a bad fit costs little to reverse; a full mockup request may be overkill there.