Product Intelligence for AI-native teams

Make your best bet
in minutes, not weeks.

Speed up product work with the agent that automatically makes sure every bet is backed by evidence and helps each person stay on top of the next step.

Built by teams from

  • Spotify
  • Google
  • Adobe
  • PayPal

A whole new way to lead product.

  • Outcome-driven Share your objectives. Humfrid makes sure your output actually has an impact on outcomes.
  • Proactive The metrics, data and work that matter to you, before you have to ask.
  • Connected Signals from your tools automatically mapped to your goals and features.
  • Data-driven Evidence for and against each bet, with the sources attached.
  • Personalized Every answer grounded in your context, role and scope.

Automatic product discovery

What to bet on next, already answered.

Humfrid finds the next opportunity as the work happens. He continuously picks up signals, maps them onto opportunities, and tells you where to focus next.

01.

Captured automatically.

Signals across all your tools captured and classified - metrics, customer evidence, and what your competitor just shipped.

02.

Automatically mapped to the opportunity.

Each signal lands on the opportunities and work it affects. Supporting evidence builds up on its own.

03.

Instant access in Slack.

Know what to build and not, with the sources attached, right where you work.

Decision log

Decide once, and keep moving.

Humfrid writes the decision down as it happens, with who made it and why. The next person moves without asking.

  • Humfrid picks the decision up from the work itself, in Slack and in the tools, without someone filing it. The log stays current because the team never has to remember to write it down.

  • The metric, the message, or the interview is kept with the decision. The next person sees why the moment they need it.

  • Slack, analytics, tickets, and interviews are already attached to the decision. No one spends the afternoon pulling them back together.

  • Each decision keeps the one it replaced, with the date. The team sees how the call moved and starts from there.

  • Work that contradicts a decision is flagged the day it starts. The team can stop it before the week is spent building it.

Decision Keep one onboarding step Priya · #leadership
Data Step 1 completion −4pp
Decision Keep one onboarding step
  • Slack · #leadership
  • Step 1, −4pp
  • Paywall on the tour
  • Maya, onboarding interview
Decision Add a second step May 2
Decision Keep one step. Tighten step 1. May 9 · Current
Decision The tour stays free May 9

Conflicts with work in flight

Decision A paywall on the same flow Today
#leadership
PR
Priya just now

Keep one step. Tighten step 1.

Decision Keep one step. Tighten step 1.

The difference

Product speed at every stage.

  • Early Understand your customers and find product-market fit faster.

    Before

    You ship a lot.
    • Yet answers come slowly.
    • Understanding customers means going through dashboards and meeting transcripts.

    After

    You see what works.
    • Humfrid keeps track of your hypotheses, connects the signals from your tools and tells you what works - so you can learn faster and ship the right thing.
    • Humfrid combines all your research and gives you answers in no time.
  • Scale Keep moving at startup speed as you grow.

    Before

    Projects stall.
    • You get stuck in arguments about the right way forward.
    • Projects stall because someone forgot to follow up.

    After

    Projects keep moving.
    • You make decisions based on evidence from customers and data, while working from clear, testable hypotheses that help you understand the right way forward.
    • Humfrid keeps track of decisions and commitments, so projects keep moving.
  • Enterprise Fewer meetings. Sharper discussions, with the evidence attached.

    Before

    Meetings and lots of sync.
    • You're stuck in back to back meetings every day to share context and discover misalignment across work and teams.
    • The highest paid person makes decisions, even if they're wrong.

    After

    Same shared context.
    • Everyone is working from the same shared context.
    • All data and customer learnings needed to make an argument are less than 10 seconds away.
    • Misalignment is surfaced automatically, resulting in fewer sync meetings.
    • Humfrid briefs each person ahead of every meeting with what was last decided and questions to ask, so that every meeting is effective.

Proactive

The right person already knows.

A metric drops, two teams collide, a deadline slips. Humfrid tells the person who can act, the day it happens.

  • Metric anomalies
  • Team misalignment
  • Scope creep
  • Launch at risk
  • Slipping commitments
#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

Questions that took days, answered in seconds.

Ask in Slack. Humfrid pulls the full picture from every connected tool, with the source on each line.

  • Will we reach our Q4 goals?
  • Why did the metric move?
  • What have we tried before?
#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 3GitHub 4Linear 5Slack

Calendar + Humfrid

Only meetings that count.

Arrive to every meeting with a brief on what previously decided and what questions to ask to move your goals forward.

Google Calendar
1:1 with Jordan
Today, 2:00 – 2:30 PM
Jordan Product
Direct message
Humfrid App 1:50 PM

1:1 with Jordan at 2.

He was going to share the activation audit by Friday. Here’s where it stands, from Slack, Linear, and last week’s note.

The spec hasn’t reached eng yet. It may be with legal, or the priority may have moved. Worth asking what would help.

A good question: what’s in the way, and does this still serve the activation goal?

Google Calendar
Northstar
Today, 11:00 – 11:30 AM
Northstar 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
Board meeting
Thursday, 4:00 – 5:00 PM
Board
Direct message
Humfrid App 4:00 PM

Board at 4. A draft is ready for you to edit.

Step 1 fix: +1,800 activations a month, from two engineers. That’s realized. Northstar: €240k ARR, pending SSO. That’s a forecast.

Activation is down 4pp, with the cause noted, so you can talk about it rather than look it up.

Each number says whether it already happened or is still a forecast.

Google Calendar
Quarterly review
Thursday, 10:00 – 11:00 AM
Product leadership
Direct message
Humfrid App 9:40 AM

Q3 review at 10. Here’s the quarter.

7 of 9 initiatives shipped. Checkout refunds and the pricing test are still open.

Activation is up 2pp, against a 4pp goal.

The shorter tour shipped. The paywall work on that flow is still in progress.

Google Calendar
Discovery
Today, 3:00 – 3:45 PM
Product 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
Product 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

The why, right in the IDE.

Developers and their coding agents build from the same goals, customer evidence and decisions as everyone else, through MCP. The agent knows what was decided and why before it writes a line, so the code matches what should be built.

Works with

  • Claude Code
  • Cursor
  • Codex
  • Grok
  • Hermes
  • Autonomous
terminal connected

$ 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.

  • Editable memory
  • Never trains models
  • SOC 2 Type II in progress
  • GDPR compliant

Read more →

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.

Head of Product

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.

VP, Product Marketing

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.

Product Director

This is what I wish I’d had my whole career.

CPO

FAQ

Common questions.

How is Humfrid different from ChatGPT, Claude, and other copilots?

Humfrid is built for the teams that build the product. He holds the bet, the evidence behind it, and what each person needs to do next, and he keeps the product team coordinated around that. A copilot answers when you ask. Humfrid brings the product thinking, and keeps the team on the same work.

Read more on Humfrid vs copilots →

What does it take to get started?

Share the bet and the documents he needs, and give him access to the systems the work already lives in. He starts in Slack.

We have strict AI policies. Can we still use Humfrid?

Your data stays yours. We don't train on it, we don't sell it, and you can leave with everything anytime.

Security · Talk to the founders

Make your best bet
in minutes, not weeks.

Humfrid is the agent that helps your product org find the most impactful bets and stick to them.