What should I look for in a platform when scaling from 10 to 100 agents?

So you're thinking about growing from a small team to a proper battalion. The first thing you'll discover is that the shiny features that got you to 10 agents become massive liabilities at 100. Most platforms are designed to sell seats, not to scale efficiently. Forget the marketing checklists; here's what will actually bite you.

The core issue is that costs and complexity don't scale linearly. That "per-agent" pricing model is a trap. At 100 agents, you're not just paying 10x the cost of 10 agents; you're paying for the privilege of hitting the limits of their architecture. You need to dissect their API rate limits, concurrency, and how they handle bulk data operations. A platform that feels snappy with 10 concurrent users might fall over with 50. Ask them for the actual, documented API limits and the performance specs for their largest customers. If they dodge, walk away.

From an architectural standpoint, you're moving from a simple setup to a distributed system. You need to evaluate:
* **Orchestration vs. Chatty APIs:** Can you update 1000 tickets with a single API call, or do you need 1000 calls? This directly impacts your integration costs and stability.
* **Data Isolation & Reporting:** At scale, running a report shouldn't lock the entire ticket database. How do they handle analytics workloads? Can you self-host the data warehouse, or are you stuck with their expensive, sluggish reporting module?
* **Integration Sprawl:** With 10 agents, you might have a couple of Zapier hooks. With 100, you have a mission-critical service mesh. Look for platforms with webhooks that actually provide meaningful payloads and support for idempotency keys to handle failures gracefully.

```json
// A "good" webhook payload vs. a useless one
// Good: Includes resource ID and enough data to act without a callback
{
"event": "ticket.updated",
"idempotency_key": "abc123-456-def",
"ticket": {
"id": 12345,
"status": "closed",
"custom_fields": {...}
}
}

// Bad: Just a notification that forces an extra API call
{
"event": "something_happened",
"resource_id": 12345
}
```

Finally, consider your escape velocity. At 100 agents, migrating is a year-long project, not a weekend task. Scrutinize their data export functionality *now*. Is it a real, queryable database dump, or a zip file of JSON blobs that requires their proprietary middleware to parse? The more "special sauce" in their platform, the more locked in you become.

Just my 2 cents