Retool · Product sense · Senior · 45 to 60 minutes

Who should Retool target first?

Retool is a platform that helps developers build internal tools such as admin panels and operational apps more quickly. Answer this product management case and get it graded line by line against a weighted rubric.

Segmentation
Hypothesis design
Product strategy
Go to market judgment
PMF metrics

The situation

David Hsu has an early Retool MVP, a developer tool for building internal apps with basic UI components like tables, buttons, and text inputs. A handful of companies have shown interest, but their needs vary widely, from support dashboards to billing workflows, and the product still has important gaps such as limited integrations. The team is pre launch, small, and doing founder led outreach with little brand recognition or inbound demand. Several customer groups seem plausible, developers at small startups, developers inside larger companies, teams using legacy internal app tools like FileMaker or Access, and engineers building ad hoc internal apps in JavaScript or React. Hsu asks you to recommend where Retool should focus next. The team needs an approach that narrows the initial customer profile, sharpens the message, and guides what to build and learn over the next phase. This is hard because the product sits in a category many developers instinctively dislike, drag and drop tooling, while the broader problem, building internal tools, seems common but fragmented across use cases. A bad choice could waste scarce engineering time, create misleading customer signals, or push the company toward a market that will not produce durable product market fit.

What to produce

Write a 1 to 2 page product strategy memo.

Your answer must

Choose an initial target customer profile, including user type and company context, and explain why it is the best starting point now.
List the top 3 to 5 hypotheses Retool should test next, including at least one about user pain, one about adoption barriers, and one about product capability gaps.
Propose a lightweight learning plan for the next phase, including how the team should use outreach, demos, and product feedback to validate or reject the strategy.
Recommend the most important product and messaging priorities for the chosen target, and explain what not to build or say yet.
Define the primary early success metric and 2 to 3 supporting signals that would indicate Retool is moving toward product market fit.
Call out the biggest risks and second order effects of your plan, including what evidence would make you change direction.

Constraints

The team has very limited engineering bandwidth and cannot support many segment specific features at once.
The current product mainly offers basic building blocks for internal apps and does not yet cover every integration or workflow.
Customer acquisition is mostly cold outbound and direct founder conversations, not strong inbound demand or brand pull.
The audience is technical and will quickly reject a product that feels buggy, vague, or positioned for non developers.

Format

Use clear section headings and concise bullets. A simple table for segment choice, hypotheses, and tests is welcome.

How Retool actually played it

The founder lays out a hypothesize, test and iterate loop used to reach about 100 happy customers before launch. A repeatable approach to early product discovery.

Write the hypothesis before you build
Count happy customers as the early fit metric

Built from Retool's Path to Product-Market Fit: Getting to 100 Happy Customers, Faster by First Round Review.