Find the right people
Build a customer interview screener
Turn a recent customer behavior into a recruiting question. Separate the people who use a workflow from the people who buy it, and keep interview notes in your browser.
Build a screener →Start with one useful decision
Less guessing.
A clearer next step.
You do not need a fixed founder identity to start. You need a way to check an assumption, listen to a customer, and decide what to build next.
FounderType brings together practical guides, source-based case discussions, and a short working-style reflection. Use them to turn an idea into a small, observable experiment.
Written and maintained by chengcheng. Full quiz results are free and require no email.
From reflection to action
Tools for your next founder decision
Choose the resource that matches the uncertainty in front of you. Start with the people closest to the problem, keep evidence separate from inference, then decide what to test.
Validate an assumption
Design a founder experiment
Write down a claim, choose a low-cost test, and decide in advance what result would make you continue, change direction, or stop.
Build your experiment brief →Understand the problem
Run a useful customer interview
Use past-behavior questions, distinguish evidence from compliments, and capture what people already do to solve the problem.
Prepare an interview →Reduce the first build
Scope a smaller MVP
Separate the outcome from the feature list. Keep the smallest end-to-end workflow that can test your next important assumption.
Create a scope boundary →Review customer evidence
Turn interview notes into a decision
Separate observations from interpretations, keep counterexamples visible, and choose a next test that fits the remaining uncertainty.
Read the evidence review guide →A reflection, not a prediction
What do you tend to do first?
Twenty hypothetical situations explore four working-style labels: Builder, Visionary, Operator, and Hustler. Your result describes the points assigned to your answers. It does not measure ability, diagnose personality, or predict startup success.
Read the questions, scoring method, and limitations. Answers stay in this page's memory; they are not sent to our server or saved after you reload.
Take a moment to reflect
Choose the answer closest to your usual first response, even if several could work. If you have not faced a situation, answer hypothetically.
- 20 questions, one answer per question.
- You control when to move on and can go back to change an answer.
- Your full result appears immediately, without a name or email.
The labels and weights are an editorial reflection framework, not a validated psychological assessment. No result is a better or worse kind of founder.
Choose an answer, then select Next. Use Tab and the arrow keys to navigate the answer choices.
Your current answer pattern
| Working style | Raw points | Share |
|---|
Shares total 100% after rounding. They describe this set of answers, not population percentiles, fixed personality traits, or chances of success. Small differences need not be meaningful.
Use the result as a prompt for a real decision. Your situation, collaborators, skills, and available evidence matter more than a label.
Read all four working styles
You can use every profile without taking the quiz. Compare the habits, trade-offs, and exercises rather than treating any label as a permanent identity.
Make it tangible
Builder
Turn an idea into something people can try. Pair making with a check that the problem matters.
Read the Builder profile →Connect possibilities
Visionary
See a possible direction. Turn the big picture into a claim you can test this week.
Read the Visionary profile →Create repeatability
Operator
Make a process visible and reliable. Check the goal before optimizing the workflow.
Read the Operator profile →Learn through people
Hustler
Start conversations and commitments. Keep promises aligned with what can actually be delivered.
Read the Hustler profile →Read with a critical eye
Case discussions, with sources
A founder story can illustrate a decision without proving that it caused success. Read the evidence, separate reported facts from interpretation, and consider when the lesson would fail in your own situation.
- Starbucks: what a retail experience can teach a founderA case discussion about positioning and customer experience.
- Airbnb: learning from an early customer problemCheck the original sources and the limits of the comparison.
- Alibaba: examining a marketplace decisionLook for a decision you can test, rather than a formula to copy.
- HP: a first product and an early customerCompare the founders' circumstances with your own constraints.
See our editorial policy for sourcing, corrections, and the distinction between evidence and interpretation.