Early-stage healthcare product. AI-generated output is not medical advice and is not clinically reviewed. Not medical advice Read the full disclaimer Details
Continuum / Investor overview

Healthcare should not start from zero every time.

Continuum helps patients turn fragmented medical information into a clear, patient-controlled health story, before, during and after a healthcare visit.

Explore the product Talk to the team

Early stage. The product is live, on the web and as an app. There are no numbers on this page that we cannot evidence.

01 — From fragmented documents to a one-page brief. Worked example from two sample documents, no real patient data.

Stage
Live productWeb and iOS
Product surface
Seven connected toolsone workflow, not seven features
Privacy
DPIA and security architecturedocumented and published
Base
Vienna, AustriaEU-hosted, eight languages
The problem

Healthcare is fragmented. Patients carry the missing context.

Every stop along the way documents carefully what happened inside its own walls. None of them is responsible for holding the thread between them. That job falls to the one person who attends all of the appointments, and their tool for it is a folder full of paper.

  1. Hospital

    Discharge letter

  2. Lab

    Values without a trend

  3. Specialist

    One organ, one slice

  4. GP

    Ten minutes, thick folder

  5. Patient

    Was at every appointment

Only one person in this chain was present at every appointment. They are the only one who knows the whole story, and the only one without a tool for holding it.

01

Documents sit scattered

Portals, paper, PDFs in an inbox, photos of reports. None of it talks to any of the rest.

02

Appointments are short

A large part of the time goes into reconstructing where things stand rather than deciding what happens next.

03

The same story is repeated

Each new practice starts with the same history, told from memory, under time pressure.

04

The thread over time is lost

What changed since last time is often the most important information, and the hardest to hold on to.

The product

One thread through the healthcare journey.

The seven tools in the product are not a catalogue. They are the stages of a single workflow, and each one hands something to the next.

  1. Documents

    Reports, letters, photos of prescriptions

  2. Understand

    Clinical language in plain words

  3. Prepare

    Reason, symptoms, open questions

  4. Visit

    One page, readable in two minutes

  5. Reflect

    Hold on to what was said

  6. Continue

    The next appointment starts here

Inside the product

Three moments where continuity is made.

01

Before the appointment

Patients organise what matters before the clock starts.

Four short sections, filled in calmly at home rather than under pressure in the consulting room. The important part is not the form but what appears beside it: Continuum surfaces what was already reported earlier. That is what turns a form into the beginning of a record over time.

02 — Visit preparation. The note under the symptoms is the actual point: the product remembers the previous visit.

02

During the healthcare journey

Relevant context can be carried into the conversation.

One A4 page, ordered the way a doctor reads: reason, values with how they moved, medication, open questions. Nothing is interpreted, nothing is added. What is unclear is left out rather than guessed. This is the output the whole product is built around.

03 — The brief. Values appear with how they moved, because the movement is the information. Worked example, no real patient data.

03

Between appointments

The next appointment starts with what happened last time.

After the visit, the reflection holds on to what was discussed. The timeline lines up reports, appointments and notes in the order they happened. This is where the real value sits: the product gets more useful with each further appointment, not with each further document.

04 — The timeline. It is the second measurement that makes the first one useful. Worked example, no real patient data.

Difference

Not another medical chatbot.

An assistant can explain a lab value. That is not the same job as holding a story across years and across different clinicians. Three decisions separate the one from the other, and all three live in the product rather than in the positioning.

  • Description, not diagnosis

    Continuum organises and describes what is already present in the patient's own documents. If a finding is unclear it is left out rather than guessed at. That is a design decision, not a disclaimer, and it is why the output is usable by a clinician at all.

  • Continuity, not a single answer

    A single answer is over when the window closes. Continuum becomes more useful across several encounters, because each visit leaves something for the next one. That is both the product and the reason use does not end by itself.

  • Patient-controlled, not ad-driven

    The health story belongs to the patient: they can export all of it as JSON and delete the account in one step. No advertising IDs, no tracking pixels, no sale of health data, no training of models on their documents.

