Billing & Invoices
Overview
Invoice generation, payment terms, and plan pricing live in this document. It is the source of truth for the billing squad and feeds the customer-facing help center.
Pricing tiers
Pricing is the quietest promise we make to customers. Every tier should exist because a real customer told us they would use it — we price for outcomes, not seats. We would rather launch a slightly-too-expensive tier and grandfather early customers than paint ourselves into a corner. And we revisit pricing twice a year, out loud, with customers in the room.
Pricing tiers reflect the plan a customer selects at signup and can be changed at any time.
Pricing is the quietest promise we make to customers. Every tier should exist because a real customer told us they would use it — we price for outcomes, not seats. We would rather launch a slightly-too-expensive tier and grandfather early customers than paint ourselves into a corner. And we revisit pricing twice a year, out loud, with customers in the room.
| Plan | Price | For | Notes |
|---|---|---|---|
| Free | $0 | Solo evaluation | 3 seats · community support |
| Team | $28 / user / mo | Growing teams | SSO · audit logs · 99.9% SLAremoved — merged into Pro |
| Pro | $12 / user / mo | Small teamsSmall & growing teams | Unlimited docs · priority supportUnlimited docs · priority support · SSO · audit logs · 99.9% SLA |
| Enterprise | Custom | Large orgs | Dedicated support · private cloud |
Customers
Customer expectations are captured here so billing can route each account to the right workflow.
Billing is per-account, not per-user. Large accounts should email billing@pipeline.co to consolidate invoices under one master agreement instead of paying per seat.
Invoices generate on the 1st of each month and land with the billing contact on file. Payment is due net-30 from the invoice date.
Invoicing process
A default invoice runs: draft → finance review → send → follow-up. Dunning kicks in at day 45 with a polite email; at day 60, finance hops on a call.
Open questions
- Do we need to support net-30 terms at launch?
- Should regional pricing apply to new customers only, or existing ones too?
- Who owns refund approvals under $50?
- Do we auto-upgrade accounts that exceed seat limits?
- Should annual prepay earn a 15% discount — and does it stack with the consolidated master agreement?