When you run everything yourself, you develop a habit of rushing through communications to save time for building. I once sent a super quick, blunt answer to a customer because I wanted to get back to coding, and it completely ruined the tone of the conversation they thought I was being rude. It s tough because you're trying to be as helpful and fast as possible, but efficiency can easily strip the warmth out of your messages. How do you keep your replies friendly and human when you're overwhelmed with daily tasks?
Today, I read a TechCrunch article about what investors are no longer looking for in SaaS, or rather, what to avoid if you don't want to lose their interest.
The red flags were:
Too easy to replicate light AI wrappers, generic horizontal tools, basic CRM clones, generic productivity or project management tools.
No real depth products where differentiation is mostly UI and automation, anything without proprietary data, surface-level analytics.
Becoming obsolete workflow automation tools that coordinate human work (agents are taking over), integrations as a moat (MCP is making connectors a commodity), and "workflow stickiness" products trying to keep humans inside their software.
I scout for a handful of investors in Silicon Valley. One of my jobs is to cut through the noise and surface the gems. Every so often, someone sends me a blurb that s crisp, compelling, and makes me want to learn more. When that happens, I usually take a meeting and sometimes even make intros.
That said, most blurbs I see aren t great. Founders are flying blind because no one s willing to be brutally honest with them. Let s fix that.
whenever i give an agent write access i keep the riskiest action behind a separate check it cant talk its way past, because a prompt injected request looks exactly like a normal one. routing is plain code, the llm only writes the message. where do you draw the line, payments, sending emails, db writes?