Product at Complyance Engineering background
At Complyance, I work across the product experience for direct customers and partners. That includes country expansion, onboarding, platform and API flows, pricing, and the execution needed to make those pieces hold together.
Product at Complyance
Product core
Living systemScroll to change its state
Inside the system
The product sits at the centre. What surrounds it determines whether it works.
I separate written rules from what customers and local partners can actually use, so the unknowns are visible before a team commits to a launch.
The workaround nobody questions is often where the insight lives.
A green status can hide information in the wrong format or an invoice another system later rejects. I follow the work from onboarding through recovery, including the handoffs and failures between them. The unusual cases show whether the workflow was really understood.
Visible is not the same as valid.
Packaging does not end on a pricing page. It becomes access rules, usage limits, quote logic, and support work. I follow those choices into the product and ask what happens when usage runs out. The commercial idea has to survive implementation.
A test can prove a rule. It cannot approve a price.
What gets agreed eventually becomes engineering work, a country plan, or a promise to a customer. I keep the evidence, owner, and remaining uncertainty attached. That lets the team act without pretending every question has already been answered.
A decision is complete when the next person knows what happens next.
Case study · Field note · Publication
Selected thinking from my product work, plus the independent briefing I publish for AI product people.
How I replaced one readiness signal with four named gates, clear owners, and evidence that stays attached to the decision.
Read the case studyWhy a country rule can change onboarding, shared platform behaviour, partner APIs, operating evidence, and the promise a commercial team can make.
Read the noteA weekly, evidence-aware briefing on the AI changes that may alter a product decision. Each story ends with a posture: act, discuss, or monitor.
Read the latest issueHow I work
Product decisions here reach regulation, data, APIs, operations, and support. I stay close to those details before simplifying the experience.
The visible feature is usually one part of a longer path through regulation, data, APIs, operations, and support.
My engineering background helps me challenge abstractions, work directly with implementation details, and make better tradeoffs.
CurrentlyProduct at Complyance
Background
I started in software engineering, working close to the code and the people using it. Over time, the questions I cared about moved outward: which problem deserves attention, how the whole journey fits together, and what tradeoff the business can defend.
That path now informs my work at Complyance. I can move between a customer workflow, an API contract, a country requirement, and a pricing assumption without treating them as separate worlds.
Earlier engineering work on GitHubGet in touch