Why We Built DocLens

The idea for DocLens didn't start as a product plan. It started as the same small frustration, over and over: knowing we'd written something down, somewhere, and having no real way to find it again except opening documents one at a time until we recognized it.

Google Drive's search is genuinely good at finding the right documents — it looks inside them, not just at their titles. But every time it handed us a list of four or five documents that all matched, we hit the same wall: which one actually has the sentence we need, and where in it? Half the time we couldn't even tell the candidates apart at a glance — grid view, which is what most people browse Drive in, truncates long titles with an ellipsis, so four “matches” often looked like four identical, cut-off names. The search would point us at a pile of candidates and then leave us to do the real work by hand — opening each one, pressing Ctrl+F, scrolling, hoping.

That last step was the part that never got easier, no matter how good Drive's own search got. So we decided to build the piece that was missing.

What we actually wanted

Not a replacement for Google Docs. Not another app to check. Just an answer to one specific question, every time we searched: show me exactly where this appears, and let me go straight there.

That became DocLens's entire premise. It sits quietly alongside Google Drive and Docs search — no new tab, no separate workflow — and for every document in your results, it shows the actual passages where your search term appears, in context, not just a title and a “this matched” checkmark. Click one, and the document opens already scrolled to that exact spot. No second search inside the file. No scrolling to guess.

Where that leaves us

DocLens is still early, and still shaped directly by the same everyday annoyance that started it — the gap between “Drive found the document” and “I found the sentence.” If you've felt that gap too, that's exactly who we built this for.