Why we built Fumitsuu One.
Recruitment fairs are where months of hiring work actually get decided. The software around them was still spreadsheets, paper, and goodwill. We built Fumitsuu One to replace that.
The software around recruitment fairs was always the weak link.
A recruitment fair is where a candidate and a school recruiter meet, talk, and come away with a decision that would take weeks of email otherwise. That matters.
The tools supporting those events were a patchwork: a Google form for registration, a spreadsheet for booth assignments, a handwritten list for check-in, a separate tool for interviews, and an email thread holding the rest together. The useful part of the day kept getting lost in the infrastructure.
Fumitsuu One is the system we wanted when we were running these events ourselves. One platform, one data model, and one live state underneath everything.
Four principles underneath the platform.
Every role, same data, same clock.
Organisers, schools, recruiters, candidates, and staff all look at the same live state. No exports, no nightly sync jobs, no parallel spreadsheets to reconcile at the end of the day.
An event is a state machine, not a checklist.
The phase engine moves a fair through Arrival, Session, Fair, and Interview. Features unlock by phase, so the platform guides the day without anyone needing to remember what happens next.
Vacancies, interest, and outcomes have structure.
Every vacancy carries 40+ structured fields. Every expression of interest has a status. Every interview has a duration, a booth, and an outcome. The paper trail is implicit.
Your own platform, not an inbox.
Every organisation on Fumitsuu One runs on its own subdomain, with isolated data, branding, and billing. You're not a row in someone else's CRM.
A modern stack, on purpose.
Better than last year, starting now.
Build an organisation, list your school, or create a candidate profile. Every event on Fumitsuu One is one more piece of the platform.