> one shot prompt

Not OP, but definitely not a one shot prompt. However because of AI it takes far less resources to replicate services like these rather quickly.

▲

tra3 5 hours ago | parent [-]

That’s what I thought. I wonder if that’s true though. I’m sure 80% take no time but actually productizing it takes forever. Now you’ve got a maintenance burden too. I’m really curious how long it would take to implement harvest and the ecosystem around it these days.

▲

gofreddygo 4 hours ago | parent | next [-]

Its a problem but it isn't.

Home grown product isn't going to match a saas product's features. But you dont need most of it anyway. so home grown gets the job done. Till it hits entropy or the roi is gone. Problems will show up a few months / years down till it isn't worth the effort or the savings.

Saas products that survive this AI wave are going to come out stronger on the other end.

▲

joefitzgerald 4 hours ago | parent | prev [-]

It took me about 10 days to update an existing business app that I used to include functionality replacing harvest time tracking, invoicing (with a far superior QBO sync, saving us days of people time per month), and forecasting (Forecast was never well integrated with Harvest).

Yes, we are picking up a maintenance burden but the 10x price increase in our case made it a very easy cost/benefit equation, and I decided that as a primary technology in a consulting business it was worth controlling it.

▲

tra3 4 hours ago | parent [-]

How much time do you expect you’ll spend improving it? In other words, are you going to keep adding features?

Trying to understand what the LLMs mean to the saas world. Will you have to become a time tracking/invoicing pro? Where’s the break even I wonder.

	▲	hdjrudni 4 hours ago \| parent [-]
		If it's an internal app, you stop adding features when you have all the features you need. I've vibe-rebuilt several apps for myself and after a certain point I don't feel like anything is missing so I just stop touching it entirely except to fix a rare bug here and there.