7 Comments
User's avatar
Himanshu Bhatia's avatar

This is really interesting. Do you think the same idea could work for service-based businesses too? For example, agencies where pricing isn't fixed and depends on project scope, team size, or engagement model. Curious if you've seen any good implementations for that.

Tom Orbach's avatar

100%, I'd maybe give estimations/criteria for determining the price in the .md file. That way the AI could suggest the user the ballpark range.

Yuliia_k.o's avatar

Thank you a lot for such an informative article🤝

Hari Prasad's avatar

I have been asking my team to do this for our products, and I am so happy that you have brought out such an insightful thing to closely discuss and talk about. Loved the no bs approach, keep up Tom!

Manish's avatar

Never thought a pricing. md file would become a marketing asset, but this actually makes a lot of sense.

Orel's avatar

Added it to WriteStack as well :)

Mustafa Kamal's avatar

The thing that's going to bite teams isn't building the .md file, it's that the sale shows up with zero attribution. Agent reads your pricing.md, buys, and there's no referrer, no UTM, nothing in GA. So you "win" the deal and your dashboard calls it direct/none. If you ship one of these, put server side logging on the .md and .json endpoint hits first, otherwise you can't even tell agents are shopping you, let alone which ones convert. The pricing file is step one. Measuring agent demand is the part nobody's set up for.