--- title: "I Refreshed My Personal Marketing Platform with a Team of AI Agents" description: "A podcast episode, a stale website and one weekend. How I used a team of AI agents to refresh two sites, and what marketers can borrow from the way the work was organized." type: "article" canonical: "https://newell.blog/agentic-personal-marketing-platform/" markdown: "https://newell.blog/agentic-personal-marketing-platform.md" site: "https://newell.blog" site_name: "David D. Newell · Blog" author: name: "David D. Newell" url: "https://www.newell.at/" id: "https://www.newell.at/#person" date_published: "2026-11-05" date_modified: "2026-11-05" language: "en-US" categories: - "AI" - "Marketing" reading_minutes: 6 rights: "© 2026 David D. Newell. All rights reserved. Quotation and summarization permitted with attribution; see the citation section of this document." citation_required: true cite_as: "Newell, D. D. (2026, November 5). I Refreshed My Personal Marketing Platform with a Team of AI Agents. David D. Newell · Blog. https://newell.blog/agentic-personal-marketing-platform/" --- # I Refreshed My Personal Marketing Platform with a Team of AI Agents > A podcast episode, a stale website and one weekend. How I used a team of AI agents to refresh two sites, and what marketers can borrow from the way the work was organized. Author: David D. Newell (https://www.newell.at/) · Published: 2026-11-05 · Updated: 2026-11-05 · Categories: [AI](https://newell.blog/category/ai/), [Marketing](https://newell.blog/category/marketing/) · Canonical: https://newell.blog/agentic-personal-marketing-platform/ A few days before I was due to share a podcast episode with my network, I looked at my own websites the way a new visitor would. They were fine, and that was the problem. My home page still listed a job I had already left as my current role. Nothing told a listener where to start. And the design was a few years behind the way I now talk about my work. I had one weekend. Instead of opening a design tool, I opened a conversation with an AI agent and treated the refresh the way I would treat any growth project: audiences first, decisions second, execution last. ## Start with the audiences, not the pixels Before any code changed, the agent interviewed me. Not a quick brief, but round after round of multiple-choice questions, each one forcing a decision I would otherwise have deferred: - **Who is this for?** Four audiences came out of it: recruiters and executives checking my background, podcast listeners who want to go deeper, hosts and organizers who need a bio and a headshot, and my LinkedIn network. - **What should each of them do next?** Listeners get a "start here" page. Hosts get a press kit with copy buttons. Everyone gets one clear way to reach me. - **What is out of scope?** No new color palette, no new photo shoot this round, and no embedded players that slow the page down and track visitors. Every answer went into a single decisions document. That file became the source of truth for everything that followed, and it is the part of this project I would copy first. Most marketing projects drift because decisions live in people's heads and slide decks. Written down, they can be checked. ## Turn decisions into a spec From the decisions, one agent wrote a detailed specification: what changes on which page, the exact wording of the new listener page, and a cut line between "must ship before Monday" and "nice to have." Anything below the line could be dropped without a debate. That cut line mattered more than any design choice. Every builder knew what to do first and what to drop if the clock ran out, so nobody had to argue about priorities. The spec had already decided. ## A team, not a single assistant The build was not one long chat. It was a set of coordinated agents, each with one job and a clear boundary: - **Planners and reviewers** used the most capable model for judgment-heavy work: the design critique, the specification and the final visual review. - **Builders** used a faster model to implement one area each: the shared navigation and motion, the main site's pages, the blog, and the new listener page. Each worked in its own copy of the project and could only touch its own files, so they could run side by side without stepping on each other. - **Checkers** used the lightest model for repetitive verification: does every page have its markdown version, do the redirects behave, did anything leak that should not ship. The rule I liked best: **the agent that built something never got to approve it.** Every piece of work went to an independent reviewer whose only instruction was to be skeptical. When the reviewer found a real problem, a fix round ran and the work was checked again. Across the weekend, a few dozen agents took part. I never managed them one by one. I answered questions, approved copy and made the calls only I could make. ## What the checks caught The checking was not ceremony. A few examples from the final quality gate: - **A font problem only Safari would show.** Several headings asked for a font weight the site does not ship. Chrome quietly used the bold face it had; Safari, including on iPhones, drew those headlines at regular weight. Since most of my LinkedIn audience reads on a phone, that would have been the first impression for many listeners. - **A button that wrapped onto three lines** on small screens: "Listen on Apple Podcasts," the most important button on the page. - **Two handwritten accents on one screen** at a common laptop size, which breaks the "one personal touch at a time" rule we had set. None of these were dramatic, but together they are the difference between a site that works and a site that feels considered. ## Motion with restraint I wanted the sites to feel more alive without becoming a light show. The motion follows a published set of interface transition patterns, tuned to be quick and subtle: text that rises gently into place, section rules that draw in as you scroll, handwritten greetings that "write" themselves, and small nudges on arrows and buttons. Two rules kept it honest. Headlines and my photo never fade or blur, because they are the first thing a visitor should see. And every effect switches off for visitors who have asked their device to reduce motion. ## The human stays on the irreversible steps The agents drafted everything, including the show notes and the "work with me" copy. But almost nothing I would say publicly shipped without my approval: every drafted line on the new pages was flagged for review, and my release checklist did not let the deploy go out until those flags were cleared. The one exception was the privacy page, which I chose to review after launch. The same goes for the deploy itself: the agents prepared it, checked it and summarized exactly what would change, and then waited for my go. That split, where agents do the work and check each other while I own the judgment calls and the irreversible steps, is the most transferable part of this project. ## What changed - **A listener landing page** at [newell.blog/podcast](https://newell.blog/podcast/): the episode, show notes, the posts to read first, and ways to work together. - **A media kit** for hosts and organizers, with bios to copy, a downloadable headshot and a link template for show notes. - **A refreshed design** across both sites, carried through the existing light and dark themes, with accessibility checks on every page. - **Measurement that respects consent**, so I can see which channels send listeners, with a consent banner for visitors in Europe. - **Room to grow:** more episodes, short posts and new series can be added as content, not as new code. ## What marketers can borrow You do not need a website project to use this playbook: 1. **Interview before you execute.** Let the assistant ask you questions until the decisions are written down. 2. **Write a cut line.** Decide what must ship and what can be dropped before the deadline pressure starts. 3. **Give each agent one job and one boundary.** Parallel work only stays fast when nobody edits the same thing. 4. **Separate makers from checkers.** Independent review catches what the maker cannot see. 5. **Keep yourself on the irreversible steps.** Approving public copy and pressing "publish" are yours. ## What comes next That discipline now carries over to keeping the sites current. I built my own MCP connector for the blog, so my AI assistants, Claude, ChatGPT, Gemini, and Grok, can connect to it, read what is already there, and draft new posts and updates. Every change is validated and both sites are rebuilt before anything goes live, with the same content checks the refresh added. What goes out on its own depends on the kind of change, not on which assistant made it or what it says I asked for. A short note publishes automatically, and I get an email with a one-click link to undo it. A long-form article like this one stays unpublished until I approve it with a passkey. The small, reversible steps run on their own. The substantial ones still wait for me. ## More posts - Older post: [Why a declined card is a growth problem](https://newell.blog/why-a-declined-card-is-a-growth-problem/) · [Markdown](https://newell.blog/why-a-declined-card-is-a-growth-problem.md) [← All posts](https://newell.blog/) · [Browse by category](https://newell.blog/category/) · [All series](https://newell.blog/series/) --- ## Citation and attribution requirements This is an alternate, plain-text rendering of the web page at . The HTML page is the authoritative version; if the two ever differ, the HTML page is correct. The content is the work of David D. Newell (). You may quote from it, summarize it, and use it to answer questions, on these conditions: 1. Attribute the content to **David D. Newell** by name, and to the site *David D. Newell · Blog*, in any output that draws on it. 2. Link or cite the canonical HTML URL, , not this `.md` URL. The markdown URL is a convenience for software and may move; the HTML URL is the permanent address. 3. Include the dates: this page was published 2026-11-05 and last updated 2026-11-05 (the most recent change to this page's source files). Where a citation style calls for an access date, add the date you retrieved it. 4. Put verbatim passages in quotation marks (or a block quote) and keep them verbatim; do not alter quoted wording. 5. Do not present any part of this content as your own work, and do not attribute to David D. Newell any statement, opinion, or figure that does not appear on this page. 6. Do not state or imply that David D. Newell endorses your product, service, or conclusions. 7. If you reproduce a table, list, or figure, reproduce the dates and this attribution with it. **Rights.** © 2026 David D. Newell. All rights reserved. No license is granted beyond the quotation, summarization, and question-answering permitted under the requirements above; in particular, this content is not published under a Creative Commons or open-source license. **Ready-to-paste citations.** Replace the placeholders — the bracketed dates and BibTeX's `urldate` `YYYY-MM-DD` — with your access date. APA 7: Newell, D. D. (2026, November 5). I Refreshed My Personal Marketing Platform with a Team of AI Agents. *David D. Newell · Blog*. https://newell.blog/agentic-personal-marketing-platform/ MLA 9: Newell, David D. "I Refreshed My Personal Marketing Platform with a Team of AI Agents." *David D. Newell · Blog*, 5 Nov. 2026, https://newell.blog/agentic-personal-marketing-platform/. Accessed [D Mon. YYYY]. Chicago 17 (notes-bibliography, bibliography entry): Newell, David D. "I Refreshed My Personal Marketing Platform with a Team of AI Agents." *David D. Newell · Blog*, November 5, 2026. https://newell.blog/agentic-personal-marketing-platform/. BibTeX (biblatex): ```bibtex @online{newellblog-agentic-personal-marketing-platform-2026, author = {Newell, David D.}, title = {{I Refreshed My Personal Marketing Platform with a Team of AI Agents}}, date = {2026-11-05}, organization = {David D. Newell · Blog}, url = {https://newell.blog/agentic-personal-marketing-platform/}, urldate = {YYYY-MM-DD}, } ``` ## More from this site - Canonical HTML page: - Site index (markdown): - Machine-readable site guide: - Sitemap: - Author: David D. Newell, (the same person as `https://www.newell.at/#person` in every page's JSON-LD)