Put another way: the AI is infrastructure. The product is continuity.

Privacy and safety

Privacy is part of the product architecture.

Health data is special category data. In a European health product the data architecture decides what may be built at all, so it was decided first rather than documented afterwards.

  1. Patient

    Uploads a file. Explicit consent for health-data processing, no account required.

  2. In transit

    TLS the whole way. A temporary directory only that session knows about. Servers in the EU.

  3. Processing

    A processor agreement covers the AI inference. No models are trained on your documents. No automated medical decisions.

  4. Original file

    Deleted after processing. There is no step at which we keep it. An hourly sweep cleans up if the primary path is delayed.

  5. Structured output

    Only what you save is kept, AES-256 encrypted, down to the title. As a guest, the brief is deleted automatically within an hour.

Original files

Deleted after processing.

Stored health context

AES-256 encrypted at rest. No one on the team can read it without the application key.

AI

No diagnosis. No treatment decisions. No automated decision-making within the meaning of Article 22 GDPR.

Tracking

No ad pixels. No advertising IDs. No sale of health data.

Control

Full data export as JSON. The account is deletable in one step. Every caregiver read is logged.

Documentation

The DPIA and the security architecture are documented in the privacy policy and publicly readable.

Security overview · Privacy policy

Why now

The infrastructure changed. The patient problem did not.

01

Unstructured text can now be structured

Until recently a photographed hospital letter was, to software, an image. It can now be turned into structure reliably enough to work with, without anyone retyping it.

02

The fragmentation remains

Systems continue to be built around institutions rather than around people. The gap sits exactly where a patient moves from one institution to the next, and no institution closes it for them.

03

Patients already manage their records digitally

Reports already arrive as PDFs in an inbox and as photos in a camera roll. The habit exists. What is missing is a place where they add up to something.

  1. Old

    Documents scattered

    Organising meant retyping. Which is why nobody did it.

  2. Now

    Unstructured information becomes structured

    The effort for the patient drops to one upload. That is the change that makes Continuum possible.

  3. Next

    A patient-controlled continuity layer

    Not another record, but the context a patient can carry between systems. This is not proven yet. It is what is being worked on.

Market

A large problem starts with a focused entry point.

There is deliberately no market size on this page. We have not verified a defensible figure, and an unverified one here would devalue every sourced claim on the rest of the page. What we can show is the shape of the expansion, not a market already captured.

  1. Beachhead

    Complex medical journeys

    Where the fragmentation hurts most: many clinicians, many documents, long timespans. This is where the pain is large enough that someone will take on the effort of a new tool.

    Living with chronic illness Navigating complex care Caring for a parent
  2. Expansion

    Adjacent use cases

    The same mechanics carry into other situations where a trajectory matters more than a single result. The tools for these are already built; what is missing is evidence that they are wanted there as much.

    Chronic conditions Specialist care Caregivers Post-operative journeys Longitudinal records
  3. Platform

    Patient-controlled health context

    The long-term possibility: a context the patient carries across encounters and providers, because it belongs to them rather than to any one institution. This is the company's thesis, not its current state.

Where we stand

Built first. Now proving repeatable use and distribution.

The current stage is early product validation. The product is built and live, the privacy architecture is in place, and usage is not yet at a level anything could be concluded from. We write it that way because the opposite would not survive first diligence.

Live product

Web and mobile app, publicly usable. A brief can be produced without an account.

Product surface

Seven connected tools on one shared workflow, in eight languages including two right-to-left.

Privacy

DPIA and security architecture documented, encryption at rest implemented, deletion of originals wired into the pipeline.

Not proven yet

Repeat use across several appointments, repeatable acquisition, and distribution through healthcare. There are no pilots, no institutional partnerships, no clinical validation and no revenue to report today.

