01
Define the Finish Line
Turn the client's loose idea into one observable outcome without adding assumptions.
Made for Financial Advisors
Turn Someday Into a Real Deadline
Also useful for: Financial Planners, people in Finance
30 min
Intermediate
Planning
Make a Financial Decision
Convert an undefined financial goal into practical timing ranges, clear dependencies, backup dates, and a documented next step.
We'll use them to write your prompt.
Completed ✓
Make Your Play
Give us the situation. We’ll build the prompt.
Replace vague timing with a deadline the client understands and the financial plan can test.
Your answers save as you type.
What you'll do
This is the plan inside your prompt. Add your details first. Then follow these steps with ChatGPT or Claude.
02
Sort the Timing Triggers
Separate the events that shape timing by how much control the client has over them.
03
Set a Target Range
Build a useful range instead of forcing an unsupported single date.
04
Map the Dependencies
Put required decisions and events in the order they need to happen.
05
Choose Fallback Timing
Prepare a backup date that responds to the most important source of uncertainty.
06
Lock the Next Action
Convert the timing work into a follow-up that moves the planning process forward.
Make Your Play
Turn Someday Into a Real Deadline
Tell us what the prompt needs to know
Start with the questions below. Each answer personalizes the playbook and builds the prompt you’ll use at the end.
Your situation
Describe the financial goal in the client's current words, including the intended outcome.
0/10000
Summarize the financial, family, work, and lifestyle facts that affect the goal's timing.
0/10000
Enter the words currently used to describe when the goal should happen.
List the events or conditions that would signal it is time to act.
0/10000
List the decisions, approvals, funding needs, or outside events that must happen first.
0/10000
Select how much flexibility exists around the final date.
Enter the date from which the proposed timing should be measured.
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
01
Define the Finish Line
Turn the client's loose idea into one observable outcome without adding assumptions.
02
Sort the Timing Triggers
Separate the events that shape timing by how much control the client has over them.
03
Set a Target Range
Build a useful range instead of forcing an unsupported single date.
04
Map the Dependencies
Put required decisions and events in the order they need to happen.
05
Choose Fallback Timing
Prepare a backup date that responds to the most important source of uncertainty.
06
Lock the Next Action
Convert the timing work into a follow-up that moves the planning process forward.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
Start with the client’s own words. If several goals appear, choose one goal and run the sequence separately for the others. Treat the proposed dates as planning ranges, not promises.
Advanced instructions
Test the target window against cash flow, savings capacity, debt obligations, benefit eligibility, family events, and other plan milestones. Replace assumptions with confirmed facts before updating formal projections.
Use this when
A client wants to buy, retire, fund education, travel, or clear debt but describes the timing as "someday," "eventually," or "when things settle down."
You'll need
- Client goal
- Client context
- Current timing language
- Timing triggers
- Known dependencies
- Date flexibility
- Planning date
You'll get
- A vague goal rewritten as a specific outcome
- An earliest date, preferred target window, and latest acceptable date supported by stated facts or labeled assumptions
- Every known timing trigger and dependency categorized
- A fallback date tied to a clear activation condition
- One immediate planning action and one client follow-up question documented
By the end of this playbook
You will have:
- A vague goal rewritten as a specific outcome
- An earliest date, preferred target window, and latest acceptable date supported by stated facts or labeled assumptions
- Every known timing trigger and dependency categorized
- A fallback date tied to a clear activation condition
- One immediate planning action and one client follow-up question documented
Examples
Progress 1 of 6