What shapes a SaaS product for the United States
The American market rewards SaaS products that are easy to buy. For a small customer that means a card and a clear price. For a large one it means clearing procurement, security and legal, and the product either helps with that or slows it down.
| Topic | What it means for your product | Decide early |
|---|---|---|
| Security review | Larger customers send a questionnaire and commonly ask for a SOC 2 report, single sign-on, audit logs and a penetration test summary before they sign | Which of these your first target customers will insist on |
| Sales tax | States differ on whether a subscription to hosted software is taxable, and a seller can owe tax in a state once its sales there pass a threshold, with no physical presence | A tax engine connected to billing from the first invoice |
| Automatic renewals | State laws, with California's among the strictest, require clear renewal terms before purchase, a reminder in some cases and a way to cancel online that is as easy as signing up | The wording at checkout and the cancellation path |
| Your privacy role | Under state privacy laws you are usually a service provider or processor for your customers' data, which calls for a contract limiting what you do with it. Customers often send their own terms | Your standard data processing agreement and list of vendors |
| Industry rules | Selling to healthcare brings HIPAA and a business associate agreement, selling to schools brings student privacy laws, and selling to government brings its own authorization programs | Which industries you will sell to first |
| Accessibility | Public universities, governments and many large companies ask for an accessibility conformance report based on WCAG before they buy | Whether accessibility testing is part of every release |
| Getting paid | Self-serve plans run on cards. Larger contracts are invoiced and paid by ACH or wire, often through the customer's procurement system | How purchase orders, invoices and payment terms are handled |
Product workflows we build for the US market
Self-serve signup to renewal
The path most customers take, with each legal detail handled inside the flow.
- Create an account
- Reach a first result in guided setup
- Choose a plan with renewal terms shown
- Tax calculated for the billing address
- Receipt and renewal date emailed
- Cancel online at any time
Enterprise deal
What happens between a verbal yes and the first login.
- Security questionnaire completed
- Data processing agreement signed
- Single sign-on configured
- Users provisioned automatically
- Order form and invoice issued
- Paid by ACH
Usage-based billing
For products priced on what customers consume.
- Usage events recorded
- Running total shown to the customer
- Alert before a limit is reached
- Invoice built from the meter
- Disputes settled from the event log
Data rights request
When one of your customer's own users asks to see or delete their data.
- Customer admin opens a request
- The person's records located
- Export produced or deletion queued
- Completed inside the legal deadline
- Record kept for the customer
What we build
Multi-tenant architecture
Tenant isolation designed first, with data boundaries enforced in the database and tested in every release.
Enterprise features
Single sign-on, automatic user provisioning, roles, audit logs and admin controls, present from the start so they are not rushed in for the first big deal.
Billing and tax
Subscriptions, seats, usage metering and invoicing through a billing platform, connected to a tax engine for state rules.
Compliance-minded engineering
Encryption, access reviews, logging and change control arranged so your auditor can find evidence without a scramble.
Product design
Onboarding that gets a new account to its first result quickly, and settings an administrator can understand. See SaaS UI/UX design.
APIs and integrations
A documented API, webhooks and the integrations your customers ask for most. See API development.
What we need from you
- Your ideal customer and the problem they pay to solve
- Pricing and packaging, at least in draft
- Security or privacy questionnaires already received from prospects
- Counsel's input on terms of service and renewal wording
- A decision maker for product trade-offs
Ownership and licensing terms are defined in the project agreement.
A readiness checklist for a US SaaS launch
Before development starts
0 of 8 checkedWhat to do next
Tell us who buys the product, how they will pay and what you have built so far. We will reply with our view of the architecture, the enterprise features worth building first and a sensible first release. Start a conversation or book a 30-minute call.
Common questions
Is SaaS subject to sales tax in the United States?
In some states. Each state decides whether hosted software is taxable, and the answers differ, sometimes by type of customer or product. A company can owe tax in a state once its sales there cross that state's threshold. Most SaaS companies connect a tax engine to billing and register state by state as they grow. Your accountant decides where to register, and we make sure billing can apply the result.
When does a SaaS company need a SOC 2 report?
When the customers it wants begin to require one. Mid-size and large companies commonly ask for it during procurement, and its absence can stall a deal. It is an auditor's report on your company's controls, so it cannot be bought with the software. What we can do is build the product and its infrastructure so that the evidence exists from day one.
What do enterprise buyers expect before they sign?
Typically single sign-on with their identity provider, automatic provisioning and removal of users, role-based permissions, an audit log, data export, a signed data processing agreement and answers to a security questionnaire. Many also ask about uptime commitments and support hours. Building the first four into the product early costs far less than adding them under deadline for a deal.
What do auto-renewal laws require of a subscription product?
The details vary by state, but the common requirements are to present renewal terms clearly before the customer pays, obtain consent to them, send a confirmation that explains how to cancel, and let a customer who signed up online cancel online. Some states add reminders before long terms renew. Have counsel approve the wording. The product should make the compliant path the default.
Where to go from here
Related serviceSaaS DevelopmentA subscription product needs more than features