For founders of small teams

Stop being the nag. Keep the loops closed.

Humfrid tracks open promises, briefs you in the morning, and follows up so you don’t have to. You pick the channels. You approve the nudges.

Free credits to start · Channel-level Slack control · No credit card

At 20 people you still hold the company in your head.

What you can’t hold: every soft promise. The invoice waiting on approval. The “I’ll own the migration” that two people both thought the other meant. Being the human follow-up machine is the part of the job that burns you out.

I handled most of the follow-ups. Here’s what still needs you.

Not another feed of work. A short list of open loops that actually need a founder call — and a trail of the ones Humfrid already closed or nudged (with your okay).

Works with the tools you already use

Start here

The wedge for small teams: follow-ups and the morning brief.

Company-wide “brain” stories are for when you can’t hold the org in your head anymore. Until then, earn the seat by closing loops and clearing your morning.

Waiting on others

Open loops that don’t die quietly.

The contractor invoice nobody approved. The customer promise from a call that never became a ticket. The two engineers who both think the other owns the migration. Humfrid tracks them — and follows up so you don’t have to be the nag.

  • Soft nudges with the original ask attached
  • You choose whether to send, edit, or escalate
  • Works in a 12-person Slack as well as a bigger one

Morning brief

What moved overnight — before the stand-up scramble.

Not five tabs to reconstruct the night. One short brief: what advanced, what’s stuck, and what still needs a human call. Built for the founder who still holds most of the company in their head — and hates rediscovering it every morning.

  • Goals and commits that moved
  • Promises that slipped
  • One decision that needs you — not twenty that don’t

Capture

That thing said on a call? It doesn’t vanish.

Customer said they’d send the data room Friday. You said you’d intro them to eng. Neither became a ticket. Humfrid catches commitments from the channels and docs you connect — so “we’ll do that” doesn’t die in the call notes.

  • Pulls promises out of Slack and meetings
  • Links them to the person who said them
  • Surfaces them before the customer asks again

Built for the room where Maya sits ten feet away

Not a surveillance bot. A draft you control.

You see it first

Follow-ups land in your DM as drafts. Send as you, send as Humfrid, edit, or drop. Nothing public by default.

Channels you choose

Comp, board prep, and “we need to let someone go” stay out unless you invite him into that channel.

Calendar is a setting

Default: propose the invite. Autonomous booking only if you turn it on. No surprise “you already booked it?”

Where he works

Lives in Slack. Asks before he acts.

Same coworker fantasy — without the creepy autonomy.

How it works

Understands what you connected. Delivers what matters.

01

Watches the channels you allow

Only the Slack channels, docs, and tools you connect — not the whole company by accident.

02

Tracks the open loops

Commitments, ownership fog, and slipped dates — compared to what you said mattered.

03

Proactive and personalized

Briefs and draft nudges to you first. Public or teammate-facing only when you say so.

When you grow into it

Org-wide brain is a scale story. It’s here when you need it — not the reason to start.

When two workstreams pull opposite ways

Same-day fork detection across teams. Useful when you can’t hold every thread in your head anymore — usually past ~50–80 people.

Company brain that compounds

Goals, decisions, and learnings that stay searchable. The longer you’re on Humfrid, the less you re-litigate “why did we decide that?”

Signal for every seat

Proactive and personalized briefs for each person — not just the founder — when the team is too big for you to be the human router.

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

Group Product Manager

“Cuts through noise. I only see what still needs a human.”

Founder · product team

“The follow-ups alone paid for it. I stopped being the nag.”

CEO · 18-person startup

We’re honest: a lot of “company brain” love comes from bigger orgs. The follow-up wedge is what small teams feel on day one.

Trust

Scary permissions, spelled out.

At your size, Slack holds board prep and hard HR threads. Humfrid only sees what you invite him into.

  • Channel-level Slack control — not whole-workspace-or-nothing
  • Nudge approval — you send, edit, or drop before anyone else sees it
  • Calendar writes are opt-in — draft by default
  • SOC 2 Type II infrastructure · encryption in transit and at rest
  • Not used to train third-party foundation models on your workspace
  • Disconnect and delete anytime · Security · DPA

Pricing

Clear numbers. No “from $49” mystery.

You weren’t about to hire a $150k chief of staff. You might hire a 21st engineer or an ops generalist who does follow-ups plus recruiting and vendors. Humfrid isn’t that person — it’s the slice that closes loops so that hire (or you) isn’t buried in nagging.

Build

$49/mo

1 person · usage credits included

  • Morning brief + follow-ups
  • Channel-scoped Slack
  • Free credits to start
Get started for free

Grow

$149/mo

Up to 5 people · most small teams start here

  • Everything in Build
  • Higher usage allowance
  • Priority support
Get started for free

Scale

$899/mo

Up to 10 people

  • Everything in Grow
  • Higher usage allowance
  • Onboarding help
Talk to us for 10+

Annual billing saves ~17%. Free trial credits first — prove follow-ups in a few days before you care about a plan.

Questions from founders our size

I’m 20 people. Do I actually need this?

If open loops and follow-ups are already eating your week, yes — that’s the wedge. You probably don’t need “org-wide fork detection” yet. Start with follow-ups and the morning brief; grow into the rest.

What does pricing actually mean at our size?

Build is $49/month for one person. Grow is $149/month for up to 5 people. Scale is $899/month for up to 10. Larger teams: talk to us. Free credits to start — you can try before you pick a plan.

Which Slack channels can he see?

Only the channels and DMs you explicitly allow. Channel-level control is the default — not “whole workspace or nothing.” Comp, board, and sensitive HR threads stay out unless you invite him in.

Will this feel like surveillance to my team?

Nudges are designed to go to you first. You choose send / edit / don’t send. We’re not dropping public @-mentions that make someone feel watched from ten feet away — unless you ask for that.

Can he book my calendar by himself?

Not without permission. Calendar writes are opt-in. Draft invite first is the default; autonomous booking is a setting you turn on, not a surprise in a screenshot.

How is this different from ChatGPT?

ChatGPT starts from zero every chat. Humfrid keeps the open loops, commitments, and goals across days — so Monday’s brief knows what slipped Friday.

SOC 2? Where’s our data?

We run on SOC 2 Type II infrastructure (see our security and DPA pages). Your data isn’t used to train someone else’s model. Disconnect and delete anytime.

What if we leave?

Export and delete. No hostage data.

Give it four days on follow-ups.

Connect one or two channels. Let the morning brief and open-loop tracking earn the seat. If they don’t, leave — no hostage data.