Docplanner

1.1 Identity and business model

Docplanner began in Poland in 2012 as an online doctor-appointment booking platform and has expanded into a two-sided healthcare marketplace plus software provider for clinicians and clinics. Bloomberg describes the company as connecting 100 million monthly users with 2.8 million medical professionals in January 2026, while Docplanner's own site reports 25 million appointments booked last month, 100 million monthly patient visits, and 300,000 active doctors. Those company figures use different populations and denominators from Bloomberg's reported user and professional counts, so they should not be treated as directly interchangeable. The product model combines patient discovery, reviews and booking with provider tools for scheduling, patient flow, online presence and clinic operations. Current headquarters reporting is inconsistent: historical and financial sources place the operating center in Warsaw, while a 2026 third-party profile places headquarters in Amsterdam. The company remains privately held and current revenue, ARR and customer-account counts are not independently disclosed in the assigned evidence.[CO001, CO002, CO003, CO004, CO005]

1.2 Leadership, founders and governance

Mariusz Gralewski is identified as Docplanner's founder and chief executive in Bloomberg's January 2026 interview and in the 2019 financing announcement. The assigned evidence names him consistently but does not provide a complete current executive roster, board composition, voting arrangements or succession plan. The 2019 One Peak announcement described a team of more than 1,000 employees, whereas the same source's company description referred to a team of 300, illustrating why headcount should be dated and source-qualified rather than carried forward as a single current number. Docplanner's own careers page confirms active functions spanning marketing and public relations, customer success and sales, IT, product and data, finance and administration, and human resources, but it does not establish leadership incumbents. Key-person dependence on Gralewski is therefore material for diligence, while formal governance and management depth remain open questions.[CO006, CO007, CO008]

1.3 Funding, valuation and milestones

Docplanner's financing history is well documented through its 2013-2019 rounds in the assigned sources, although totals and currency conversions vary by database. TechCrunch reports a 2016 $20 million Series C that brought total raised to $34 million; One Peak reports a €80 million Series E in May 2019 that brought total raised to approximately €130 million. Multiples.vc reports a Series F valuation of $1 billion in September 2021 but gives conflicting round and total-raise figures elsewhere on the same page. Bloomberg's January 2026 report says the company is considering a public listing and an AI strategy, but does not establish a completed 2026 financing or current valuation. The milestone record therefore supports historical expansion, acquisitions, product development and scale, while current equity terms, debt covenants, liquidation preferences, secondary transactions and a fully comparable current valuation remain unresolved.[CO009, CO010, CO011, CO012, CO013, CO016]

1.4 Exhibits

2.1 Market boundary and economic model

Docplanner's addressable market is not one homogeneous healthcare software category. The observable boundary includes patient-facing discovery, reviews and appointment booking, plus paid practice-management software for providers. The provider side includes scheduling, patient-flow management, reminders, online presence, documentation and related workflow functions; the integration guide shows that third-party medical software providers can synchronize appointment slots and bookings through a REST API. The company therefore sells into provider operating budgets while creating patient demand on a marketplace. The included spend is provider software and demand-generation spend tied to booking and workflow; excluded spend includes clinical care, insurance reimbursement, general-purpose hospital information systems and consumer health activity unrelated to provider acquisition or scheduling. Status-quo substitutes are phone-based scheduling, manual administrative work, provider-owned websites, local directories and internally built practice software. This boundary matters because marketplace reach and SaaS monetization are related but not interchangeable units.[CM001, CM002, CM003, CM004]

2.2 Sizing lenses and adoption drivers

The available evidence supports a triangulated sizing approach rather than a single TAM assertion. A historical supply-and-demand lens reports 20 million patients and 325,000 monthly bookings in 2019, while later secondary pages report materially larger platform activity and a 2026 ARR estimate; these figures are not directly comparable because their dates, definitions and issuer quality differ. A provider-workflow lens is supported by the company's stated SaaS use cases and by the API's restricted access for medical software providers, indicating a workflow-integration market rather than only a listing marketplace. Geographic expansion and acquisitions can widen the reachable market, while local brands, healthcare trust, compliance, switching costs and integration authorization constrain the rate at which nominal demand becomes paid revenue. The 2019 financing announcement explicitly tied proceeds to continued penetration in Europe and Latin America, product development, hiring and potential acquisitions; that is evidence of the intended growth vector, not proof of market size or unit economics.[CM005, CM006, CM007, CM008, CM009, CM011, CM014, CM015, CM016]

