HelpKit
Publish a customer help center from articles written in Notion.
Business overview
Public positioningPublish a customer help center from articles written in Notion. Official page checked 2026-10-19 describes Dominik personally running HelpKit without a customer-success team. The 2022 milestone describes his transition to full-time indie work; headcount is self-described.
How it makes money
Monthly/yearly subscriptions and optional AI chatbot add-on.
Business breakdown
Researched Oct 19, 2026Source-linked product facts, followed by MRRTrace analysis of the customer problem, workflow, trade-offs and questions to test.
The customer problem
A small software company may already write internal notes in Notion but still need a clear public help center. Maintaining a second editor creates duplicated work. Analysis: the buying decision is whether a publishing layer saves enough support and maintenance effort to justify another subscription.
Core workflow
- Write and maintain support articles inside the team's existing Notion workspace, keeping the editorial task close to product work.
- Publish those articles through HelpKit as a customer-facing knowledge base with search and a more suitable reading interface.
- Review customer questions and improve the documentation; evaluate the optional AI add-on only after the underlying answers are dependable.
What customers pay for
Analysis: track successful self-service answers and time required to update documentation, rather than counting published pages alone. These are proposed evaluation measures, not measured HelpKit outcomes.
Distribution signals
Observed channels and entry points; their performance is not inferred.
- Founder visibility and direct customer contact
The founder publicly shared the 2022 milestone and described handling customer meetings. This establishes an accessible founder narrative, but does not quantify how many customers the channel acquired.
Evidence
Trade-offs
- Analysis: depending on Notion can reduce editor-building work while exposing the business to upstream publishing and integration changes.
- Analysis: personal support can improve learning, but interruptions and specialist customer requests may constrain a solo operator.
Open questions
- Which recurring customer questions could a searchable article answer without a support conversation?
- Would customers pay for a polished publishing layer, or are their requirements already met by simpler Notion sharing?
A MRRTrace reading of public product material. Trade-offs and questions are editorial analysis.
Revenue evidence
founder-disclosed- Reporting period
- Historical MRR milestone disclosed June 16, 2022
- Figure as of
- Jun 16, 2022
- Reporting method
- founder-disclosed
- Source checked
- Oct 19, 2026
Founder milestone with more than 130 paying customers. Historical subscription run rate; not current revenue, profit or independently verified receipts. The income source uses $ without an explicit currency code; preserved as Unspecified $ and excluded from USD comparisons.
Dominik Sobe founder disclosure, 16 June 2022Pricing
Pricing pageMonthly and annual help-center plans, with optional AI add-on; see current pricing
The source page may change its prices, limits, or offer after the recorded check date.
What founders can learn
Editorial notesA narrow documentation layer around an existing writing tool; study support workflow and personal onboarding rather than building a broad CMS.
These are MRRTrace observations, not statements by the founder or proof of a repeatable outcome.
Source material
4 sources- HelpKit official website Public source · Checked Oct 19, 2026
- Founder income disclosure Public source · Checked Oct 19, 2026
- Official product and pricing Public source · Checked Oct 19, 2026
- Official solo-operator statement Public source · Checked Oct 19, 2026