MarketFit's PH launch just concluded few hrs back (i.e. on Sep 28).

A big thanks to everyone who cheered us and gave us feedback.

We christened Sep 28 as Don t Sell. Solve Problems day and many endorsed this idea.

It's an interesting aspect of psychology.

Try telling someone directly to change a certain habit or adopt a new mindset and in 9 out 10 cases it won't work.

Now, give them a tool that makes life easy for them but subconsciously develops a certain habit -- and they will readily adopt it.

When you think of this question - Feature selling vs problem solving , think of yourself as a buyer

1. Do you want to hear about features or do you want to hear about solutions to your problems/ pain-points?

2. Do you like sellers who answer your questions instantly (& accurately) vs those who answer vaguely or ask for time to get back?

3. Do you like sellers who even bring up problem-areas/ideas that you missed & their solutions?

I've been watching this weird trend in B2B sales, and it's honestly keeping me up at night.

Everyone's rushing to implement AI sales tools (rightfully so - the efficiency gains are insane), but we might be accidentally breaking the entire profession.

MarketFit is coming to PH on Sep 28.

There is a special offer just for 1-day (Sep 28) check our post on 28th.

Fun bit 1:

Customers/Prospects can ask just any questions on your sales pitch/ presentation.

So, what do you do?

1. Do you just say 'let me get back' and take time to come back?

Hi PH :)

We've had our PH launch precisely 1 month ago, and we're now making a little over $1k MRR.

(could've been around $2k but we had to refund some because product wasn't ready yet)

I was at the office of a buyer who was looking to evaluate MarketFit.

The Sales Head wanted to try it out in real scenarios.

He called three of his team members from pre-sales team to his cabin.

Still feels unreal. Last week, we crossed 10,000 people using Pretty Prompt!

Just 3 months after launch .

What started as a weekend hack to solve our own problem, is now loved by so many users around the world!

Today, I noticed a small update on my profile while replying to your comments.

A new button has been added specifically, the option to "downvote" a comment.

The AI gold rush feels like it rewards teams who ship fast. Many teams are working on a 9-9-6 (9am-9pm, 6 days a week) schedule to keep up with the state of the art breakthroughs and features. Does this give teams an edge against their competition or is this slowly burning teams out.
If you're building in the AI space, I would love to hear what your take is:

• What works for your team and do you follow the 996 schedule?

• Did following a 996 culture create more bugs or actually lead to breakthroughs and push you ahead of your competition?

• How would you balance your life outside of work if you followed this schedule?

Making this post to raise awareness and ideally find a middle ground for teams that are currently growing and trying to keep up with the competition

Being an engineer myself, I see that many people are outputting more code than ever. Some of it being generated vs. written, the volume of code being outputted has definitely risen. 
There seems to be a shift from "is this something we can build?" to "should we build this and ship it?"
For people who have been recruiting or looking to recruit recently, what roles are you hiring for? 

1. Role title (I've seen a rise in PM's and Designers personally)

2. What exactly can they do that AI can't (yet)

3. Specific signal that you look for when hiring

Are you moving headcount from one type of role to another? 
Would be interested to hear from other growing teams! 

Traditional professions like doctors, judges, and the like need specialised academic guidance (certificate) + experience. I agree.

But what about technical and humanities? So far, everyone has argued that a university will bring contacts (I'm not arguing, that's true... but the same can be done with hustling/projects).

With this whole AI trend, many tools are trying to be invisible: not apps you open, but helpers that quietly run in the background. They show up just enough interface: a chat box, a nudge, or an API call to deliver value, but otherwise stay out of sight.

With today s agent hype, this idea feels like it s accelerating. Agents promise to handle tasks across your apps without you lifting a finger.

I launched my SaaS company, Encharge, in 2019 with less than $1,000 in my account, no funding, no network, no audience, and no accelerators. It generated $2 million before we sold it. Here are 17 things I learned from it.

1. Startups are a last-man-standing game.

The one to win is not the fastest, smartest, or best. It's the most persistent and resilient.

Today, I am co-organising my first hackathon in my country, and I will give a talk to the participants about Product Hunt as one of the ways to distribute a product.

Some participants may hear about the platform for the first time, and I would like to encourage them a little in building and launching products.

Today, I came across an article on Techcrunch describing research that found that AI models not only hallucinate, but also lie.

While these are small lies, such as claiming that a task was completed when it wasn t, researchers stress they haven t seen harmful scheming in real-world use yet, but warn risks will rise as AI takes on more complex tasks.

I work at an early stage startup and I'd estimate 70-80% of our codebase is vibe coded (510k lines). To be clear, it's not 1 shot "build this feature." More like, "implement get_slim_documents for Jira in the exact same way we did it for the Confluence connector."
Comfort with AI coding tools is actually something we gauge during interviews/work trials. Looking at our peer companies, it's exactly the same.
My hypothesis/assertion is that companies founded ~2022+ are fundamentally intertwined with "vibe coding." In 5 years, programming will connote vibe coding more than it will connote non-AI assisted work.
Am I crazy? Pigeon-holed in the SF startup world? Naive? Would love to hear more thoughts/diverse perspectives on this.

While developing, we spent good amount of time in making small changes from UX perspective. And users liked it.

We continued to watch after our public launch. And visiting some customers' office and quietly observing them use MarketFit, gave us a few new insights- as small as removing 2 words from an onscreen message, or enhancing the video demo so that users are able to realize 100% benefits or just changing relative position of menu items.

Supabase recently surveyed over 2,000 startup founders and builders to uncover what's powering modern startups: tech stacks, GTM, and approach to AI.

See full report here