Where it fits
Bonsai separates a basic project tier from plans that include client-facing commercial workflows and a portal. The pricing page uses a per-user unit, which means the number of paying staff matters even when the client count is described as unlimited. Agencies buying only for document intake should compare the portal and form requirements against the overhead of adopting contracts, scheduling and finance in the same platform.
Five paid Essentials users at the stated annual equivalent of USD19 each produce a USD95 monthly equivalent and USD1,140 annual base, not a USD228 subscription for the whole agency. At USD25 per user month-to-month, five users would spend USD125 each month. Test which people actually need paid internal access and whether the portal and questionnaire can handle a client handoff. If contracts and finance already work elsewhere, account for maintaining two sources of client data before adding this suite.
Worth a closer look if…
- Agencies evaluating a portal alongside proposals, contracts and invoices.
- Teams that can define the number and duties of internal paid users.
- A buyer who needs to compare an Essentials workflow against a higher branding tier.
Check before you commit
- A Basic subscription is not evidence of client-portal access.
- Removing provider branding appears at a different tier from the basic portal.
- Per-user annual pricing creates a full-year cash commitment for each paid seat.
Brand surfaces & evidence
Product-level notes are separate from the plan-specific evidence below.
A per-user client and project platform with a portal on higher-than-basic plans.
Official source ↗ · 2026-11-12Exact plan support not established
Client-facing billing surface not established
No complete app-surface verification recorded
Original media and complete historical record need verification
No plan-specific verification recorded.
No plan-specific verification recorded.
No plan-specific verification recorded.
No plan-specific verification recorded.
No plan-specific verification recorded.
How clients participate
Trial the questionnaire and client-portal route independently of the internal project interface. Do not infer external-user permissions from the number of paid staff seats.
Read the participation checklist ↗Exit & export
Ask how client records, signed documents, attachments and relevant project history can be exported. Financial exports alone do not prove that all client-facing conversations are portable.
Make the exit test ↗