Draft. Replace the text in [brackets] with real details the client has approved before publishing.
Where they were stuck
[In a few plain sentences: what wasn't working before. For example, staff were matching payments by hand in spreadsheets, and new customers waited days to be approved because documents were checked by email.]
What made it tricky
- It's real money. Every payment has to be counted exactly once, even if the internet drops halfway through.
- Strict rules. Banks and regulators require proper identity checks and an audit trail. [Add any specific deadline or audit.]
- [Any other limits: budget, launch date, systems we had to connect to.]
What we built
A secure online platform where business customers can send, receive and track payments, plus an online sign-up that checks identity automatically. [Add two or three decisions you made and why, in plain words.]
For your tech team
Next.js front end, FastAPI services, PostgreSQL double-entry ledger with idempotent transactions, automated KYC/AML checks, deployed on AWS ECS with CI/CD and infrastructure as code.
What the client got to keep
- The written plan and designs for every screen
- All the code, in their own GitHub account
- Hosting in their own Amazon (AWS) account, with step-by-step guides
The result
[A result the client will confirm, e.g. "Now handles over $140M in payments a year with almost no downtime" and "New customers are approved in X minutes instead of Y days".]