Finance
Insta Fincorp
A platform for handling money and everyday financial tasks
Key outcomes
- Delivered the product on schedule, with clear goals agreed before the work began
- Reduced rework by agreeing scope and priorities before any build started
- Kept each launch steady and predictable through close coordination between teams
The problem
When money is involved, you cannot just push out updates and hope for the best. Insta Fincorp needed to handle customer accounts, payments, reports, and other sensitive tasks, and do it reliably, release after release, without ever putting security or record-keeping at risk.
What I did
- Ran the whole project, from working out what was needed, to planning the work, testing it with the client, releasing it, and keeping everyone informed along the way.
- Kept a close eye on the risks and on how the different parts depended on each other. In a money business, a missed connection between two features is not a small slip. It can turn into a serious problem.
- Watched progress constantly so releases stayed steady and predictable, and the business could plan around them.
Why it was tricky
The payment features were all linked. Change one thing and it could ripple into the reports, the account balancing, and the security checks. Keeping an up-to-date picture of what affected what, and being honest about the risks, was the difference between calm, steady releases and constant firefighting.
How it turned out
The platform is live at instafincorp.com, with steady and dependable releases where security really matters, and risk tracking clear enough that everyone felt confident each time we went live.
A sample of my work
Illustrative only. It contains no confidential client information.Delivery board
A view of the board I used to keep the work visible and moving.
To do 2
-
Upload of identity documents
New feature -
Exporting account statements
New feature
In progress 2
-
The loan application process
New feature -
Matching of payments
New feature
Client review 1
-
The sign up screens
Awaiting client approval
Completed 2
-
Sign in and user permissions
Delivered -
The main dashboard
Delivered
A sample of my work
Illustrative only. It contains no confidential client information.Risk and issue log
How I tracked the risks and dependencies on a finance platform where security and accurate records matter most.
| ID | Type | Item | Impact | Owner | Status and response |
|---|---|---|---|---|---|
| R1 | Risk | A change to one payment feature could affect the reports and account balances. | High | Project Manager and development lead | Managed. The dependencies were mapped and each change was reviewed before release. |
| R2 | Risk | Security and access controls must hold at every release. | High | Development and testing teams | Managed. Security checks were part of every release, not left to the end. |
| D1 | Dependency | The payment service must be available and tested before go live. | High | Development team | Tracked. The connection was confirmed and tested ahead of each release. |
| A1 | Assumption | Releases follow a steady, agreed schedule the business can plan around. | Medium | Project Manager | Confirmed with the client at the start. |