u/Forward-Practice-625

Our Founder was scrolling X late at night.

Ghibli-style portraits were everywhere. Every other post. Flooding timelines.

He closed the app. Opened it again. Still everywhere.

He texted the team.

"We're building this. Tomorrow."

Nobody asked "are you sure?" Nobody said "let's think about it."

We just moved.

Day 1 & 2: → Bought ChatGPT Plus to unlock Ghibli generation → Built a landing page from scratch → Set up photo upload and preview flow → Basic email automation to receive and send images back

Payment gateway wasn't ready yet.

So we did what any scrappy team does.

First customers were handled entirely over email. Someone paid. We generated their portrait manually. Sent it back.

Chaotic. Manual. But it worked.

By Day 3, payments were live.

We pushed SnapArt on our personal social accounts. No ads. No influencers. No budget.

Just us, our networks, and a product that was exactly what people wanted at exactly the right moment.

Then the first payment notification came in.

I don't think any of us expected to feel what we felt.

It wasn't about the money.

It was the proof.

Someone found us, trusted us with their photo, and paid for what we built overnight.

That meant everything.

What followed was one of the most electric weeks we've had as a team.

Customers sending in photos of their families. Couples gifting portraits to each other. One customer's wife cried happy tears seeing her Ghibli portrait.

We weren't just riding a trend. We were creating memories for people.

5,000+ photos processed. A payment every 4 minutes. One week. Zero paid marketing.

After 7 days, we called it off.

Not because it stopped working. Because we knew what it was — a trend window, not a long-term business.

Riding it longer would've been chasing noise.

So we shipped. We learned. We moved on.

The thing nobody tells you about working at a startup:

It's not the big milestones that stay with you.

It's the 11pm "we're building this tomorrow" text. It's the first manual order processed over email. It's watching the first payment come in on something you built in 48 hours.

That's what makes you never want to go back.

https://preview.redd.it/d1m6ncgh8rqg1.png?width=2152&format=png&auto=webp&s=3ff59d7f5c4a9394d45a0b196d8aa60031d4a909

I watched a founder make a ₹50 lakh mistake.

We were just starting out. He reached out for help.

Former merchant navy captain. 20+ years at sea. Building an app for crew members.

"How long have you been building?" I asked.

"14 months. We're almost there."

14 months. My stomach dropped.

"How many crew members have tested it?"

Silence.

"None yet. We want it to be perfect first."

Here's the thing:

This guy KNEW the problem inside out. He lived it for two decades.

He knew exactly what features crew members needed. What pain points to solve. What the app should do.

But he had zero idea how to:

• Get the first 100 users
• Keep them coming back
• Build a distribution engine
• Create a GTM strategy

His agency was bleeding him dry. Slow development cycles. Feature after feature. No urgency.

No marketing happening. No waiting list being built. No early testers giving feedback.

Just... building. In the dark. For over a year.

Domain expertise is powerful.

But it's not enough.

Because knowing the PROBLEM ≠ knowing how to build a BUSINESS around solving it.

The captain knew what crew members struggled with.

But he didn't know:

• How to capture their attention in a noisy market
• How to get them to download and actually use the app
• How to retain them after the first session
• How to turn them into advocates who'd bring others

Those are different skills. And he was learning them the expensive way.

The brutal truth?

5 early testers would've saved him 12 months.

5 crew members using a half-built version would've told him:

• "This feature you spent 3 months on? We don't care about it."
• "This thing you didn't build yet? That's what we actually need."
• "We'd use it, but not the way you think. Here's how we'd actually use it."

Instead, he's about to launch something that might be technically perfect but commercially DOA.

If you're building something right now:

Stop asking "Is it ready?"

Start asking "Who's using it?"

Because the market doesn't reward perfect products.

It rewards products that solve real problems in ways people will actually adopt.

And you can't know that until real people are using it.

Get 5 users. Today. Not when it's "ready."

Let them break it. Let them tell you what's wrong. Let them show you what you missed.

That feedback is worth more than 6 months of isolated development.

The captain had the domain knowledge. He just needed to let the market in before it was too late.