2.3 Buyers, adoption path, and unresolved sizing

The principal paying customer is a healthcare professional, clinic or institution buying software and visibility; the patient is the marketplace user, and the provider or clinic budget owner controls adoption. The likely adoption path is discovery of provider demand, conversion to scheduling and patient-flow tooling, then deeper workflow integration where authorized APIs and operational value justify switching. Public evidence supports this mechanism, but it does not disclose segment-level pricing, attach rates, paid conversion, retention, customer acquisition cost, or incremental margins. Nor does it provide a comparable geography-by-segment denominator from which to calculate SAM or SOM. The market should therefore be underwritten as a set of testable provider and patient workflows, not as the full value of digital health. The next diligence step is to obtain cohort-level revenue, provider counts by country and product, contract sizes, retention, and the share of booking volume that is monetized.[CM010, CM011, CM012, CM013, CM014]

2.4 Exhibits

3.1 Competitive landscape and alternative set

The buyer's alternative set is wider than online-booking marketplaces. Built In identified Zocdoc and Doctolib as direct peers in 2019, while Multiples currently places NexHealth, Heidi Health, Phreesia, and several other public and private businesses in a broader comparable set. Those lists establish relevant names, not product equivalence: the pool does not contain current peer product documentation sufficient to normalize geography, customer segment, workflow breadth, or revenue model. Hospitals can also choose incumbent HIS or EHR workflows, and practices can retain call centers or assemble scheduling and communications components internally. Docplanner itself has historically used mergers and acquisitions, including Doctoralia and later jameda and TuoTempo, to consolidate local demand and add capabilities. The landscape is therefore a mix of direct marketplace rivalry, adjacent workflow software, institutional incumbents, and internal-build substitutes rather than a single homogeneous software category.[CP009, CP011, CP012, CP014]

3.2 Capability breadth, buyer fit, and pricing opacity

Docplanner is documented across patient discovery and reviews, online booking, practice administration, telehealth, and patient engagement. Historical reporting also describes the dual marketplace-and-cloud- software model, while Twilio's 2026 release adds evidence of a voice agent for booking, confirmations, and planned insurance-verification workflows. This breadth can reduce the number of tools a smaller practice needs, but it is not universal: SectorPunk explicitly considers the product less relevant for large hospital systems requiring deep HIS or EHR integration. Comparative capability cells remain unknown where the assigned pool contains only a competitor name. Pricing is even less decision-ready. SectorPunk displays "$100-$150" and "Min: $50,000+" while calling pricing mid-range, but does not define the billing unit, market, package, or contract term; it cannot be treated as verified list pricing or realized revenue.[CP001, CP002, CP003, CP006, CP008]

3.3 Distribution power, localization, and switching costs

Current supplier-issued evidence describes meaningful distribution: Twilio reported more than 100 million monthly website visits, 22 million monthly bookings, and use by 300,000 doctors in March 2026. LeadIQ instead reports a network of more than 2.8 million healthcare professionals and more than 20 million monthly bookings. These figures use different denominators and should not be reconciled into one provider count. Built In's older assessment attributed differentiation to Docplanner's international-market growth, and the localized-brand and acquisition history supports a market-by-market distribution strategy. Workflow breadth plausibly raises switching friction once scheduling, documentation, communications, and financial operations are embedded, but public retention, churn, migration-cost, and multi-homing evidence is absent. The resulting moat case is strongest on distribution reach and workflow integration, not on measured contractual lock-in.[CP004, CP005, CP012, CP013, CP015]

3.4 Moat durability and displacement risk

The moat is not fully self-contained. Noa Booking runs on Twilio ConversationRelay and Programmable Voice, showing that a strategically important interface depends on external communications infrastructure even though Docplanner owns the healthcare workflow and localization. Twilio reports that doctors using the agent saw twice the bookings of traditional call-center users and that 1,300 doctors were onboarded in three days, but this is partner-issued proof without cohort definitions or independent replication. ARR Club's report of growth from EUR 50 million to EUR 275 million ARR is similarly uncorroborated in the assigned pool and should not be used as a peer benchmark. Large-system integration limitations, opaque pricing, heterogeneous competitors, and the possibility that communications or AI vendors enable modular internal builds all constrain durability. The investment case needs customer-level retention and win-loss evidence before marketplace scale can be translated into a defensible switching-cost moat.[CP002, CP006, CP007, CP010, CP016]

