Executive summary / Personal profile

Know which fact the book count represents

Chief Data Officer India

A book sent to a shop, a copy bought by a reader and a revised report are different facts. I want the software to keep them different.

Open to Board appointments · Executive opportunities

01 / Leadership approach

I learned data work among book boxes and catalogue sheets, where a neat total could conceal several kinds of movement. I still ask what happened to the copy, which product it belongs to and what was known when a report was issued. Better data should help a publisher inspect those distinctions rather than give every question the same convenient number.

02 / Areas of responsibility

Separating book movements from reader sales
Preserving publication-product identity
Keeping issued reports distinct from revised views
Funding data correction with clear decision ownership

Data colleagues: 39; Three heads; ₹10.8 crore annual operating expense
Company revenue: ₹96 crore; FY 2025–26; 230 employees in March 2026
Publishing-data experience: 30 years; Distribution records through software data leadership

Evidence from practice

Withdrawing a dispatch total presented as reader sales: In 2022 a product summary described 16,000 copies dispatched into a retail channel as reader sales.
Keeping separate products inside a shared catalogue title: A 2024 catalogue review examined 420 product groups assembled from customer records.
Showing what was known when the report was issued: In 2025 a review of a 5,000-line reporting extract found 312 records that had arrived after the original report for the period was issued.

The complete case record ↗

I keep publishing records intelligible from the warehouse movement to the report a commercial team reads.

I am CDO of Ruqneli Publishing Systems in Guwahati. We build catalogue and distribution-data software for book publishers and their trading relationships. My thirty-nine colleagues work through three heads within ₹10.8 crore annual operating expense, alongside a separately approved ₹2.4 crore platform programme. The company employed 230 people in March 2026 and recorded ₹96 crore revenue in FY 2025–26. I do not treat that company scale as a claim to own our customers' publishing or accounting decisions. Our job is to make the records and the product's interpretation of them understandable.

My first appointment was in book-distribution records in 1996. I learned that a shipment was not necessarily a reader sale, and that the same title could appear in products a buyer needed to distinguish. Later software roles added another problem: a report could change after late records arrived, while the person reviewing an earlier decision saw only the revised result. These are practical questions about what happened, what the system knew and what a summary is entitled to say. They deserve attention before a larger dataset makes the wrong interpretation look more convincing.

The cases here show three corrections. We rebuilt a movement summary that had labelled sixteen thousand dispatched copies as reader sales. We reviewed product groups that had joined distinct publication formats. We changed reporting so late accepted records did not silently replace the account available at an earlier date. Each required funded work and cooperation with customer specialists. I retain the original mistaken approval and the limits of the review. A corrected report is useful evidence; it is not proof that every record is complete or that a publisher's financial treatment has been independently assured.

Dispatches were not a count of reader purchases

A reviewed movement account reconciled 1,000 opening copies plus 16,000 receipts with 9,700 reader sales, 2,400 returns, 600 promotional copies and 4,300 closing stock. We withdrew the shipment-as-sales label.

A familiar title concealed different saleable products

Of 54 suspect groups within 420 reviewed catalogue groups, 19 were confirmed duplicate descriptions and 35 contained products that needed separate identities. We repaired the grouping rather than merging by title alone.

The revised account needed its own reporting date

A 5,000-line reporting review found 312 late records:266 accepted after review and 46 unresolved. We retained the issued snapshot and a dated revised view instead of silently replacing history.

Current focus

I am strengthening how our products explain the unit, identity and reporting date behind a number, including where the customer must resolve an unanswered question.

Conversations I welcome

I welcome data-leadership discussions in specialist software and a first board conversation about the reliability of commercial evidence.

The leadership record

Trusted with consequential decisions.

Formation

Bachelor of Science in StatisticsParquvi Science College · 1996

Amal kept the original dispatch interpretation and the cost of correcting it in the same account. He made the revised product claim easier to examine without pretending the mistake had created a financial benefit.

Pavitra NelquviCEO, Ruqneli Publishing Systems

The full record ↗

Contact

I welcome data-leadership discussions in specialist software and a first board conversation about the reliability of commercial evidence.

Board appointments
Executive opportunities

Write to Amal Contact page