Rewrite a Consulting Site Around Paid Outcomes
Restructure an existing consulting site around customer problems, paid outcomes, credible proof, and a clear contact path.
When to use this recipe & what to provide
When to use it
Restructure an existing consulting site around customer problems, paid outcomes, credible proof, and a clear contact path.
Bring this context
- Current site and source access
- Ideal customer and offered services
- Real proof, case studies, and contact details
Why this structure
Separating the buying decision from background information improves clarity without discarding the founder’s existing work.
Assumptions
You have permission to use the supplied materials. Required access and any external actions remain subject to your agent environment.
Suggested autonomy, approval gates, and recovery instructions are selected below. Review them before copying.
Outcome / Objective
Start with what should exist when the work is done.
Context
Give the agent the facts it needs.
Job / Scope
Define the work. One task or phase per line.
Constraints / Preserve
Protect the things that already work.
Execution Strategy
Choose how the work should proceed.
Autonomy
Allow routine decisions within the defined scope.
Approval Gates
Require explicit approval before consequential actions.
Return Conditions
Define when the agent should hand control back.
Failure / Recovery
Preserve progress when something goes wrong.
Definition of Done
Make completion objectively checkable.
Resource Strategy
Behavioral guidance, not a prediction of usage.
Your inputs stay in this browser. No account, AI API call, or cloud synchronization. Avoid shared devices for sensitive project context.