Captured automatically.
Signals across all your tools captured and classified - metrics, customer evidence, and what your competitor just shipped.
Product Intelligence for AI-native teams
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




Automatic product discovery
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.
Signals across all your tools captured and classified - metrics, customer evidence, and what your competitor just shipped.
Each signal lands on the opportunities and work it affects. Supporting evidence builds up on its own.
Know what to build and not, with the sources attached, right where you work.
Decision log
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.
Conflicts with work in flight
Keep one step. Tighten step 1.
The difference
Before
You ship a lot.After
You see what works.
Before
Projects stall.After
Projects keep moving.
Before
Meetings and lots of sync.After
Same shared context.Proactive
A metric drops, two teams collide, a deadline slips. Humfrid tells the person who can act, the day it happens.
Activation slipped 4pp overnight, mostly on step 1 of the new onboarding tour. @maya that's your flow.
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.
@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.
@priya Thursday's launch is at risk. The shorter tour still isn't in, and step 1 is the open question.
@dana the pricing test was committed for this week. It's still in review, and the squad is on the refactor.
Instant
Ask in Slack. Humfrid pulls the full picture from every connected tool, with the source on each line.
@Humfrid are we on track with our priorities?
Not fully. 2 of 4 priorities are on track1. The other two:
Calendar + Humfrid
Arrive to every meeting with a brief on what previously decided and what questions to ask to move your goals forward.
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?
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?
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.
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.
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.
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.
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
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
$ 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
See and edit everything Humfrid knows. Your data stays in your workspace and is never used to train a model.
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
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.
Share the bet and the documents he needs, and give him access to the systems the work already lives in. He starts in Slack.
Your data stays yours. We don't train on it, we don't sell it, and you can leave with everything anytime.
Humfrid is the agent that helps your product org find the most impactful bets and stick to them.