"The Anti-Roadmap: Five Things We Will Not Build"

#The list that is also a product page

Most product roadmaps are lists of things the team is building next. This post is the opposite. It is the list of things we are deliberately not building, and it is one of the most important pages on the site.

The reason is that owntime exists because of a specific frustration with what time trackers became: hosted team platforms that can reprice you, hold your data, and keep adding features until the price follows. Every feature we say no to is a protection against becoming the thing we left. So here is what we will not build, and the honest reason for each.

#1. Hosted team SaaS

This is the big one, and it is the reason the other four exist.

We will not build a hosted team platform with an admin console and per-seat pricing. That is Harvest's cost structure, and it is exactly the structure that made the repricing possible. Seat pricing means recurring revenue. Recurring revenue means a server to justify. A server to justify means the incentive to reprice is always there.

We know this costs us sales. I get emails every week from studios that want a team dashboard with seats and an admin panel, and I understand the need. But building it would contradict the entire thesis of the product. owntime is licensed buy-once, one license covers up to three people, and there is no admin console because there is no server to administer. A studio of six buys two licenses. That is the honest math, and it stays that way.

#2. Real-time multiplayer editing

Related, but distinct. We will not build live multi-user editing of the same timesheet.

The reason is the same architecture problem. Real-time multiplayer means a server coordinating the edits, and a server means the subscription logic creeps back in. Our answer to "team sync" is the file: a shared SQLite file or a user's own storage, eventually a CRDT merge if demand actually requires it. Not live. Not hosted. Not a server.

If your studio needs five people editing one timesheet at the same time, in real time, from phones, owntime is not your tool, and this page just saved you a trial. We are for solo consultants and small agencies where each person keeps their own file and the team rolls up the exports.

#3. Scheduling and resource forecasting

We will not build Harvest Forecast. No scheduling. No resource forecasting. No "who is free next Tuesday" view.

This one is partly scope, and partly honesty about category. Forecasting is a different product category. It is huge, it requires a server, and we are not going to build a shallow version of it and bolt it onto a time tracker. We will skip it until someone pays us to say no twice, which is the real test: if a paying customer asks twice, the need is real enough to reconsider. Until then, it stays off the roadmap.

#4. An integrations marketplace

We will not build a hundred-plus integrations marketplace.

We will pick the three that matter: QuickBooks or Xero CSV mapping, a Slack webhook for notifications, and calendar import. That is the realistic ceiling, and the reason is the same architecture problem in a different costume. Integrations are where subscriptions creep back in, because each integration is a relationship with another platform that has its own pricing and its own churn risk. We would rather do three integrations well and keep the product serverless than build a marketplace that turns us into a platform.

If your workflow depends on a dozen integrations, Harvest or Toggl is the better fit, and I would rather you use the right tool than use ours with a workaround.

#5. Online payments processing

We will not process payments.

Your owntime invoice can carry a payment link, Stripe or similar, but the payment lands in your account, not ours, and owntime never touches the funds. The reason is compliance. Processing payments means regulation, and regulation means the kind of operational overhead that justifies a subscription. We link out. You keep the merchant relationship. We stay out of the money.

#The anti-roadmap is the product

I want to be honest about why I publish this list, beyond transparency. It is a commitment device.

Every few months, an email arrives asking for one of these five things, and the easy answer is "we will add it to the roadmap." The honest answer is "that would break the product." Publishing the refusal makes it harder to quietly add the feature later, because you will call me on it. This page is a promise I am asking you to hold me to.

It is also, practically, the best qualified-lead filter I have. The people who read this page and buy anyway are the people who want exactly what we are building. The people who read it and leave are the people who would have churned in a month anyway. Both outcomes are good.

#What we are building instead

Since a refusal is more useful with a direction, here is where the effort goes instead.

The daily-driver loop is closed and in the box today: the weekly grid, tasks under projects, idle detection, the invoice flow, import, budgets, margins, reports, and your-own-cloud backup. What continues is hardening — import breadth, polish, the small frictions. Features that run locally, on your file, without a server. Features that do not require a subscription to keep working.

That is the product. The anti-roadmap is what keeps it that product.

See the full roadmap · Try owntime free for 14 days · Compare with Harvest