BTSE Crypto Exchange
Back-office tooling and the data pipelines underneath it for a global crypto exchange — the part of an exchange its customers never see and its finance team lives in.
- Client
- BTSE
- Sector
- Crypto exchange
- Scope
- Back office · Data pipelines
- Status
- Shipped
An exchange settling institutional clients has to answer one question every month, per client, without argument: what is owed, and how was it worked out. BTSE was answering it in spreadsheets assembled by hand from several systems.
We built the invoicing side of the back office — client and fee configuration, a calculation that shows its own working line by line, and a settlement summary a client can be sent as it stands.
Invoice management, fee configuration, and the breakdown that explains a settlement.
Discovery before specification
Before a feature was specced we watched people do the job it replaces. The spec usually changes after that, and it is cheaper to change it then.
A shared channel, not an account manager
The client had a channel with the engineers writing the code, and a standing invitation to the morning standup.
Something on staging every week
Work was judged by using it rather than by reading a percentage. Two-week plans, re-planned on Fridays, so a wrong assumption cost a sprint instead of a quarter.
Reviewed, tested, handed over
Every change was read by a second engineer before it merged. Tests, a README and a recorded walkthrough came with the handover.