Guide · Planning
A 2027 AI plan for agencies
For 2027, an agency should budget for six kinds of AI work: client-facing support agents, internal workflow automation, CRM and HubSpot hygiene, moving off per-task automation pricing, MCP connectors for clients’ SaaS, and EU AI Act disclosure work for EU clients. This guide gives you a worksheet to price each one from your own numbers, rules for build, buy or partner, and a dated calendar. It has no market statistics, because we have none we can verify.
How to use this plan
Treat it as a one-page exercise for your next planning meeting. Work through the questions, fill the line items from your own invoices and time records, then use the decision rules to decide which builds you do yourself, which you buy and which you hand to a partner. Check the calendar last, because a fixed date should move a build earlier, not decide it.
The six builds to consider
| Build | Who it is for | Read more |
|---|---|---|
| Client-facing support agents | Clients with repeat customer questions, such as Shopify stores | Holiday support guide, custom AI agents |
| Internal workflow automation | Your own intake, reporting and handoffs | Internal workflow automation |
| CRM and HubSpot hygiene | Any client whose automations depend on clean data | HubSpot cleanup |
| Moving off per-task pricing | Clients with growing Zapier or Make bills | Cost guide, custom automation |
| MCP connectors for clients’ SaaS | Software clients who want ChatGPT, Claude or Cursor to use their API | MCP server development |
| EU AI Act disclosure | Clients with EU users or EU-facing AI features | Disclosure checklist |
You do not need all six. Pick the two or three where clients are already asking, or where a deadline below forces the issue.
Budgeting worksheet
Fill this in with your own figures. We leave the amounts blank on purpose, because ours would be guesses.
Questions to answer first
- Which clients have asked for AI work in the last six months, and for what?
- Which of your own processes lose the most hours each month to copy, paste and chasing?
- Which clients run automations on per-task pricing, and has their run count grown?
- Which clients have EU users, and who owns disclosure on each?
- Who on your team can maintain what you build, and how many days a month can they give it?
Line items
| Line | What to put in it |
|---|---|
| Model and API usage | Measured cost per task times expected tasks. See the cost guide. |
| Automation platform fees | Current plan, renewal date, and the billing unit (tasks or executions). |
| Build days | Days per project times your day rate, or the sprint price if you buy one. |
| Maintenance | Days per month to monitor, fix and update, per live system. |
| Data cleanup | One-off effort before any agent reads a CRM. |
| Compliance work | Inventory, disclosures and evidence for EU clients. |
| Contingency | A margin you set after reviewing last year’s overruns. |
Build, buy or partner: decision rules
- Buy when an existing tool does the job and the client accepts its limits and its pricing unit.
- Build in-house when the workflow is core to your service, you will reuse it across clients, and you have someone to maintain it.
- Partner when scope is fixed and short, the skill is outside your team, or work arrives faster than you can hire.
- Decline when the client cannot say what a good result looks like. No team can build to an unstated target.
- Whichever you pick, write down who owns maintenance after launch before the build starts.
Dated calendar, 2026 to 2028
| Date | Event | Source |
|---|---|---|
| 2 Aug 2026 | EU AI Act Article 50 transparency obligations apply. | Commission FAQ |
| 1 Dec 2026 | Zapier Next Gen Zaps and the Zapier SDK also use tasks; each successful Next Gen run uses at least one task. | Zapier help |
| 2 Dec 2026 | End of the grace period for Art. 50(2) marking, for systems placed on the market before 2 Aug 2026. | Commission FAQ |
| 2 Dec 2027 | Annex III stand-alone high-risk obligations, as moved by the Digital Omnibus, Regulation (EU) 2026/1744. | Hunton |
| 2 Aug 2028 | Annex I product-embedded high-risk obligations, as moved by the Digital Omnibus. | EUR-Lex |
Add your own dates beside these: client renewals, platform renewals and your budget sign-off. For the Article 50 detail, see the disclosure checklist.
Questions
What AI builds should an agency budget for in 2027?
Six are worth pricing: client-facing support agents, internal workflow automation, CRM and HubSpot hygiene, moving off per-task automation pricing, MCP connectors for clients' SaaS products, and EU AI Act disclosure work for EU clients. Budget only for the ones your clients have actually asked about.
Should an agency build, buy or partner for AI work?
Buy when a tool already does the job and the client accepts its limits. Build when the workflow is core to the client and no tool fits. Partner when the work is fixed in scope, outside your team's skills, or arrives faster than you can hire.
What does a partner-overflow build team do?
Kingdom of Kumar takes overflow builds from agencies as fixed-scope sprints of $500/month, or $500/month for build days, such as HubSpot cleanup and n8n, Zapier or Make migrations to custom automation.
Which dates should an agency put in its 2027 plan?
Put in 1 December 2026 for Zapier's Next Gen task change, 2 December 2026 for the end of the Article 50(2) grace period, 2 December 2027 for Annex III high-risk obligations under the Digital Omnibus, and 2 August 2028 for Annex I.
Do you publish market statistics in this plan?
No. The plan is a framework of questions, budget lines and decision rules. It contains no market statistics because we have not verified any, and the worksheet has no invented amounts.
Next step · Partner overflow
Kingdom of Kumar works as an overflow build team for agencies: fixed-scope sprints of $500/month, or $500/month for build days, scoped in writing before work starts. Typical overflow is HubSpot cleanup and n8n, Zapier or Make migrations to custom automation. Email Mayank Raj with the scope and the deadline.