Timeline Calculation
Total Weeks = Base Weeks (by complexity) à Team Multiplier à Experience Multiplier
Base Timeline by Complexity
| Complexity |
Base Weeks |
| Simple |
2 weeks |
| Medium |
6 weeks |
| Complex |
12 weeks |
* Configurable in Settings
Team Size Multiplier
| Team Size |
Multiplier |
Reasoning |
| Solo Developer |
1.5x |
One person doing everything |
| Small Team (2-4) |
1.0x |
Baseline (optimal balance) |
| Medium Team (5-10) |
0.7x |
More parallel work possible |
| Large Team (10+) |
0.6x |
Max parallelization (w/ overhead) |
Experience Level Multiplier
| Experience |
Multiplier |
Reasoning |
| Junior (0-2 years) |
1.5x |
Learning curve, more support needed |
| Intermediate (2-5 years) |
1.0x |
Baseline (competent developer) |
| Senior (5+ years) |
0.75x |
High efficiency, fewer mistakes |
| Expert (Architect) |
0.6x |
Optimal paths, architectural foresight |
Phase Time Allocation
Each Phase Duration = Total Weeks à Phase Percentage
| Phase |
Default % |
Purpose |
| Planning & Design |
25% |
Requirements, architecture, design |
| Development |
45% |
Coding, implementation |
| Testing & Quality |
20% |
QA, bug fixes, UAT |
| Deployment & Docs |
10% |
Release, documentation, training |
* Configurable in Settings
Complexity Detection
Complexity is determined by keyword matching in your project description:
- đĸ Simple: Keywords like "simple", "basic", "straightforward"
- đĄ Medium: Keywords like "moderate", "standard", "typical"
- đ´ Complex: Keywords like "enterprise", "advanced", "scalable"
Technology Detection
Technologies are recommended based on keyword scores:
- ⥠Apex: "business logic", "trigger", "integration", "API"
- đ¨ LWC: "component", "UI", "interface", "frontend"
- đ Flow: "automation", "workflow", "process"
- đ Integration: "external", "API", "third-party"
Higher keyword matches = Higher priority recommendation
â ī¸ Important: These are estimated timelines based on industry averages. Real-world timelines depend on: business requirements, technical debt, team dynamics, organizational processes, and unforeseen challenges. Always add buffer time for your specific context!