Aignoz.com · Vellore, India
A doctor came to First500days with a concept and no plan. Twelve weeks later Aignoz was live — patient apps, doctor apps, an admin panel and an AI assistant that routes people to the right specialist.
01 — Founder Perspective
Draft — pending founder approval
“I knew the problem I wanted to solve because I see it in practice: patients arrive at the wrong door, and by the time they reach the right specialist, time has been lost that nobody gets back.
What I did not have was a business. First500days structured the idea into an execution and launch plan, then built the whole thing — the patient apps, the doctor apps, the admin panel and the AI assistant that gets a patient to the right consultant.
Three months from an idea to something doctors and patients actually use. That is not the pace I expected.
02 — Executive Summary
Aignoz is building a health operating system for doctors — the layer through which a practitioner runs consultations and through which a patient reaches the right practitioner in the first place.
When First500days was engaged, Aignoz was at idea stage. There was clinical conviction behind it, but no defined strategy and nothing built. That is the most common place for a doctor-founded venture to stall: the medical insight is real, and the path from insight to product is a different discipline entirely.
First500days did two things. It structured the business idea into a defined execution and launch plan, and it developed the product: patient apps for Android and iOS, a doctor app on web and Android, an admin panel, and an AI assistant that talks to a patient about their problem and points them to the right consultant.
Three months later, Aignoz is live and running.
03 — The Venture
A patient with a symptom faces a question medicine never asks its practitioners to answer for themselves: which kind of doctor is this for? People guess, ask a relative, search the internet, or default to whoever is nearest. The consultation that follows is often with the wrong specialist, and the real one happens weeks later.
Aignoz addresses that gap at the front. Its AI assistant holds a conversation with the patient about what they are experiencing and directs them to the appropriate consultant — a routing decision, not a clinical one. The doctor then works inside the platform, which is where the "operating system for doctors" description comes from: consultations, patients and practice management in one place rather than scattered across phones and paper.
The founder is himself a doctor, which is why the venture starts from the practitioner's side of the problem rather than the app-store side of it.
On the AI: the assistant's function is triage-adjacent routing — understanding a described problem well enough to send the patient to the right specialty. Nothing on this page claims it diagnoses, treats, or substitutes for clinical judgement, and the platform routes to a human doctor in every case.
04 — Where They Started
Aignoz was at the earliest stage a venture can be engaged at. What existed was a practising doctor's read of a real problem. What did not exist was everything that turns that read into a company.
Two lines is an honest summary of an idea-stage venture. It is also the reason the engagement was scoped the way it was: with nothing to inherit and nothing to fix, the only question was what to build first and in what order.
05 — The Challenge & Our Response
A tight engagement with a narrow scope: make the business make sense, then build the thing.
The direction was unclear. A clinical insight is not yet a business — it says nothing about who pays, what ships first, or how the thing reaches its first doctor and its first patient.
We structured the business idea and defined the execution and launch plan — the scope, the sequence and the route to going live that the build was then held against.
Nothing had been built. For a platform that has to serve patients and doctors simultaneously — and add an AI layer between them — starting from zero in three months is an unusually compressed brief.
We developed the AI-enabled product end to end: patient apps on Android and iOS, a doctor app on web and Android, an admin panel, and the AI assistant that routes a patient to the right consultant.
06 — The Venture-Building Journey
The concept was worked into a business with an execution and launch plan behind it. On a three-month clock this step is the one people are tempted to skip; skipping it is what turns a short build into a long one.
All five applications were developed together — patient, doctor, admin and the AI layer. Building the patient side alone would have produced an app with nobody on the other end of it.
Aignoz went live and is running today, with the platform in the hands of both sides it was built for.
07 — What We Built
Where a patient describes their problem, is routed, and books the consultation.
Full parity on iPhone, so reach is never limited by a patient's handset.
Where practitioners run consultations and manage their patients from the desk.
The same practice, on the device a doctor actually carries between rooms.
Where the company manages doctors, patients, consultations and platform content.
Five applications, one system — and an AI layer whose only job is to make sure the patient reaches the right human.
08 — Business Outcomes
Aignoz went from an idea with no strategy behind it to a live, running platform with both sides of the consultation built and an AI layer in production — inside a single quarter.
No doctor counts, patient numbers, consultation volumes or revenue figures are claimed on this page. This engagement covered strategy and product; the outcome is the platform and the plan behind it, stated as of May 2025.
09 — Before → After
10 — The Lesson
Aignoz started with something most startups would pay for and cannot buy: a founder who understands the problem professionally. It still could not move, because domain expertise and company-building are different skills.
Knowing exactly what is broken in your field tells you what to build. It does not tell you what to build first, who to serve, or how it reaches anyone. That translation is its own piece of work.
A patient app with no doctors on it is a waiting room. All five applications shipped together because the service does not exist until both sides can use it.
The assistant routes patients to the right specialist — a narrow, checkable task with a human at the end of it. Narrow AI that works beats broad AI that impresses, especially in healthcare.
The distance between an expert's insight and a product anyone can open is where most specialist ventures stop. It is a shorter distance than it looks, if someone is accountable for crossing it.
Every founder starts at zero — the first 500 days decide what you are standing on at the end of them.
We use cookies to run this website and, with your permission, to understand how it's used and to measure our advertising. You can accept all, reject all, or choose which ones you're comfortable with. You can change your mind at any time from the Cookie settings link in the footer.
Share a few details and our team will get back to you within 24–48 hours.