메뉴
Estimate realistic project timelines, break down hours by feature/phase, include buffer for revisions, set achievable client expectations, and avoid over-promising deadlines you can't meet.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Deep market analysis that downloads an entire industry into your brain. Searches forums, Reddit, industry sites, events, and platforms to uncover pain points, language, opportunities, and the perfect software solution to sell them.
Strategic amplification mode that reveals blind spots, untapped opportunities, and hidden leverage points in any business strategy, entrepreneurship idea, or creative content project. Cuts through noise to show what others miss.
Transform any boring B2B business problem into a complete software blueprint with architecture, database schema, feature breakdown, and step-by-step implementation plan formatted as a CLAUDE.md file ready for development.
Generate 30-50 deep discovery questions for any business type to uncover hidden pain points, workflow bottlenecks, and $15K+ software opportunities during client conversations.
Calculate the right price for custom software projects ($8K-$50K+) based on complexity, value delivered, and client ROI. Includes justification, pricing tiers, negotiation strategies, and ROI calculations to present to clients.
Discover untapped B2B software opportunities by analyzing specific industries for boring business problems, pain points, willingness to pay, competition levels, and where to find these businesses.
| name | time-resource-estimator |
| description | Estimate realistic project timelines, break down hours by feature/phase, include buffer for revisions, set achievable client expectations, and avoid over-promising deadlines you can't meet. |
Stop over-promising. Deliver on time with realistic estimates.
Input: Project scope and features Output: Realistic timeline, hour breakdown, buffer calculations, client communication
Authentication & User Management: 6-8 hours
CRUD Operations (per model): 4-6 hours
Forms (per complex form): 3-5 hours
Dashboard/Analytics: 8-12 hours
File Uploads: 4-6 hours
PDF Generation: 6-8 hours
Email Notifications: 4-6 hours
Integrations (per service): 10-15 hours
Mobile Responsive: +20% of total hours
NEVER give estimates without buffer.
Rule of thumb:
Total: Base × 1.5
Example:
Full-time work (40 hrs/week):
Part-time work (20 hrs/week):
Always add 1-2 weeks for:
Safe timeline formula: (Estimated hours ÷ weekly hours) + 2 weeks
Fire Inspection Software (80 base hours)
Week 1-2: Foundation (20 hours)
Week 3-4: Core Features (30 hours)
Week 5-6: Field Features (20 hours)
Week 7: Polish & Testing (10 hours)
Week 8: Client Review & Revisions
Total: 8 weeks (80 hours × 1.5 buffer ÷ 20 hrs/week = 6 weeks + 2 week buffer)
What to say: "Based on the scope, this will take 6-8 weeks from kickoff to launch."
What NOT to say: "This is 80 hours of work, so if I work full-time it's 2 weeks."
Why: Hours mean nothing to clients. Weeks are tangible.
During proposal: "Timeline: 6-8 weeks
This assumes:
If any of those change, timeline adjusts."
Put it in writing. Protects you from "why is this taking so long?"
❌ "We need this in 2 weeks" → Unrealistic for anything substantial ❌ Unclear requirements → Will cause delays and rework ❌ Multiple stakeholders → Slow approvals ❌ "Just like [complex SaaS]" → They underestimate complexity ❌ Client never responds fast → Adds weeks to timeline
Solution: Build timeline expectations into contract.
Be honest early:
"Hi [Client],
Quick update on timeline. We hit an unexpected complexity with [feature]. This is adding 3-5 days to the schedule.
New delivery date: [date] instead of [original date].
Apologies for the delay - I'd rather get it right than rush it.
[Your Name]"
Better to reset expectations early than miss deadlines.
Before giving a timeline, verify:
If anything is unclear: Add more buffer or say "I need to scope this more before committing to a timeline."
High Confidence (±1 week):
Medium Confidence (±2 weeks):
Low Confidence (±4 weeks or "TBD"):
Adjust buffer accordingly.
Under-promise, over-deliver.
vs.
Same work. Different perception.
Add buffer. Deliver early. Look like a hero.
