"I Got Mad and Built a Clone: The Real Origin Story of owntime"

#The unoriginal part

I am going to tell you the origin story of owntime, and I want to start by admitting that the first half is unoriginal, because honesty about that matters more than a good hook.

In August 2026, Harvest raised prices. Reports put the increase around 1500% for some teams after Bending Spoons acquired the company. I was one of the people who got the email. I was angry. I read the Hacker News thread, 111 points and 110 comments of people saying the same thing I was thinking. And then I did what a lot of angry people on the internet do: I opened a code editor.

That part is unoriginal. "SaaS company raised prices, developer built an alternative" is not a new story. Octopus Deploy had the same thing, and the Hacker News comment was four words: "so we built a clone instead." I read that comment the way you read your own name in someone else's diary.

If the story stopped there, it would not be worth telling. A lot of angry-week projects die on day three, or day thirty, or when the angry person realizes that building software is less fun than being mad about software. The reason this story is worth telling is what happened after the anger.

#The week I did not sleep well

I am a consultant. I bill clients for time. I had a Harvest subscription that I used for my own billing and for a couple of small clients I advise. When the new pricing landed, I did the math on what it would cost to stay, and the number was absurd enough that I started looking at alternatives.

But looking at alternatives meant facing the thing I had been avoiding: I would have to move my history. Years of entries. My billing memory. The thing I opened when a client asked "what did we work on in March last year?" Every alternative I looked at meant exporting, importing, and hoping nothing broke. I had done that dance before, and I did not want to do it again.

So instead of switching, I spent a week building the thing I wanted instead. Not a business. Not a product plan. A tool that could do what Harvest did for me, could never reprice me, and would let me bring my history with me.

I did not sleep well that week. Not because the work was hard, but because I kept thinking I was being ridiculous. I was a consultant with client work, not a startup founder. Building a time tracker was not a rational response to a price hike. But I could not stop, because every time I looked at my Harvest invoice, I got mad again, and anger is a fuel

#The constraint that made the product

Somewhere in the middle of that week, I made a decision that became the whole product.

I decided there would be no server.

This was not a technical decision at first. It was an emotional one. I did not want to run something that could hold anyone's data, because holding data means being responsible for it, and being responsible for it means being a company, and being a company means eventually having to monetize the thing I was building, and monetizing it meant subscriptions, and subscriptions meant I had become the thing I was trying to leave.

So no server. The app would run on your Mac. Your data would be a file on your disk. The license would verify offline. If I disappeared tomorrow, your copy would keep working. I turned off my wifi one night to test it, and when the timer kept ticking, I knew the constraint was right.

That constraint is the whole product. Every feature in owntime is a feature that can run locally, on your file, without a server. The import, the invoices, the estimates, the backups, the R2 mirror, everything. The anti-roadmap, the things we will not build, is just the list of features that violate the constraint.

#The part nobody tells you about building in anger

Here is the part of the origin story that does not make it into the launch post: building in anger is a terrible foundation for a product, and I almost quit twice.

The first time was around day five, when the anger faded and I realized I had committed to maintaining a piece of software for strangers. The second time was around day twenty, when I showed the first working version to a friend and he asked "but how will you make money," and I did not have a good answer.

The thing that kept me going was not optimism. It was stubbornness, and a specific kind of stubbornness: I did not want the version of me that got the Harvest email to have been wrong. If I quit, the angry version of me was just a guy who got mad and did nothing. If I finished, at least he was a guy who got mad and built something.

I am telling you this because the "build in public" version of this story is cleaner than the real one. The real one is angrier and more uncertain and less photogenic. But it is the true one, and you are considering trusting this product with your billing history, so you deserve the true one.

#What I want you to take from this

owntime is not a startup. It is a tool one person built because he got a price hike he thought was unfair and could not find an alternative he trusted. The early-bird is not a growth hack. It is me pre-selling to fund the build instead of building on hope, because I did not want to finish the app and then discover nobody wanted it.

I am not going to promise you I will be here in five years. I do not know if I will be. What I can promise you is that the app will work in five years whether I am here or not, because it does not need me to run. No server, no subscription, no phone home. The worst case of buying owntime is the tool stops improving and your file keeps working. The best case is it keeps getting better.

If you got the same email I did, and you are looking at this wondering whether a solo developer's angry-week project is a safe place for my billing history: that is a fair question. The honest answer is the history lives in a file you hold, the app works offline, and you do not have to trust my promises. You can turn off your wifi and see for yourself.

That is the whole story. Unoriginal anger, a constraint, and a week I did not sleep well. The rest is just shipping.

Try owntime free for 14 days · See pricing, one time · Read the honest roadmap