THE MARKETING HUB

Marketing requests arrived by email, Slack, and hallway. Nothing was tracked in a single place. Deadlines surprised the team because each request lived wherever it was submitted — a thread here, a sticky note there, a forwarded message that sat in someone's inbox. Duplicate requests burned hours: two people independently commissioning the same asset, neither aware the other had asked.

The deeper problem was capacity invisibility. When a new request landed with a tight deadline, there was no systematic way to answer whether it could actually be done by then — the answer came from whoever happened to have context, not from the data. That meant either over-promising or a last-minute scramble to reprioritize.

My employer, a fintech, also used a project-management platform as its record-of-truth for the marketing team and an external agency. Any new intake tool had to sync there — not replace it — which meant the integration had to be a first-class citizen, not an afterthought.

The Marketing Hub is a production marketing-operations portal, deployed as a private internal tool (View screenshot). One submission form — 12 fields covering task description, requester, priority, deadline, objective, audience, deliverables, services, reference links, destination, assignee, and date — creates three artifacts at once: a Kanban card on the live board, a deadline entry on the priority-coded calendar, and a synced row in the appropriate project tracker. All three views are generated from the same record and always reflect the same state.

The Kanban board uses drag-drop swimlanes so status updates happen where the work is visible. The calendar codes entries by priority so the team sees crunch points before they arrive. Neither view requires a separate manual entry after intake — the record propagates automatically and the tracker sync tracks its own status per row so failures surface immediately.

The design system is the employer's own: proprietary font family, brand palette, logo. The portal looks like one of the company's own products, not an off-the-shelf tool skinned for the org.

The portal shipped with a written walkthrough guide intended for a CMO demo. That constraint shaped the design: every view had to be immediately legible to a non-technical audience, and the happy path — submit a request, watch it appear on the board and calendar, confirm the tracker row — had to work flawlessly on the first try. Onboarding theater is the enemy of adoption; the guided walkthrough exists to show the value in under five minutes, not to paper over a complicated interface.

The employer-branded design system was critical here. A portal that looks foreign to the organization gets ignored. One that looks like it belongs gets used.

The routing and project-tracker integration wave — 30 commits across May 31 and June 1, 2026, building on the core product shipped in the first two days — was written by the studio's agent fleet working from a written specification. One frontier-tier planner decomposed the spec, mid-tier builders implemented against clean-context prompts, and the operator reviewed and deployed. That is the same conductor pattern documented at /work/conductor-pattern: frontier tokens for judgment and verification, cheaper tokens for the typing. The integration wave landed without regressions to the core product — the spec was tight enough that builders never needed to infer scope.

The build broke into two focused waves. The core product — intake form, Kanban board, calendar view, database schema, all 28 API endpoints — shipped in the first two days. The routing and tracker integration wave followed on May 31–June 1: dual-destination routing, per-row sync status, duplicate detection, and the SLA capacity check. Thirty commits, two phases, one production deployment as a private internal tool (View screenshot).