Email, Excel, and four separate programs: the hidden cost of scattered tools
Publishers aren't worn down by a lack of tools but by an abundance of them. Submissions in email, reviews in a spreadsheet, sales on another site — what gets lost is context.
Taking inventory of a publishing house’s tools is an entertaining exercise. The typical result looks like this: submissions in an email inbox; reviewer tracking in an Excel file (usually named something like “reviewer_tracking_FINAL_v7_updated.xlsx”); contracts in a shared folder; typesetting files in another folder, or on the typesetter’s computer; sales in an e-commerce package; accounting in an entirely separate program; and the institutional memory in the head of an employee approaching retirement.
If you read that list and smiled, you probably recognized it. And you probably know this too: each of these tools does its own job perfectly well. The problem is not the tools — it is the gaps between them.
The bill for the gaps: copying, waiting, searching
The cost of scattered tools accrues in three line items, and none of the three appears in any budget spreadsheet.
Copying. In how many places does the same piece of information live by hand? The author’s name is typed separately into the submission email, the reviewer spreadsheet, the contract, the catalog, and the accounting program. Sooner or later, one of the five copies drifts from the others — and nobody can tell which one is right. The book’s price changed; the store was updated, but was the price list in accounting?
Waiting. Every crossing between tools requires a human act: “let me ask whether the files came back from typesetting,” “let me send accounting this month’s sales list.” These acts get forgotten, postponed, or collide with someone’s holiday. The work itself takes minutes; the waiting takes weeks.
Searching. Perhaps the most expensive of all. If the answer to “where are this book’s reviewer reports?” lives in an email thread from three years ago, finding it is an archaeological dig. When an institution loses an employee, what it usually loses is not labor but the address book: the one person who knew where everything was kept is gone.
The common denominator of these three items is this: scattered tools lose you not information but context. The information exists, somewhere; but a view called “everything about this work” exists nowhere.
The anatomy of a Tuesday
Let’s not leave it abstract; let’s follow an ordinary Tuesday at a publishing house run on scattered tools.
9:20 a.m.: The editorial office opens the three submission emails that came in overnight. One has no abstract — an “incomplete” email goes back to the author. The other two are keyed by hand into the reviewer-tracking sheet; in one name, a Turkish “İ” goes in as “I,” and three months from now a search will come up empty because of it.
10:45: The editor notices a reviewer invitation that has sat unanswered for two weeks — notices it because the author asked about the process. A reminder is written. Since no screen shows how many other invitations are sitting unanswered, the rest wait to be noticed.
1:30 p.m.: Accounting asks for last month’s sales list. The table exported from the store dashboard is converted by hand into the format the accounting program wants: forty minutes, two copy-paste errors.
3:10: A call from the printer — “which was the final version of the cover file?” The designer is asked; the designer is on leave. It rolls over to tomorrow.
4:40: An author asks about a clause in a contract from two years ago. The contract is found in the folder; but the one person who remembers which addendum was attached to it is the coordinator who left last year.
The day’s balance sheet: nobody slacked off, everyone was busy — and perhaps a third of the working hours went not into the work itself but into carrying the work from one tool to another. What makes this picture uncomfortable is that it is not the exception but the average.
The remedies people try, and why they fall short
Institutions living this pain usually pass through two interim remedies.
The first is the discipline push: naming conventions, folder templates, “the sheet gets updated every Friday” rituals. It works for a while; then, in a busy issue period, the first Friday is skipped and the system quietly collapses. Every structure that rests on human discipline weakens precisely when humans are busiest — that is, precisely when it is needed most.
The second is the integration push: wiring the tools together. A script that pushes the spreadsheet into accounting, a connector that decrements stock from the store… These have value but are fragile; every tool update snaps a link, and maintaining the integrations becomes a job in itself.
The third way attacks the root: information is born in one place and serves every need from there. The author’s name is entered once; submission, review, contract, catalog, and invoice all read the same record. When a sale happens, the stock decrement, the invoice, and the royalty accrual are not chores to be carried by hand into separate programs — they are automatic consequences of a single event. The answer to “everything about this work” is the work’s timeline — from submission to the latest sale.
We built Nasirus for exactly this third way; books, journals, articles, and chapters flowing through one system is not a marketing line — it is our architectural choice.
A one-week test for your own institution
If you want to measure what the scatter is costing you, work through next week keeping notes on three questions:
- How many times this week did you carry a piece of information from one tool to another by hand?
- How many times did you go hunting for “where is this file/decision/report?” — and how many minutes did it take on average?
- How many tasks sat still, waiting for someone to remember something?
Most teams abandon this tally on day one — because the numbers are uncomfortable. Discomfort is the first sign of change. Send us your tallies (contact), and in the demo we’ll show what exactly those three questions look like once the process runs in a system.