Skip to website
Rustom VelzariChief Operating Officer · Essays & perspective

Rustom Velzari · Chief Operating Officer · India

A career built around the meaning of completion

Chief Operating Officer

Thervani Document Systems

Sector
Industrial document conversion, metadata and retrieval services
Ownership
Two founding families 62%; employee trust 18%; regional investment partnership 20%
Company scale
₹136 crore revenue and ₹14 crore operating profit in FY 2026
Employees
950 at March 2026
Geography
Vadodara, Nashik, Raipur and client-site teams across India
Reporting to
Chief Executive Officer
Team
780 operations colleagues through six heads
Financial scope
₹82 crore delegated annual operating expense; no separate company P&L claim

Mandate

Make delivery commitments depend on source accountability, agreed acceptance and visible unresolved work.

Outcomes

  • Approved reprocessing of 86,000 images within a 740,000-image delivery
  • Paused and reconciled a sixty-eight-box dispatch plan against sixty-seven boxes received
  • Kept 180 unresolved revision questions visible after client clarification
  • Connected retrieval tests with a defined metadata improvement exercise

Decisions in context

As COO I became responsible for connecting the stages of conversion rather than optimising each one independently. Six heads lead 780 operations colleagues, with ₹82 crore in delegated annual expense. I report to the CEO and present operational choices to directors without holding a statutory seat. Recent decisions have involved accepting the cost of rework, pausing intake until source quantities were reconciled and preserving revision questions that only a client could answer. Those decisions affect margin and timing, so commercial and finance colleagues must see their consequences before the service account is closed. My remit does not include engineering approval of the source or authority to decide its legal retention. I have concentrated on making those boundaries visible in delivery discussions. The appointment has reinforced my view that an operating total is useful only when it explains which obligation has been met and which remains open.

Reason for the move

Current role; improving the operating account from intake to accepted and usable records.

Director of delivery operations

Thervani Document Systems

Sector
Document preparation, capture and indexed digital delivery
Ownership
Private company with founding-family control and employee/investor minority interests
Company scale
₹114 crore revenue in FY 2019
Employees
820 at March 2019
Geography
Vadodara and Nashik centres with project teams at customer sites
Reporting to
Chief Operating Officer
Team
510 operations colleagues through five heads by FY 2019
Financial scope
₹58 crore delegated annual operating expense by FY 2019

Mandate

Coordinate intake, preparation, quality and delivery without losing the account of exceptions between teams.

Outcomes

  • Assigned owners for unresolved items crossing production stages
  • Separated repeat capture from accepted-record counts
  • Established client clarification routes for metadata exceptions

Decisions in context

The delivery appointment brought several operating stages under my responsibility and made the handovers between them more important than any individual team's report. I led five heads and 510 operations colleagues by FY 2019. A capture team could finish its work while a metadata question remained unanswered, and the combined report needed to preserve that distinction. I asked supervisors to identify who could resolve an exception and whether the answer belonged within our company or with the client. The title included director, but it was an executive operating position and not a statutory board appointment. My authority covered delegated delivery expense, with commercial commitments and company finance handled through their established owners. This period taught me to build an account that another manager could use without hearing the entire history from me. It prepared me for the COO role by making the dependencies between production, scope and acceptance explicit.

Reason for the move

Promoted to COO following a planned leadership succession.

Quality manager

Thervani Document Systems

Sector
Industrial-record digitisation and document conversion
Ownership
Privately held, founding-family controlled
Company scale
₹75 crore revenue in FY 2012
Employees
580 at March 2012
Geography
Vadodara and customer project locations in western and central India
Reporting to
Head of operations
Team
Thirty-four quality reviewers by FY 2012
Financial scope
₹3.8 crore annual quality-function expense by FY 2012; no commercial pricing authority

Mandate

Explain conversion defects and source limitations in terms of the client's intended record use.

Outcomes

  • Separated capture defects from limitations already present in originals
  • Broadened reviews beyond familiar defect categories
  • Recorded the evidence supporting acceptance exceptions

Decisions in context

