Getting Started
Floatless helps SaaS teams run subscription billing, usage-based billing, invoicing, payment collection, and customer recovery without wiring those workflows directly into product code.
This getting started path is for operators, founders, revenue teams, and engineers who need to understand how the platform fits together before launch.
What you'll do
- Create your workspace and invite the people who will manage billing.
- Complete business verification where required for payouts and payment operations.
- Configure products, prices, tax behavior, invoice appearance, and payment settings.
- Add or import customers.
- Create orders or subscriptions.
- Run billing, review generated invoices, and collect payment.
- Connect public APIs and webhooks when another system needs billing data.
Start with one simple product and one test customer. Once the invoice lifecycle is correct, expand into coupons, usage, taxes, and integrations.
Prerequisites
- A business email address.
- Legal business details for KYB, if your workspace will process payments.
- At least one product or service you plan to bill for.
- A customer record with billing contact and billing address.
- A decision on whether billing will be flat-rate, seat-based, usage-based, or a hybrid model.
Recommended learning paths
| Goal | Start here |
|---|---|
| Launch billing for a new SaaS product | Create a product |
| Understand how Floatless models revenue | Products and Pricing models |
| Run recurring billing operations | Bill runs |
| Configure recovery for failed payments | Failed payments and retries |
| Integrate another system | Public API overview |
| Prepare for finance review | Compliance and security |
Platform map
Floatless uses a simple operational chain:
Product -> Price -> Customer -> Order or Subscription -> Bill Run -> Invoice -> Payment -> Reporting
Most setup issues come from skipping one of these dependencies. If an invoice does not look right, inspect the product price, customer tax settings, subscription dates, and bill run configuration before editing the invoice manually.