A growing fintech's ops team had outgrown their off-the-shelf accounting stack but couldn't justify a full migration. They needed a thin layer that wrapped the existing system, added what was missing, and didn't break what worked. We embedded for a quarter.
Three decisions that shaped the build.
Wrap, don't replace.
We sat on top of their existing ledger. No data migration. No parallel-run risk. They could uninstall us tomorrow and not lose a row.
Power users wrote the spec.
We spent the first two weeks pair-shadowing the ops team. Half the v1 features came from screenshots we took watching them work.
Released weekly, not monthly.
Every Friday a real piece went live. The roadmap got rewritten three times based on what stuck.
What went live, and what it did.
They wrapped the system we already had instead of forcing a migration. Six weeks in, nobody on the team wanted to work without it.
Prayojana
An elderly care app that families actually open daily.
READ THE CASE STUDY →