A transformation lands on time when every piece of it can be checked before the cutover, and when nothing ships until the verification is done. I ran that same discipline twice — once as a project manager for a company rebrand, once as the person directing an agent team that rewrote a live website. Both times, the same shape: break the work into verifiable pieces, stage everything, change nothing live until you know what you're changing from.
The Banyan rebrand
I was project manager for the rebrand at Banyan, a SaaS company where I worked from October 2015 to January 2017. The rebrand was completed on time and widely regarded as a success. My part was outlining workloads, delegating tasks, and keeping people accountable — the standard project-management shape.
The same discipline, agent-directed
In September 2026, I directed LEGION — the AI agent organization I built to run Adroit's systems — to rebuild Adroit's own website. The scope was 74 existing pages and posts updated in place and 17 new pages created, with every one of the site's 96 comparable URLs verified to match staging on status, title, H1, theme, and the Sadyr widget before cutover. The site went live at adroitmktg.com on 23 September 2026.
The rebuild also cut the site's footprint measurably. Compressed file sizes on the home page: JavaScript fell from 103 KB to 2 KB, CSS from 78 KB to 10 KB, HTML from 79 KB to 34 KB. Eight plugins were retired in favor of native theme code — Happy Elementor Addons and its Pro version, Elementor Designer Powerup, Performance Lab, Hummingbird, Smush, Cookie Law Info, Redirection, plus one unused header template removed. Native replacements were built for forms and scheduling, redirects, the cookie notice, and CDN image optimization.
The site was also made machine-readable without a redesign. Every refreshed page serves a Markdown twin at /<path>/index.md, /<path>.md, and /<path>/?format=md, with /llms.txt and /llms-full.txt served per the llms.txt convention. Structured data (JSON-LD) was added across the site: Service schema on 40 service and capability pages, SoftwareApplication schema on the 2 product pages, and FAQPage schema parsed from Markdown headings on pages with 2 or more question/answer pairs — 18 questions total.
Stage first, verify, then cut over
The go-live itself followed the same cutover discipline a company rebrand would have required: staging content was exported and replayed onto the live environment with zero errors. A backup and a pre-golive database dump were taken first. Live form submissions from before the cutover were left untouched.
That 96-out-of-96 URL verification against staging was the same gate a rebrand project manager would have put on launch day: every URL must match the new state, not the old one, before anything changes live. The difference is that the agent team produced the pages and I verified them, rather than a design team producing them and a project manager verifying them.
LEGION started in March 2025, about the same time OpenAI (11 March), Google (24 March) and Google again (9 April) publicly converged on orchestration as its own architectural layer — what would later be called a harness. The industry was converging on the same structure Todd was building: a runtime around the model, with tools, memory, state and approval gates, not just the model alone.
What carried over
Both transformations depended on breaking the whole thing into pieces that could each be verified independently before the cutover, not shipped as one irreversible leap. A rebrand lands on time when each workload has an owner and a finish line you can check. A 74-page website rewrite lands on time when each of 96 URLs has a verified state before go-live.
The principle is the same whether the work is delegated to people or to agents: stage everything, change nothing live until the verification is done, and take a backup first. Punctual delivery and 96-out-of-96 URL verification are both expressions of that same discipline.