TL;DR
- A regional infrastructure company's capacity reservation process would be announced by wire at an industry conference on a Tuesday. The brief arrived the Friday before, with a hard Monday 3 PM sign-off
- Deliverables: a new public page with full copy and SEO configuration, a persistent site-wide banner, a new mailbox with send-as permissions, a Google Analytics 4 property built from scratch, and the press release on the media tab within 30 minutes of the wire
- We stayed on the client's existing WordPress and Divi stack instead of a platform migration, and solved the banner with a maintained plugin after custom code failed across themes and browsers
- Everything shipped, tested across seven browser and device combinations, and signed off before the deadline. The wire crossed Tuesday at 11 AM and the site held
The Situation
A regional infrastructure company was days away from the most important commercial moment of its year: a formal capacity reservation process announced via BusinessWire at a major industry conference. The entire inbound engagement path ran through the website. A press release would cross the wire, utility executives and trade press would land on the site within minutes, and there was exactly one route to engagement. A new page. A banner. A button. No fallback.
The project brief arrived a few days later than ideal, which is not unusual. Everyone is managing five things at once, and the emails that matter most are often the ones that get written, reviewed, and rewritten before they go out. The brief itself was detailed, thorough, and well-organized. But the timeline from "brief received" to "wire crosses" was tight, and the work was real.
This is the kind of situation where having a fractional CTO copied on earlier conversations would have made a material difference. Not because the work could not be done, it could and it was, but because infrastructure decisions made under deadline pressure are always more expensive than infrastructure decisions made with time to think. A few earlier conversations would have changed the shape of the weekend considerably.
What We Actually Did
The deliverable list looked like this: a new public page with full copy, mobile-responsive layout, and SEO configuration; a site-wide persistent banner on every page; a new email mailbox configured end-to-end with send-as permissions; a Google Analytics 4 property built from scratch and installed on the site; and a press release added to the media tab within 30 minutes of the wire crossing Tuesday morning.
What that list does not capture is the range of roles involved in getting it across the line. Over the course of 72 hours, this project required someone to function as project manager, developer, QA engineer, systems architect, account manager, and technical advisor simultaneously. Scoping the work, coordinating the team, making real-time architectural decisions, testing across seven browser and device combinations, managing the client relationship, and watching the wire Tuesday morning. That is not a job description, it is a weekend.
The build itself ran Saturday through Monday, with a developer on cleanup and cross-browser QA Monday morning, and press release monitoring Tuesday at launch.
The Decisions That Mattered
The platform question. The site runs on WordPress with Divi. Divi is our preferred builder; we hold a grandfathered developer license that we extend to clients as part of their hosting plan. In the right hands it produces a professional result; the catch is that "the right hands" part is load-bearing. Attempting this build without deep familiarity with the stack, under this timeline, would have introduced real risk.
We briefly considered bypassing the existing site entirely and rebuilding it on v0.app deployed to Vercel. The site is a modest footprint, and that kind of rapid scaffold-and-deploy is well within our range. We set it aside: introducing a full platform migration during a 72-hour window with a wire release landing simultaneously is the kind of move that looks brilliant if nothing goes wrong and catastrophic if anything does. DNS propagation alone could have taken down the launch.
The more viable alternative we considered was standing up the new page as a standalone deployment: its own Vercel project, separate lifecycle, decommissioned after the 45-day campaign window. For a time-limited campaign page with a clear end date, that architecture is clean. We stayed on WordPress because it was the lower-risk path given the timeline, but the standalone approach is worth considering for future campaign launches.
Buy vs. build. The site-wide banner, a persistent, non-dismissible bar above the existing navigation on every page, looked simple and was not. Getting custom PHP or CSS to reliably sit above a Divi header across themes, templates, and browsers is the kind of problem that looks solved until it is not. AI coding tools, which we use regularly, generated several approaches that did not survive contact with the actual environment. A free, widely maintained WordPress plugin solved it in twenty minutes. That is the right call every time: crowd-sourced solutions have been tested against thousands of configurations by developers who care about their reputation. Custom code has carrying costs. We would rather hear about a problem from a plugin's issue tracker than from a client on launch day.
A Note on the Hosting Plan
This client is on one of our original hosting plans, a hands-off arrangement designed for sites the client manages themselves. At that tier, we keep the lights on. We do not proactively monitor WordPress admin notices, handle security notifications, manage plugin updates, or provide priority support for time-sensitive launches.
Our current managed plans at Concierge Web Hosting include all of that, plus developer hours for routine changes, analytics reporting, and the kind of ongoing relationship where we know about a launch before the brief arrives. The gap between the two is not just price. It is the difference between a server and a partner.
Where This Is Going
The client purchased its site from a commodity WordPress provider. It is a clean, functional site. But a company executing a multi-year contracted infrastructure process, announcing via BusinessWire, and managing a structured inbound pipeline is not really a commodity WordPress company anymore.
Most growing businesses hit this inflection point. The symptoms are familiar: plugin update notices nobody is reading, a security notification that sat in a spam folder, something that looked wrong on mobile for two weeks before anyone noticed. The fix is not necessarily a new platform. It is a new way of working. Version control. Git-based deployments. CI/CD. Language models in the build process to accelerate everything from scaffolding to QA. Fast turnaround without a full-time development team.
That is the model we build toward for clients who are ready for it. You do not need to hire a CTO, a developer, a QA engineer, and a project manager. You need one partner who can play all of those roles and knows when to bring in additional resources. That is what 37SOLUTIONS does.
The Outcome
Everything shipped. The page was live, tested, and signed off before the Monday 3 PM deadline. The banner was running on every page. The email was configured and tested end-to-end. Analytics was installed with client access before the wire crossed. The press release was on the media tab within the window. All 30-plus items on the mandatory testing protocol passed.
The wire crossed Tuesday at 11:00 AM. Traffic hit the site. The chain held.
Frequently Asked Questions
Can a campaign page really be built in a weekend? Yes, when the brief is complete, the stack is familiar, and someone is making the architectural calls in real time instead of scheduling meetings about them. The risk is not the build. It is the decisions made under pressure, which is why the platform question got settled in the first hour.
Why not migrate to a faster platform during the launch? Because a platform migration and a wire release on the same day is two launches, and the second one has no fallback. A standalone campaign deployment is the clean version of that idea, and it is the one we would reach for next time with a week's notice.
When is a plugin better than custom code? When the problem is common, the plugin is maintained, and the failure mode of custom code is "it works in three browsers." A site-wide banner over a page builder's header is exactly that problem. Twenty minutes with a maintained plugin beat several hours of generated code.
What does a hands-off hosting plan not include? Monitoring of admin notices, security notifications, plugin updates, and priority support for time-sensitive work. Those are the managed plan. This client got the launch done on the hands-off plan because it called early enough on a Friday; the managed relationship is what makes early notice the default.