Moving into quality management required me to challenge production schedules I had once been responsible for meeting. I led a team that reached thirty-four reviewers and worked with capture supervisors to explain why a defect mattered to the intended use. A repeat scan could correct some problems; others belonged to the original and required a recorded limitation or a client decision. I initially placed too much emphasis on a small set of familiar defect categories because they were easy to compare across jobs. That made reporting consistent but could obscure unusual source characteristics. I changed the review approach to allow concerns beyond the standard form and asked teams to explain their significance. The role gave me experience in disagreement that had a direct schedule cost. It also taught me that quality authority works better when its reasoning is understandable to the people who must perform the correction.

Reason for the move

Appointed to lead delivery operations across the wider conversion process.

Conversion-line supervisor

Thervani Document Systems

Sector
Reprographic preparation and early digital conversion of industrial backfiles
Ownership
Privately owned by two founding families
Company scale
₹28 crore revenue in FY 2002
Employees
260 at March 2002
Geography
Vadodara processing centre and nearby industrial clients
Reporting to
Production manager
Team
Eighteen operators
Financial scope
Daily labour and consumable coordination within the production budget; no independent capital or pricing authority

Mandate

Organise capture work while keeping source identity, repeat work and pending decisions distinguishable.

Outcomes

  • Separated repeat captures from daily completed-work reporting
  • Flagged material needing different preparation before capture
  • Maintained source identifiers through line handovers

Decisions in context

I joined Thervani to supervise eighteen operators preparing and capturing industrial backfiles. The move added responsibility for a team's work and introduced larger volumes than I had handled as a job coordinator. Different source conditions made a single daily output count misleading, particularly when repeat captures appeared alongside new work. I began showing those categories separately and asking the production manager to distinguish a capacity problem from a source question awaiting the client. I coordinated labour and consumables within the production budget, with no authority to set prices or approve capital purchases. The appointment gave me practical knowledge of how a well-intended throughput measure could encourage teams to finish the easiest work while difficult obligations remained. It also developed my ability to explain a delay before it became a surprise at dispatch. That combination led to the quality-management role.

Reason for the move

Promoted to quality manager as conversion programmes and review requirements expanded.

Records assistant, later job coordinator

Kelmavi Engineering Records

Sector
Engineering drawing reproduction and records preparation
Ownership
Privately owned regional partnership
Company scale
₹8 crore annual service revenue by FY 1994
Employees
Seventy-two by March 1994
Geography
Vadodara and industrial customers in Gujarat
Reporting to
Records-room supervisor
Team
Individual assistant initially; coordinated four operators from 1991
Financial scope
Job preparation and handling records; no budget, P&L or engineering approval authority

Mandate

Reproduce and return source records with their identifiers and handling history intact.

Outcomes

  • Maintained source identifiers during reproduction jobs
  • Escalated unclear source markings rather than infer their meaning
  • Coordinated small jobs with recorded return of originals

Decisions in context

My first appointment followed a diploma in printing and reprographic technology. I prepared copies, kept identifiers with the source material and returned originals through the records-room supervisor. From 1991 I coordinated four operators on small jobs, but I had no budget or authority to approve engineering content. The work showed me that a technically good reproduction could still be the wrong service if its identity or revision had become detached from it. I learned to ask about unclear markings and to record the answer rather than produce a neat assumption. Customers often needed the original back quickly, so preparation and return were as important as the time spent at the machine. Over nearly seven years I became more confident coordinating other people's work and discussing source conditions before accepting a job. I moved to Thervani for a larger supervisory remit and exposure to digital conversion.

Reason for the move

Joined a larger conversion business to supervise a production line.

What I am looking for next

I want the operating account at Thervani to distinguish more clearly between production progress and the client's ability to use the result. That means a coherent view of accepted records, source limitations, unresolved classifications and retrieval evidence, with the cost of correction visible. It also means developing supervisors who can explain an exception without waiting for me to reconstruct it. Beyond the company, I am considering one first external board appointment in a specialist service or industrial-support business. My provisional allocation is twenty-four days annually, including preparation and travel, subject to employer consent and the role's actual demands. I would contribute questions about acceptance, custody and the meaning of reported completion while learning the broader economics of the prospective company. I would not arrive as an additional production controller or imply that my experience authorises decisions in every records domain. A useful next chapter would strengthen collective oversight and the quality of management's account, with a clear boundary between board scrutiny and operating direction.