My contribution to a board
I would help directors inspect the business choices concealed inside a technical promise. My supplier experience has shown how a precise calculation can apply the wrong sequence, how a valid default can belong to the wrong client and how a successful application reversal can leave incompatible records behind. Those are questions about the meaning and limits of a commitment, not invitations for a board to redesign the software. I would ask management to connect the engineering evidence with the client obligation and the work that remains. I have no statutory seat and would be learning the responsibilities of a first appointment. My experience presenting to directors does not substitute for that learning. I would want colleagues with the sector, financial and legal judgement needed to assess matters outside my engineering remit. The useful contribution would be a clearer investment or service decision, with management retaining delivery ownership and client specialists retaining professional authority over the rules their systems implement.
Judgement in practice
01Accepting that our shared calculation had chosen a rule
Thirty-seven of 500 synthetic fixtures disagreed with the approved result map because the shared component rounded at a different stage. I had approved the component and needed to own that assumption. The ₹54 lakh correction and ₹12 lakh annual support expense made the client-approved sequence explicit; all 500 fixtures later matched that map. I would bring the same question to a board: which business distinction has a proposed simplification removed, and who had authority to accept that removal? The result did not establish actual customer overcharges or refunds. It showed a defined implementation correction. Directors should hear both the narrower evidence and the continuing cost, without treating technical precision as proof that the underlying instruction was authorised.
02Retaining two deferred features in the release account
Forty synthetic rollback scenarios initially produced 29 compatible results. A ₹1.1 crore programme supported 38 after revised sequencing, while two features remained deferred and the programme moved four weeks later. I would not present the withheld features as passed tests or the narrower release as universally reversible. The board-level judgement was whether the supported commitment justified the expense and delay compared with the original proposal. That required explaining what restoring an earlier application would mean for records already written. My contribution would be to keep the evidence, commercial consequence and unresolved work together, so that an attractive completion headline does not quietly remove responsibilities that still matter to clients and to the company's future investment decisions.
My first year on a board
During induction I would learn how the company defines its service commitments and which promises carry the greatest business consequence when they are misunderstood. I would examine a few recent engineering investments through the board's agreed process, following the approved scope into acceptance and continuing support. A useful example would include a decision management narrowed or deferred, because that shows how the organisation handles a limit rather than only how it presents success. I would ask who approves client-specific rules, how shared services represent those rules and how the evidence is selected for a release decision. Those questions would need to become specific to the company's operating model instead of remaining an insurance-software checklist. I would seek feedback from the chair about whether my interventions clarified the decision. Contact with engineers and product colleagues would follow agreed channels. I would not issue implementation instructions or create a second acceptance process beside management's own responsibilities.
Conflicts and their management
Qelvazi's founders, institutional investor, employee ownership vehicle, twenty-two insurer clients and technology partners create a relationship map that must be examined before any appointment. I would obtain employer consent and disclose relevant interests before receiving sensitive material. Having no personal holding does not remove the interest attached to continuing employment or access to client plans. A proposed board whose central business repeatedly involves my employer or its clients may be unsuitable even if a series of recusals appears technically possible. I would not transfer configuration records, private pricing rules, diagnostic samples or unreleased product plans into another board discussion. Appropriate advice must address independence, eligibility, applicable directorship and committee limits, and the particular responsibilities proposed. The twenty-day allowance also needs testing against preparation, travel and exceptional events. A role should leave sufficient time and freedom from conflict to contribute meaningfully rather than relying on my title while excluding me from its consequential decisions.
My independence statement
No independent status is claimed. Employment, investor, client and supplier relationships require appointment-specific review before any proposed independent role.
Board and committee exposure
Presented to the Board or a committee
Qelvazi Insurance Systems
Engineering investment and release-risk reviews
January 2022–Present
Presents as CTO through the CEO; holds no statutory seat, committee membership or director's vote.