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 "Relay is a minimal embeddable HTTP server library for C++ that lets developers expose a clean local API inside any application with just a few lines of code. Instead of dealing with complex frameworks or external services, developers can instantly turn their desktop app, game engine, or tool into an API-driven system using a simple route-based interface. Under the hood, Relay handles raw sockets, HTTP parsing, and an efficient event loop, but exposes a clean, modern API that feels as simple as defining functions. This makes it ideal for performance-sensitive applications where full web frameworks are too heavy but some form of structured communication is still required.

From a business perspective, Relay starts as a widely adopted open-source utility because of its simplicity, performance, and zero-dependency design—positioning it as the “go-to embedded HTTP layer” in C++ ecosystems. Once adoption grows, monetization can expand into advanced modules such as observability dashboards, authentication layers, distributed debugging tools, and enterprise support for teams embedding Relay in production systems. The long-term opportunity is not replacing web servers like nginx, but becoming the default internal communication layer inside non-web software. Competing tools like Boost.Beast, Crow, Pistache, and cpp-httplib are either too complex, too heavy, or too opinionated—Relay’s winning strategy is extreme simplicity, predictable behavior, and a developer experience that makes embedding a server feel like adding a function, not a subsystem." get?

Accepted Answer

"Relay is a minimal embeddable HTTP server library for C++ that lets developers expose a clean local API inside any application with just a few lines of code. Instead of dealing with complex frameworks or external services, developers can instantly turn their desktop app, game engine, or tool into an API-driven system using a simple route-based interface. Under the hood, Relay handles raw sockets, HTTP parsing, and an efficient event loop, but exposes a clean, modern API that feels as simple as defining functions. This makes it ideal for performance-sensitive applications where full web frameworks are too heavy but some form of structured communication is still required.

From a business perspective, Relay starts as a widely adopted open-source utility because of its simplicity, performance, and zero-dependency design—positioning it as the “go-to embedded HTTP layer” in C++ ecosystems. Once adoption grows, monetization can expand into advanced modules such as observability dashboards, authentication layers, distributed debugging tools, and enterprise support for teams embedding Relay in production systems. The long-term opportunity is not replacing web servers like nginx, but becoming the default internal communication layer inside non-web software. Competing tools like Boost.Beast, Crow, Pistache, and cpp-httplib are either too complex, too heavy, or too opinionated—Relay’s winning strategy is extreme simplicity, predictable behavior, and a developer experience that makes embedding a server feel like adding a function, not a subsystem." scored 87/100 (🔥 Ship It). This is the kind of OSS wedge that quietly eats a market—ship it, then monetize the pain.