> Asana's core business is now a prompt

What do you mean? Like a claude code one shot prompt?

> 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.

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.

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.

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.

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.

I have a long list of features to add to the app, things that Harvest and Forecast never did to help me plan and run the business. It’s worth noting that 100% of our payments are ACH so I did not have to do Stripe integration or other payment processor integration.

But we were finally able to model the notion of the “prime contractor” which is a part of our business. Sometimes we have both an end-client and an intermediary (prime contractor) for the same project, meaning different legal entities for the bill-to and ship-to entities. We had workarounds in Harvest and QuickBooks for this but now it’s directly modeled into our app and it saves us a lot of them.

Time tracking and invoicing are unavoidable complexity in a consulting business, particularly at scale when you’re spending lots of time dealing with edge cases like invoice reinsurance (driven by time card mistakes, changes to purchase order numbers, or the need to move time from one purchase order to another).

We’ll probably have some weeks where we need to spend 2-8 hours to maintain the Harvest/Forecast functionality. And other (most?) weeks where we spend no time. The real takeaway here is we finally have a tool that perfectly models our business, and saves days of person-effort every month. It will probably allow us to delay hiring incremental operations personnel. That alters the break even calculation significantly.

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.

I argued this before. I think it makes no sense for eg an estate agents to vibe code a CRM, but if you're a tech firm (or a big firm with a tech department) I think it is worth a shot, especially if you only use 50% of the features in the software you pay for.

I think it is a figure of speech.

I built a markdown editor and viewer to better than the best I've bought or used in the macos App Store in 81 prompts.

I've built a very good ticketing system and it took a lot more prompts than that.

So, you’ve spent a good amount of time on it, to where you hope there’s only a week left, it does a lot less, is less accessible, you can’t fully use it yet, and it’s buggy.

I think the only lesson for SaaS providers, yourself and myself included, is how willing people are to cut off their noses to spite their faces. :)

Similar story here, except we went from Jira to a custom Plane.so build. Everyone from product to engineering loves it, gets features they want added quickly. And for me, I mainly have Claude keep track of everything (mcp).

The Jira billing administration will remain as a business school case study of dark patterns for years. Can't wait for the EU to put their nose into it.

same, I transitioned my teams from asana to linear this week, saving money for better product

Loom was another recent one. $10/month -> 200 something. Why? Apparently people with the same domain as me now required an account including developers who left the company 3 years ago.

I recently discovered Zoom Meetings has a Clips feature which is a Loom clone.

I already pay for Zoom, so dropped Loom in a heartbeat.

I literally just found out about Loom yesterday while scanning upwork (yes, I know!) to see what’s going on. A lot of companies say “must send a loom video or will not be considered” which seems odd to me. It’s odd they have a preference of the video hosting as I’d prefer to just self host a video on my own domain. Anyway, tried out loom and it s pretty freaking feature bloated but suppose it’s nice the title can auto-generate based on auto-transcription…? Yikes now that I’m thinking about it more.