Private beta · Singapore
Rosters that staff themselves.
Scheduling for agencies, roadshow teams, swim schools and freelance collectives. Build the event once; the engine proposes who works it, the crew accepts on their phones, and the hours come out the other end as an invoice and a contractor statement.
We are onboarding a small number of operators before general release.
Week roster
Mon
Tue
Wed
Thu
Fri
Sat
Sun
14
15
16
17
18
19
20
Confirmed
Still open
Draft
How it works
One event, three people who need different things from it.
Everybody signs in at the same place and sees the part of it that is theirs. Nothing about the other two is visible to them, and that is enforced by the database rather than by the screen.
The office
Build it once, staff it in a click
Create the event, set the positions, rates and skills, and let the auto-assignment engine propose a roster. It shows you why each name is there and what rule it had to bend — and a bent rule is one you have to agree to by name.
The crew
Accept on a phone, clock in at the venue
Offers arrive with pay, place and time. Accept, decline with a reason, or ask the team to cover one you cannot work. Clock in inside the geofence; your hours and what you earned are yours to see, all the way to the statement.
The client
See your sessions, move one, join the list
Parents and account contacts see the sessions they booked, request a reschedule, and take a place on the waiting list when a class is full. When a seat comes back, it is offered to them — never booked on their behalf.
What's different
Most of this product is the awkward parts other rosters leave to a spreadsheet.
The scheduling is table stakes. What takes the work off somebody's evening is everything that happens around it.
01 · the engine
It shows its working
Every constraint is one of three things: hard and never bendable, overridable with a reason on the record, or soft and merely scored. An override covers only the violations you were actually shown — never one that appeared afterwards.
02 · freelancers
Nobody is double-booked, even across agencies
A freelancer working for three agencies on the same platform cannot accept two overlapping shifts, whoever offered them. That is one constraint in the database, not three policies that have to agree.
03 · money
Commission, and the jobs that cost the worker to attend
Pay by hour or by shift, commission on results by whichever of three parties is actually paying, and the roadshow booth where the worker pays a participation fee. A cost never looks like an earning on screen.
04 · compliance
A switch, not a sermon
Right to work, certificate expiry, rest days and hour ceilings are enforced only by the organisations that turn them on. When one is on, a lapsing licence is a warning weeks out — not a hard block on the morning it matters.
05 · getting paid
A locked month becomes paper
Lock the pay period and every figure freezes. Out come one invoice per client and one contractor statement per worker — GST on the invoice where the agency is registered, and never on the worker's side, where it is not the agency's tax to charge.
06 · honesty
A projection never looks like a fact
Every derived figure carries how it was reached, and says what it could not count: shifts with no rate, hours not yet recorded, lines it could not bill. A number that hides its gaps is the one that gets somebody in trouble.
Built here
Singapore is not a localisation setting.
Most scheduling software is built for employees on a payroll. The crews here are self-employed, paid on commission, and often working for several agencies in the same week. That changes what the software owes them.
- Contractors, not employees What a hirer owes a self-employed person is a payable, so the artefact is a contractor statement — not a payslip, and no CPF the hirer does not owe.
- GST belongs to the seller Registration, rate and number live on the organisation. Rates can be entered inclusive or exclusive, and the registration number is stamped on every invoice.
- Work passes are a first-class field Permission to work is tied to an employer and expires. Both the block and the warning are built in, for the organisations that need them.
- PDPA by construction No national identifiers are held. Contact details are visible only to people who share a job with you, and every access rule is enforced in the database.
Where we are
The hard half is built and proven.
We built the data layer first — the rules about money, consent, capacity and access — and made it prove itself before a single screen existed. The application is in build now, and we are taking on a small number of operators alongside it.
- Data layer
- Complete and verified
- Checks
- 538 behavioural checks passing
- Engine
- Specified, inputs live
- Application
- In build
- Region
- Singapore (ap-southeast-1)
Run a crew that deserves better than a spreadsheet?
Tell us what you staff, how many people, and what breaks first. If it is a fit we will put you on the early-access list and come back with dates.