The small print here is the gotcha:

"Your base rate includes core features. As your team grows, additional invoices, projects, clients, and tasks are billed based on what you use, so you're never overpaying."

Harvest / Bending Spoons moved to charging for usage on top of the per-seat cost. Want to bill a new client? Now you need to pay more per month. Client gave you a new project? That's now a higher monthly fee again. Previously the Solo plan could have as many projects as you liked.

I commented when it happened to me on HN here:

"They took my ~$100/yr Harvest time-tracking Solo plan, increased the price by 2.5x for a more restricted plan than I had... or I could get back the plan I had for $20,000/year."

https://news.ycombinator.com/item?id=48849810

Click through to the comment if you want the punchline on how I solved this for myself.

EDIT: Found my Twitter post at the time with my screenshot from inside the Harvest interface: "Your plan is changing soon! You're on a Solo plan and will be moved to the Enterprise plan." mhermann above has an even better screenshot.

https://x.com/syneryder/status/2060707054709567582/photo/1 https://x.com/syneryder/status/2060844948250087816

▲

toomuchtodo 6 hours ago | parent [-]

Can you share what you vibe coded? Well done!

▲

SyneRyder 6 hours ago | parent [-]

There wasn't much skill involved, but if there's credit to be had for giving Claude a few screenshots, API docs and iterating on the design while doing human product testing, then I guess I'll take it!

I haven't shared it because it's rough (you know what vibe code looks like underneath!) and I only implemented the features I needed. So there's no external IFTTT-like hooks, it probably doesn't internationalize well, and I didn't need collaboration features. I also don't want to be on the hook for supporting a codebase that isn't the core of what I do. My real goal was to see if I could implement a replacement for myself in less than the cost of one annual seat, even at API pricing.

But I'm surprised to see Harvest is still in the news about this... so, maybe! Thanks for the encouragement!

	▲	toomuchtodo 6 hours ago \| parent [-]
		No worries, and you're welcome! My ask for you to share wasn't to have to provide support (as an open source project maintainer, I completely understand), but I am gathering examples of this type of build mode, I think there is great value in building a positive feedback loop where it becomes easier to build replacements when the rug is pulled. This potentially "outruns the enshittification" if you will, a meta version of open source that sits on top of the building via tokens. > My real goal was to see if I could implement a replacement for myself in less than the cost of one annual seat, even at API pricing. Indeed. Yes we can, and we can continually improve upon this process. Onward! Thanks again for sharing!