01.
Captured automatically.
Customer conversations, and who was in them, captured against the hypothesis you are testing.
For founding teams
Find traction,
faster.
Startups are messy. Humfrid makes your journey less messy by identifying and continuously testing your hypotheses, so you learn faster and ship what people want.
Built by teams from
A whole new way to succeed with your startup.
- Outcome-driven Set a goal. Humfrid identifies opportunities for reaching it, and how to test them.
- Proactive The metric, the customer line, and the work that just changed, before you go looking.
- Connected Signals from the tools you already use, mapped to your hypotheses.
- Data-driven Evidence for and against each assumption, with the sources attached.
- Personalized Every answer grounded in your company and what you are testing.
Assumptions
Know when to pivot.
Write down who you believe the customer is. Humfrid tests that hypothesis against what buyers actually say, across every conversation, and shows when the evidence tells you what to pursue next.
02.
Mapped onto the hypothesis.
Each conversation lands on the hypothesis it tests. The reasons to pursue it, and the reasons not to, build up on their own.
03.
Instant access in Slack.
See why to pursue it, and why not, with the sources attached, right where the team works.
Decision log
Stay focused.
Humfrid keeps track of the decisions you make and why you made them, to keep you accountable and always learning what works, and what doesn't.
Humfrid picks the decision up from Slack and the tools, the moment it is made. The log stays current on its own.
The metric, the message, or the interview stays with the assumption. The next person sees why the moment they need it.
Slack, analytics, tickets, and interviews are already attached to the decision.
Each assumption keeps the one it replaced, with the date. You can see what you believed, and the next test starts from there.
Work that contradicts the assumption is flagged the day it starts. The team can stop it before the week is spent building it.
Slack · #leadership
Step 1, −4pp
Paywall on the tour
Maya, onboarding interview
Conflicts with work in flight
#leadership
PR
Priya just now
Keep one step. Tighten step 1.
Proactive
The data you need before you ask.
The same pain shows up across conversations, a metric moves, two people build from different beliefs. Humfrid tells the person who can act, the same day.
#metrics
Humfrid APP 7:42 AM
Activation slipped 4pp overnight, mostly on step 1 of the new onboarding tour. @maya that's your flow.
#leadership
Humfrid APP 9:15 AM
Heads up: @sam is putting a paywall on the flow @priya just made free. I booked you both a 20-min sync today at 2:30.
#product
Humfrid APP 4:30 PM
@priya the checkout rewrite grew from 8 to 13 tickets: the payment provider can't do partial refunds. Moving refunds to v2 keeps the June date.
#launch
Humfrid APP 11:05 AM
@priya Thursday's launch is at risk. The shorter tour still isn't in, and step 1 is the open question.
#leadership
Humfrid APP 3:10 PM
@dana the pricing test was committed for this week. It's still in review, and the squad is on the refactor.
Instant
The answer, while the question is still fresh.
Ask in Slack. Humfrid pulls the picture from your tools, with the source on each line.
#product
PR
Priya 8:12 AM
@Humfrid are we on track with our priorities?
Humfrid App 8:14 AM
Not fully. 2 of 4 priorities are on track1. The other two:
- Activation: step 1 is still down 4pp2. The shorter tour merged last night3, but two Linear issues4 are putting a paywall on the same flow.
- Checkout: at risk. Refunds grew the scope, and moving them to v2 keeps the June date5.
1Goals 2Metrics 3
GitHub 4Linear 5Slack
Goals 2Metrics 3GitHub 4Linear 5Slack Calendar + Humfrid
Learn from every conversation.
Walk into every conversation with what you already know, what you need to learn next and the questions you need to ask.
Google Calendar Northstar
Today, 11:00 – 11:30 AM
NNorthstar Customer
Direct message
Humfrid App 10:50 AM
Northstar at 11. You’re already caught up.
They’ve asked for SSO three times, and it’s on the enterprise goal. The export fix they flagged shipped last night, so you can lead with that.
Usage is down this week. Worth asking how the rollout feels on their side.
A good question: is SSO the thing in the way, or is it further down the list?
Google Calendar Discovery
Today, 3:00 – 3:45 PM
PProduct Onboarding
Direct message
Humfrid App 2:40 PM
Discovery at 3. The goal on the table is activation.
What we know from customers: the first screen is unclear, and two people this week stopped before the tour finished. Nobody in those calls asked for a second step.
The decision for the room is whether to shorten step 1, or talk to a few more people before changing it.
Google Calendar Standup
Today, 9:15 – 9:30 AM
##product
Direct message
Humfrid App 9:02 AM
Standup in 15 minutes. Here’s a place to start.
Step 1 is down 4pp since yesterday. The shorter tour merged last night, which is the likely place to look.
Maya has been waiting on the paywall tickets since yesterday. A yes or no there would unblock her.
Opening there gives her an answer she’s been waiting on.
Google Calendar Retrospective
Friday, 4:00 – 4:45 PM
RProduct squad
Direct message
Humfrid App 3:40 PM
Retro at 4, on the shorter onboarding tour.
What happened: it shipped two days ago. You kept one step and tightened the first screen. A second step had been in the plan for a week before that.
What worked: this week’s interviews said the first screen is clearer, and two people finished who had stopped before.
What didn’t: step 1 is still short of the activation goal, and the tour went out before the team had a shared read on what success looked like.
MCP + Humfrid
Build something people want.
Connect to Humfrid via MCP and your coding agents will get all decisions and customer evidence right in the IDE. The agent will know your customers as well as you do.
Works with
$ add a second step to the onboarding tour
onboarding/tour.ts
+steps.push("second step")
stopped before writing.
#leadership, Priya, last week
keep one step. tighten step 1 first.
$ shorten step 1 instead? [y/n]
Secure
Your context, governed and secure.
See and edit everything Humfrid knows. Your data stays in your workspace and is never used to train a model.
What people are saying.
Humfrid understands more than Claude even though it has access to less context. Previously I had to prompt Claude 5 times to get an answer that makes sense. Humfrid just gets it.
I’d pay $500 out of my own pocket just for the meeting prep. I’m always in back to back meetings and Humfrid helps me through my weeks.
I’ve been using Humfrid recently and loving it. Tools like this are the future - not just for product teams, but for organizations at any size.
This is what I wish I’d had my whole career.
FAQ
Common questions.
How is Humfrid different from ChatGPT, Claude, and other copilots?
Humfrid is built for the small team shipping the product. He holds the assumption, the evidence behind it, and the next step for each person, and he keeps that team on the same bet.
What does it take to get started?
Share the assumption you are testing and the documents around it, and connect the tools the work already lives in. He starts in Slack.
We have strict AI policies. Can we still use Humfrid?
Your data stays yours. It is never used to train AI models or sold, and you can export it and delete your workspace at any time.
Find traction,
faster.
Humfrid helps founders find traction from what the data, customers and market are already saying.