Kibu is the kind of startup most people miss because the market does not announce itself in startup language.
It is not a general AI tool. It is not a creator platform. It is not a developer product. It is software for organizations serving people with intellectual and developmental disabilities - I/DD providers - where the daily work is split between care, programming, documentation, compliance, billing, and staff coordination.
That is exactly why it is interesting.
The best vertical SaaS companies usually look boring from the outside and obvious from the inside. Once you see the workflow, the pain is not subtle. Direct Support Professionals need to spend time with people, not reconstruct notes at the end of the day. Administrators need clean records for audits and reimbursement. Providers need age-appropriate programming, not a folder of random worksheets. Families want to know what happened. Regulators want proof.
Kibu’s bet is that all of those jobs belong closer together than the old software stack allowed.
The wedge: content before compliance
Most healthcare-ish software sells to administrators first. Kibu’s unusual move was that the wedge was not only documentation. It was meaningful, age-appropriate content for adults and teens with I/DD, paired with tools that eventually made the documentation easier too.
That order matters.
If you start with compliance software, the frontline staff experience can become an afterthought. If you start with content and daily programming, you see the actual work before you design the record of the work.
Kibu’s current product now includes documentation, Electronic Visit Verification, billing integrations, eMAR, medication tracking, time tracking, goal tracking, AI note support, AI report generation, and a content library. But the buyer-facing promise is simpler: help disability providers spend less time on paperwork and more time supporting people.
The content side gives staff something useful to do with participants. The documentation side turns the work into clean records. That combination is the wedge.
Kibu’s own product copy frames the gap clearly: most platforms were built around administrative functions, while Kibu was built around the daily service experience. Its “What Makes Kibu Different” page says the company combines curriculum and documentation because, in many agencies, curriculum and records live in separate systems, notebooks, apps, or paper forms.
That is not a feature checklist. It is a workflow thesis.
How the first customers actually showed up
The origin story is unusually physical for a software company. Kibu’s own story page says it started with dodgeball. Daniel Caridi has repeatedly described the beginning as a small gym in Connecticut with five people and a dodgeball; the company later became a platform serving disability providers across the country.
The exact legal timeline is slightly messy. Caridi’s public profiles describe Kibu as starting in 2019. TrustMRR lists the company as founded in January 2022. The cleanest way to read that is that the program and founder-market learning began earlier, while the current revenue-tracked software company appears later.
That distinction is useful, not confusing. Kibu did not begin as “we should build an EHR.” It began close to the people and providers the software would later serve.
The early distribution also seems to have mixed community presence with public media. Customer-story pages show providers discovering Kibu through events, media, and word of mouth. The Arc Caddo-Bossier story, for example, says the organization first learned about Kibu through Good Morning America coverage of Billy Blanks Jr.’s accessible fitness work. Other customer stories show Kibu adapting content to provider requests and becoming part of day-program routines.
That is not a generic SaaS funnel. It is category trust: show up in the community, prove the content is dignified and useful, then earn the right to touch documentation and compliance.
The growth machine
Kibu’s growth machine has three loops.
1. The frontline adoption loop
The people who feel the pain are Direct Support Professionals and program staff. If the software makes their day harder, the sale dies after implementation. If it makes documentation, activities, and reports easier, the product spreads inside the organization.
Kibu’s customer stories repeatedly point to staff-level relief: faster notes, fewer spreadsheets, easier program planning, and content that feels appropriate for adults rather than childish. The Family Resource Associates story is especially useful because it shows the wedge clearly. A new state documentation requirement made spreadsheets untenable; Kibu handled documentation while also giving staff content participants actually wanted to use.
That is the strongest kind of vertical SaaS proof. The product does not just satisfy an executive requirement. It removes a daily irritation for the people who can make or break adoption.
2. The compliance expansion loop
Once Kibu is in a provider organization for content or documentation, it can expand toward the adjacent systems that make administrators care: EVV, billing, eMAR, ISP goal tracking, state forms, audit-ready reports, and role-based permissions.
The logic is straightforward. A provider organization does not want more tools. It wants fewer places where compliance can fall apart.
Kibu’s documentation suite includes AI-assisted note writing through Magic Pen and AI-powered report generation through Clara. The important part is not “AI” by itself. The important part is where AI sits: inside a compliance-heavy workflow where staff already have to turn messy human activity into structured records.
That is a much better AI use case than a generic writing assistant. It has a narrow context, a clear output, a buyer who cares about time saved, and a compliance reason to keep improving accuracy.
3. The provider-community loop
Kibu’s market is relationship-driven. Providers attend conferences, know peer organizations, follow state-level policy changes, and care about what similar agencies are using.
That makes visible customer proof unusually valuable. ANCOR says Kibu already serves more than 40 ANCOR members across 18 states. Kibu’s own documentation page lists named organizations and testimonials. Kibu’s 2025 year-in-review says the team attended 14 conferences across 11 states, and Kibu’s PR around Daniel Caridi’s Forbes 30 Under 30 recognition says the company partnered with more than 250 disability providers in nearly all 50 states.
Those numbers do not all measure the same thing, but together they show the channel: trade associations, conferences, customer stories, and provider-to-provider trust.
For a vertical SaaS company, that can be more durable than paid acquisition. A broad ad campaign can create leads. A provider hearing from another provider can change a shortlist.
The numbers, stated carefully
TrustMRR lists Kibu with about $234,000 in MRR, 375 active subscriptions, roughly $200,000 in trailing-30-day revenue, and about $3.1 million in all-time revenue. The important caveat is that the Stripe API key had expired when the page was checked; the data was last updated April 19, 2026.
That still makes the figure useful, but not live.
The revenue signal is supported by Caridi’s own public profile language, which says Kibu is over $2 million ARR, and by public expansion claims from Kibu and ANCOR: hundreds of providers, nearly all states according to Kibu PR, and more than 40 ANCOR members across 18 states according to ANCOR.
The subscription count is especially interesting. If Kibu is doing about $234,000 in MRR across 375 subscriptions, the blended monthly revenue per subscription is around $625. That is not consumer SaaS. It is not enterprise mega-contract SaaS either. It sits in the middle: high enough to support hands-on implementation and customer success, low enough that a provider can justify it without a year-long procurement process.
That middle zone is where many strong vertical SaaS companies live.
Framework read: what passes, what does not
Pain: very strong. Documentation, billing, compliance, staff burnout, and program planning are recurring operational pains for disability providers.
Buyer: clear. Provider executives and administrators buy, but DSP adoption matters. Kibu’s advantage is that it appears to serve both sides: admin records and frontline ease.
Market: narrower than horizontal SaaS, but better than it looks. I/DD providers are numerous, compliance-heavy, and relationship-driven. This is not a market where every customer acts alone.
Behavior change: moderate to high. Providers may be replacing spreadsheets, legacy EHRs, paper records, or separate curriculum tools. Implementation matters. Kibu reduces this risk by making the frontline interface simple and by selling a workflow, not just a database.
Distribution: strong for the category. Conferences, association partnerships, customer stories, media, and provider referrals are credible channels in a market where trust matters more than ad polish.
Unit economics: likely better than low-ticket SaaS, but implementation load is the watch item. If every customer needs heavy customization, margins can suffer. If Kibu’s templates and state-aware workflows scale, the model becomes much stronger.
Moat: workflow specificity. A generic EHR can copy features. It is harder to copy the content library, provider relationships, state-specific documentation behavior, and the product intuition that comes from staying close to the actual service environment.
The result is a strong vertical SaaS profile. Kibu is not impressive because the market is glamorous. It is impressive because the market is specific, painful, and underserved.
What you can steal
Steal the “start close to the work” principle. Kibu’s advantage comes from understanding the gym floor, day program, DSP workflow, and audit file before turning those into software. You cannot spreadsheet your way into that insight from the outside.
Steal the content-plus-compliance wedge. A pure compliance product can feel like surveillance. A pure content product can feel nice but nonessential. Kibu becomes stronger by connecting activity to documentation, engagement to records, and staff relief to executive ROI.
Steal the narrow AI placement. Magic Pen and Clara work as a lesson because they are not generic AI wrappers. They sit inside a painful, repetitive, high-context workflow where the buyer already understands the cost of bad notes and slow reports.
Steal the community distribution model. In a trust-based vertical, conferences, associations, named customer stories, and public proof inside the category matter more than broad startup attention.
What you cannot steal is the category trust. You do not get to sell into disability services with generic SaaS language and expect people to believe you. Kibu’s best evidence is not a growth hack. It is proximity.
That is the transferable thesis: if you want a durable vertical SaaS business, do not start by asking where AI can be inserted. Start by finding a room where the work is important, the software is bad, and the people doing the work can tell you exactly where the day breaks.
Sources
Company and founder sources:
- Kibu Our Story - origin framing around the dodgeball program.
- Kibu Documentation Suite - product surface, Magic Pen, Clara, EVV, billing, eMAR, security, and customer logos/testimonials.
- Kibu Content - content and activity product positioning.
- Kibu: What Makes Kibu Different - workflow thesis, curriculum-plus-documentation positioning, 500+ lessons, and provider roles.
- Kibu Year in Review 2025 - 2025 product releases, conference activity, Forbes recognition, and nearly-all-50-states expansion language.
- Customer Stories: Family Resource Associates - documentation pain, implementation speed, staff workflow, and Clara use case.
- Customer Stories: The Arc Caddo-Bossier - media-driven discovery, content requests, and daily program adoption.
Third-party and tracker sources:
- TrustMRR - Kibu - MRR, active subscriptions, all-time revenue, founder, and data-last-updated caveat.
- TrustMRR - Daniel Caridi founder page - founder-linked verified revenue rollup.
- ANCOR partner profile: Kibu - association-level validation, over 40 ANCOR members across 18 states, and platform positioning for I/DD providers.
- PRNewswire: Kibu CEO Daniel Caridi named to Forbes 30 Under 30 - Forbes recognition, provider count, nearly-all-50-states claim, and product summary.
- ABC News / Good Morning America segment - accessible fitness/media context referenced by customer discovery stories.
- People profile of Billy Blanks Jr. and Kibu - independent coverage of the accessible fitness layer that helped Kibu gain early visibility.
Note on gaps: Kibu has unusually good customer-story and category evidence, but less public financial history than Rezi or Postiz. The TrustMRR revenue snapshot is useful but not live because the Stripe API key had expired as of April 19, 2026. Treat current revenue as “at least recently verified,” not real-time.