Launch week at 0 customers: a 7-day debrief

Treelance launched 7 days ago. Here's the honest accounting:

• 59 views on the IH launch post, 12 comments (most from one substantive exchange with a designer in the thread)
• 6 views total on the founder Twitter account, including 5 from a #buildinpublic post
• Site analytics show 45 visitors over the week, but a meaningful portion of that is probably me testing. Real external traffic is likely in the single digits.
• 0 customers
• 0 followers on the founder Twitter account at launch, roughly the same now

And one design feedback exchange that's done more for the product than any of the numbers above. This is the debrief I wish someone had written for me before I launched.

What I shipped and how it landed

I launched Treelance on a Thursday morning. No Product Hunt, no big push. Just the IH post, a Twitter thread to a 0-follower account, and a quiet site that hadn't seen real traffic before.

The numbers were small in the way I expected. The IH algorithm doesn't surface fresh-account posts from solo founders with no platform history. A Twitter thread to 0 followers stays there. My analytics dashboard shows 45 unique visitors over the week, but when I look honestly at that number, most of it is probably me testing on two different machines and someone I asked to test it for bugs. The actual count of strangers-who-found-treelance.app this week is probably in the single digits.

That's an uncomfortable number to state directly. It's also the truth.

The lesson from the metrics: launch numbers for a 0-follower founder are not a signal about the product. They're a signal about the distribution work that wasn't done before the launch. Treelance got small numbers because Treelance had 0 followers, not because Treelance is or isn't a good product. Those are different problems and I'd been conflating them.

The unexpected value

About 18 hours after the launch post went up, someone in the IH thread left a substantive comment. Not the usual "looks great, congrats" comment. A real design critique.

The critique was specific: my brand wasn't conveying enough trust signal. The green I'd chosen read as soft. The visual weight wasn't carrying the operational confidence the copy was claiming. As a designer working in an adjacent product space, she could tell my visual identity was undersold relative to what I was offering.

My first reaction was defensive. The brand was something I'd worked on for weeks. I'd thought through it carefully. I'm glad I didn't reply immediately.

When I came back to the thread a few hours later, the critique was still right. She wasn't wrong about the brand. She was telling me something I'd been half-noticing myself but hadn't named. The conversation that followed went four rounds across multiple days. We went back and forth, surfaced the actual disagreement, and both moved a step.

By the end of it, three things were underway that I hadn't planned for launch week:

-Rebuilding the brand mark with significantly heavier visual weight
-Reframing the catalog around brand-coherent design across founder products, not just App Store submission
-A real professional relationship with someone I'd never have met without the launch

The math here is uncomfortable for the founder ego: one substantive conversation with one peer in your space is worth more than 100 strangers viewing your post. The launch isn't the asset. The launch is what might attract a peer's attention. The peer is what compounds.

What I learned about the product

A week of looking at this honestly has changed where I'm pointing the product.

I led the launch with App Store submission. Screenshots, ASO copy, the submission pack. That was case study zero because it was the product I'd built for my own app first.

It's also a competitive category. AppScreenshotStudio, AppDrift, AppShots, AppLaunchpad, and several other AI-native tools have made App Store screenshots into a near-commodity at $9-39/mo. Competing there means competing on price and feature parity, which is the wrong fight for a solo founder without a clear single-product advantage.

The thing I have that those tools don't have: brand consistency across every product an indie founder ships. Screenshots, OG cards, Instagram packs, Twitter headers, pitch decks, press releases, social posts. Same brand, every output. No competitor delivers this. The catalog itself is the moat, and I'd been spending the launch arguing for one product instead of the system that makes them all work together.

So the next thing I'm building, shipping in the next 2-3 weeks, is a conversational Studio for brand-coherent design across that broader catalog. Same pipeline underneath, same human review layer for the writing and strategy products, but a different front door. One that demonstrates the brand-coherence story instead of just claiming it.

The App Store products stay in the catalog. They're just not the lead anymore. There are better tools for that one job. There's no better tool for the bigger one. This isn't customer signal yet, it's competitive analysis and product thinking. Customer signal will follow when there's something new to react to.

Where this leaves things

7 days in, single-digit real visitors, 0 customers, 1 relationship that mattered, and a clearer picture of what Treelance should be than I had on launch day.

If you're launching as a solo founder with no audience, expect small numbers, watch for the peer who shows up with sharp feedback, and treat the launch as the first conversation, not the last. The numbers from week 1 aren't the product's verdict. They're the distribution work that hadn't happened yet.

The build continues. Studio ships in a few weeks. I'll write again when there's something to show.

Treelance: https://treelance.app
On X: @nithya_builds and @treelance_app (product)

Thanks for reading.