DomainFintech & critical product
In briefMake financial products safer without freezing growth.
I connect architecture, security, compliance, reliability and roadmap decisions for financial or regulated products.
Chapter 1 · Findings
Incidents or bugs have immediate customer, financial or regulatory impact.
The roadmap keeps moving, but every change touches sensitive business rules.
Leadership has to balance speed, compliance and robustness without clear tradeoffs.
Technical debt makes audits, integrations or product changes riskier.
Chapter 2 · Case files
Chapter 3 · Warning signs
Incidents are fixed quickly but keep returning in another form.
Critical business rules are understood by only one or two people.
Audits or integrations trigger urgent fixes.
Leadership senses risk but lacks a reliable technical read.
Chapter 4 · Inspection
Critical flows: payments, tax logic, reporting, data and access rights.
Architecture areas that expose reliability or compliance risk.
Testing, monitoring, rollback and incident practices.
How product/risk tradeoffs are documented and decided.
Chapter 5 · Intervention
Map critical risks
I separate technical irritants from risks that can cost money, compliance or customer trust.
Prioritize without freezing growth
I sequence the work so the foundations become safer without turning every issue into a rewrite.
Make decisions legible
I translate technical options into business impact: risk, timeline, cost, trust and future capacity.
Chapter 6 · Answers
Is this only for fintech companies?
No. The same logic applies when data, money, compliance or customer trust make mistakes expensive.
Have you led engineering on a financial product?
Yes. I was Head of Engineering at Gridky for 5 years: more than 40,000 properties, 12 tax regimes, banking-grade security requirements and three product lines (Real estate, SCPI, Insurance). The reduction in production bugs is estimated at around 80%, as qualified in the Gridky field account.
Do you have to freeze the roadmap to make the product reliable?
Not for long. At Gridky, the Drynuary paused new features for a month and a half. Test coverage went from 10% to 50%, and the testing requirement stayed in place once the roadmap resumed.
Next
A tool to prepare the conversation, a diagnosis to understand the context, and support to take action.
Hundreds of Slack exceptions every morning, a team split in two, a priority client waiting. Then a month without a single new feature, negotiated with the CEO. I still stand by it: in my view, the most profitable decision of the year.