Software we run ourselves.

Two applications, both written for edtech, both in daily use inside Ucanly before we offered them to anyone else. Sold as a deployment on your own domain and your own database — not as a seat on ours.

Book a demo

Ucanly Sales CRM

The counsellor desk, the manager’s sheet and the follow-up, in one place.

Built for edtech admissions teams. Leads arrive, get allocated to counsellors, get called, and turn into enrolments and payments — with the manager able to see all of it without asking anyone for an update.

What it does See a demo

Ucanly Marketing CRM

Send email your students actually receive, and see what happened to it.

Contacts, lists and segments, a campaign builder, automations, and the deliverability work most tools leave to you — SPF, DKIM and DMARC checks, suppression handling and one-click unsubscribe built in rather than bolted on.

What it does See a demo

Side by side

Which one do you need?

Most institutes end up running both, because they solve different halves of the same problem: one talks to people who have already raised their hand, the other reaches the ones who have not. But they are sold separately and neither needs the other.

	Ucanly Sales CRM	Ucanly Marketing CRM
What it is for	Working a pipeline of enquiries until they enrol or close.	Reaching a list of people by email, and knowing what happened.
Who is in it daily	Admissions counsellors, and the manager allocating their work.	Whoever writes and sends the mail. Usually one or two people.
What it usually replaces	A shared spreadsheet, plus a WhatsApp group for handovers.	A per-seat mail tool, or sending from a personal inbox.
The thing it is strict about	Who owns each lead, and when it was last touched.	Authentication and list hygiene, so mail actually arrives.
Where your data lives	Your own subdomain and your own MySQL database. Not shared with another institute.
What it needs to run	Ordinary PHP and MySQL shared hosting. No Composer, no SSH, no container platform.
What it needs from you	A domain to send from, if you want it emailing students.	Your own AWS account for sending, and DNS access to verify it.

Commercials

How it is sold, and what you are responsible for

We would rather you knew the shape of this before a call than after one.

Your domain, your database

Each customer gets their own deployment: your subdomain, your MySQL database, your AWS account for sending. Your student data does not sit in a database shared with another institute.

Runs on ordinary PHP and MySQL shared hosting.

We install and hand over

We deploy it, run the installer, connect your sending domain and create your first admin. After that the app applies its own updates from its admin panel when we ship a new version.

Best when you have a team already working leads or sending mail, and want to stop doing it in spreadsheets.

Pricing is per deployment

Quoted against the size of your team and how much of the setup you want us to do. We publish no price list because no two of these deployments have been the same.

Priced on request, agreed in writing before any work starts.

Two things to know before you buy. Each install serves one organisation — there is no shared tenancy, which is the point above about your own database, but it also means a second brand means a second deployment. And the email templates ship with Ucanly’s own wording; re-branding them for your institute is part of the handover rather than a switch you flip.

Next step

Have a look at a working one.

Both products have a demo environment loaded with invented data. Tell us which one you want to see and we will send you a login.

Book a demo Talk to us first