3.5 Exhibits

4.1 Monetization and public traction

Docplanner monetizes two connected workflows rather than a single software seat: patients use a marketplace to discover and book care, while doctors and clinics can pay for software and visibility tools. A 2019 financing announcement describes the provider product as SaaS used to optimize patient flow, reduce no-shows, and digitize practice administration (CI006). The same announcement reported 20 million patients, 325,000 monthly bookings, more than 5 million listed healthcare professionals, and operations in 30 countries at that time (CI006). More recent third-party pages describe over 20 million monthly bookings across 13 markets (CI005) and 2.8 million healthcare professionals (CI004), while another tracker reports $290 million of ARR as of July 2026 (CI003). These figures are not directly comparable because the sources use different dates, populations, and definitions; the ARR figure is not independently audited in the retained evidence. The commercial model therefore has plausible cross-sell economics, but the public record does not establish conversion, retention, realized pricing, or segment mix.[CI001, CI002, CI003, CI004, CI005, CI006, CI007]

4.2 Cost structure and capital dependency

The disclosed use of funds points to a cost base shaped by sales, customer success, product, R&D, legal/compliance, marketing, and acquisitions. In 2019, Docplanner said the €80 million Series E would fund market penetration, product development, hiring, and potential bolt-on acquisitions, while the company had surpassed 1,000 employees and was hiring for nearly 100 roles (CI006). A contemporaneous financing report likewise said the funds would accelerate SaaS rollout and R&D and expand commercial and support teams (CI007). By contrast, the independent Unquote account reported that Docplanner was not generating significant free cash and needed to raise capital for growth; it also reported PLN 67 million turnover and PLN 15 million EBITDA for the Polish ZnanyLekarz business, not the consolidated group (CI011, CI012). A company news tracker states that the group reached EBITDA profitability in 2025 (CI005), but no retained source provides consolidated cash, burn, debt maturities, working capital, capex, or runway. Profitability may improve capital adequacy, but it does not remove financing and execution diligence needs without current consolidated accounts.[CI006, CI007, CI011, CI012, CI013, CI014]

4.3 Underwriting verdict and missing inputs

The evidence supports a diversified revenue mechanism with a large installed marketplace and provider-software footprint, but it does not support a precise valuation or forecast. Multiples records a $1 billion September 2021 valuation and approximately $139 million raised across seven rounds (CI008); Unquote independently reported a 2021 round at a unicorn valuation while noting that the amount raised was undisclosed and that sources expected another financing (CI010). These sources support financing history and valuation context, not current equity value or cash available. Public pricing, customer-level contract terms, CAC, payback, gross margin, net revenue retention, churn, ARPU, attach rate for Noa, debt obligations, and consolidated cash remain unverified in this pool. The financial stance is therefore research-more: the operating model is credible and potentially increasingly efficient, but underwriting should wait for reconciled segment revenue, cohort retention, contribution margin, cash-flow, and capitalization-table evidence.[CI008, CI009, CI010, CI015, CI016]

4.4 Diligence priorities

The highest-value next step is a reconciled financial pack rather than another headline traction estimate. Management should provide monthly recurring and non-recurring revenue by marketplace, subscriptions, and enterprise products; bridge bookings and provider activity to recognized revenue; and show gross margin by product and geography. The pack should also include cohort retention, paid-provider conversion, CAC and payback by channel, support and service-delivery costs, consolidated EBITDA-to-cash conversion, working capital, capex, debt facilities and maturities, and current cash runway. The retained sources provide enough evidence to formulate these requests, but not enough to answer them: company-issued announcements describe intended investment and operating metrics, while third-party databases disagree on scale and do not expose underlying methods.[CI003, CI008, CI010, CI015, CI016]

4.5 Exhibits

5.1 Product surface and maturity

