Producing the evidence, then living with its interpretation

Mandate

Connect spatial-product commitments with the evidence, permissions and professional acceptance they require

Outcomes

• Withdrew a positional claim unsupported by checkpoint examination
• Kept ten height records outside the reconciled account
• Preserved three hectares without ground observations
• Distinguished permitted, restricted and unresolved source uses

Decisions in context

My CTO appointment in April 2022 brought product promises and technology investment into the same executive responsibility. Qelzami now employs 380 people and records ₹ 158 crore FY26 revenue. I lead 61 colleagues through five leads within ₹ 12.2 crore FY2026–27 expense and a separate ₹ 4.5 crore development programme. Nandita retains enterprise authority and Arun leads qualified survey acceptance. Early in the role, I endorsed an accuracy claim that the later checkpoint examination did not support. The correction made the boundary between attractive specification and defensible commitment personal. Subsequent work examined height references, ground observations and source permissions. The CTO appointment carries no statutory seat, and I hold no personal equity in Qelzami. The outside role I am considering would require me to question management's evidence collectively, with the discipline to leave technical execution and professional conclusions to the people responsible for them.

Reason for the move

Continuing the technology remit while preparing for a first outside board contribution

Mandate

Bring receiving-user requirements into platform development and service explanations

Outcomes

• Connected product representation with the client's next decision
• Retained source context across processing and export
• Joined technical development with accountable capability descriptions

Decisions in context

Returning to Qelzami in December 2017 was a deliberate move back to the supplier after learning how its material was received. The business had 265 employees and ₹ 104 crore revenue for FY ending March 2018. Forty-two technology colleagues worked through four leads within ₹ 8.6 crore annual expense. I asked developers to consider how a customer would interpret an export after it had left the original delivery conversation. That question affected representation, source context and explanations of proposed capabilities. It did not remove the need for efficient processing or make every possible client use our responsibility. It helped us identify which assumptions belonged in the agreed service. My later promotion expanded the remit, but the proposal error in the CTO role showed that learning on the receiving side did not automatically protect every commercial statement I would endorse.

Reason for the move

Promoted to CTO with broader investment and product-commitment responsibility

Mandate

Make externally supplied spatial material understandable for its intended advisory use

Outcomes

• Examined the difference between supplier completion and receiving-use readiness
• Kept qualified engineering decisions with the relevant practice
• Brought gaps in source observation into delivery discussions

Decisions in context

I joined Jemzari in July 2012 to understand spatial delivery from the receiving organisation's side. The director title was functional and carried no statutory appointment. The company employed 240 people and reported ₹ 92 crore revenue for FY ending March 2013; I led twenty-seven colleagues through three leads within ₹ 5.2 crore annual expense. A file could arrive on time and still leave the advisory team uncertain about what its surface represented. Qualified designers retained their professional decisions, while my team helped preserve the source account they needed. This period changed my understanding of completeness. I became less impressed by a smooth representation when its observation limits were difficult to recover. Returning to Qelzami offered a chance to address those questions earlier, in the products and processes that determined what the receiving user would eventually be able to see.

Reason for the move

Returned to Qelzami to influence the technology and representation behind supplied products

Mandate

Connect acquisition records, processing context and client delivery

Outcomes

• Preserved reference descriptions through platform workflows
• Investigated questions arising when clients combined sources
• Learned where a successful export left interpretation unfinished

Decisions in context

My first Qelzami appointment began in September 2007. The company had 108 employees and ₹ 36 crore revenue for FY ending March 2008. Fourteen platform colleagues worked through three leads within ₹ 2.3 crore annual expense. We connected acquisition material, processing and the delivery of spatial products. The most instructive questions often arrived after a successful export, when a client combined our work with another source. A reference difference or an unexplained gap could become significant in a use the processing team had never discussed. I learned to ask what context needed to travel with the file, while accepting that the survey practice and client retained decisions outside software delivery. Those questions led me to Jemzari rather than simply to a larger platform team. I wanted to experience the next stage of responsibility instead of assuming that our own definition of completion explained it.

Reason for the move

Moved to a civil-advisory business to understand the receiving side of spatial delivery

Mandate

Make processing tools retain the specifications needed to interpret their outputs

Outcomes

• Returned absent reference questions to survey owners
• Distinguished convenient defaults from authorised specifications
• Managed a small software function with explicit spending limits

Decisions in context

The software-lead role began in April 2001 with eight colleagues through two leads and ₹ 74 lakh annual expense. Pemzavi employed 130 people and recorded ₹ 23 crore revenue for FY ending March 2002. I learned that a tool could keep a process moving by inserting a default while making the resulting product harder to explain. My responsibility was to help developers distinguish an authorised specification from a convenient assumption. That required working with survey owners rather than expecting programmers to infer meaning from whatever value made the next operation succeed. The management challenge included explaining why a controlled unresolved response could be preferable to an apparently finished answer. Joining Qelzami widened the service around the software, connecting acquisition and client delivery more directly to the platform decisions for which I would be responsible.

Reason for the move

Joined Qelzami for responsibility across a wider survey-platform service

Mandate

Prepare survey records while retaining their observation and reference context

Outcomes

• Learned to preserve the explanation accompanying field records
• Raised incomplete specifications within a supervised process
• Built practical understanding of processing and interpretation

Decisions in context

After graduating in survey technology in June 1995, I joined Pemzavi in July. The company employed fifty-four people and reported ₹ 6.6 crore revenue for FY ending March 1996. I was part of a seven-person processing group, with no reports and no spending authority. Supervisors taught me to retain the explanation accompanying field records rather than reduce every observation to an apparently self-explanatory number. I did not own survey acceptance or client commitments. My contribution was to prepare material carefully and raise gaps in the specification instead of filling them through guesswork. Those habits became relevant when I later helped build the tools performing similar operations. The promotion to software lead required me to make the discipline understandable to others, including colleagues whose familiarity with processing code did not necessarily include the field context behind each value.

Reason for the move

Promoted to lead the geospatial software group