Your students already write with AI.
Your institution can’t see any of it.
Most of the AI use on your campus is happening in consumer chatbots your department has no policy over, no visibility into and no record of. Tesify gives students structure, citations and originality checks inside a workspace your institution defines. Students write every word — you keep the oversight.
Sound like your campus? 😮💨
Three problems land on the same desks in almost every institution right now.
Policy that can’t keep up
Each faculty has written its own AI rule, students get different answers depending on who they ask, and nobody owns the version that counts.
A growing integrity caseload
Cases take weeks, rest on contested detection scores, and the panel spends its time arguing about tooling instead of scholarship.
Tool sprawl
Overlapping licences across departments, renewal dates nobody tracks, and no clear read on which of them students actually open.
What your institution actually gets 🎒
Support that reaches the cohorts your writing centre cannot staff one by one.
Structure students follow
A chapter framework that matches your programme’s thesis guide, so supervisors stop re-explaining the same skeleton every term.
Originality at cohort scale
Students check their own work before submission, so weak citations get fixed at draft stage rather than becoming an integrity case.
One citation standard
Your faculty’s house style applied across the whole cohort, which removes the formatting corrections that eat supervisor review time.
Deployment on your terms
Built with GDPR-readiness, FERPA-awareness and SSO and LMS integration as explicit design goals. We will walk your DPO through the detail.
Evaluate it the way you actually buy 🚀
No tender required to find out whether it works. Start with one department.
Scope a pilot 🎯
We agree the cohort, the term and what you want to learn — supervisor hours saved, draft quality, integrity referrals — before anything is signed.
Run it with one cohort 📊
One department, one term. Your IT and data protection teams review deployment while students use it on live theses.
Decide with evidence ✅
You take the pilot’s results to committee and decide whether to extend. If the answer is no, it stops there.
With integrity, always 🤝
Built for GDPR-readiness, FERPA-awareness and SSO and LMS integration. These are design goals we will evidence during your review, not certifications we claim to hold — and we would rather you hear that from us than discover it in procurement.
What Tesify is
- A workspace that organises a thesis into chapters and moves students through one at a time.
- An assistant that suggests improvements on what the student already wrote.
- Citations and references in your faculty’s house style, built automatically.
- An originality check the student runs themselves, before submission.
What it is not
- It does not write the student’s text: every sentence is theirs.
- It is not an AI detector and does not tell you who used a chatbot.
- It does not erase matches or “guarantee” a similarity percentage.
- It does not replace your academic integrity policy or your panel’s judgement.
What procurement always asks 🤔
🔐 Who owns the work students create?
The student does. Their thesis is their intellectual property and stays that way. We do not sell it, we do not share it with third parties, and we do not use student work to train artificial intelligence models. Your institution’s own rights over student work are governed by your regulations, not by us.
📄 Can you sign a data processing agreement?
Yes. A DPA is part of the standard institutional deployment, and we expect your data protection officer to review it before a pilot starts. Bring your own template if you prefer to work from it — most universities do, and we would rather review yours than argue about ours.
👁️ What can supervisors and administrators actually see?
Whatever your institution configures during deployment, and nothing beyond it. The default is that the supervisor sees the student’s document and its citations — the same thing they would see on paper. Cohort-level reporting is available where you enable it. We do not surface anything you have not switched on.
🧪 What does a pilot actually involve?
One department, one term, one cohort. We agree in advance what you are measuring — supervisor hours, draft quality, integrity referrals — so the decision at the end rests on your evidence rather than our demo. There is no obligation to continue and no charge for the pilot itself.
💷 What does it cost?
Institutional pricing is scoped per pilot — no public price list yet. What it depends on is cohort size, deployment scope and whether you want SSO and LMS integration. We will give you a written figure before you take anything to committee.
🤖 Does this detect AI-written text?
No, and we would be careful with any vendor who says theirs does reliably. Tesify is not an AI detector. It reduces the problem from the other direction: students work inside a structured environment with citation support and their own originality check, so there is less reason to reach for a chatbot and more of a record of how the work developed.
🔗 Does it integrate with our LMS and SSO?
SSO via SAML and integration with the major LMS platforms are supported deployment paths, and we scope the specifics with your IT team during the pilot rather than promising a one-click install. Tell us your stack in the first conversation and we will tell you honestly what the work involves.
🎓 Does this replace our Turnitin or iThenticate contract?
No, and it is not sold as a replacement. Those are submission-point detection systems; Tesify works at the drafting stage, before anything is submitted. Most institutions run it alongside an existing detection contract, and we would rather sit next to your incumbent than ask you to unpick a renewal.
Start with one department.
Decide with evidence. 💪
Scope a pilot with a single cohort this term and take the results to your committee.
Request an evaluation