About Researchify

Research supervision runs on a stack of tools that were never meant to talk to each other. The meeting is in a calendar, the notes are in a document, the reading list is in an email, the draft is in a shared drive, and the record of what a scholar was actually asked to do last month is in somebody’s memory. Nothing is wrong with any one of those tools. The gaps between them are where supervision quietly falls apart.

The cost lands unevenly. A professor supervising eight scholars spends the first ten minutes of every meeting reconstructing where things were left. A scholar who was given three things to do walks away certain of two. Neither is a discipline problem; it is a record-keeping problem, and software is good at record-keeping.

One lab, one place. A professor sets up a lab, invites scholars with a link, and from then on the work has somewhere to live.

• Scholars, groups and classes. Organise scholars into cohorts, classes or project teams. Tasks, meetings and announcements can each target a single group, and every group has a shareable invite link.
• Tasks and submissions. Assign work with a deadline and an expected output, let scholars submit against it, then approve, reject or send it back for revision with notes attached.
• Meetings. Scheduling creates the event on your Google Calendar, generates a Google Meet link and invites every participant. Rescheduling or cancelling in Researchify updates the calendar event and tells everyone.
• Meeting summaries and action items. Give Researchify a transcript, from a connected recording service or pasted in by hand, and it produces a summary, key points, follow-up topics and action items. Action items become real, assigned tasks, so the gap between the meeting and the work closes.
• Analytics. Submission rates, task status and meeting attendance, per scholar and per group, so a supervisor can see where someone is stuck before it becomes a crisis.
• Lumi. A built-in assistant that answers questions about your own lab in plain language, and can create tasks and schedule meetings for professors.

Professors and research supervisors, their PhD scholars, and co-supervisors. The three roles see genuinely different products rather than the same screen with buttons hidden.

• Professors run the lab: scholars, groups, tasks, meetings, reviews, announcements and analytics.
• Scholars see their own work - what is assigned, what is due, what they have submitted and how it was reviewed, plus their own progress analytics.
• Co-supervisors are scholars a professor has given supervisory powers to. The professor chooses each permission individually, and can limit it to named scholars rather than the whole lab.

Supervision records are sensitive. They contain unpublished research directions, candid assessments of students, and sometimes transcripts of conversations people assumed were private. We treat that as the constraint it is.

• A lab’s data stays in that lab. Visible to the professor, their scholars and the co-supervisors they assign.
• Transcripts are opt-in. Nothing is recorded or summarised unless a professor connects a recording service or pastes a transcript in. It is off until somebody turns it on.
• We ask for the narrowest access we can. Researchify requests calendar access to create and update your meetings. It does not ask to send mail from your mailbox, and it does not read your inbox.
• Researchify is ad-supported. Third-party display ads appear across the site, including inside the signed-in application, and the ad network sets its own cookies in your browser. Ads are framed separately from the page, so they are not shown your scholars, submissions or transcripts. We do not sell or hand any of your lab’s data to advertisers.

The full detail - what is collected, who processes it, how long it is kept and how to have it deleted - is in the privacy policy.

Researchify is built and operated by Kravos Tech Pvt. Ltd., a software company registered in India. We are a small team, we work directly with the labs using the product, and there is no support queue between you and the people who wrote the code.

That is deliberate, and it is the main thing the founding programme buys: the first 10 labs get 60 days free with no card, a rate locked for 3 years, and direct influence over what gets built next. We would rather have ten labs we talk to every week than a thousand we never hear from.

Free to start, with no card required. You can set a lab up, invite scholars and run real meetings before paying anything.

After that, plans are priced per lab per year by scholar count. Monthly billing is available, and paying annually costs the equivalent of ten months. Founding labs pay 9,000 rupees a year rather than 25,000. Current pricing is on the landing page, and the commercial terms are in the terms of service.

We answer our own email. If you supervise research and something here is wrong, or missing, or nearly right, we want to hear it - that feedback is what the roadmap is made of.

Reach us at info@kravos.tech or through the contact page.