Everything people ask before onboarding

A vendor FAQ is usually written by whoever owns the sales funnel, which is why the awkward questions are missing from most of them. The test for whether one is worth reading is simple: find the answer that costs the company something. If there isn't one, the page is a brochure with a chevron on each row.

So the list below includes the answers we would rather not give. We hold no SOC 2 and no ISO 27001. We do not sign Business Associate Agreements, which makes our health-records product a poor fit for a covered entity today. Pacific POS needs a connection, so a site with unreliable connectivity should hear that before a Friday service rather than during one. Rates are not published anywhere on this site. And if what you want is a vendor with a thousand-person support organisation, we are honestly not it. Those sit in the same accordions as everything else rather than in a footnote nobody opens.

The questions are grouped the way they get asked — getting started, contracts and billing, hardware, security and data, support, and who we are. Thirty-odd questions in one accordion is a wall; six short lists means the person who came for one hardware answer is not scrolling past onboarding to reach it.

Nothing here is a substitute for asking. If your situation has a wrinkle — an existing system nobody wants to migrate, a site with no reliable connectivity, a regulator with an opinion — the useful version of this conversation happens on a call, not in an accordion.