Case studies
Three platforms we designed, launched and still operate. Real context, structural decisions, measured results - and what remains open.
Ndjanguih
Moving association management out of shared spreadsheets
1
Single source of truth
0
Dues spreadsheet left
24/7
Self-serve member access
- Web
- SaaS
- Cloud
- Automatisation
Context
Associations track members, dues and rotating savings in duplicated spreadsheets: nobody knows who paid, treasury is rebuilt by hand and every committee handover starts from scratch.
What was blocking
- Dues tracked across several files, with no reliable history
- Rotating savings cycles computed by hand, a source of disputes
- No trace of decisions or committee mandates
Our intervention
Member registry and roles per mandate
Dues, reminders and receipts automated
Rotating savings cycles computed and logged
Audit log and mandate handover
ConciergeX
Regaining control over maintenance requests
100 %
Requests traceable end to end
1
Official channel instead of three
SLA
Response times measured, not guessed
- Mobile
- Web
- Cloud
- Intégrations
Context
Requests arrive by phone, email and text. Work orders live in people's heads, delays go unmeasured and owners ask for a status update every week.
What was blocking
- Fragmented intake channels, duplicates and lost requests
- No formal prioritization of emergencies
- No way to prove response times were met
Our intervention
Single intake desk for all requests
Priority matrix and target response times
Mobile field tracking with photos and sign-off
Dashboard for owners and managers
PrestaGo
Fitting provider booking into one single journey
2
Two sides served: client and provider
0
Calls required to book
48 h
From search to service
- Marketplace
- Web
- Mobile
- Paiements
Context
Finding the right provider meant endless phone back-and-forth: uncertain availability, case-by-case pricing and no follow-up after the appointment.
What was blocking
- Availability never up to date, missed appointments
- Hard to establish trust between client and provider
- No data on actual demand per service
Our intervention
Search by service, area and availability
Calendar and automated confirmations
Verified profiles and post-service reviews
Demand and conversion tracking
Constants
What these three dossiers share
Beyond sectors, the same working rules come back from one engagement to the next.
A short initial scope
Every dossier started with a production-usable subset, not the full platform imagined at the outset.
Process before tooling
We wrote the real flow - who does what, in what order - before opening a code editor.
Sensitive data framed early
Access, isolation and logging are set in the first version, never bolted on after launch.
Ownership after launch
These platforms are operated, fixed and extended: living products, not closed deliveries.
How to read them
How we document a case study
Every dossier follows the same structure, so you compare situations rather than promises.
- 01
Context and constraints
What existed before, who used it and what was actually blocking - without rewriting history.
- 02
Structural decisions
The choices you can't undo: data model, identity, isolation, integrations.
- 03
Delivery in slices
A first useful release, then increments measured with real users.
- 04
Results and what's next
What changed, what stays open and the roadmap we own going forward.
Does your situation look like one of these dossiers?
A 30-minute session is often enough to name the real blocker and size the first useful slice.