CRM for agencies: the number to read before you pick one

Our own Pipedrive account, read on 22 September 2026, reports a ceiling of 120,000 API tokens a day. That is 30,000 base tokens times a plan multiplier of two, times two active seats. One search costs 40 tokens, so the whole marketing agency gets 3,000 searches a day, across every client account it runs. Sign a thirteenth client and that ceiling does not move. The CRM we install today is Twenty, and what a seat costs there. This page is not for every agency. Insurance, staffing, travel and property firms call themselves agencies too, and a recruitment agency wants an ATS rather than a CRM. What follows is for the prospecting, marketing or creative shop that holds several client accounts inside one CRM and wants to know what breaks at the twelfth client.

Read your daily token ceiling before you compare a single feature

We install CRMs for clients. We have put HubSpot, Pipedrive, folk and Attio into production, and we now refuse to install anything other than Twenty. The reason is a header we read on our own production account on 22 September 2026 at 16:27 UTC: `x-daily-ratelimit-token-limit` came back at 120,000, and `x-daily-ratelimit-token-remaining` at 105,149. We had already burned 14,851 tokens that day, before the afternoon sync jobs had even run.

Pipedrive publishes the formula, and on our account it checks out exactly. The daily budget is 30,000 base tokens, times a plan multiplier, times the number of seats. The multipliers run Lite 1x, Growth 2x, Premium 5x, Ultimate 7x. We are on Growth with 2 active seats out of 8 registered users, so 30,000 x 2 x 2 = 120,000. On our account the formula comes out exact with 2 and not with 8, so it is the active seats that count; Pipedrive itself never defines the word seat in its documentation. Costs per action: a single record is 2 tokens, a list 20, an update 10, a delete 6, a search 40. Once the budget is spent the API returns 429 until the reset, which happens at midnight on Pipedrive's server timezone, and that timezone is not necessarily yours. It matters when you schedule an overnight run: a budget exhausted at 23:00 reloads an hour later, not a day later.

The short-window limit is not one number either. It depends on the plan and on the authentication mode: 40 requests per 2 seconds for Growth with an API key, 20 on Lite, 100 on Premium, 120 on Ultimate, and four times those figures in OAuth. And the same page states a limit that matters more for this article's whole calculation: the search API is capped at 10 requests per 2 seconds, on every plan and every mode. A search-heavy enrichment pass hits that wall long before it dents the daily budget.

Now put the agency shape on top of that. The budget is indexed on seats and on plan tier. It is not indexed on the number of client accounts you run. Every client you sign shares the same 120,000 tokens. At 40 tokens a search, 120,000 tokens is 3,000 searches a day for the whole agency. Split across twelve clients, before any automation writes a record, that leaves 250 searches per client per day.

Twenty, which is the CRM we now install, publishes a different unit: 100 requests per minute, in batches of 60 records, on REST and GraphQL alike. What its documentation does not say is what that ceiling applies to. The page does not say whether it holds per workspace, per API key, per instance, or per something else entirely. We read the page on 22 September 2026 and the scope simply is not there. That changes the shape of the argument. Pipedrive publishes exactly what its ceiling is indexed on, and HubSpot publishes its ceiling per account and per plan tier. Twenty publishes a number with no scope attached.

Price-wise, the difference is smaller than the listicles suggest. Twenty is $9 per user per month on Pro, $19 on Organization, on annual billing, which is the default view of their pricing page and is marked 25 percent off; the month-to-month price is not displayed. All three tiers carry unlimited custom objects, custom fields and seats, Pro included. What Organization buys is per-row permissions, SAML and OIDC SSO, and a custom domain; it does not buy capacity. The pricing tiers as we last read them are on its entry, and the open-source core can be self-hosted for free.

HubSpot publishes its ceiling per account and per plan tier: 250,000 calls a day on Free and Starter, 625,000 on Professional, 1,000,000 on Enterprise. The table carries no seat figure in either direction, so we will not claim that adding a seat changes anything or that it does not. What the table does show is a ceiling attached to the account, not multiplied by headcount. We have installed both HubSpot and Pipedrive. We have not read folk's or Attio's daily ceiling, so both stay out of the comparison.

Give each client a workspace

A workspace per client still decides how you organise the data. Whether it also isolates quota, we cannot promise: Twenty's rate-limit scope is unpublished. The mechanics of that split, and what it costs you in admin, are covered in what a workspace per client costs you. What we can state is narrower: the separation itself is certain, and on quota isolation Twenty's documentation leaves the question open.

Name the three integrations you actually run

Ours are n8n, the automation engine that writes into the CRM; Fillout, the booking form that writes into it and creates the record; and Praiz, the call recorder that drops the summary. Three integrations, each making API calls, each drawing on the same daily budget. A search-heavy n8n scenario at 40 tokens a call eats a Pipedrive day faster than any human user.

One limit to state plainly. A Twenty API key is created in the settings of one workspace and is scoped to a role in that workspace, and the documentation we read on 22 September 2026 describes no cross-workspace reading. Reporting across all your clients means one key per client. On the other side of that trade, unlimited objects on the entry plan means each workspace can carry its own data model.

And if you arrived here from page one looking for time tracking, capacity planning and invoicing, you are looking for a PSA. We read the first four pages of Google results on this query on 22 September 2026, and they cover project management, time tracking, invoicing, the client portal, financial forecasting and resource allocation. Six functions, and every one of them belongs to an agency-management tool, not to a CRM.

Run the reading on your own account in one command

On Pipedrive, call any endpoint with your API token and read the response headers: `x-daily-ratelimit-token-limit` is your ceiling, `x-daily-ratelimit-token-remaining` is what is left of it today. On HubSpot, with a private app token, look for `X-HubSpot-RateLimit-Daily-Remaining`. Over OAuth, HubSpot does not return that header, so this reading only works with a private app token. The command is a single `curl -i`; we have not verified the equivalent on folk or Attio.

Whatever number comes back, divide it by your client count, then by the token cost of your most frequent call. And where a vendor publishes a number with no scope, as Twenty does with its 100 requests a minute, ask the question in writing before you sign. The full entry, with the API surface and the CRM category are the next stops if yours comes back shared. This page earns nothing from the recommendation: there is no affiliate link on it.