Loading page…
Healthcare transportation billing and scheduling software shortens payment cycles and coordinates Medicaid rides.
About 100 employees across three countries
In a fragmented healthcare niche, one customer can reveal the workflow, but six months building only for that customer can still produce the wrong product.
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
Kinetik sells an end-to-end platform for non-emergency medical transportation. Its revenue-cycle product helps local transport providers submit insurance claims, while its scheduling product lets health plans and health systems arrange rides for members. Founder Sofia described an industry handling roughly 400 million rides a year across about 20,000 transport providers. The initial insight came from a provider still managing rides and billing through paper and sprawling spreadsheets, with insurers taking about 60 days to pay. Three cofounders spent time inside transport offices, built integrations with dispatch systems and clearinghouses, and automated claim generation. Kinetik says its workflow cut payment time to 21 days and reduced a 40-hour process to 30 minutes. After COVID disrupted ride volume, the company expanded from billing into scheduling, shifting from a narrower payments product toward a broader infrastructure platform. Sofia said Kinetik was approaching eight figures in ARR and had about 100 employees across the United States, Bangladesh, and Serbia. Those figures are founder-reported.
For a healthcare workflow product sold to small transportation operators, start where dispatch, billing, and reimbursement already collide: in the provider’s back office. Map one week of ride completion, claim preparation, denial handling, and payment follow-up with the owner and the staff doing the work.
The quick-reference card — acquisition channels, replication playbook, risks & traps, and our verdict — is members-only.
Join the Unicorn Club — $5/moCancel anytime, in one clickPaste into Claude Code / Codex and get a working version of this product end-to-end.
Two production-grade prompts per idea — a full build spec and an SEO growth plan — plus 10 tailored build specs a week. Members only.
Join the Unicorn Club — $5/moCancel anytime, in one clickEvery claim traces back to a listed source — open any of them and check the number yourself.
Data credibility: The cofounder reported approaching eight figures in ARR, about 100 employees across three countries, and specific customer and workflow metrics in an interview. No dashboard, filing, or third-party verification was cited; figures are unaudited founder reports.
A first dollar in this category should follow a measurable improvement to billing operations, not a broad promise to modernize healthcare. Start with a provider whose claims can be traced from completed ride to payer response.
For Kinetik, a useful growth loop comes from making each completed ride produce cleaner billing data and making each new provider improve the reliability of the operating workflow.
A healthcare platform founder can face long periods when customers are too busy, cautious, or disrupted to provide clear signals. Kinetik encountered an extreme version when COVID sharply reduced transportation activity just as the team was preparing to scale billing sales.
Kinetik combines two workflow layers in non-emergency medical transportation. The revenue-cycle management side serves transport companies: it connects dispatch information to insurance billing so completed rides can generate claims without manual re-entry. The scheduling side serves health plans and health systems, allowing coordinators to book rides for members and select an appropriate mode of transport. The platform sits between patients, payers, brokers, and local transport providers, where operational handoffs create delays and data errors. The initial product integrated with dispatch products and payer-clearinghouse infrastructure. The founder said a process that had taken 40 hours could be completed in 30 minutes, and payment time moved from 60 days to 21 days for users of the system. These are reported outcomes, not independently audited measures. The product’s complexity is not just software: customer onboarding requires understanding local provider operations, payer rules, integrations, and responsibility across a multi-sided network. That creates defensibility when the implementation knowledge is converted into repeatable workflows, but also makes the product harder to build and support than a generic billing dashboard.
Kinetik charges transportation companies for its revenue-cycle management platform and sells a scheduling platform to health plans and health systems. That two-sided customer base gives the company access to both the supply side of rides and the organizations arranging member transportation. The transcript does not specify contract sizes, pricing units, gross margin, or revenue split between products, so those economics should not be inferred from the ARR figure. For a founder evaluating this model, the key commercial choice is whether to price per provider location, claim volume, or software seat while keeping payer-side contracts distinct. Provider pricing should reflect the labor and financing benefits created by faster, cleaner reimbursement. Health plan pricing can be tied to workflow coverage and operational outcomes, but procurement and implementation cycles may be longer. Avoid hiding support and integration work inside a flat subscription: measure onboarding hours, ongoing exception handling, and usage by account. The company’s reported approach demonstrates that a niche vertical can support multiple paid workflows when each buyer sees a separate operational benefit.
This is an integration-heavy healthcare software business with meaningful labor and compliance costs. The transcript describes a three-person founding team, an 18-month initial build, dispatch integrations, payer connections, and early spending of about $80,000 in the first six months, followed by additional founder investment. It also describes a later product expansion and a team of about 100 across three countries. No detailed infrastructure stack, cloud bill, gross margin, or compliance-cost breakdown is given, so a founder should model those separately rather than extrapolate from revenue. Budget for secure handling of sensitive health and ride data, reliability, integration maintenance, implementation staff, and support for low-tech local operators. Clearinghouse and payer connectivity can create partner costs and operational dependencies. The best path to healthier margins is to standardize integrations, automate exception queues, and build onboarding checklists around provider size and dispatch system. Keep custom work explicitly scoped; otherwise a high-touch sales model can consume the subscription economics. Validate unit economics by cohort, including time to launch and support load after the first few billing cycles.
Copy the field research, the focus on an expensive recurring workflow, and the translation of product value into the customer’s own cash-flow language. Kinetik’s founders spent time inside transport companies and learned how rides, claims, and payments actually moved before building a more standardized product. The caution is equally useful: the team said it spent six months with one customer and built the wrong customized product. Interview a dozen operators before committing to architecture, compare their dispatch and billing processes, and identify the smallest common workflow. Then sell a pilot around one measurable result such as claim preparation time or reimbursement delay. Change the approach by making integration scope and success criteria explicit from the first agreement. Do not start by attempting a full payer-provider network; earn trust on a narrow use case and expand only when usage and renewals support it. This pattern fits founders with healthcare operations access, patience for enterprise and SMB complexity, and the ability to sell in person. It is a poor fit for someone seeking a quick, self-serve launch.
Kinetik’s main risks come from healthcare complexity and its dependence on coordinated behavior across several parties. Payer rules and integrations can change, providers may resist new workflows, and small operators can have limited capacity for implementation. If a transport company cannot reliably map completed rides to claims, the software may inherit messy source data rather than eliminate it. A scheduling platform also depends on health plans and transport networks having accurate availability and member information. COVID illustrated an additional exposure: ride volume can fall sharply when the underlying service market is disrupted. Rapid expansion into adjacent products can dilute engineering and sales focus, especially when the original segment is still being standardized. A founder should track retention, onboarding time, claim acceptance, days to payment, and support burden by customer cohort. Build a narrow, repeatable integration path and ensure the product can create value for one side of the network without waiting for universal adoption. The revenue and customer figures in the interview are founder-reported; they are not independent proof of margins or long-term retention.
The four founder playbooks — first customers, first dollar, the flywheel, the silent stretch — are in the Unicorn Club, on this idea and on all 1,403 others. The story, the numbers, the sources and every later section stay open to everyone.
Join the Unicorn Club — $5/moCancel anytime, in one click