For MD, MS, DNB and MBBS students in India
We will not write your thesis. We will build almost everything around it.
Most of what makes a postgraduate thesis miserable is not medicine. It is data living in three notebooks and a WhatsApp group, a proforma that changed in month four, a statistics package nobody taught you, and a submission format that rejects your file at 11pm the night before. We are engineers. That is the half we can take off you.
What is in it for us
We would rather say this than have you wonder.
Redenn is a software company. We build web applications, databases and AI tooling — for hospitals, for clinics, and for two health products of our own. Doing that work we kept meeting residents running real research off a single laptop with no backup, hand-counting a proforma into Excel at two in the morning, six weeks from submission.
So we opened this up. There is nothing to buy here and nothing to sign. Some of the people reading this will run their own practice in eight or ten years, and will need a website and something to answer their phone. If a few of them remember who built their data capture in 2026, this page has paid for itself. That is the entire commercial case, and it is years away.
Where we draw the line
We do not write, rewrite, restructure, paraphrase, shorten, “polish” or run any tool over a single sentence you will submit for assessment.
Not the introduction. Not the review of literature. Not the discussion. Not the abstract. Not the covering letter to the journal. If it goes in with your name on it, it came out of your head.
We do this
We never do this
A viva is not a test of the document. It is a test of whether the person in the chair is the person who did the work.
Your external examiner has read hundreds of these and has about ninety seconds of curiosity to spend on you. They will pick one table and ask why that test and not another. They will ask what you did about the fourteen cases lost to follow-up. They will ask what surprised you, which is the question with no memorisable answer at all.
A student who did their own analysis handles all of that, because they were there when the awkward things happened. A student holding a document somebody else built does not fail loudly — they go quiet, and the silence sits in a small room in front of two people who write your name down.
Work that is not your own does not expire, either. It can surface years later, at a first consultant post or a fellowship application abroad, and in India it can reach your registration. We are not going to be the reason that happens to someone.
If that reads like a restriction, look at the left-hand column again. There is a great deal there, and none of it is the part that gets found out.
The honest arithmetic
About 45% of a thesis is work we can take off you.
Not all of it, and we would rather show you the split than let you find the gap later. We are three engineers. We do not employ a statistician, so we teach the statistics rather than run them for you. This is our own estimate of where the three years go, and you are welcome to argue with it.
- 45%Engineering and process we can take off you now
- 14%Needs a statistician we do not employ
- 24%Your own clinical work — patients, consent, values
- 17%The writing, off-limits by design
- 45% Engineering and process we can take off you now
- 14% Needs a statistician we do not employ
- 24% Your own clinical work — patients, consent, values
- 17% The writing, off-limits by design
Stage by stage
Three years, and who does what in each of them.
Topic and feasibility
Months 0–3We build or run
- A prior-art search across PubMed, Scopus and Cochrane, with the strategy written down so it is reproducible and citable.
- The feasibility questions to take to your department — how many eligible cases last year, is the outcome measurable with equipment you already have, has this been answered already.
- Your objectives critiqued as questions. Does your primary outcome actually answer objective two?
Stays with you
- Choosing the question, and defending it to your guide.
- Getting the case numbers out of medical records. We cannot, and a confident guess here is worse than no answer.
Protocol and synopsis
Months 3–6We build or run
- Study design consultation and the reporting checklist that matches it — STROBE, CONSORT, STARD, PRISMA or CARE.
- A case record form where every field traces back to a stated objective, plus the data dictionary: types, units, allowed ranges, coding, and what counts as missing.
- Your university's or NBEMS's own template applied — headings in the order they expect, annexure order, certificate block.
- Zotero set up, library de-duplicated, Vancouver style installed, and the Word plugin that always breaks, fixed.
- The sample size formula taught, with the inputs laid out, so you can walk your guide through it.
Stays with you
- Every sentence of the protocol narrative.
- Confirming the sample size with your guide and your institution's statistician. We teach it. We do not calculate it for you.
Ethics, registration, CTRI
Months 4–9We build or run
- The ethics submission pack assembled against your institution's own checklist — cover letter, protocol copy, CRF, participant information sheet, consent form in the language pair required, undertakings, conflict-of-interest form.
- A resubmission tracker for clarification letters. Three weeks answering a clarification costs a whole meeting cycle.
- CTRI prepared field by field, sitting with you while you fill it under your own account, before you enrol anyone.
- Your university's topic-registration deadline tracked, and the format checked before it goes.
Stays with you
- Signing and submitting everything. It is your study and your committee.
Collection
Months 9–28We build or run
- A mobile-first data capture app that works offline on hospital wifi, validates each field, checks ranges, timestamps an audit trail, holds study IDs only — no names, no hospital numbers — and exports clean in one tap.
- A real database behind it: encrypted, backed up nightly, versioned. Not one laptop and one pen drive.
- A recruitment dashboard — recruited, screened out, lost to follow-up, which fields are missing on which cases — and an alert the moment your trajectory misses your submission month.
- If recruitment falls short: the honest routes out. An ethics amendment to widen criteria or extend the window, or a reframe to a pilot that reports the number you actually achieved.
Stays with you
- Seeing the patients, taking consent, recording the values. All of it.
Analysis and write-up
Months 24–30We build or run
- Cleaning and coding scripts you run yourself, plus a cleaning log — every exclusion, recode, unit conversion and outlier decision, with its reason and your adjudication recorded.
- Plotting scripts that turn your dataset into your figures, so when an examiner asks you to redraw one, you can. Publication quality, colour-blind safe, axes labelled.
- Your university's thesis template applied: margins, pagination, automatic contents and figure lists, certificates, annexure order, binding spec, copy count.
- An honest explanation of similarity screening — what the score measures, why methods sections always score high, and why pushing a draft through a third-party checker can deposit it in that service's repository and flag you against your own earlier work.
Stays with you
- The introduction, the review of literature, the results narrative, the discussion, the abstract. Every sentence.
- Interpreting your own numbers. We can show you what the output means. We cannot have been there when the awkward things happened.
Viva and after
Months 30–36We build or run
- A question bank built from your own design — why this sample size, why this test and not another, what you did about the cases lost to follow-up.
- A mock viva, run properly, with the questions that have no memorisable answer.
- After it is accepted: turning the work into a manuscript is a different job with different rules, and we will tell you what those are.
Stays with you
- Sitting the viva. That is rather the point.
Your guide
Everything here is something we would happily send to your guide.
So we offer it first, before you ask. When we start on a protocol, an analysis, or anything that becomes part of what you submit, we will copy your guide in from day one if you want us to. Most people decline, and that is entirely fine — the offer is the point.
If there is anything on this page you would not want your guide to read, we have written the page badly.
Already in practice and looking at the software side of a clinic? That is a different page — medical and healthcare.