Nurse-run 30-day wound and symptom checks after surgery, paid by hospitals
TL;DR Suturely gives hospitals a nurse desk that checks every surgical patient's wound photos and symptoms on set days for 30 days after discharge. Problems go back to the operating surgeon the same day. The hospital pays because it finally sees its own infection rate after patients leave.
Most surgical site infections show up after the patient has gone home. A multicentre Indian study across hospitals in Delhi, Manipal and Mumbai found infections in 161 of 3,090 surgical patients, or 5.2%, and 66% of those cases were picked up only by post-discharge follow-up[1]. The authors note that no Indian surveillance system covers the period after discharge[1].
So hospitals count only the infections that come back through their own doors. Patients who see a local doctor, or who wait too long, never appear in the numbers.
Surgeons lose the chance to step in early, and quality teams end up reporting infection rates that look a lot better than they really are, which helps nobody except the slide deck at the board meeting.
What it does, in regulatory terms - nurse follow-up and escalation under the operating surgeon's protocol. No diagnosis or treatment is given by the software or the nurses. Teleconsultation and any prescribing stay with the registered doctor under the Telemedicine Practice Guidelines[2]. Photo review is by people, so the product stays outside CDSCO's medical device software scope[3].
At discharge, the patient or a family member is enrolled. On days 3, 7, 14 and 30 they get a call or message asking for a wound photo and answers to a short set of questions on fever, pain, discharge and redness. A trained nurse reviews each case and sends anything off-protocol to the surgeon's team. Every case becomes a line in the hospital's infection register.
The seed promised data-driven telehealth that improves recovery, and I've reframed that. Trials of telemedicine after abdominal surgery show mixed effects on readmissions and little change in emergency visits[4]. Suturely sells measurement and earlier contact, not fewer readmissions.
The patient benefits but the hospital pays. A per-surgery fee of ₹300–600 is my assumption, because no public price exists for this service. Mid-size private hospitals with infection-control committees and accreditation ambitions are the first buyers. Orthopaedic and caesarean-heavy hospitals have the most cases. Patients pay nothing, which keeps enrolment at discharge simple.
The 2024 multicentre study gave India its first solid number on post-discharge infections[1]. Funded players are moving into surgery care too - one surgery-booking platform raised a $12 million (about ₹116 Cr) Series A in April 2025 and plans an AI patient-care platform[5]. The DPDP Rules of November 2025 clarify consent for health data[6].
No public figure exists for post-discharge surgical follow-up in India. The narrow signal is clinical, since two in three surgical infections are found only after discharge[1]. Next door, one surgery-booking platform has facilitated over 30,000 surgeries[5], a sign of how many patients a single platform touches.
Surgery-booking platforms coordinate bookings, pricing and support, but their focus is before and during the hospital stay[5]. Health-record apps run patient records and clinic software, not post-operative follow-up[7]. Large hospital chains call some patients after discharge in-house. I couldn't find an Indian service that runs structured post-discharge wound surveillance for other hospitals.
| Difficulty | Moderate (40/100) |
| Starting capital | ₹50 L–1 Cr |
| Time to launch | 5–8 months |
The software is modest. The hard part is getting surgeons to agree on one protocol, getting patients to send usable photos on day 14 when they feel fine and selling hospitals a number that may make their infection rate look worse at first. Nobody enjoys paying for bad news.
Yes, partly. The service itself needs no special permit, but it works inside medical rules.
Building this outside India? The categories above usually have a local equivalent, so check with your own regulator.
Don't trust AI to decide whether a wound is infected. That call stays with the nurse and the surgeon, and automated infection scoring would likely make the software a regulated device.
Want to work out the AI layer for Suturely? Talk to Yash →
Here's what can go south -
I'd back this for a founder with an infection-control or hospital quality background. If you want a consumer app then look elsewhere. Prove two things first - that 70% of enrolled patients send a day-14 photo at two hospitals, and that one quality head uses the register in a committee meeting.
Plan for roughly ₹50 L–1 Cr, mostly nurse salaries, the follow-up software and the months it takes to sign the first hospitals.
No single licence, but nurses must work under the surgeon's protocol per the Telemedicine Practice Guidelines, photo review should stay human to avoid device rules and you must comply with the DPDP Act.
Yes, post-discharge infections are missed in many health systems. Check local nurse scope rules and health data law before you sign a hospital.
The free Suturely validation kit has the line-by-line capital breakdown, the effort scoring, the rules and permissions checklist, a 14-day validation sprint with pass/fail targets, a 90-day launch plan, 10 interview questions for hospitals and patients, and 5 assumptions to test. Download the kit →
Thinking about building Suturely or something close to it? The make-or-break work is getting a hospital to pay for a number that may look worse before it looks better. If you need a hand, you know where to find me. Talk to Yash →
For illustration only. Names are fictional and ideas hypothetical; sourced facts are real but may be out of date. Nothing here is legal, financial or professional advice, and Yash Khatri is not personally liable for any use of it. Read the full disclaimer.