We tested our SDK against 10 Claude subagents. Our SDK ran 1,165% faster.
By The Verbiflow teamThere are two reasonable ways to run batch outbound work from a coding agent. You can have Claude Code write one job using the Verbiflow SDK. Or you can have Claude Code send the work to 10 Claude subagents and let each one handle one company. We ran the same task both ways: find every security certification claimed on the trust pages of 10 well-known SaaS companies, with the same SDK, model, and task. Here’s what we saw.
Wall clock
Retries needed
Same answer
What the test shows
If you are analyzing one company, asking an agent to do it directly is probably fine. The setup cost of building one job may not be worth it for a one-off task.
Outbound work is rarely one company. Once the same operation needs to run across 10, 100, or 1,000 accounts, the tradeoff flips. You pay the setup cost once, and every additional company after that runs faster and with fewer failures.
The agent version treated 10 companies like 10 separate jobs. The SDK version treated them like one batch.
The principle
The SDK version still uses LLM calls for extraction, classification, and reasoning where needed. The difference is that those LLM calls run inside one structured job with concurrency, caching, retries, and shared state instead of inside 10 separate agent loops.
Use the agent to design the workflow. Use the SDK to run the repeated work, including the LLM steps.