Three differences that compound across the engagement.
- Continuity, not rotation. The team that scopes is the team that ships. With a freelancer pool, you re-brief every sprint and re-establish trust every time the named contractor changes. With a partner, the project lead and the senior engineers are the same people from week one to go-live.
- Single accountability. One contract, one project lead, one signed-off scope. When something slips, there is one phone call to make, not a thread of "who owns this" between three contractors and a project manager.
- Production responsibility. A freelancer ships and leaves. A partner stays accountable for what was built - the quality of the architecture, the choices made under deadline pressure, and what happens when the client comes back after launch.
Freelancer pools have their place: short, well-defined, low-risk tasks where speed beats continuity. Custom builds for the agency's clients are usually not that. The cost of the rotation - re-briefing, knowledge loss, integration risk, post-launch ambiguity - tends to outweigh the per-hour savings within the first project.