The front of the curtain is always pretty: logos, demos, “we do AI,” a case study with a big percentage. Behind the curtain is where you find out whether anyone owns architecture — or whether you are buying theater.
My rule for owners is simple enough to use in a sales call: make them show you behind the curtain. Can they answer one real infrastructure question without drowning you in model names?
What counts as an infrastructure question?
Pick one and do not accept a pivot:
- Where does the data live, who can write to it, and what happens when the model is wrong?
- What is your eval loop for the agent that talks to customers?
- If we fire you tomorrow, what do we still own — systems, prompts, content, logs?
- Are we buying tools or a layer? (See tools ≠ agentic systems.)
- Show me the path from lead to booked job when a human never touches the happy path — and where a human must.
If they cannot answer, they are not an expert — they are a novice with marketing (expert or novice). If they refuse to show the curtain, believe them.
When this test saves you
Before a six-figure “AI transformation” retainer. Before you put someone on your association mainstage ( don’t give rookies the mic). Before you confuse a weekend demo with production (demo ≠ product).
It also saves you from the old agency move in a new costume: monthly fees, foggy work, beautiful reports — the agency model is broken for the same reason. Invisible work is invisible infrastructure.
Failure modes when you skip the curtain
- Bolt-on bills. APIs taped to legacy junk — the bill arrives later.
- Cardboard AI. Seeded demos that collapse under the one question that breaks products — is the data real?
- Architecture orphans. No one owns the layer, so every tool is a dead end on the maturity ladder.
Proof — open curtain on purpose
This site publishes machine-readable truth on purpose — /entity.md, /llms.txt, a Prediction Ledger with dates. Our rebuild numbers are public in 320 to 38. That is not vulnerability for its own sake. It is how you earn the right to ask other people to open their curtain.
How to run the test without being rude
You are not accusing anyone of fraud. You are buying judgment under uncertainty. Say: "We only partner with people who can open the curtain on infrastructure — can we spend ten minutes on data flow and failure modes?" Professionals say yes. Costumes change the subject to branding, vibes, or a bigger demo. Believe the subject change.
Write the question down before the call so you do not negotiate it away under charm. Charm is part of the curtain. Your job is to look behind it anyway.
Bring a technical person to the call if you are not one — not to be rude, to translate. When the answers get vague, your translator will feel it in their body before the slide does. That feeling is data. Do not override it because the logo reel was pretty.
After the call, write three bullets: what they showed, what they deferred, what they owned. If the deferred list is longer than the shown list, you do not have a partner yet — you have a brochure. Keep shopping. The curtain test is how you protect payroll from pretty fog.
Pair the curtain test with AI Expert or Novice and refuse partners who fail either. Diligence is how owners stay free — of fog retainers, of cardboard demos, and of stages that sound smart while teaching nothing operable.
Action
Put one infrastructure question in every partner and speaker brief this month. Require a diagram, not a slogan. If you want a partner who expects that test, start at Work with Jennifer. If you want the architecture argument on stage, book Jennifer or read AI Superpowers Are an Architecture Decision.