Skip to content

Problem-Solution Fit Evidence

Tangible proof that real users or partners have the problem and use this product to solve it.

Methodology

What We Look For

Evaluation Criteria:

  • Public case studies or customer stories
  • Design partner or customer quotes
  • Evidence in announcements, docs, or PR
  • Real workflows described by users
  • Specific problems solved

Data Sources:

Source TypeExamples
PrimaryPublic case studies, customer stories, partner announcements
SecondaryCustomer tweets/threads, Discord/forum messages describing workflows

Scoring Factors

  • Specific, named customers or partners score higher
  • Generic claims without evidence score lower
  • Multiple independent sources increase confidence
  • Detailed workflows and outcomes score better

Guide

Finding Information

Step 1: Identify Your Customers/Users

Who uses your product and why?

  • Named design partners
  • Public customers or projects
  • Prominent users in your community
  • Integration partners

Step 2: Gather Evidence

Collect proof of problem-solution fit:

  • Published case studies
  • Customer quotes or testimonials
  • Partnership announcements
  • User-generated content describing workflows
  • Integration documentation from partners

Step 3: Document Specific Problems Solved

For each customer/user:

  • What problem did they have?
  • How does your product solve it?
  • What results did they achieve?
  • Can you quantify the impact?

Submitting Evidence

When submitting problem-solution fit evidence:

  1. Case Studies:

    • Link to published case studies
    • Customer name and company
    • Problem statement
    • Solution and outcomes
  2. Customer Quotes:

    • Direct quotes from customers
    • Attribution (name, title, company)
    • Context of the quote
    • Link to source (tweet, blog, video)
  3. Partnership Announcements:

    • Official partnership announcements
    • Integration documentation
    • Joint press releases
    • Conference presentations featuring customers
  4. User-Generated Content:

    • Tweets or threads describing use cases
    • Discord/forum posts with workflows
    • GitHub issues or discussions
    • Video demos from users

Growing crypto's GDP by automating treasury allocations to builders creating real value.