Describe the boundaries you actually need

A three-person team serving two clients has at least two different counts before any software is chosen. Staff seats describe people who need access. Client workspaces describe how work and permissions are separated. Connected mailboxes, domains, contact inventory and message volume add further units. A vendor’s unlimited-users label does not establish that every client workspace or sending account is included.

Begin with access requirements. Decide who must see each client’s records, who can change billing and who owns the mailbox and domain accounts. A shared login is not evidence that a plan provides the required permission boundary.

Write one budget line for each billable object

Use an illustrative scenario of 3 team members, 2 client workspaces and 6 mailbox licenses. These numbers are inputs, not a recommendation for how many accounts should send. Allocate each actual purchase once. If two team members access the same client space, do not invent a second workspace charge unless the vendor’s terms actually bill that object twice.

Conversely, do not divide a quoted per-workspace amount by the number of staff and compare it with a per-user amount as if both represented the same scope. Record the billing unit beside the number. When workspace fees are not verified, leave them unknown and keep the overall total visibly incomplete.

Check whether usage pools are shared

A contact allowance can be shared across an account, allocated per workspace or governed by another rule. The same uncertainty applies to messages and data credits. Ask whether one client’s usage can exhaust another client’s allowance and whether administrators can set useful boundaries. Do not assume that creating a second workspace doubles every quota.

Smartlead’s official pricing page includes client/workspace and API dimensions. We have not verified one complete software-tier and add-on quote for the same billing cycle. Ask for that named configuration before assigning the cheapest number visible elsewhere on the page.

Account for handover before the contract starts

For each client, name the owner of domains, mailboxes and data-provider subscriptions. Check whether the proposed tooling can export the information and configuration you are entitled to retain. Ask about access after cancellation and how a client moves to another operator. A low first-month bill can hide substantial handover work.

These questions do not require buying a more expensive package by default. A simpler account structure or a clearer contract may solve the problem. Record unsupported permissions as a constraint rather than estimating that a future upgrade will probably fix them.

Finish with a capacity and cost record

Compare sending software with sending software for the same task. Compare data purchases in their own action units. Combine their costs only after each category is understood. Save the scenario’s source dates, workspace assumptions, renewal terms and unresolved fields. No combination of staff seats, client counts or mailbox licenses predicts results; it simply makes a procurement decision auditable and easier to revise.

Use a handover checklist for each client

Create a separate row for Client A and Client B showing domain registrant, mailbox administrator, sending workspace administrator, billing owner and export recipient. A staff member’s access to both rows does not mean that client data should be combined. Ask which quota is shared before assuming that two client workspaces double the allowance.

At exit, the client should know which subscriptions it owns and which service access ends with the agency relationship. Confirm the export fields, usable format, credentials transfer process and cutoff date before work begins. A PDF report is not necessarily an export of contacts, campaigns or settings that another operator can continue using.

  • Count each billable object once and label its owner.
  • Test the required CRM operation and access boundary, not just whether an integration logo appears.
  • Ask whether removing one workspace changes another client’s quota or billing.

Sources and further reading

Source-based editorial research. Vendor terms can change; confirm the current contract before purchase.

Continue your research