Imagine having a team
that never guesses.
You never build it, never brief it and never manage it. Every answer it gives you traces back to the thing it came from — a document you uploaded, a rule a university published, an assessment you sat.
One shared intelligence.
A student's team
12 specialists · 7 working todayReads what you upload, works out where you can actually get in, and turns all of it into something you can show. Every member hands its work to the next, so you explain yourself once. Free, forever, and never for sale.
See a student's teamA university's team
5 specialists · 2 working todayWorks the pipeline you already have, forecasts where your intake lands, and reaches students who genuinely fit your published rules — never touching what a student is shown. Reachable from your own systems over a REST API, an OpenAPI spec and an MCP endpoint.
See a university's teamAn employer's team
5 specialists · 2 working todayFinds people whose claims already have documents behind them, and briefs you from evidence the candidate agreed to share. Consent-gated end to end, and reachable from your own systems over a REST API, an OpenAPI spec and an MCP endpoint.
See an employer's teamA student's team
Free, forever12 specialists · 7 working todayA university's team
Subscription · commission on outcomes5 specialists · 2 working todayAn employer's team
CTIP5 specialists · 2 working todayThey hand work to each other.
Three teams, but not three products. An employer sets a real problem and it reaches the students who fit it; what they build becomes proof; the proof is what makes them findable. Here is that circle closing.
An employer puts a real problem up — not a job ad, an actual piece of work.
It goes to the students whose profile and evidence genuinely fit it. Nobody is spammed.
What they build lands on their own file as proof, with provenance attached.
That proof is exactly what deep search reads — so the employer meets someone they have already watched work.
What passes between them is never a list of people. It is one student's evidence, moving under consent they gave and can withdraw at any time. That is the only reason this circle is allowed to exist — and the reason a competitor cannot assemble it from three separate products.
Nobody on this team can be bought
Verdicts are computed from rules universities publish. There is no dial anyone can pay to turn — not a lower one, not a higher one. A university relationship can never reach a student-facing verdict, match score or recommendation, and a build check fails the day that stops being true. That is why a student's team is free forever without being for sale.
Fair questions
Are all of these working today?
No — 11 of the 22 work today. The rest are marked with a dashed border and each one says what unlocks it, so you can tell at a glance which is which. We would rather show you where this is going than quietly ship a shorter list.
Do I have to set any of this up?
No. You never build the team, never brief it and never manage it. You upload your documents and sit one assessment; every member works from that same file, and hands work to each other without being asked.
Can a university pay to change what a member tells me?
No. Verdicts are computed from rules universities publish, and there is no dial anyone can pay to turn — not a lower one, not a higher one. A commercial relationship can never reach a student-facing verdict, match or recommendation, and a build check fails the day that stops being true.
Can I reach the team from my own tools?
It was designed as an open system rather than a closed product, so the team is reachable from outside it. For universities and employers that is open today: your organisation's key opens the same typed capabilities the desk itself uses — over a REST API, an OpenAPI spec, and an MCP endpoint your own agents can call — scoped to exactly what that key may see. The student capabilities exist in the same registry and the desk calls them every day; what does not exist yet is a key a student holds themselves. That door is deliberately shut, not unfinished — it opens when a student can see and revoke that access for themselves, because a key to your own file is only yours if you can take it back.
Could my team reach me where I actually am — WhatsApp, or a message?
That is the intention, and the platform already knows the shape of it. Your desk names WhatsApp and Zalo today and says exactly what each one is waiting on. Of WhatsApp it says: the channel rail — specified, not built, and it will ask for your number and your yes before a single message. Nothing is sent anywhere until a channel is opened, and opening one is your decision, per channel, and revocable. A team that reaches you where you live is only worth having if it can never reach you where you did not invite it.
Is this one AI, or really separate members?
Separate members, one file. Each has its own machinery, its own preconditions and its own output — open any member page to see what it produces and when it can act. What they share is your student file, which is why the answer one gives is consistent with the answer another gave last week.
Put your team to work.
Start freeEvery member of a student's team is free, forever. No card, and you can erase everything whenever you want.