The product is best understood as a two-sided healthcare workflow platform rather than only an appointment directory. Public descriptions identify patient discovery, appointment booking, reminders, telemedicine, messaging, intake, provider calendars, patient records, billing, and integrations. Docplanner's own integration guide documents a REST API with standard GET, POST, PUT, PATCH, and DELETE methods and offers PHP and .NET client libraries. That is concrete evidence of an integration surface, while the external feature inventory adds practice-management and communication capabilities. The evidence does not show which modules are generally available in every market, which are paid tiers, or how Noa.ai is integrated into production workflows. Maturity should therefore be described as established at the platform and API surface, with module-level availability and AI adoption still requiring verification.[CE001, CE002, CE003, CE004, CE005]

5.2 Workflow, integrations, and operating architecture

The observable operating model links patient acquisition to provider scheduling and then to communications and practice administration. The API guide says access is limited to medical software providers and that resources are authorized individually by each customer, which implies controlled partner provisioning rather than an unrestricted public API. Vonage's customer case describes SMS, WhatsApp, video, two-factor authentication, reminders, surveys, and appointment summaries, and says Docplanner used Vonage to move across channels and maintain delivery flexibility. These sources support a layered architecture of marketplace, provider workflow, integration/API, and communications services. A third-party profile reports AWS and Hetzner hosting in Germany, but the evidence does not disclose data schemas, deployment topology, service-level objectives, failover design, or measurable delivery and uptime performance. Those omissions matter because healthcare workflows are sensitive to missed messages, scheduling errors, and privacy controls.[CE006, CE007, CE008, CE009, CE010]

5.3 Differentiation, dependencies, and trust gaps

Docplanner's defensibility appears to come from the combination of marketplace demand, provider workflow depth, local operating footprint, and integrations rather than from a disclosed proprietary algorithm or hardware asset. One Peak describes ongoing product development, legal/compliance hiring, and potential acquisitions; that is a strategic priority statement, not proof of shipped technical differentiation. The Vonage case provides partner-reported evidence of a decade-long dependency and rapid use of video during the pandemic, but also highlights the risk of relying on an external communications layer. Public sources in this pool do not establish independent penetration testing, certifications, incident history, clinical safety controls, data-retention policy, or support SLAs. A diligence process should request those artifacts before treating the product as low-risk infrastructure.[CE011, CE012, CE013, CE014]

5.4 Technology exhibits

The architecture exhibit separates documented product layers from assumptions. It shows only components supported by the retained sources and labels the external communications dependency explicitly. The accompanying tables preserve the distinction between an observed capability, a company or partner claim, and an unanswered diligence question. This separation is important for a healthcare platform because a documented API method is not the same as a tested production control, and a partner case is not an independent reliability benchmark. The exhibit therefore provides a traceable operating hypothesis, while the evidence gaps identify the artifacts needed to confirm implementation quality, security posture, and current module coverage.[CE002, CE006, CE011]

5.5 Exhibits

6.1 Customer segments and buying motion

Docplanner serves two linked customer populations: patients who search for and book care, and healthcare professionals or institutions that pay for software, visibility, and practice workflow tools. The platform's local brands and country-by-country expansion support a segmented go-to-market rather than a single global product motion. The 2019 financing description says the SaaS tool helped doctors and clinics optimize patient flow, reduce no-shows, and digitize practice administration, while the 2025 podcast describes SaaS for healthcare professionals as the main revenue source. These are credible descriptions of the commercial design, not proof of current segment-level revenue or willingness to pay. Buyer, user, and payer can differ within a clinic, and the public record does not disclose segment ARPU, procurement cycle, or conversion from free marketplace visibility to paid software.[CU001, CU002, CU003, CU004]

6.2 Adoption trajectory and named proof

The evidence shows substantial historical and recent usage signals, but the metrics are not directly comparable because publishers use different dates, populations, and definitions. One 2019 company release reported 20 million patients, 325,000 monthly bookings, and more than five million listed professionals; a 2025 independent podcast described 110 million monthly users and 180,000 doctor clients; and a 2026 company-profile source reported more than 20 million monthly bookings and 2.8 million healthcare professionals. Rather than treating these as a single growth series, the trajectory table preserves each source's metric and vintage. Named operational proof is stronger where a customer or implementation partner gives workflow outcomes: Flobotics describes an EHR integration across four markets, with 10,000+ monthly processes and 98% automated processing, while HubSpot documents multi-language inbound marketing use. These examples demonstrate deployments and outcomes for particular workflows, not company-wide retention or unit economics.[CU005, CU006, CU007, CU008, CU009]

