Question 1

Why did my startup get a low score?

Accepted Answer

Low scores usually reflect weak market fit, crowded competition, unclear differentiation, or high execution risk. Our AI analyzes your idea across these dimensions and explains the main issues in the breakdown. Use the verdict and suggested pivot to refine your concept and re-roast to see improvement.

Question 2

What do the roast score tiers mean?

Accepted Answer

Ship It (85–100): Strong idea, worth validating further. Decent (70–84): Promising but has gaps to address. Needs Work (50–69): Significant issues; use feedback to iterate. Roasted (0–49): Major concerns; consider pivoting or solving the core problem before building.

Question 3

How does DontBuildThis score startup ideas?

Accepted Answer

Our AI evaluates your idea on market fit, competition, differentiation, execution risk, and clarity. It returns a score out of 100, a tier, a verdict, and a detailed breakdown so you know exactly what to improve before spending time and money building.

Question 4

Can I improve my startup idea score?

Accepted Answer

Yes. Use the breakdown and verdict to address weak points, then submit an updated idea or pivot. Many founders improve their score by narrowing the problem, clarifying the target customer, or strengthening their unique angle.

Question 5

What is a good score for a startup idea?

Accepted Answer

Scores of 70+ indicate promising ideas worth exploring. 85+ suggests strong potential. Scores below 50 mean the idea likely needs significant rework or a pivot before it’s worth building.

Question 6

What score did "Payroll managers and clerks at mid-sized construction firms (20-100 workers across multiple sites) spend 30-45 minutes *every single workday* manually collecting, verifying, and reconciling timesheets. They juggle:

- Handwritten or Excel timesheets from multiple foremen  
- Cross-checking worker classifications (apprentice, journeyman, subcontractor) against complex union/company rules  
- Matching hours to job codes or cost centers pulled from project management tools for billing accuracy

Errors cause delays, disputes, and fines. Over 20% of payrolls have errors inflating labor costs, eating into tight margins, and damaging worker morale. Payroll delays frustrate everyone and risk compliance violations with union contracts and labor laws.

Existing time tracking apps like ClockShark or TSheets don’t solve classification or job costing reconciliation. Payroll software focuses on paychecks, not upstream validation. So clerks hack together Excel macros or manual double-checks — a massive waste of labor hours that costs $495/month per location just in payroll clerk time, not counting error fallout." get?

Accepted Answer

"Payroll managers and clerks at mid-sized construction firms (20-100 workers across multiple sites) spend 30-45 minutes *every single workday* manually collecting, verifying, and reconciling timesheets. They juggle:

- Handwritten or Excel timesheets from multiple foremen  
- Cross-checking worker classifications (apprentice, journeyman, subcontractor) against complex union/company rules  
- Matching hours to job codes or cost centers pulled from project management tools for billing accuracy

Errors cause delays, disputes, and fines. Over 20% of payrolls have errors inflating labor costs, eating into tight margins, and damaging worker morale. Payroll delays frustrate everyone and risk compliance violations with union contracts and labor laws.

Existing time tracking apps like ClockShark or TSheets don’t solve classification or job costing reconciliation. Payroll software focuses on paychecks, not upstream validation. So clerks hack together Excel macros or manual double-checks — a massive waste of labor hours that costs $495/month per location just in payroll clerk time, not counting error fallout." scored 91/100 (🔥 Ship It). This is a painkiller, not a vitamin. Ship it yesterday.