The brief
Build a Fractional AI Executive marketing site that does not look or feel like every other AI consultancy site on the internet. Visible pricing. Named operator bench. Audit trail as the product, not the marketing claim. Texas-bilingual edge. No infrastructure leakage. No fabricated metrics. No em dashes. No "Sergio reviews every X" framing that creates contractual binding.
The hard part is the operating discipline. Anyone can write copy. Few can ship a site that respects its own locked constitutional rules across every surface while still feeling alive.
The construction shape
Every page renders in plain HTML before any JavaScript runs. The operator bench treated server-rendering as a discipline, not a default. Answer engines (ChatGPT, Claude, Perplexity, Gemini) skip pages that hide their content behind JavaScript shells, and we did not want to be skipped. The framework choice is intentionally not the story; the operating posture is.
Every page carries its own Service or Article or HowTo JSON-LD plus FAQPage where relevant. The root layout emits Organization plus LocalBusiness plus WebSite schema on every route, so AI engines have entity grounding from any landing page, not just the home. The audit-trail concept that PQV sells to customers shows up here in the form of every page logging its publication date, every essay declaring its author, every claim grounded in an internally verifiable source.
Operating in the open
The bench shipped this site against a locked rulebook visible to every operator working on it. No dollar amounts except PQV's own tier prices. No percentages anywhere. No competitor names with prices attached. No "fast or proper" tradeoff offered to the founder; the proper path was the only one. Every commit cites the rule it respects and the rule it was tempted to violate.
When something broke (a Discovery Sprint conversion path returning HTTP 503 because a payment gate had not been removed; a /skills page rendering empty cards because client-only hydration hid them from crawlers; an apex /llms.txt file falling out of sync with the canonical pricing page after a tier change), the operator bench named the break, fixed it, and logged the fix to the audit trail. No "we are looking into it" stalling. No private email thread. The fix shipped in a pull request with a body that explained what changed and why.
The pricing decision
The constitutional rule originally said no dollar amounts on any public PQV surface. The founder consulted external feedback and changed the posture. The carve-out for PQV's own published pricing was locked, with the verbatim founder directive cited inside the rule file so future operators reading the rulebook understand the reasoning. The whole site reflected the new posture in a single coordinated propagation: visible prices on /pricing, /skills, /services, the strategic landing pages, the /llms.txt file, the FAQPage schemas, the marketing strategy document, the legal contract drafts, the post-Sprint Roadmap template, and the customer-portal SOW pattern.
Every document touched by the change was tracked in a single library on the ops dashboard. The pricing change propagated cleanly because the library was the source of truth. The audit trail of its own propagation is now part of the proof.
What we did not do
The site does not name the specific tools or models behind the operator bench. It does not list a tech stack as a credibility signal. It does not promise percentage outcomes. It does not quote competitor prices in comparison tables. It does not publish testimonials with manufactured customer names. It does not claim certifications PQV does not hold. Every constraint exists because the operating model is the moat, and the operating model is undermined the moment the bench pretends to be something it is not.
What this proves
The platform that produced this site is the same platform a paying customer engages. If the bench can ship dozens of constitutional-compliant pages, schemas, audits, and contract scaffolds against a locked rulebook in a few days, it can ship the equivalent against a customer's actual marketing operating layer in the same shape. The dogfood is the proof. The site is the artifact.
If you want to see the operating bench at work
Visit /live for the rolling snapshot of recently shipped artifacts. Visit /agents for the named operator bench. Visit /pricing for the four outcome tiers with visible prices. The complimentary Discovery Sprint is the way to get the same shape applied to your own operating layer.