Thomas Plat

WE JUST HIT 1,000 USERS 🎉

8 days ago this didn't exist

Today there are 1,000 founders on Strivle.

This is honestly CRAZY. I built this last weekend because I was bored, fully expecting nothing to come from it, and now there are 1,000 of you here building, posting, helping each other, telling your friends about it. Watching this community come together has been one of the best weeks of my life.

To every single one of you posting your progress, dropping feedback in my DMs, sharing the platform without me asking, defending it in Reddit comments, just being here, thank you. This is your community as much as it's mine and I mean that. None of this happens without you.

Here's where we're going from here.

The next few weeks are going to be massive. Mobile app dropping on the App Store soon so you can post from anywhere. Public profile pages so your work shows up on Google when people search you. More verification integrations beyond Stripe so pre-revenue founders, mobile founders, and people using other payment processors can all be seen for what they ship. Bookmarks, better DMs, smarter notifications. A real Signal score so the ranking reflects more than just MRR.

We've got TinyLaunch live right now and Product Hunt right after, going for #1 of the day. If we hit it, this thing goes to a whole different level.

But the part I'm most excited about isn't the features or the milestones. It's that we're building the place builders should've had a long time ago. Somewhere your work gets seen on merit. Somewhere the loudest voice doesn't win. Somewhere being early actually matters because the network you build here will compound for years.

You're early. You'll always have been early. The first 1,000 on a platform like this become the names everyone references later.

Let's keep going. Next stop, 10,000.

I just can't stop.

A few weeks ago, I told myself I'd stop building features and focus on marketing. Instead, I spent the last few days rebuilding Jetpacked's landing pages.

The problem wasn't the design. It was the positioning.

Without realizing it, the website was trying to compete with platforms like Vercel and Railway. That was never why I started Jetpacked.

I built jetpacked.ai because I kept seeing builders struggle with real-world deployments. Not perfectly structured demo apps, but messy applications, legacy projects, and side projects that still need to get online.

I wanted Jetpacked to be a place where builders get help after they've finished coding. A platform that guides you through deployment instead of expecting you to figure everything out yourself.

So I reworked the site to reflect that:

• The homepage now focuses on deploying anything . Even messy apps and saving builders time.
• There's a much stronger emphasis on the human side of Jetpacked and making complex infrastructure approachable.
• I added a Stacks page so it's clear what Jetpacked supports (and what it doesn't).
• The Stories section now includes customer testimonials and the story behind why I built Jetpacked in the first place.

It's still a work in progress, but it finally feels aligned with the vision I had from day one.

I'd love some honest feedback on the new website.

Pricing is one of the topics that are definitely hard to get right. In order to offer a fair and sustainable pricing model, you first have to understand your own product.

I spent the last couple of days rethinking the pricing model for Jetpacked and ended up switching from subscription-based pricing to per-project pricing. Here is what I learned.

There is no need to obsess over subscriptions

Subscriptions are amazing. I love binging Netflix, but not every product naturally fits into a subscription model.

For Jetpacked, the problem was that projects are not equal.

One user might have:

- A production SaaS serving real customers

- A tiny staging app

- Three experiments they haven't touched in months

Trying to fit all of that into "Starter", "Pro", and "Premium" plans felt artificial.

Users think in projects, not accounts

If one project suddenly gets traffic, why should the user have to upgrade their entire account?

What they actually want is: "This project needs more power." and not "I guess I need the Pro plan now."

Pricing should follow value

The more I thought about it, the more it became obvious that the project itself is the unit of value.

A project can be:

- Free

- Small

- Production-ready

- High traffic

Each project can grow independently.

Sometimes the best product decisions come from realizing you've been forcing a familiar business model onto a product where it simply doesn't belong.

Read more on our blog: jetpacked.ai/guides/project-based-pricing-is-no…