Introducing Humfrid: every product team's favorite agent
Humfrid is the Slack-native product ops agent that tracks goals, sharpens thinking, and keeps product teams aligned. Here's what he does and how to start.
Introducing Humfrid: every product team’s favorite agent
Humfrid is a product ops agent that lives in Slack with your team. You give him your goals. He watches metrics, remembers decisions, and shows up in the channel when something drifts, with a clear next step and the evidence behind it. He also DMs you as a thinking partner when you are about to bet a quarter on a weak idea.
That is the short answer to “what is Humfrid.” The longer one is for product teams who are tired of tools that only produce more output, and want an agent who cares whether the work ladders to the goal.
Who Humfrid is for
Humfrid is for product managers, founders, and product ops people who already run the work in Slack: roadmap debates, metric drops, customer quotes, “are we still doing X?” threads. If your team lives in Linear and GitHub but the real decisions still happen in channels and DMs, Humfrid sits where those decisions actually form.
He is also for teams that use coding agents. When an engineer asks Humfrid for context over MCP, they get the goal, the customer evidence, and the metric to move, not a half-remembered Slack scroll. What ships matches what you meant to build.
If you want a chat box that drafts tickets on demand and forgets them, this is not that. Humfrid is closer to a senior product ops person who never stops watching the quarter.
A quick note on the name
If you knew us as Humfrid, same company, same product spine. Humfrid is the face of that product: the agent product teams actually talk to, while the underlying graph of goals, decisions, and memory still powers every turn.
What Humfrid does: three jobs
The product site puts it plainly. Humfrid tracks goals. He sharpens thinking. He keeps everyone aligned. Those are not three slogans. They are three loops you can see in Slack.
1. Humfrid tracks your goals
You set an objective and the metrics that prove it. Humfrid keeps reading them after the planning meeting ends.
When activation drops 6% after a longer signup, he says so in the channel, names the likely cause, and offers a leaner flow draft. When checkout v2 has been live nine days with flat conversion and rising refunds, he reports how the bet actually landed. When the team is quietly 8% behind a quarterly goal, he surfaces the gap and a plan to close it.
Most tools wait for you to open a dashboard. Humfrid treats “watching the last bet while you start the next one” as the job. Goals stay connected to live work, not to a slide from last Monday.
2. Humfrid sharpens your thinking
Before a customer call, he can gather what you already know and draft questions for what you do not. After dozens of calls land in memory, he helps you back a decision with the exact quotes, not a vague sense that “users want dashboards.”
He also pushes back. Two support tickets are not a trend. A wish is not evidence. A bet you already lost once should not get a quiet second chance without someone saying so. Agreeable agents produce more text. Humfrid holds ideas to the standard your best PM would, before you spend the quarter.
When you are about to jump into building, he can force the simple questions: who is it for, what problem are we solving, how will we know it worked? That pause is the product. Output volume is easy. Output quality is the scarce thing.
3. Humfrid keeps teams aligned
Product work breaks when two groups plan opposite things in different channels. You made a flow free last week; growth scopes a paywall on the same flow. Humfrid notices the conflict and asks for a five-minute sync before both ship.
Alignment also means the coding agent gets the same brief as the PM. Via MCP, Humfrid hands over the assigned task, the feedback from customer calls, and the activation target. The engineer does not rebuild context from scratch. The team does not re-litigate a decision that was already made.
Under the hood, that only works because goals, decisions, evidence, and work share one memory. Without shared memory, every agent and every human is a silo with a confident take. With it, the status of the work is the same picture for everyone.
A day with Humfrid (what you actually see)
Morning: a metric moved overnight. Humfrid posts in the product channel before standup, with the delta, the likely cause from recent changes, and one proposed next step. You accept, edit, or ignore. Either way, the quarter’s goal stays in view.
Midday: you have a customer call. Humfrid DMs a short brief from past notes on that account, plus questions that test the hypothesis you care about this week. After the call, the useful quotes land in memory, tagged to the goal they inform.
Afternoon: engineering picks up a task. Through MCP, Humfrid answers with the objective, the activation target, and the research that scoped the work. Nobody pastes a 40-message Slack thread into the editor.
End of day: two teams almost shipped opposite plans. Humfrid flagged the conflict at 9am. The sync took five minutes. The wrong ship did not leave the dock.
None of that is magic. It is goal memory, evidence, and alignment applied where product teams already work.
What Humfrid is not
Humfrid does not decide strategy for you. He will assemble options, flag weak evidence, and name contradictions. You still choose the market, the segment, and the irreversible calls.
He does not silently ship irreversible changes. Meaningful moves stay in review. He proposes; people commit.
He does not replace your judgment about what to build. He returns the hours you spend reassembling context, chasing metric drift, and re-explaining the “why” in every channel.
We only claim what we can demo without flinching: goal tracking tied to work, evidence-backed pushback in Slack and DMs, conflict flags across teams, and context handoff to coding agents through the same graph.
How to start
- Add Humfrid to Slack (free to start, no credit card).
- Point him at the goals and metrics that define this quarter.
- Invite him into the channels where product actually decides.
- When you want a walkthrough, book a demo.
For how the loops work end to end, read How it works. For plans, see Pricing. If you want the broader category, start with What is a PM agent? and AI agents for product teams.
The bottom line
Humfrid is every product team’s favorite agent because he does the unglamorous work that keeps product creative: he remembers the goal, he challenges the weak bet, and he stops two channels from shipping opposite plans. He lives where your team already talks. He writes back to the same memory your agents and humans share.
Give him your goals. See if the quarter gets quieter, and clearer.
Make your product team AI-native
Humfrid gives your product team superpowers — just add it to Slack, and it will start working alongside you to reach your product goals.