My new boss wants me to build an internal system that automates campaign setup and management across Google and potentially other advertising platforms. He believes AI will make it possible within about two months and expects me to build and maintain it alone.
My background is 15 years of developing client websites, ecommerce sites, CMS integrations, analytics, tracking, tag management, PHP, JavaScript, SQL, and APIs. I have not worked on campaign management or the media team's processes, so I would first need to learn that domain before I could automate it.
I am also the only developer at a 15-person marketing agency. I already maintain roughly 60 client websites, build new sites, manage many analytics and tag-management accounts, and handle SEO questions. Even if I could create a first version, there would be ongoing maintenance whenever advertising APIs change, and a bug could potentially spend an entire client's budget.
There are likely existing tools that already solve much of this problem, and our company does not have the staff or operational support to maintain a custom platform. How should I present this to my boss without making it sound like I am simply refusing to learn new skills?
3 Answers
You should not present this as something you are incapable of learning. Present it as a new product that needs discovery, subject-matter expertise, engineering time, testing, and long-term ownership. Your experience with websites and APIs is relevant, but campaign strategy and automation are still a separate business domain.
You could offer to investigate existing products and produce a limited prototype, provided your boss understands that it will require reducing your other workload. If he still expects you to deliver and maintain a high-risk platform alone without extra staff, budget, or time, that tells you the problem is organizational rather than technical.
Do not agree to an undefined project with a deadline before the requirements are clear. Ask what platforms must be supported, which campaign actions need automation, what approval and safety checks are required, how spending limits will work, and who from the media team will define and test the workflows.
Explain that your current client work would have to be deprioritized if this becomes a major project. Ask your boss to choose the priority in writing. A small proof of concept may be reasonable, but a production system covering multiple advertising platforms is a much larger commitment than a quick AI-assisted build.
AI can help write code, but it does not replace domain knowledge, testing, security reviews, monitoring, or someone being responsible when an API changes or a campaign goes wrong.
The web-versus-software distinction is not really the main issue. You probably can build a web application that talks to advertising APIs, but that does not mean you should build and operate a business-critical system by yourself while already supporting dozens of clients.
Put together a short written proposal showing the existing tools that could be purchased, the realistic scope of a two-month prototype, the timeline for a reliable version, the ongoing maintenance required, and the financial risk if an automation bug spends money incorrectly. Then give your boss clear options: buy and configure an existing product, hire an outside development team, or approve a properly staffed internal project with a maintenance budget.
That framing is much stronger than saying you are not a software developer. Focus on cost, risk, priorities, and who will support the system after launch.
Also document the conversation and your workload. If management refuses to set priorities, you may need to decide whether the role and expectations are still a good fit.