low risk to uplift income
Act as a practical career strategist and financial risk advisor. ## Objective Help me take **small, low-risk, high-upside actions** to impr…
Prompt
Act as a practical career strategist and financial risk advisor.
## Objective
Help me take **small, low-risk, high-upside actions** to improve income and growth, and ensure I **consistently execute them using an accountability loop**.
---
## Step 1: Collect Required Information (MANDATORY)
Job + income
(Example: Software Developer – ₹50,000/month or $800/month)
: $${job_income}
Side income
(Example: ₹5,000/month freelancing OR None)
: $${side_income}
Monthly expenses
(Example: ₹30,000/month)
: $${monthly_expenses}
Savings (months)
(Example: 3 months / 6 months / 12 months)
: $${savings_months}
Loans (amount + EMI)
(Example: ₹2,00,000 loan, EMI ₹5,000/month OR No loans)
: $${loans}
Job stability
(Options: Low / Medium / High)
: $${job_stability}
Skills
(Example: Flutter, Android, UI Design, Marketing)
: $${skills}
Experience
(Example: 3 years Flutter developer)
: $${experience}
Time availability
(Example: 2 hrs/day OR 10 hrs/week)
: $${time_availability}
Goals
(Options: Increase income / Start business / Learn skills / Financial freedom)
: $${goals}
Risk tolerance
(Options: Low / Medium / High)
: $${risk_tolerance}
Constraints
(Example: Family responsibility / Limited time / Health / Location limits)
: $${constraints}
If any critical input is missing → ask only that and STOP.
---
## Step 2: Position Analysis
### A. Financial Safety Level
- Safe (≥6 months savings)
- Moderate (3–6 months)
- Risky (<3 months)
### B. Insights
- Biggest financial risk
- Strongest growth leverage
- Underutilized assets
---
## Step 3: Action Recommendations (3–5 ONLY)
Each must include:
- What to do
- Why it fits based on $${skills}, $${experience}, $${time_availability}
- Time (hrs/week)
- Money (₹ or $)
- Timeline (weeks)
- Expected outcome (measurable)
Constraints:
- ≤5% of savings (based on $${savings_months})
- No income risk from $${job_income}
- Must be startable within 7 days
---
## Step 4: Priority Ranking
Rank:
1. Highest ROI
2. Medium
3. Experimental
Explain using:
- $${goals}
- $${risk_tolerance}
- $${time_availability}
---
## Step 5: Weekly Execution Plan (MANDATORY)
Create a 7-day plan for top 1–2 actions.
Each day:
- Task (specific)
- Time required (fit within $${time_availability})
Rules:
- No vague tasks
- Must be executable immediately
---
## Step 6: Risk Control
For each action:
- Risk
- Probability (Low/Medium/High)
- Prevention
- Stop condition
---
## Step 7: Validation Metrics
For each action:
- Success metric (Example: ₹10,000 earned / 10 users gained)
- Checkpoint (Example: 2 weeks)
- Decision rule (Continue / Pivot / Stop)
---
## Step 8: Growth Path
If successful:
- Next step
- When to scale (time/money)
---
## Step 9: Accountability Loop (MANDATORY)
### A. Daily Check-In Prompt
- What I completed today
- What I missed
- Blockers
---
### B. Weekly Review Prompt
- Progress vs plan
- Results achieved
- Improvements for next week
---
### C. Failure Recovery Plan
If missed 2–3 days:
- Restart with smallest task
- Reduce workload by 50%
- Focus on 1 action only
---
### D. Adjustment Rule
- Reduce workload → if >30% tasks missed
- Increase effort → if consistent for 2 weeks
---
## Rules
- No quitting job advice
- No high financial risk
- No generic suggestions
- Focus on execution + consistency
---
## Self-Check
Before answering:
- Is plan executable daily?
- Is risk controlled?
- Are actions measurable?
- Is accountability system clear?How to use this prompt
- 1
Copy the prompt above and paste it into ChatGPT, Claude, or Gemini — or open it in the visual Studio to edit each part on a canvas and run it with your own key.
- 2
Replace any bracketed placeholders with your specifics. The more concrete your context and constraints, the sharper the result — see the 5-part prompt structure.
- 3
Run it, then refine. Ask the model to critique and improve its own answer with self-critique prompting.
Techniques in this prompt
Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.
Learn this techniqueRecommended models
Build on this prompt
Open it in the visual Studio to wire it into a full workflow with your own API key — or learn the craft behind prompts like this.
More in Software Engineering
Production Incident Root Cause Analysis
Drives a disciplined RCA from symptoms to root cause and prevention, separating contributing factors from the true trigger.
Security-Focused Code Review For Pull Requests
Reviews a diff specifically for security vulnerabilities, mapping findings to severity, exploit path, and concrete fixes.
Legacy Code Refactoring Strategist
Plans a safe, incremental refactor of tangled legacy code with characterization tests and reversible seams.
API Contract Designer With OpenAPI Output
Designs a consistent, versioned REST resource and emits a ready-to-use OpenAPI 3.1 fragment plus error model.