A working CRM in eight days
A Singapore hospitality CRM maker, about to meet a serviced-residence group writing a tender for a new CRM, with Salesforce also in the room.
/work/bfnCame in new build
- System
- Hospitality CRM, working prototype for a tender
- Ask
- A prototype for commercial, operations, marketing and IT
- Region
- Singapore
The piece Four blocks on one plate, one bar through all four: four residences on the same record.
- 8daysbrief to working platform
- 4residencesin every copy
- 200%zoomaccessibility suite passed
- Every model calllogged with where it ran
The ask
A working prototype for everyone who would choose the system, built from what each of them needs.
The real problem
A demo made of screens loses to whoever has the most screens.
The group had to be able to use it on its own, with nobody from our side driving.
Screens, or one record
- Idle
- Live
- Strain
- Fail
A screen demoA demo made of screens, each one on its own, with someone from our side driving.
What we builtEvery channel lands in one list, every screen views the same record and each person gets their own copy.
What we built
We built it with AI on days 3 to 8 and checked it screen by screen against the five rules m-anant wrote down first. It opens on today's decisions, each with its evidence, options and owner.
Messages from WhatsApp, email, reviews and the front desk land in one list. A plain sentence describing an audience becomes rules you can read and edit. The AI earns more work one approval at a time.
How we made it hold
Every fact on screen shows its source and every model call shows where it ran, so the group can check what the system tells them.
Backstage The decisions behind the build, and the hardest problem
Decisions
Open on today's decisions.
Each with its evidence, options and owner, and every screen a view of the same record.
Let the AI earn more work one approval at a time.
Any approval can be reversed, and every model call and policy action is logged with where it ran.
A resettable copy for each person.
The meeting can run on the real product with no risk of one person's changes breaking another's demo.
Ruled out
A demo made of screens.
It loses to whoever has the most screens.
The hardest problem
The group had to be able to use it on its own, with nobody from our side driving. Every fact on screen shows its source and every model call shows where it ran.
The difference
- Eight days from brief to a platform the group can use without us in the room.
- A login for anyone in the group, each with their own resettable copy.
- The production build passes its full accessibility suite.
