Founder Readiness Assessment

I'd register a domain name, incorporate a company, and explore patent or trademark protection right away. I need to protect my idea from being stolen.

I'd define a specific customer profile and schedule a structured round of open-ended discovery interviews with strangers before doing anything else.

I'd compile a survey of questions about whether my product is something a customer would like and send it out to a list of strangers.

I'd start building a prototype. Customers and investors need to see something real as soon as possible.

I'd build a brief document clearly articulating the problem I'm solving, the customer segments I'm targeting, and the value I'm providing to each. Then use that to build marketing materials for further validation.

I'd concentrate on building a prototype. Customers need to see something tangible as soon as possible.

I'd write a pitch deck and start pitching to investors to get seed funding. You can't build a business without money.

I'd design a marketing campaign promoting the product and getting customers to sign up for a wait list. I need to validate that I know how to sell my product before building anything.

I'd start building out my vision with Lovable or another low-code platform right away and start showing it to people for feedback.

I'd start shopping my idea around to find people to collaborate with. I can't do this alone.

I'd build a deck, start pitching investors relentlessly and entering pitch competitions and applying for prestigious accelerators. If I can get validation from the startup community it will buy momentum and everything else will get easier.

I'd go all-in and get an MVP built quickly using a freelancer or development shop. I need to build something real before I can sell it.

I'd simplify the value prop, redesign onboarding, and run rapid tests to ensure users grasp the core benefit within seconds.

I'd add more features so they're likely to find something useful as they explore the product.

I'd move forward and test the same product with a larger group of users. Odds are good that these early testers were not the right audience.

I'd adjust features and messaging incrementally, then retest with the same user group for comprehension.

I'd run a structured alignment session on values, working styles, responsibilities, and conflict norms, then test our ability to collaborate with a small project before moving forward.

I'd move forward but define clear areas of responsibility and a decisionmaking hierarchy. I value their experience and skills, but in the end there needs to be a clear understanding of who is in charge.

I'd structure a strict agreement that defines their job responsibilities, ownership stake, and intellectual property rights. Clarity in business relationships is key. If they don't want to play by the rules, they're not the right fit.

You've identified a product idea you think is a great idea, and your early conversations with friends and peers show enthusiasm. What do you do next?

You've completed discovery interviews and the feedback is generally positive. What do you do next?

You've got a clear vision of a product in your mind and your savings will cover 3 months of startup runway. What's your next move?

You've built a prototype, but a small number of early testers don't understand the value without heavy explanation. What's your next step?

You've found someone who might be a good technical cofounder. They're smart, experienced, and available, but you've noticed small points of friction in communication and personality. What's your approach?

Your Assessment Results