The Feature Nobody Sees Is the One That Takes the Longest

I spent about 30 years in corporate IT before I started Klass Concepts. I've built a lot of things - enterprise systems, integrations, internal tools. But last year I did something I'd never done quite this way before: I built a consumer app, by myself, from scratch, and shipped it.

The app is Klass-RM Uploader, a Mac tool that makes it easy to get documents onto a reMarkable tablet. The problem it solves sounds simple. The app itself is not simple.

What I want to write about isn't the shipping - it's what surprised me about which parts of the work took the longest. Because it mirrors something I see constantly in small businesses: the most important work is usually the work nobody notices.

The Visible Feature List

Getting files onto a reMarkable tablet is, in principle, straightforward. reMarkable gives you a few different ways to upload your files, but they're clunky if you're trying to move files from a Mac on a regular basis or want some kind of automation.

So I built drag-and-drop upload for PDFs, images, EPUBs, text files, and Markdown. An "Upload Files" picker. A macOS share extension so you can send to the app from anywhere. A "Print to Klass-RM Uploader" helper on Mac. URL and web-article capture that converts to EPUB. Watched folders that auto-upload anything you drop into them. Background uploads. Large-file handling. Comic conversion (CBZ/CBR). Shortcuts and Siri integration. Sticker packs.

That's a lot of features. A fair number of them took meaningful engineering work. But none of them is what I'm going to tell you took the most time.

The Feature That Took the Longest

The feature currently in beta - calendar-synced planners - sounds like this on the surface: connect your Mac's calendar, generate a multi-view planner document (year view, quarter view, month, week, day, event pages, contact index), send it to your reMarkable, and keep it updated as your calendar changes.

The "send it to your reMarkable" part was the easy part.

The hard part: keeping it updated without destroying handwriting you've added to existing pages.

Here's the problem. A reMarkable planner is a PDF. When your calendar changes - a meeting moves, an event gets added - you could just regenerate the whole PDF and overwrite the old one. But that wipes every note and annotation you've written in the margins. People actually use these planners. They take handwritten notes in the day-view pages. They annotate the weekly spread. If every sync erased all of that, the feature would be worthless.

So I built an in-place sync mechanism. Every page in the planner has a logical slot - "week of June 9," "day view for June 18," "event page for the dentist appointment." When the planner regenerates, the system reconciles a slot-to-page map. Pages that haven't changed carry over exactly. Pages that have changed (a new event was added, a time shifted) get updated. Pages the user duplicated and wrote on - preserved. Pages removed from the calendar get tombstoned with a placeholder rather than deleted, so the page numbers don't shift and nothing else gets displaced.

Users will never see this mechanism. It's completely invisible when it works. They'll just notice that their planner updates and their handwriting is still there. If it ever fails, they'll notice that too - by losing notes they can't get back. So it has to work every time.

Why the Invisible Work Takes the Most Time

There's a principle I've observed in software over three decades: the features users describe in five words - "sync my calendar," "remember my handwriting" - are often the ones that take fifty times as long as the features that sound complicated.

The drag-and-drop uploader? Built in a few days. The in-place sync reconciliation? Weeks of design, implementation, and edge-case testing.

The reason is that visible features have clear success states. A file either uploads or it doesn't. A picker either opens or it doesn't. Users can see the failure and report it. Invisible features have invisible failures, and invisible failures can be catastrophic. Losing three months of handwritten annotations because a sync edge case wasn't handled - that's not a bug report, that's a user who never comes back.

This dynamic shows up in small businesses constantly. I see it in the Small Business Efficiency Checkup work I do with clients.

The visible work - answering emails, delivering the service, sending invoices - is what the business day looks like from the outside. The invisible work - the consistent follow-up process, the onboarding documentation, the file organization that lets anyone find anything - is what determines whether the business scales or stays fragile.

The Parallel

When I look at how a small business is actually running, I'm looking for the in-place sync mechanism. The thing that keeps work from getting lost when something changes. The thing that runs underneath every client interaction and makes it look effortless.

Most of the time, that mechanism doesn't exist. Files are in email. Processes are in people's heads. The onboarding checklist is "watch what I do." None of this is visible until something breaks.

The businesses I've worked with that are easiest to run have invested in the invisible layer. They have a consistent place for every type of document. They have a written process for the things that happen repeatedly. They have a system that doesn't depend entirely on one person knowing where things are.

That's not because they had more time. It's because at some point, someone decided that building the thing nobody sees was worth the time it takes.

What This Week's Beta Is About

I'm currently running a limited Pro beta for Klass-RM Uploader v1.1.0, which includes the calendar-synced planners and Obsidian/Markdown note sync (the same in-place mechanism, applied to your notes). Both features work the same way under the hood: a reconciliation pass that figures out what changed, updates only what needs updating, and leaves everything else alone.

If you use a reMarkable and want to try it, the free Pro beta key signup is open through Thursday, June 25. The beta keys themselves run through June 27. You can find the app at klass.link/uploader.

The Takeaway

I'm not writing this to explain app development. I'm writing it because "the feature nobody sees is the one that takes the longest" is one of the most consistently true things I've observed in 30 years of building and running things.

Software, small businesses, consulting work - the surface is always simpler than what holds it up.

If you want to think about what the invisible layer in your business looks like, the Small Business Efficiency Checkup is a good place to start. It's a structured conversation about where time and work are disappearing, with specific things you can act on.

The Small Business Efficiency Checkup is a paid assessment for SF East Bay small businesses. It's practical, plain-English, and built around what's actually happening in your business - not a generic template. If your business relies on you knowing where everything is, that's worth a closer look.