Watch an architect shop for a PDF tool and you will see the same ritual every time. Two browser tabs, side by side, feature lists scrolling past. OCR. Form fields. Digital certificate signatures. Redaction. Measurement and takeoff. Bates numbering. Optical this, batch that. A count at the bottom of one page, in a confident font: 417 features. The other tab has fewer, so the first tab wins, and a card gets typed in, and a year later the same person is opening drawings in something they still describe as "fine, I guess."

I have done this myself. I run a small architecture studio in Vilnius, and for years I bought software the way everyone does, by the length of the list. It took me an embarrassingly long time to notice that the list I was buying and the list I was using had almost nothing to do with each other.

The week I actually counted

A few years ago, on a slow stretch between two projects, I did something a little obsessive. I kept a tally next to my keyboard of every distinct thing I did in a PDF over one working week. Not what the toolbar could do. What my hands did.

By Friday the paper was almost empty. Five marks had grown fat with strokes next to them, and everything else was a lonely tick or two. The five were not a surprise, which was the surprise:

  • Open. A heavy export from AutoCAD, Revit and ArchiCAD lands in my inbox, and I need to see it now, not after a progress bar.
  • Mark up. A cloud around a clash, an arrow, a short note. "This door swings into the accessible route." That is the job.
  • Search. Find every instance of a door tag, a room name, a detail callout, across a set that runs to hundreds of pages.
  • Compare. Rev C against Rev B. What moved. Where the grid shifted. What the contractor is about to build wrong.
  • Send. Flatten it so my markups survive, and get it back out to whoever needs it.

Open, mark up, search, compare, send. That is the working day of a drawing reviewer, and it has been for as long as I have been doing this. The 412 features I was not writing down were not fake. Someone, somewhere, needs Bates numbering. It is just that nobody in my studio has needed it in the entire life of the studio.

Why the long list wins the sale and loses the day

Here is the uncomfortable mechanic. A feature list is read once, at the moment of purchase, by someone anxious about making the wrong choice. In that moment, more looks like insurance. You are not buying the 417 features. You are buying the feeling that you will never be the person who needed feature 400 and did not have it.

But software is not used at the moment of purchase. It is used at 4pm on a Thursday when a contractor is on the phone and the drawing will not open. And at 4pm on Thursday, every feature you are not using is not free. It is sitting in the toolbar, taking up a slot, adding a menu, one more thing between your eye and the button you actually want. I have watched a new architect join the studio, open one of the big established tools for the first time, and simply freeze. Not because she was slow. Because the five things she needed were scattered across a wall of things she did not.

The industry sells PDF tools the way airlines sell seats, by the count. You are charged for a suite and you live in a corner of it. The measurement engine you paid for is used by the estimator down the hall, if at all. The form designer is a ghost. The redaction module gets opened the one time a year a lawyer asks, and you fumble through it like a stranger because you have not touched it since the last lawyer.

The features people are sure they need

When I tell people I built a PDF editor for exactly this daily loop, the first question is almost always about the features I left out. OCR. Form authoring. Digital certificate signing. Measurement and takeoff. And I understand the reflex, because I had it too. Those four sound like the serious, professional, grown-up features. Leaving them out sounds like a toy.

So let me be plain about what I built. Ncored is the tool I made for my own studio, and today it does view, markup, text edits, page organisation, search, compression and layers. It does not do OCR yet. It does not author forms. It does not create your cryptographic signature (it will verify an existing one and show you the certificate details, but it will not mint your own). It does not do measurement or takeoff yet. Those are real gaps, and I am not going to pretend a scanned survey with no text layer is something it can search today, because it cannot.

What I found, once I stopped flinching about it, is how rarely those gaps interrupt the five-verb day. OCR matters enormously the day you inherit a box of scanned as-builts, and not at all on the other 200 days you are working with native vector exports that already carry their text. Certificate signing is the strongest argument for keeping Acrobat on one machine in the office, and a terrible argument for running your whole day inside it. A gap that bites you twice a year is a tool you borrow twice a year, not the tool you live in.

Subtraction is a feature you can feel

The idea I keep coming back to is that leaving things out is not an apology. It is a design decision you feel in your hands every day. When the toolbar only holds the tools of the daily loop, the tool you want is always the one you are looking at. There is no submenu archaeology. A junior can be useful in an afternoon instead of a fortnight.

And subtraction is what buys the thing everyone actually wants and no feature list ever advertises: it opens fast, and it stays smooth on scroll, zoom and pan, even when the file is a 50-200 MB+ project set that makes the big suites reach for a spinner. That is not magic and it is not a bigger machine (though a decent i7 or i9, 32 GB of RAM and Win 11 Pro on Windows, or a modern Mac, all help). It is what you can do for the daily loop when you are not also carrying 400 features you promised someone in a sales meeting. If you want the numbers rather than my word for it, I put a heavy-drawing benchmark on real CAD PDFs up so you can check the claim yourself.

None of this means the big suites are wrong. Bluebeam is built for the large-firm workflows it advertises, and Acrobat is still the right place to send a document that needs a real certificate signature. If your day is estimating, you want the measurement engine, and you should buy it. The mistake is not owning a suite. The mistake is assuming that because your work is serious, your daily tool has to be the one with the longest list.

Buy for the day you have

So the next time you find yourself with two tabs open, comparing counts, try a different test. Do not ask which tool has more. Ask which one puts open, mark up, search, compare and send closest to your hands, and gets everything else out of the way. Then be honest about how often you truly need the rest, and keep one machine in the office for the twice-a-year jobs.

You are not buying a feature list. You are buying a Thursday afternoon. Buy for the day you actually have, not the day the sales page is worried you might one day have.

Adobe, Acrobat, Bluebeam Revu, AutoCAD, Revit and ArchiCAD are trademarks of their respective owners and are referenced here for identification and comparison only. Individual experiences with each tool may vary.