The defining problem for an agency is not volume — it is separation. Each client needs its own ideal customer profile, its own message angle, and its own numbers. Run them from one shared list with one shared template and every client gets the same mediocre results, which is also how you lose the account.
Three failures appear in the first month, and all three trace back to data that was never separated.
Every campaign lives in its own project — a container holding one ICP, one lead list, one set of generated emails and its own tracking. Nothing is shared between projects, so client A’s contacts cannot appear in client B’s campaign.
| Client need | How it is handled |
|---|---|
| Distinct targeting per client | One project per client; the ICP is inferred from that client’s product description and stored with the project |
| No list bleed | Leads belong to a project; campaigns run against one project at a time |
| Per-client reporting | Sent, delivered, opened, clicked, replied, bounced and unsubscribed are tracked per lead inside the project |
| Predictable client billing | Credits are consumed per action — ICP 1, displayed lead 1, generated email 1, send 2 — so cost per client is recoverable |
Report on outcomes the client cares about, not activity. Sends are what you did; replies are what it produced.
Reusing one message angle across clients because it worked once. The angle that worked for a cybersecurity client does not transfer to a restaurant supplier — what transfers is the process: infer the ICP, generate per prospect, follow up on a schedule, and read the numbers per client rather than in aggregate.
Create a project per client, describe that client’s product in a sentence, review the inferred ICP with the client, generate leads, then draft and send. Follow-up is opt-in per lead and stops on reply. Because every project holds its own ICP and its own tracking, a client-facing report is a read of one project rather than a spreadsheet you assemble by hand.
Yes. Each client is a separate project with its own ICP, leads, generated emails and tracking. Accounts are per user, so one login can hold many client projects without mixing their data.
Credits are consumed per completed action, so the cost of a client’s campaign is traceable: ICP inference 1 credit, each displayed lead 1, each generated email 1, each send 2. A failed send costs nothing, so a project’s total credits map closely to the work delivered.
What clients want is outcome data — positive reply rate, cost per reply, dominant objection. Mailor tracks per-lead state (sent, delivered, opened, clicked, replied, bounced, unsubscribed) inside the project, so you can report the layer that matters without exposing the whole dataset.
Reuse the process, not the copy. Angles are tied to a specific buyer’s situation — a cold email that landed for one client’s industry reads as irrelevant to another’s. Mailor regenerates copy per prospect from that project’s ICP, which is what keeps campaigns from converging on one voice.