FAQ
Six founder questions. Honest answers.
The objections a 10–200-person team founder actually has before joining the waitlist — written plainly, in the order we hear them, with no marketing fluff. Each one ends with a pointer to where the full answer or the install lives.
What founders ask
The six real questions.
Written in the same order we hear them on intro calls — anonymity first, pricing last.
When a pulse opens, the system assigns every active teammate a fresh random handle for that window — something like otter-7. There is no map from that handle back to a person, on purpose. The handle changes every pulse window, so the person behind yesterday's otter-7 may be a different person next week. What reaches the model is per-team aggregate buckets — not the handle, not the response, not any identifier a third party could pivot on.
No. Aggregates go in, raw responses stay out. The model is scoped to team-level signals: an aggregate sentiment score per team per day, the distribution of response buckets, and the pulse question text itself. It never sees the response a teammate typed, never sees a name, never sees a channel-side user ID.
We instruct the model that raw responses are never available, and we never ship a feature that would require them. This is the principle the rest of the product bends to, not a setting you have to remember to flip.
Their handle simply stops rotating in. Pulse counts drop into the denominator cleanly, aggregate trends keep rendering, and there is no offboarding checklist for you on the data side — there was no map from a handle to a person in the first place, so there is nothing to delete. The retention window for raw response text is 14 days; metadata is 90 days; aggregates are indefinite, in aggregate form only.
Slack ships on day one of early access. Microsoft Teams follows in the first 90-day cohort and is included in Growth at no extra license — same product, native Teams app, no connector SKU, no double-billing. Pick both at install if your org straddles Slack and Teams; the dashboard unifies the view either way.
The short version: TinyPulse and Culture Amp were built for the mid-market engagement-survey cycle — quarterly reports, a portal nobody opens, and a sales motion. Moodkin was built for the under-200 remote-first weekly pulse — native in Slack and Teams, anonymous at ingest (not as a toggle), and one concrete manager ask per day. You can see the side-by-side on every row founders actually compare on.
One number: less than $5 per seat per month. There are three plans — Free up to 10 people, Team up to 50, Growth up to 200 — but every plan ships the full pulse + sentiment + nudge loop. Higher tiers add multi-team rollups, identity, and audit trail. Early-access teams get the founder rate locked for the first year. No annual contract, no setup fee, no five-figure floor.
Yes — the full privacy page walks through what lands in our database, what gets sent to the model, what the retention windows are, and what the rotating-handle mechanism looks like in practice. Read it once before you decide.
Three of these point to /pricing — one to /compare — and the rest back to the early-access form. We keep the marketing surface small on purpose: every answer lives somewhere you can return to.
Early access
Still have a question?
Drop your work email below and we'll send the install playbook and book the 30-minute kickoff. Founder rate is locked for the first year.
We'll only email you about early access. No newsletter, no drip campaign.
Want the full picture
See the pulse run on your own team.
Drop your work email below and we'll send the install playbook and book the 30-minute kickoff. Founder rate is locked for the first year for every early-access team.
Join the Moodkin waitlist