Inkwell
FeaturesAIPricingCompareFAQOpen app ↗
Sign inGet started →
← All writing

One notebook, not nine tabs

Craft2 July 20266 min readThe Inkwell team
the short version

Seams between tools grow as n(n−1)/2, so the ninth tab costs far more than the second. Integrations and all-in-one suites move the seams rather than remove them. The only real fix is objects that were never separate.

Adding a tool feels free. It usually is, at first — the free tier is generous, the onboarding is delightful, and the thing it does, it does better than whatever you were doing before.

The cost shows up later, and it never appears on the invoice.

The arithmetic nobody does

Two tools have one seam between them. Three tools have three. Four have six. The seams grow as n(n−1)/2— quadratically, while your tool count grows one at a time, which is exactly why the ninth tab feels like it costs the same as the second and doesn't.

Nine tools is thirty-six possible seams. You won't maintain all of them. You'll maintain the six or seven that your week actually crosses, and each one is a place where a piece of context has to be carried by hand, by you, from one app to another.

✳

A seam isn't a feature gap. It's the moment where two tools each hold half of something true, and neither knows about the other half.

What a seam costs

Take one that most freelancers have: a timer in one app, invoices in another.

You track two hours and ten minutes on Tuesday. On the last day of the month you open the invoice, and now you must decide what those two hours and ten minutes were. Was it the homepage or the onboarding flow? Both, probably. You round to two hours because two hours and ten minutes looks fussy on an invoice, and you write “homepage work” because that's what you remember.

Multiply by twelve entries and three clients. The invoice you send is not a lie, exactly, but it is a reconstruction. It is your memory of a month, formatted. And the ten minutes you rounded away, thirty-six times, is six hours you did and were not paid for.

The tools weren't bad. The timer was excellent. The invoicing app was excellent. The error lives in the space between them, and the person who paid for it is you.

Switching costs are attention costs

The other tax is smaller per instance and enormous in aggregate. Every move between tools costs a context reload: where was I, what was this called, which of these two projects is the one with the deadline.

You don't notice it because it never arrives as a bill. It arrives as a Tuesday where you were busy for nine hours and can't say what you did.

The tempting wrong answer

The obvious fix is an all-in-one platform. Buy the suite; the seams disappear.

Except they mostly don't. A lot of suites are nine mediocre apps behind one login. The seams moved — they're now inside the product, between modules that were acquired in different years and share a navigation bar and nothing else. You still retype things. You just do it without changing tabs, which feels like progress.

The other wrong answer is integrations: a webhook between the timer and the invoicer. Now you maintain a seam on purpose, and it breaks when either side ships a change, and it's your problem at 11pm on the last day of the month.

What actually removes a seam

A seam disappears when the two things were never separate to begin with. Not synced. Not integrated. The same object, looked at from two directions.

A tracked hour is an invoice line, in a way that requires no copy, because it was never anywhere else. A milestone is what the client sees in their portal, so there is no second list to keep in step with the first. An expense ispart of the project's margin, immediately, rather than a spreadsheet you reconcile in January.

This is not a clever technical trick. It's a decision about what the software is for, made early, and then defended — because the pressure to add a module that duplicates an object you already have is constant, and it always arrives disguised as a feature request.

What it costs to have one notebook

We should be honest that this trade has a downside. A single tool cannot be the best available option at every individual job. There are better standalone timers. There are more powerful invoicing systems, with dunning and multi-currency and a proper accounting export. If your work is mostly one of those things, buy the specialist. You'll be happier.

One notebook wins when your week crosses the seams often — a job, some clients, a side project, all in the same seven days. Then the thing you want is not nine excellent tools. It is one adequate tool with no gaps in it, because the gaps were where your Tuesday was going.

That's the whole argument. If it matches your week, there's a free plan, and the handbook starts by telling you not to migrate everything at once.

Newer →Why we built Inkwell
Inkwell

A personal OS for makers who juggle work, life, and ideas. Made by 2 humans in a small studio.

System status
✳Vault-encrypted journal · AES-256 at rest
Product
  • Features
  • AI assistant
  • Pricing
  • Compare
  • Use cases
  • Changelog
  • Roadmap
Resources
  • Handbook
  • Press kit
  • Status
Company
  • About
  • Manifesto
  • Blog
  • Contact
Legal
  • Privacy
  • Terms
  • Refunds
  • Security
  • Cookies
© 2026 Inkwell Labs · Made on paper, shipped as pixels.