Hey, it's Sam.
Yesterday was about judgment. Today we build systems.
I want to show you a simple mental shift that changes how you build:
It’s the difference between guessing what your AI needs and having it tell you directly.
Why This Matters
For years, I kept this "perfect" client intake form.
Master checklist. Every question I could think of. Constantly updated.
Still sucked.
Why? Because I was guessing.
Every project needed different data.
Every strategy had unique requirements.
My generic template was like bringing a Swiss Army knife to surgery.
Missing inputs = mediocre outputs.
The problem I was building tools for AI without asking AI what it needed.
Like cooking for someone without asking if they're vegetarian.
The Architect's Approach
Here's the shift:
AI users guess what to feed the model.
AI architects asks the model what it needs to succeed.
Instead of creating a generic, one-size-fits-all template, we can use our V2 strategy blueprint to have the AI generate a custom input template for that specific strategy.
Take your V2 strategy blueprint. Feed it to AI with one question:
"To execute this at a world-class level, what exactly do you need from the client?"
The AI builds its own briefing doc.
Custom requirements for that specific strategy.
No guessing. No gaps.
Now it’s working with a list it made itself.
Your Input Definition System
Here’s the system to make that happen.
This prompt takes your V2 strategy and tasks the AI with reverse-engineering its own perfect input requirements.
# Task
Create an exhaustive and structured "Client Intake Checklist" by reverse-engineering a given strategic blueprint. The checklist should be organized by section and tailored to help gather all relevant client data needed to implement the strategy with precision.
## Persona
You are a Senior Implementation Strategist and Strategic Systems Designer. You specialize in operationalizing strategic blueprints into executable plans through meticulous data extraction, client discovery, and implementation design. You are detail-obsessed, pattern-savvy, and implementation-driven.
## Considerations
- The strategy to be analyzed may be abstract, generic, or overly high-level.
- Your job is to surface all possible data blind spots that would inhibit a high-fidelity implementation.
- Think like both a systems consultant and onboarding specialist: what would you need to ask the client to fully activate this blueprint?
- This intake will be used by client-facing teams (strategists, project managers, ops specialists), so your checklist must be clear, exhaustive, and implementation-ready.
## Steps
1. Analyze each section of the strategy line by line.
2. For each section:
- Identify its purpose and intended outcome.
- Ask: What would a strategist, implementer, or project manager need to know from the client to apply this section effectively?
- Derive the necessary questions, data types, and delivery formats.
3. Organize your intake by the same structure as the blueprint (mirror headings/sections).
4. Under each section, list:
- **Questions to Ask the Client**
- **Data Points Needed** (Be specific: not "audience" but "demographic breakdown, psychographics, etc.")
- **Required Format** (e.g., narrative, spreadsheet, KPI dashboard, time series, brand doc, etc.)
5. Use markdown formatting to present your output clearly.
## Constraints
- Do not summarize or rewrite the blueprint.
- Do not invent strategy components beyond what is provided.
- Do not skip ambiguous or underdeveloped sections; instead, surface what questions are needed to clarify them.
- Be obsessively complete. Your goal is zero guesswork.
- Use terminology that aligns with strategic, operational, and client-facing roles.
## Success Qualities
- Comprehensive: No component of the blueprint is left without mapped intake items.
- Client-Centered: All questions and formats are accessible and implementable by real-world clients.
- Implementation-Ready: The output can immediately be used to build a project plan or kickoff session.
- Section-Mirrored: The intake structure mirrors the blueprint's structure exactly.
## Stakes
A sloppy or partial intake will sabotage implementation, frustrate the team, and lead to strategic misalignment. A well-structured intake creates clarity, drives momentum, and derisks execution from day one.
## Output Format
Use markdown with the following structure:
```
# Client Intake Checklist for [Blueprint Title]
## [Section Title from Blueprint]
### Questions to Ask the Client
-
-
### Data Points Needed
-
-
### Required Format
-
-
(Repeat for each section of the blueprint)
```
---
[Paste your V2 Blueprint below to begin:]What comes back is next-level.
A complete intake system. Built by AI, for AI.
Before: Generic template → Missing data → Weak outputs → Client disappointment
After: Custom checklist → Complete data → Strong outputs → "You thought of everything"
Build With Clarity, From Day One
Imagine the workflow:
For every new strategy, you run this prompt.
Minutes later, you have a bespoke intake checklist—tailored to the project.
You never forget a key detail.
You don’t have to chase missing inputs halfway through.
And the quality of your AI’s output?
Predictable. Consistent. High-grade.
That’s what happens when you stop guessing and start architecting.
Today's Move (15 minutes) 🫵 💥
Build your first AI-generated tool:
Grab your V2 Blueprint from yesterday
Run the Input Architect prompt
Save the output as your Master Input Template
Compare it to any generic template you've used (Prepare to be humbled)
Tomorrow: What if the client can’t answer your beautiful AI-generated questions?
(Spoiler: We turn that into an opportunity too.)
—Sam