One
Your landing page
The AI-Specify landing-page lab is five drafts for the Cloudmaven × Everest AI-Specify offer, plus a chooser that puts three of them side by side. It was built on 12 July 2026, independently verified on 13 July, and moved off one hard drive into the repository on 14 August. Its status has not changed: undeployed and unapproved. Nothing on cloudmaven.com links to it.
Each image shows the top of the page; the full drafts are in the repository. The recommendation of variant C is the builder’s own, written on 12 July 2026. No client, and nobody at Cloudmaven, has accepted it.
What changed since the PDF you got on 28 July
That review flagged two blockers found on 13 July. Both are now closed.
The fake password gate is gone, and real access control replaced it.
A password in a static page is not access control: the whole page, gate included, is sent to anyone who asks for the file, so the gate only bought false confidence. It was removed on 14 August. What actually holds the lab closed now: the password wall in front of the staging host, a no-index instruction on all six pages, a rule in the site’s robots file that keeps crawlers out of the whole lab, the lab’s absence from the sitemap in two independent places, and no link to it from anywhere on the site.
Checked rather than assumed: 54 requests across the six pages and nine address forms, every one answering with the identical page byte for byte; 30 browser runs, with zero password fields, zero hidden blocks and zero console errors.
The invented “CSV twice a month” figure is gone everywhere.
Nobody could find a source for the frequency, so the number went and the claim stayed. It came off variant C on 14 August, off the second draft that still carried it word for word on 16 August, and off the served 12 July audit file the chooser links to. Searching the whole repository for the phrase now returns nothing.
Publish it, or change the offer. The pages are finished and the two blockers that stopped them are closed, so nothing technical is holding them back. What is holding them back is that AI-Specify is still recorded in the release map as not cleared for release — a private artifact rather than a campaign. Either you clear it and it goes out, or the offer changes and the pages are rewritten to match. Neither can happen without you.
Two
The new website engine, proven
The words came across unchanged.
All 286 pages of the current site were rebuilt on the new engine and then checked page by page against a capture of the live site — 314,986 words, identical on every one of the 286.
The address problem that would have broken the launch is fixed.
Every one of the 286 web addresses would have quietly changed shape on switchover day, breaking what Google has indexed; that is now corrected on all 286, and a second, independent reviewer re-tested it, reintroduced the fault twice to be sure the check catches it, and confirmed it holds.
The contact form really sends.
The form on all three contact pages posts into the same live HubSpot forms the current site uses — confirmed three ways, and confirmed too that with scripts switched off the page still shows the email address and the phone number.
Three
The design directions
The directions are being collected onto one page so they can be looked at together.
That page is being assembled now; the link goes live with it. What is in the repository today, one line each:
- 12 August — four treatments of the same four pages at two widths: faithful, compact, editorial, human.
- 12 August — three standalone concepts: systems resolve, diagnostic desk, control room.
- 12 August, second pass — two spacious technical directions: technical editorial, blueprint narrative.
- 12 August, third pass — two complete homepage prototypes: ledger light, night blueprint.
- 13 August — two homepage versions prepared for Christoph: one dark, one light.
Four
The staged go-live
Stage one is the technical cutover: the same words on the new engine, which is a DNS change plus a proxy toggle and is reversible with a single record. It is not blocked on anything technical — custody of the Cloudflare account that holds the cloudmaven.com zone is unresolved, and that alone blocks the cutover, which is the access you offered on 10 August to escalate with Jarrid. Stage two is modernizing the site page by page, once the cutover is behind us and the addresses are safe. Stage three is the positioning changes, after the session on 27 August.
Five
Five things only you can give
Five questions to answer in the room. Nobody else can answer them.
- How much of your own time do you have for this in the rest of August? Everything below needs you, not somebody standing in for you.
- Which six customers do we call for testimonials, and who makes the introduction? Open since July. Five published projects, and no outcome figures cleared for any of them.
- Will you sign off the definition of a qualified conversation, in one sentence? It is what the relaunch is measured on, and an enquiry only counts once a person logs it.
- What is your own outbound response rate today? It is the number the website has to beat, and it stays internal.
- Which booking-calendar link belongs to which region? Open since 27 July. The contact routing works without them, but “book a conversation” beats “write to the DACH team”.