Estimate the time and cost to develop a learning project
A development estimate broken down by phase and role, with assumptions, complexity drivers, and a range instead of a single guess.
The prompt
Help me estimate the development effort, timeline, and cost for a learning project.
Deliverables: [e.g. "45-minute interactive e-learning, 3 short videos, a job aid, a facilitator guide for a 2-hour session"]
Interactivity or complexity level: [e.g. "click-and-read", "scenarios and simulations", "custom animations"]
Existing content available: [none / rough slides / solid SOPs]
Team: [roles available and hourly or daily rates, or "use placeholders"]
SME availability: [DETAILS]
Review rounds and approvers: [e.g. "3 rounds, legal review required"]
Translation or localization: [LANGUAGES or "none"]
Deadline: [DATE]
Method:
- Estimate by phase: analysis, design, storyboard/scripting, development, media production, reviews and revisions, QA and testing, pilot, launch.
- Build the estimate bottom-up from the task breakdown. You may sanity-check it against development-hours-per-finished-hour ratios, but label any ratio you cite as a rough, unverified rule of thumb [CONFIRM], never as a fact.
- Identify the drivers that most change the estimate: content readiness, SME delays, review rounds, custom media, scope creep.
Return:
1. A table: Phase | Tasks | Role | Hours (low / likely / high) | Cost.
2. Total effort and cost range, and a realistic timeline with dependencies.
3. Assumptions list I can share with the sponsor.
4. Ways to reduce time or cost, with the trade-off for each.
5. Scope risks to call out before agreeing to a deadline.
Use only rates I provide; otherwise use [RATE] placeholders.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- none / rough slides / solid SOPs
- DETAILS
- e.g. "3 rounds, legal review required"
- LANGUAGES or "none"
- DATE
- CONFIRM
- RATE
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Turn business insights into an action plan with owners and deadlinesConverts findings from an analysis, review, or workshop into a prioritized action plan with owners, deadlines, and success measures.
- Turn a list of milestones into a project timeline or Gantt chartConverts milestones and dates into a phased timeline, a Gantt-style table for Excel, and a one-slide version for PowerPoint.
- Prepare evidence and narrative for an accreditation self-studyMaps accreditation standards to evidence, finds gaps, and drafts self-study narrative sections.
- Prepare my clinic for an accreditation or state surveyA readiness plan with a mock-survey checklist, document binder list, staff prep, and a tracker for gaps found before surveyors arrive.