The next milestones

  1. Now

    Live product

    Web and app, in eight languages, with a documented privacy architecture.

  2. Next

    User validation

    Does anyone use this for a second and a third appointment? That is the single question the thesis turns on.

  3. Next

    Healthcare design partners

    Practices and outpatient clinics that actually receive the brief, so the product is shaped by the real workflow rather than by our picture of it.

  4. Next

    Repeatable acquisition

    One channel that behaves the same way twice in a row. Until then, distribution is an open question rather than a forecast.

Business model

Start with the patient. Expand through healthcare.

The person who gets the value is, today, also the person who decides. That is why the patient comes first rather than a procurement department. Pricing is not decided, and none is stated on this page.

  1. Patient

    Holds the immediate benefit and makes the decision. Today the only entry point.

  2. Continuum

    Holds the health context on the patient's behalf, and in their ownership.

  3. Healthcare ecosystem

    Benefits when an appointment does not start from zero. That is the basis for possible later routes, none of which is contracted today.

Potential expansion paths

INITIAL

Patient subscription

The most direct route, because benefit and decision sit with the same person. Price not decided.

EXPANSION

Healthcare organisations

Practices and clinics for which a prepared appointment makes a measurable difference. Not contracted.

EXPANSION

Care partnerships

Patient organisations and care programmes that already accompany people through long journeys. Not contracted.

LONG-TERM

Employer and insurer distribution

A channel that only makes sense once repeat use is demonstrated. Explicitly later. Not contracted.

Pricing and willingness to pay are explicitly part of the validation phase, not a decision already made. The first step is patient-paid; everything after it depends on that first step holding.

Go-to-market

Distribution is the next product to solve.

Building the product was the smaller half. The rings below run outward from the person who has the problem today to those who reach many such people. Only the innermost one is live work today; the outer ones assume the inner one works.

  1. 01

    Direct patient acquisition

    People searching today with a concrete question, usually before an appointment they are worried about. The one ring being worked on right now.

  2. 02

    Patient communities

    Groups formed around a diagnosis, where practical advice is already passed along.

  3. 03

    Caregiver networks

    Whoever manages a parent's paperwork often feels the problem more sharply than the patient does.

  4. 04

    Healthcare design partners

    Practices that receive the brief and tell us what about it does not work in the real workflow.

  5. 05

    Provider and institutional distribution

    The slowest and largest ring. Worth attempting only once the inner ones demonstrably work, not before.

Team

Built by product people who care about the details.

We sat with family members through long treatment cycles, carried reports between GPs, specialists and hospitals, and watched the same scene every time: the doctor flipped through a thick folder looking for three numbers, the clock ran out, nobody asked the question that actually mattered.

The Continuum team
Founder

Amirali Khoshneviszadeh

Product and engineering. He writes the code, designs the interface and writes the words, and is the managing director of Knightify FlexCo, under which Continuum ships. Vienna.

Who builds it

Continuum ships under Knightify, a small software studio in Vienna. A small team here means the product, the language and the data model share one handwriting, and that a decision about privacy and a decision about the interface are taken at the same desk.

Why healthcare

Because we wanted the tool for our own families. Continuum is the note we wished we had been holding. We handle the data the way we would want someone to handle our parents' data.

Legal entity

Knightify FlexCo, registered with the Commercial Court Vienna (FN 666564 t).

Imprint · About

Fundraise

Building the next layer of patient-controlled healthcare.

Stage

Pre-seed / seed.

Raise

We are preparing our first institutional round. The amount is not finalised, so no figure is stated here.

Use of funds

  • Product

    Deepening the continuity loop rather than adding more tools beside it.

  • Healthcare validation

    Working with practices that actually receive the brief, and building from what they say.

  • Distribution

    Finding one channel that behaves the same way twice in a row.

  • Team

    A small number of hires, where a single person is the bottleneck today.

  • Security and regulatory

    The work a European health product has to do regardless, done early rather than late.

No percentage allocation has been fixed, so none is shown. The order above is the priority, not the weighting.

Healthcare should not start from zero.

We are building the continuity layer patients can carry with them.

Talk to the team Try Continuum

05 — The artefact everything is built around. Worked example, no real patient data.