Kubecost · Product sense · Mid · 45 to 60 minutes

How should Kubecost validate demand?

Kubecost helps companies understand and manage Kubernetes and cloud infrastructure costs. Answer this product management case and get it graded line by line against a weighted rubric.

customer discovery
hypothesis framing
MVP design
prioritization
success metrics

The situation

Webb Brown and Ajay Tripathy are exploring whether to start a company around cost visibility for Kubernetes users. From their time at Google and recent industry conversations, they believe teams running Kubernetes struggle to understand which apps, teams, or environments drive cloud spend. Engineering, finance, and leadership all feel the pain, but the exact buyer, urgency, and best product shape are still unclear. They have not formed a company, raised money, or written meaningful code yet. Assume they can spend the next 8 weeks testing this idea before deciding whether to commit full time. They want to avoid building too much too early and also avoid mistaking polite interest for real demand. One path is to do many customer interviews first. Another is to put a rough product artifact in front of users quickly. A third is to try both in parallel. Webb asks you, acting as the first PM on the idea, to recommend how Kubecost should validate the problem and the initial solution. Your plan needs to identify who to learn from, what to build or not build, and what evidence would justify moving from exploration to a real product.

What to produce

Write a 1 to 2 page product validation brief.

Your answer must

State 2 to 4 key hypotheses to test, clearly separating problem, user, and solution assumptions.
Choose an initial target segment and likely champion or buyer, and explain why you would not start broader.
Propose an 8 week validation plan that includes customer conversations and any MVP, prototype, or other artifact you would use.
Define 3 to 5 success signals and decision thresholds, including at least one behavior stronger than stated interest and at least one monetization signal.
List the main risks or biases in this phase and how your plan reduces them.

Constraints

Only the two founders are available to do the work, with no dedicated sales, design, or support team.
Budget is minimal and fundraising is not part of this phase.
The team needs enough evidence within 8 weeks to decide whether to commit full time.
Do not assume a production grade platform can be built before demand is clear.

Format

Use short sections with bullets under hypotheses, target users, validation plan, metrics, and risks.

How Kubecost actually played it

Co-founder describes validating the idea through a hundred customer conversations and then launching an open-source MVP with a Medium post that drew early interest. Practical for pre-build validation.

Talk to many customers before writing code
A simple open launch can pull in early users

Built from Kubecost's Path to Product-Market Fit: Validating an Idea with 100 Customer Conversations by First Round Review.