6.3 Retention, expansion, and concentration diligence

Docplanner's apparent expansion loop combines patient demand, professional visibility, scheduling and practice-management software, and additional local-market coverage. The Flobotics case describes automation being extended to new EHRs, facilities, and geographic markets, which is evidence of implementation extensibility in one deployment. The 2019 financing release also says the company had integrated competitors in Turkey and Spain and intended to pursue further acquisitions, but that is strategic history rather than proof of current customer expansion. Public sources do not provide net revenue retention, gross retention, logo churn, contract length, paid conversion, attach rate for Noa.ai, or top-customer revenue share. AInvest's 2026 analysis explicitly frames the AI repositioning as exposed to a value-delivery risk if the AI product does not create scalable customer value. The resulting customer thesis is positive on breadth and workflow depth but conditional on verification of cohort durability and concentration.[CU010, CU011, CU012, CU013, CU014]

6.4 Exhibits

7.1 Risk priorities and thesis-break conditions

Docplanner's risk profile is shaped by the combination of a two-sided healthcare marketplace and provider workflow software. A 2026 SWOT assessment identifies inconsistent monetization across regions, difficulty integrating with legacy hospital EMR/EHR systems, high overhead across many markets, and limited deep clinical capability as weaknesses; it also identifies privacy and healthcare compliance cost, cyberattacks against sensitive health data, well-funded rivals, and macroeconomic pressure on clinic software budgets as threats. A separate technology overview says the platform operates across 13 countries and supports patient discovery, booking, communication, documentation, and financial operations, while launching an AI assistant in 2024. These facts make the most important monitoring questions operational: whether regional integrations and controls remain consistent, whether AI features are governed for healthcare use, and whether provider monetization offsets the cost of maintaining a broad footprint. A thesis break should be tied to observable events rather than assumed absence of incidents. A material privacy or security event, an enforcement action or failed certification, repeated outages or failed integrations that impair bookings or clinical workflows, or a measurable deterioration in provider retention or monetization would weaken the investment case. Public sources do not establish current values for those indicators; they support a monitoring framework, not a claim that no such event has occurred.[CR001, CR002, CR003, CR004]

7.2 Legal, regulatory, and data-governance exposure

Healthcare data creates a higher control burden than a generic scheduling marketplace. The risk source explicitly names increasing data privacy and healthcare compliance costs, and warns that cyberattacks could target sensitive patient health data. The technology source describes a broad workflow that includes documentation and financial operations, and says Docplanner operates across 13 countries. Geographic breadth therefore increases the number of legal and operational regimes whose requirements must be mapped, monitored, and evidenced, although the retained public material does not identify a current regulator, license, certification, lawsuit, or breach. AI adds a distinct layer of exposure. The 2026 SWOT assessment identifies bias, inaccurate AI-driven medical advice, sudden regulatory shifts affecting patient data, and clinician or patient resistance as threats to an AI roadmap. Those are scenario risks from an AI-generated analysis, not evidence of an incident. The diligence priority is a control inventory covering lawful data use, model validation, human escalation, audit logs, vendor contracts, and incident response for each product and jurisdiction. Without those records, residual regulatory exposure should remain high even where no public enforcement record was found in the assigned pool.[CR006, CR007, CR008]

7.3 Operating, partner, and financial resilience

Integration and scale create execution risk. The retained SWOT identifies legacy EMR/EHR integration difficulty and high operational overhead across dozens of markets, while the same assessment describes rivalry from Doctolib and Zocdoc and substitution by general search or basic calendars. The 2019 financing announcement says funds were intended for continued market penetration, product development, hiring, legal/compliance, marketing, and potential bolt-on acquisitions, and that the company had already integrated competitors in Turkey and Spain. This supports a dependency thesis around successful integrations, local operating teams, and disciplined post-acquisition execution; it does not prove current integration quality or the absence of execution misses. Financial resilience is also difficult to underwrite from the retained evidence. Historical reporting records approximately EUR 130 million raised by 2019 while a 2026 company overview labels revenue as projected and says recent investment occurred, but also warns that its AI-generated findings are not independently verified. A private-comps source reports a last disclosed USD 1 billion valuation and historical rounds, but current valuation, debt terms, cash runway, covenants, and segment margins are not established by the source set. The appropriate mitigation is current financing and operating diligence, not treating funding raised as cash available.[CR009, CR010, CR011, CR012]

