Compare
Agency vs freelancer vs in-house
For one well-scoped MCP server that has to keep working, a named studio beats both an agency and a lone freelancer: a company to invoice, a person to hold accountable, and no PMO markup. An agency wins for a multi-quarter, multi-vendor programme. A freelancer wins on price for a build you will own and never change. If you are running an enterprise integration programme with procurement gates, this is not Portkeel.
Three models, three failure modes
| Model | Best for | Failure mode |
|---|---|---|
| Agency | Large multi-vendor programmes | Overhead and account-manager churn |
| Freelancer | Cheap one-off you will own | Key-person risk at migration time |
| Named studio | One server that must keep working | Capacity ceiling on huge programmes |
Where we lose
Decide
- Is this one server, or a programme of many?
- Will it need maintaining after launch?
- Do you need a procurement-grade vendor process?
- Is price the only axis that matters?
"One server" plus "needs maintaining" points to a studio. "Programme" or "procurement-grade" points to an agency.
Delivery-model questions
- What does an agency get you?
- Process, a contract, and someone to escalate to, at a markup that pays for account managers you will mostly email around. For a large multi-system programme that markup buys real coordination. For one MCP server it usually buys overhead.
- What does a freelancer get you?
- The lowest price and the highest key-person risk. A good freelancer will build you an excellent server and may be unreachable the week the spec revises. That is fine for a build you will own afterwards and dangerous for one you need maintained.
- Where does a named studio fit?
- Between the two on purpose: a company to invoice and a named person to hold accountable, without an agency's layers. The person who reviews your code is the person who answers your email. That is the shape Portkeel is, and it suits a single well-scoped server that has to keep working.
- Who should not hire us?
- A large enterprise running a multi-quarter, multi-vendor integration programme that genuinely needs an agency's PMO and procurement machinery. We are one accountable studio, not a staffing bench, and pretending otherwise would fail you in month two.