It's saying "I'm an unnatural, non-native monoculture that does little to support biodiversity but will gladly suck up your time and money."

Sorry to speak negatively of the thing you're working on Andrew, but the subject matter is one I feel strongly about. Having a short cut lawn area has many recreational uses, but most people don't do anything except maintain most of their lawn. On top of that, many people become focused on a particular aesthetic that usually requires non-native grasses and harmful pesticides. In some places, scarse water supplies are used just to maintain a certain color.

I encourage everyone to look into replacing grass lawns with native plant landscapes, and where you do want it short cut, look into a mix of plants like clover that require far less work to keep alive than most grass monocultures.

We do home property and inventory services using AI on photos as well and the key thing we've found so far is that the biggest rival to those features is just people dragging photos into chatgpt and asking away. So the key here is differentiating from that and making something better and more accurate. What we did was to basically build a better and deeper prompt and history, e.g. context is king in a vertical. So that means the other info the user has put about the property, the memory of previous things asked or seen, combining with publicly available property info we already gather - this would make the information more valuable than straight gpt usage.

So what more can you bring to the bare prompt on the photos to help? What can you build in terms of info about the zip, so you do more 'vertical stuff' before the api call.

Please ignore most of the people on hacker ews, most of them are losers who complain about everything.

Did you craft a rich prompt template that's untuitively helpful? If so, what did you see go wrong before you had that figured out? How did you determine it was a positive improvement? How will you make sure that your prompt's benefits hold up as your original model is retired and it needs to be run against whatever new model you're left to use instead?

Or is it just that your website acts like a kind of inspiration a la "Hey, did you ever think to ask AI about your lawn problems?"? If so, how do expect people to find this inspiration when link-delivering search is being agressively retired in favor of synthesized chatbot responses already?

When I'm planting, site selection is important but I'm really slow at it, even when using AI.

I also use AI for some plant diagnosis but that hasn't led to any meaningful action, except that I'll be more thoughtful about site selection for some plants in the future.

Most of this could just be a collection of documents in a Claude project, but hey if more people are working on it I'm all for that even if there are competing tools.

My point being - your UX doesn't ask what people's goals are. Not everyone wants a "perfect lawn". Even people who do want grass may have different priorities for their grass - low maintenance vs. low water usage vs. really green, etc.

If you want your product to be different than what the lawn care guys will say, then you need to actually let people do different things in the app. Or, if you are dead set on making this into lead gen for lawn care guys, well... I personally find that somewhat disheartening, but clearly I'm not your audience.

What I don’t know yet is if the DIY I’m doing with the help of Claude is going to materialize into a lush lawn.

It has me doing pre-emergent spray, broad leaf weed killers, and moss killer.

It’s a lot of work and I’m sure there is a much better UX than saved chats.

    > Veterinarian turned founder, AI lawn diagnosis

I’d highly recommend telling Claude something like (untested myself): redesign the website, remove all emojis and all letter-spacing CSS, use non conventional typefaces, no italic serifs, limited cream/beige colors

Something along those lines.

Fun idea, good luck!

About six months ago I was spending time with a vet friend, and was hearing stories about terrible user interface and ways the software was getting in the way. The story I most remember was a 60 second timeout requirement to enter patient data before the workstation locked and required logging in again, and that a logout while still typing would cause the current notes in progress to be deleted. I have no idea if those problems are caused by regulation (a kind of kitty HIPPA compliance) or just terrible UX.

I worry that vet software is probably a terrible market as well, with regulation and established providers, maybe it's a lower margin business (certainly not a profit center) and maybe edge cases for each vet practice in the US.

As someone with domain knowledge, perhaps that's a challenge you might consider, now that AI makes coding so accessible across domains now? Since I have zero domain knowledge, it seemed like something I could never help solve.