15 Minutes Per Campaign, Hundreds of Campaigns Per Quarter
At a major entertainment company, marketing operations teams were spending 15+ minutes setting up each campaign brief - pulling project data from Wrike, cleaning up HTML-formatted descriptions, structuring the information into a strategy template, and distributing it to stakeholders. Multiply that by hundreds of campaigns per quarter, and the manual overhead was staggering. The creative work - actual strategy and positioning - was being crowded out by data wrangling and template filling.
The challenge: build a tool that could take a raw Wrike project URL, extract all relevant metadata, and generate a complete, structured campaign strategy document - automatically.
What We Built
We developed an AI-powered campaign automation tool using Python, Flask, large language models, and the Wrike API. The system accepts a Wrike folder URL or ID as input, fetches all project metadata through Wrike's REST API v4, strips HTML formatting from descriptions using BeautifulSoup, and feeds the cleaned data into the LLM with a carefully engineered prompt that generates a structured campaign strategy.
The Web Interface
The tool has both a web UI (Flask application) and a CLI version for power users. The web interface is intentionally simple - paste a Wrike URL, click generate, get your strategy document. No training required, no complex configuration, no workflow changes for the team.
Intelligent Data Extraction
Wrike stores project descriptions as rich HTML with embedded formatting, links, and metadata. Raw HTML fed directly to an LLM produces noisy, unreliable output. We built a preprocessing pipeline using BeautifulSoup that strips HTML tags, normalizes whitespace, extracts structured fields (timelines, budgets, target audiences), and presents clean, structured text to the language model. This preprocessing step was the difference between "sometimes useful" and "reliable enough to trust."
Agentic Architecture
The advanced version uses OpenAI's Agents SDK with Model Context Protocol (MCP) - a chat-loop-based interface where the AI agent can query Wrike data conversationally, ask follow-up questions about the project, and iteratively refine the strategy. This moves beyond single-shot generation into an interactive planning session backed by real project data.
Security Considerations
Enterprise marketing data is sensitive - campaign budgets, target demographics, competitive positioning, launch dates. The tool runs on internal infrastructure, not a third-party SaaS. API credentials are managed through environment variables (not hardcoded). All Wrike API calls use OAuth authentication with scoped permissions - the tool can only read project data, not modify it. And all LLM API calls use enterprise-tier endpoints with data processing agreements in place.
The Results
Campaign creation time dropped from 15 minutes to approximately 90 seconds - a 90% reduction. The tool won two out of three company-wide hackathon competitions. But the real impact wasn't just speed. The generated strategies were more consistent in structure, more comprehensive in coverage (the AI doesn't forget sections the way a rushed human does), and freed up marketing operations teams to focus on creative strategy and optimization rather than data assembly.
The tool contributed to a broader personalization initiative that drove measurable commerce improvements - proving that AI automation in marketing isn't theoretical, it's a direct revenue driver.
Why This Approach Works for Any Business
The pattern here isn't specific to campaign management. Any workflow that follows the shape of "pull data from system A, restructure it, and generate a document or plan" is a candidate for AI automation. Insurance underwriting, real estate comparables, financial reporting, vendor evaluations - the manual version takes 15-30 minutes per instance, and the AI version takes 90 seconds.
The critical insight is that AI alone isn't enough. The preprocessing - cleaning data, structuring inputs, engineering prompts, validating outputs - is what makes the difference between a demo and a production tool. If your team is spending hours on repetitive data-to-document workflows, a 25-minute consultation can identify the highest-impact automation opportunity and outline a realistic implementation plan.