What Triggered the Rebuild
Ben Rotenberg describes a simple moment. He looked at his own website and thought it looked like the site of someone who does not know how to work with AI. For a consultant who has trained and implemented AI in more than eighty organizations, that gap is hard to ignore.
His response was not a multi month project plan but a weekend experiment. One homepage with scroll driven video, just to see whether it would work.
Three Days From Idea to Live Site
Saturday's experiment became a full website on Sunday. By the third day the site was live, including a complete content migration and proper canonical tags.
This timeline illustrates a real shift in development work. The stage that used to be the most expensive, moving from concept to a working live version, is now the fastest and cheapest part of the process.
Why Performance and Search Did Not Suffer
The obvious question is whether a site built this quickly, with video on the homepage no less, can hold up in search. Rotenberg argues that it can, and frames it as a matter of infrastructure choices rather than technical brilliance.
The recipe he describes is building on Next.js, hosting on Vercel, and feeding PageSpeed Insights reports back into the model so it optimizes itself. It is a loop where external measurement guides the optimization work.
From Website to Service: The Forward Deployed Engineer
Alongside the site launch, Rotenberg is introducing a new service he calls Forward Deployed Engineer, an embedded organizational AI implementer. A specialist joins the organization one day a week and builds the tools and processes from within.
The difference from classic consulting is where the weight sits. Instead of a recommendations document, the goal is to create adoption momentum that leaves behind working systems and new habits of work.

