We take overadmissions process end to end so growth stops needing new hires... tracking, deadlines and conversions, so fewer seats remain unfilled... detailed marketing tracking so you stop paying for clicks that never convert... your admin work so your people can focus on teaching and delivery... growth engine so your intake scales without your admin scaling... payment follow ups and bank reconciliation so only genuine problems reach finance... inbound queries so your front desk stops answering the same question...
Infi is the record of what happened, and the engines that act on it. One record of every family, from first enquiry to last payment.
The platform wall
We name every system we touch,and label the ones we have not touched yet.
Messaging and the outbox
In buildStudent and school systems
PlannedIdentity and documents
In buildPayments and banking rails
In buildAnalytics and tag management
PlannedThe stack Infi runs on
Integrated- Integratedrunning today, in code you can read
- In buildthe interface exists, the connection is not live
- Planneda target, nothing is wired yet
The living system
Always online.
Always connected.
Every engine reads and writes the same record, so a change in one place is known everywhere at once. Ask in plain words and the answer comes back with the rows it stood on, which is how you check it.
In this field right now
- Enquiry00
- Document00
- Invoice00
- Approval00
- Exception00
- Duplicate00
- Admissions
- Collection
- Concierge
- Lead Administration
- OutreachEarly
- Delivery QAEarly
- LogisticsEarly
- Delivery StandardsEarly
The work in this field
Six kinds of work, each drawn with its own mark and its own clock. An exception does not pulse at all: it holds, because it is waiting on a person.
- Enquiry from a parent. Enquiry. Arrives, and does not linger.
- Open day registration. Enquiry. Arrives, and does not linger.
- Sibling of a current student. Enquiry. Arrives, and does not linger.
- Transfer enquiry, mid year. Enquiry. Arrives, and does not linger.
- Agent submitted an applicant. Enquiry. Arrives, and does not linger.
- Passport page uploaded. Document. Sits on the record and is read again and again.
- Previous school report. Document. Sits on the record and is read again and again.
- National ID on file. Document. Sits on the record and is read again and again.
- Proof of address. Document. Sits on the record and is read again and again.
- Immunisation record. Document. Sits on the record and is read again and again.
- Examination board transcript. Document. Sits on the record and is read again and again.
- Fee invoice raised. Invoice. The slowest clock. A life measured in weeks.
- Instalment plan agreed. Invoice. The slowest clock. A life measured in weeks.
- Payment rail credit matched. Invoice. The slowest clock. A life measured in weeks.
- Scholarship discount applied. Invoice. The slowest clock. A life measured in weeks.
- Offer approved by the registrar. Approval. The only mark that leaves the point. Something was released.
- Place accepted. Approval. The only mark that leaves the point. Something was released.
- Interview slot confirmed. Approval. The only mark that leaves the point. Something was released.
- Nothing sends without a person pressing send. Approval. The only mark that leaves the point. Something was released.
- Date of birth does not match. Exception. Holds. It is waiting on a person.
- Document expired. Exception. Holds. It is waiting on a person.
- Payment received, no invoice. Exception. Holds. It is waiting on a person.
- Two records, one student. Duplicate. A second copy of a document, so it takes the document colour.
- Same family, two references. Duplicate. A second copy of a document, so it takes the document colour.
It starts at the first enquiry
Long before anyone is a student. The products we read begin at enrolment, when the record already exists.
One thread, one trail
One applicant record, one message thread, one audit trail underneath all eight engines.
It is yours
Your rows, your campuses, your exception history. Nothing pooled with anyone else.
Mission
Give an institution one record of every family it deals with, and give every family a way to see where they stand.
Vision
Administration that runs itself under supervision, so the people are free for teaching and for the families.
The record starts at the first enquiry
Long before anyone is a student. No system you own keeps that record.
We read one network's own registration endpoint on 18 August 2026, and again on 20 August 2026. Of 152 campuses, fourteen returned no class list, so a parent choosing one could not finish the form. Nobody inside the network had raised it.
- Campuses live
- 152
- Form could not be finished
- 14
One estate. 152 campuses. Read 18 Aug 2026, re-read 20 Aug 2026.
Not a CRM
A CRM manages the data you already have.
Not a fee and attendance product
Those begin at enrolment. This begins at the enquiry.
Not a payment rail
Yours already moves the money.
The judgement stays with the people
The work goes to the system.
Messaging infrastructure
Messages a system writes.
A person still lets them go.
Reminders, deadlines and receipts are what families actually read. Infi drafts them against the record, in the language on the record, and puts every one in one outbox. Then they stop. Nothing sends without a person pressing send, and the release is recorded against a name and a time.
Example thread. No carrier is connected and nothing here was delivered to anybody.
Yesterday
Hello. We are completing the application for the September intake. Is anything still missing from it?
Today
- Drafted
- Held
- Released
- Queued
Good morning. Two items are still outstanding on the application: the previous school report, and proof of address.
Approval trail
- nothing released yet
An example. No carrier is connected, and no message shown here reached a family.
- 01Live
Drafted against the record
Written from the record: the item outstanding, the date that closes, the invoice that settled. Nobody starts at a blank box.
- 02Live
Held at one gate
A named second person releases every draft, and no path through the outbox skips it.
- 03Live
The language sits on the row
A template carries its language on the record, so a family’s version and the English one are the same row read twice.
- 04Q1 build
Sent from your own account
Through the account and number the institution already publishes, not one we own. The interface refuses loudly until a carrier is configured.
Payments, reconciled
A payment lands. The engine names the invoice it settles, or says it cannot tell.
Every incoming line is read against the institution’s own fee invoices: reference, amount, name, date. Most settle themselves. Watch the last one.
Six incoming bank payments are read against six fee invoices. Five settle themselves. The sixth carries a short reference that repairs onto two live invoices belonging to two students with the same family name in the same intake, so the engine attaches nothing and holds it for a person to decide.
statement file, as it arrived
fee invoices, live
One short reference repairs onto two live invoices equally well: same amount, same due date, same family name, same intake. Neither finishes clear of the other, so nothing is attached, no seat is released, and a person decides which one it is.
Nine outcomes, because a queue is worked differently for each one
two of them appear aboveAn unmatched payment comes back unmatched. Attaching it to the closest looking record would read somebody else’s fee as paid and release their seat. Nothing sends without a person pressing send.
Every name, reference and amount on this panel is invented for the illustration. No institution’s records appear here.
One record, wherever the campus is. Infi is built for institutions across the UK, Europe and Asia.
Agentic architecture
Agents do the queue. A person still signs the message.
Work lands all day from every front door you have. Agents read it, chase it, match it and draft the reply. Then everything stops at one gate, and a named person decides whether it goes.
The work lands all day
- new enquiry
- document uploaded
- unpaid fee invoice
- unmatched payment
- duplicate family
Every front door, one queue, one record underneath it.
Agents work it, your staff do not
- Chase the missing documentdone
14 families, 3 campuses
- Work the payment that will not tie outdone
reference not recognised
- Rebuild the register a person retypeddone
one session, one campus
Each is a job somebody does by hand today, on a list, in the evening.
One gate, and a person holds it
Drafted for a parent
Two documents still outstanding for the September intake.
Awaiting approval.
Nothing sends without a person pressing send. The approval is recorded against a name.
Approved, and nothing left the building. This is an example.
It goes, and the trail is written
- ✓queued
- ✓sent from your own account
- ✓logged with the approver and the time
- not delivered, the dispatch is simulated
The queue, the approval and the log are real. The send is not.
The retrieval layer
An answer, with the rows it stood on.
Retrieval runs over your own record. No pooled corpus, and no model trained on another institution's families.
A question in plain words
which offers lapsed at North Campus last intake|
Asked by a campus officer, not by an analyst.
Read out of your own record
- APP-4471offer issued
- MSG-2210reminder approved
- APP-4471offer lapsed
- PAY-8815invoice unpaid
- AUD-9902seat released
- APP-4478offer accepted
- MSG-2255draft, not sent
- CMP-0031North Campus
- PAY-8820receipt matched
Your rows. Your campus. Nothing pooled with anyone else.
With the rows it stood on
Three offers lapsed. One seat was released and is still open.
An answer without its rows is a rumour.
How it learns
The audit log comes first. The models come last.
Each step is labelled with what it is today.
- 01Live
Your audit log
Every action, with the actor and the time on it.
- 02Q1 build
Repeated sequences become a shortcut
Offered to a person. Adoption counted. Declined twice and it stops offering.
- 03Roadmap
After one full cycle, models
Lapse risk, arrears conversion, offer yield, seat forecast. Trained on your history.
The models need one full cycle of your data before they are worth anything. The first 90 days are about the record.
Built for estates
Institutions the size of an estate.
What you buy
Eight engines. One hundred and fifty six inside them.
Open one to see the delivery engines inside it, each marked with whether it runs today.
Admissions
59 delivery engines insideThe deepest of the eight. Every top ranked engine sits here.
- Registration health across 152 campusesLive
- Applicant record, one per familyLive
- Seat recovery queueLive
- Identity document reader, one vision model callLive
- Eligibility and the two age cutoffsQ1 build
- Offer lapse risk, trained on your own historyRoadmap
- Seat inventory and the weekly enrolment boardRoadmap
Underneath all eight
14Records and Access12Estate and Franchise11Reporting and Forecasting7Platform and OnboardingLive, or a slide
You can always tell which is which.
Not a disclaimer at the bottom. A design element, on every engine and every screen.
- Registration health across 152 campuses
- Bank reconciliation, nine named match outcomes
- Applicant record, campus register, seat recovery queue
- Draft, approve by a second person, then queue
- Masking computed by the database, reveal logged
- Identity document reader, one vision model call
- Thirty day identity retention register
- Audit trail on every action
- Shortcut mining over the audit log
- Background agents that assemble a whole case
- Models trained on your own admissions history
- Live dispatch through your Meta business account
- Arrears board by family, campus, class and age
- Seat inventory and the weekly enrolment board
- Applicant status page on a verified mobile number
Who it is for
Institutions the size of an estate.
One brand across many sites, two intakes a year and a payment rail the institution already owns. That is the shape every engine on this page was built against.
152
campuses, one brand
Sites on a shared name, where no two we compared held the same class list or fee schedule.
2
intakes a year
Two annual sessions with different age cutoffs, so two live cycles across one estate.
1
payment rail, already yours
By the rail's own published rule a payment can take 24 hours to show, so who is clear today is a day-old answer.
All three figures come from the one estate we read, on the dates we read it. Not a market size, and we have not measured a second estate.
Work with us
Be the design partner.
And tell us six numbers we do not hold.
None of the six appear anywhere on this page, because we cannot check them yet. Only an institution running the intake knows them.
- annual registration volume
- the online share of it
- registration to test, and test to enrolment
- call and walk-in load at the campus office
- how often a campus is full
- the owned versus franchised split
The pilot
Ninety days as a design partner. The record first, the models after.
The pilot is not about the models. It is about one honest record of your admissions, in one place, with a name and a time against every action in it.
90days
One admissions cycle, first enquiry to last payment. Every screen says whether it runs today or is designed.
- One applicant record per family, across every front door.
- An audit trail with the actor and the time on every action.
- Nothing sends to a family without a named person pressing send.