7.4 Residual exposure and diligence plan

The evidence supports a high-risk, research-more posture rather than a finding of a realized failure. Independent-style summaries describe a large healthcare network and competitive position, but several retained pages are analyst or company-sponsored summaries and mix historical and projected figures. The most decision-relevant gaps are current privacy and security controls, regulatory posture by market, incident and outage history, integration reliability, provider retention, customer concentration, current debt and liquidity, and the economics of AI products. These gaps matter because they determine whether scale is a durable moat or a cost and compliance multiplier. Monitoring should use explicit thresholds: a reportable privacy or security incident; an enforcement notice, material claim, or failed audit; repeated service or integration failures affecting booking or practice workflows; a sustained fall in provider retention or monetization; or financing terms that materially constrain product investment. Until those indicators and mitigations are evidenced, residual exposure remains material even though the assigned sources do not substantiate a current incident.[CR005, CR013, CR014, CR015, CR016]

7.5 Exhibits

8.1 Decision and price discipline

The recommendation is research-more, not buy or pass. Two independent databases identify the latest disclosed valuation as $1 billion in September 2021, but that historical mark is not evidence of Docplanner's current price or enterprise value. The retained evidence also says current control and valuation are unverified and reports a 2025 debt commitment, making equity value sensitive to debt draw, seniority, liquidation preferences, and any structured financing terms. None of those terms is visible in the public source set. Consequently, confidence is medium-low, risk is high, and the valuation stance is indeterminate. An investor should advance only to a data-room and term-sheet review, then underwrite returns from the actual fully diluted entry price rather than anchoring on the stale unicorn mark.[CV001, CV002, CV014, CV015, CV016]

8.2 Thesis and anti-thesis

The thesis is that Docplanner combines meaningful marketplace activity with provider workflow software across a broad geographic footprint. Company-issued 2025 data reports 18.7 million monthly bookings and 3.7 million healthcare professionals, while LeadIQ describes operations across 13 countries. ARR Club's $290 million ARR figure dated July 2026, if validated, would indicate substantial monetization at scale. The anti-thesis is evidence quality and capital-structure opacity: the ARR page exposes neither audited financial statements nor calculation methodology, the public valuation is five years old, and current control is explicitly described as unverified by one retained analyst source. The view improves only with audited recurring revenue, retention, gross margin, cash-flow, debt, and cohort evidence tied to the same reporting period.[CV006, CV007, CV008, CV009, CV015]

8.3 Financing history and comparables

Funding totals are not clean enough to treat as cash available or a cap-table proxy. Tracxn reports $141 million across eight rounds, Multiples reports $139 million across seven rounds, and One Peak said the May 2019 Series E brought cumulative funding to approximately €130 million. These figures use different currencies, dates, and apparent round-count conventions, so they should remain separate rather than be reconciled into an invented total. Multiples also lists revenue multiples of 1.5x for Phreesia and 5.2x for B-Soft, but it does not establish business-model, growth, margin, geography, or period comparability sufficient to select a Docplanner multiple. Dividing a 2021 valuation by a 2026 ARR estimate would mix noncontemporaneous observations and would not produce a defensible current valuation.[CV003, CV004, CV005, CV010, CV011, CV012, CV013]

8.4 Scenarios, exit readiness, and diligence asks

The scenarios are deliberately qualitative because public evidence cannot support precise valuation ranges or probability percentages. A bull case requires the reported ARR and platform scale to reconcile to audited revenue, durable retention, attractive margins, and financing without punitive senior claims. The base case is that the company has real scale but its price remains unassessable until current terms and operating quality are disclosed. The bear case combines a stale valuation anchor, unverified current control, possible debt overhang, weak retention, or compliance costs, making a value below the 2021 mark plausible but not quantifiable. Exit readiness is likewise unresolved: investors should obtain the cap table, preference stack, debt schedule and covenants, audited financials, NRR and churn, governance rights, and management's credible liquidity path before setting target return, hold period, or exit value.[CV006, CV007, CV013, CV014, CV015, CV016]

8.5 Exhibits