I.1 The problem: documents are a pile of small chores
A Tuesday, honestly told
Maya runs the office of a small architecture firm. At 9 a.m. she is told to "send the tender documents". By noon she has lived this:
- The client wants one file. She has eleven: two PDFs, a Word letter, three drawings exported as images and five scans.
- Two scans are sideways. One was fed into the scanner crooked.
- The total is far too big for the client's upload form.
- The cover letter has a page that must not go out. Another page needs a clickable contents entry.
- Someone says the scans should be searchable, "so we can find the clause later".
- The client's reply arrives: a password-protected PDF with the signed terms. She knows the password, but she wants the file open so she can attach it to a bigger pack.
- Her director asks, "What does the 80-page appendix actually say?"
Nothing here is hard. That is the problem. It is seven different jobs, each with its own tool, its own menu and its own quirks, spread across a desktop editor she opens twice a month, three browser tabs of different free sites, and a printer-scanner utility.
What it costs
The cost is not the minutes. It is the switching. Each chore means finding the right tool, remembering where the option hides, wondering whether this site keeps your file, and then checking whether the result is what you meant. By the fourth chore you are not working on the tender any more. You are working on the tools.
The pile of small chores
Look at that list again. The verbs are: merge, rotate, straighten, shrink, delete, index, recognise, unlock, explain. They belong to different families of work:
| Chore | What kind of change |
|---|---|
| Merge, delete, rotate, resize | Change which pages exist and how they sit |
| Add contents, add a table | Add structure |
| Lock, unlock, sign, validate | Change who can open or trust it |
| Shrink, straighten, repair | Change weight, tilt or health |
| OCR, extract, search | Get content out |
| Convert, create | Change format or make something new |
| Ask, summarise, list actions | Understand with AI |
Seven kinds of change. No single dial controls them.
Why one big editor is the wrong answer
The classic answer is a big desktop editor that does everything. It has real strengths. It also has costs that show up on exactly the tasks above:
- You have to learn the whole thing to do one job. Compressing a file sits three menus deep next to fifty other options.
- You have to install, license and update it, and so does everyone you work with.
- It is built for one person at a desk, not for "do this to forty files" or "do this every Monday".
- It hides the consequences. One save can quietly rebuild images, flatten a form or break a signature, and you find out later.
Why many small, focused apps are the right answer
A small app that does one job can be explained in one page, which is how this book is built. It can state plainly what it changes and what it leaves alone. It can be tried in ten seconds without a manual. And it composes: the output of one is the input of the next, the way a good set of kitchen tools works.
Maya's morning, redone: Merger for the eleven files, Rotation and Deskew for the sideways and crooked scans, Delete Page for the page that must not go out, Searchable for the clause hunt, Compressor for the upload form, Unlock for the client's reply, and Ask PDF for the director's 80-page question. Each is one page you can understand in a minute.
Try this. Write down the last document job that annoyed you. Underline the verbs. If there are three or more, you have met the pile of small chores. Keep that list: you will turn it into a chain in Part XII.
Next
How can a shelf of small tools feel like one product? The Documentize idea: one app, one job →