https://preview.redd.it/zshjpqj578pg1.png?width=2110&format=png&auto=webp&s=4a5cf7c36db2da95ab9e852338e1d3a81fd1b17f

Our founder was a backend engineer at Wells Fargo.

Good salary. Stable job. Clear career path.

He walked away from all of it.

What I've watched him do since is something they don't teach in any MBA.

Every new problem he faces — he doesn't delegate it first.

He does it himself.

Sales? He was the one scrolling LinkedIn, DMing potential clients manually before anyone else touched it.

Operations? He mapped every process by hand before building automation around it.

Hiring? He interviewed everyone himself first before trusting anyone else to do it.

Once he understood it ground up — THEN he built systems around it. THEN he passed it on.

The pattern is always the same:

Jump in → understand it → stabilise it → systemise it → delegate it.

Most people think founding a startup is about vision and delegation.

It's not.

It's about being the first person willing to do the unglamorous work.

Before you can lead a sales team — sell yourself. Before you can manage engineers — understand the code. Before you can delegate operations — run them yourself.

You can't build systems around things you don't understand. You can't hire well for roles you've never done. You can't spot when something's broken if you've never done the work.

Delegation is the goal.

But doing it yourself is always the starting point.

https://preview.redd.it/ofkvr24fxeog1.png?width=2678&format=png&auto=webp&s=25675a60d038f412f2c1659878cdd652c3f83567

We made meaningful revenue in one week.

Zero paid marketing. No investor money. 6 people and 72 hours.

Here's what actually made it work — and what most people miss about capitalising on trends.

When Ghibli portraits flooded X in April 2025, everyone wanted one.

But there was a gap nobody had filled:

Most people didn't have ChatGPT Plus. Nobody was offering it as a framed gift. No simple product existed for the non-tech crowd.

We didn't invent the trend. We just saw the gap faster than everyone else. And moved before the window closed.

Here's the framework we used (consciously or not):

1. Trends don't need perfection. They need speed. We launched with manual email fulfillment before our payment gateway was ready. Imperfect. Didn't matter.

2. Emotion converts faster than features. We didn't sell "AI portraits." We sold gifts. Memories. Framed nostalgia for your loved ones. That's why people bought.

3. Know what it is — and what it isn't. We rode it for a week. Then stopped. Because a trend window is not a business. Confusing the two is expensive.

4. Entry price removes friction. $0.99 for a digital image meant impulse buys. Low commitment = high volume. Simple math.

Most businesses wait for the perfect moment to move.

The trend had already peaked by the time they finished their planning doc.

Speed is a skill. Reading the room is a skill. Knowing when to stop is also a skill.

SnapArt wasn't our biggest project.

But it was proof that the instincts we bring to client work are real.

We don't just build. We think about revenue, timing, and what actually makes people buy.

That's a different thing entirely.

https://preview.redd.it/wad456jdp7og1.png?width=836&format=png&auto=webp&s=2063702ada0428cedb12500a7ad1d81d53944041

Early in our startup journey, I started asking founders one simple question:

“Who’s actually using your product right now?”

The answer usually tells me everything I need to know.

Here are some common answers I hear:

The dangerous ones:

• “We’re still building. Launch is in 3 months.”
• “We want to get it perfect first.”
• “We have a beta list of 500 people ready to go.”

To me, that usually translates to: they’re building in the dark.

The better answers sound like this:

• “We have 8 people testing it and here’s what they told us last week.”
• “We launched with 3 features. Users asked for X, so we’re building that next.”
• “Half our early testers dropped after day 2. We’re trying to figure out why.”

That means they’re building with the lights on.

A beta list of 500 people means almost nothing.

But 5 people actually using your half-built product? That’s gold.

Because those 5 people will tell you the truth.

Not what they might do when you launch.

What they’re actually doing right now.

The market doesn’t care about your roadmap.

It only cares whether your product solves a problem well enough that people actually use it.

And you can’t fake that insight.

You only get it by letting real users in earlier than feels comfortable.

So I’m curious:

Who’s actually using your product right now?

Not “who’s interested.”
Not “who signed up for updates.”

Who is using it today — breaking it and giving you real feedback?

If the answer is “nobody yet,” you might be building blind.