Hi, I’m Namanyay Goel, a programmer and a founder living in San Francisco.
I'm building Gigacatalyst to help SaaS companies turn every customer workflow into a native part of their product, just by talking to an AI. We're backed by Y Combinator.
SaaS is the most profitable business model on Earth.1 It’s easy to understand why: build once, sell the same thing again ad infinitum, and don’t suffer any marginal costs on more sales.
I have been writing software for more than half my life. In the last year itself, I’ve talked to hundreds of founders and operators in SF, from preseed to Series E companies.
AI is bringing an existential threat to a lot of B2B SaaS executives: How to keep asking customers for renewal, when every customer feels they can get something better built with vibe-coded AI products?
And the market is pricing it in. Morgan Stanley’s SaaS basket has lagged the Nasdaq by 40 points since December. HubSpot and Klaviyo are down ~30%. Analysts are writing notes titled “No Reasons to Own” software stocks.
The market is reflecting our new reality (Source: Bloomberg)
Whenever I bring a new friend to the Salesforce Park, they are in absolute awe. And, the meme remains true that no one even knows what Salesforce does. Whatever they’re doing, they’re clearly earning enough revenue to purchase multiple blocks in SF. ↩
Confession: I’ve been using Claude Code to write all my code for me. And I think it’s making me worse at the thing I’ve loved doing for twelve years.
I can clearly see how AI coding is rewiring our brains – it makes developers crave instant gratification instead of deep understanding, and reduces us to gamblers who pull levers for the next hit of working code.
If this is happening to me, someone who learned to code in the pre-AI era, what’s it doing to junior developers who’ve never known anything else?
A mindset shift that changed the way I think about the world
In India, knowledge is currency. Three months ago, if another founder asked me about my marketing strategy, I’d give them some generic answer and change the subject. You don’t share knowledge until there’s something in it for you.
I recently moved to San Francisco. A CTO of a unicorn startup had read one of my blog articles and we started talking over DMs. When I got to SF, I asked him to meet, and he agreed.
We met in FiDi for a casual lunch. This guy runs the entire company, and he was treating me — a new founder — like an equal. He was openly sharing his experiences, his journey, and his insights. When we were leaving, he offered to help with connections, fundraising, whatever I need.
He gave me a full hour of his day, just to shoot the breeze like two developers do.
This was nothing like what I was used to. Back in India, a person with even a 100-person office would have an air of arrogance. They’d guard their knowledge and time, only sharing when there was a clear benefit to them.
It was that day that I understood the beautiful “infinite sum game” being played in SF.
The most successful startup I’ve worked with shipped their MVP in 6 weeks.
The least successful one spent 4 months writing specs for a product that never launched.
Here’s what I’ve learned after helping dozens of teams transition from traditional planning to AI-powered development: writing-first culture made sense when building was expensive and slow. Now it’s just bureaucracy.
I celebrate another revolution around the great big ball of fire today. This was a big year for me: I founded my first product startup, all solo.
I’m doing something really hard but I realize I’ve never written down my guiding principles about why I do this. This article is mostly a reminder for me: on what it takes to achieve greatness.
Here’s what I’ve learned so far:
My favorite view of San Francisco: the legendary Dolores Park MUNI StationContinue Reading →
Every developer I know has the same frustrating ritual. Open Claude Code or Cursor and ask it to do a task. The AI gives you generic code, sometimes useful (but usually not). You correct it. It apologizes. You explain again, with additional context.
Rinse, repeat, until you want to throw your laptop out the window.
David Cramer from Sentry recently shared his AI workflow where he maintains manual rules files to give LLMs context. Solid approach, but it feels like too much copy-pasting. It’s 2025, and machines can do a better job of remembering things.
It’s funny how we’ve built the most powerful reasoning systems in human history, then lobotomized them by making them forget everything after each conversation. My question: is there a better way?