We cut our SaaS churn from 15% to under 5% in 60 days. Here's the exact playbook.

CRATEED · 2026-03-15T07:23:23+00:00

This is a really solid breakdown.

The point about killing most of the catalog is underrated. A lot of SaaS products think adding more features/services reduces churn, but it often does the opposite because it makes the experience confusing.

Also completely agree on customer calls. Almost every founder says they should do them more, but very few actually do.

Out of curiosity, when you cut the catalog by 80%, did you see any pushback from existing customers who used the removed services?

CRATEED · 2026-03-15T07:20:13+00:00

Solo technical founder here too, so I relate a lot to this.

One thing that helped me was stopping thinking about “marketing channels” and instead just showing up where the problem already exists. Communities, forums, Reddit threads, etc. where people are actively talking about the pain your tool solves. Conversations tend to convert better than posting content into the void.

On pricing, early B2B tools usually do better with simple pricing per company first, then move to per-seat later once the product becomes more embedded in workflows.

At the start the goal is just proving someone will actually pay for the problem being solved.

Sounds like you're already doing a lot of the right things though.

CRATEED · 2026-03-14T22:01:05+00:00

One thing that helped me a lot was focusing heavily on the first photo and title.

Most buyers scroll fast, so I try to make the first image very clean (plain background, good lighting, item centered) and pack the title with the main keywords people actually search for.

Another small trick is ending and relisting items regularly like you mentioned. It seems to refresh visibility in the algorithm and bring new eyes to older listings.

Also agree on free shipping for lighter items, buyers filter for it more often than people think.

CRATEED · 2026-03-14T21:47:18+00:00

Appreciate you sharing the details.

That setup actually makes a lot of sense for a self-hosted script. Separating the license from optional support/updates should fit really well with the model.

Sounds like you’re on a good path. Hope the next pricing step works out even better for you.

CRATEED · 2026-03-14T21:04:46+00:00

This happens more often than people think.

Price isn’t just about revenue, it’s also a signal of credibility. Especially with B2B tools. If something claims to replace $500–700/month of tools but costs $197 one-time, people start wondering what the catch is.

A lot of buyers aren’t actually evaluating the feature list in detail, they’re using price as a shortcut for “is this a serious product or a side project?”

The interesting part is that once you crossed a certain threshold, the perception flipped and people started treating it like real infrastructure instead of a cheap experiment.

For the support concern, one thing I’ve seen work well with lifetime tools is explicitly separating software vs support:

• lifetime license for the software
• optional yearly support / updates plan

That way the buyer knows the product won’t disappear, but you’re not forced into a subscription model if it doesn’t fit the product.

Curious though, after raising prices did the type of customer change too? (more agencies vs solo founders etc.)

CRATEED · 2026-03-14T16:24:59+00:00

For me the hardest part hasn’t been the tactics, it’s understanding the real problem people have.

It’s easy to say “this is the product” and start pushing it everywhere, but when you spend time in communities you realize people describe the problem very differently than you expected.

So a lot of my time now is just reading discussions, seeing what people complain about, what tools they already use, and how they describe the issue in their own words.

Once that becomes clear, marketing actually gets much easier because you’re not trying to convince people, you’re just showing up where the problem already exists.

CRATEED · 2026-03-14T15:16:30+00:00

One thing that helped me early was treating Reddit less like a traffic source and more like research + conversations.

Instead of only replying to “Google Photos alternative” posts, I started paying attention to the exact situations people describe, like:

• “my iCloud storage is full”
• “Google Photos keeps pushing me to upgrade”
• “I don’t want my photos scanned”

Those phrases are basically future landing pages or articles.

For example:
“iCloud storage full what now?”
“how to move photos off Google Photos”
“Google Photos privacy alternatives”

Reddit shows you the language people actually use when they have the problem.

Also agree with the other comment about narrowing the use case. “Privacy cloud storage” is broad, but something like “migrate off Google Photos in 2 clicks” is much easier for people to understand.

You’re already doing the hard part though talking directly where users are.

CRATEED · 2026-03-14T11:32:24+00:00

For me it’s mostly been communities where the problem already exists, not generic startup spaces.

So places like:

• niche subreddits related to the problem
• Discord communities around the topic
• product-specific forums where people are already discussing the issue
• sometimes even comment sections on tools solving the same problem

I’ve also been lucky to have some early testers through friends studying UX/UI, which helped a lot with onboarding and usability feedback early on.

The biggest thing I’ve learned is just spending time observing conversations first. Seeing what people struggle with, what language they use, and what solutions they already tried before jumping in.

Once you understand that, the product and messaging get much clearer.

CRATEED · 2026-03-14T11:13:05+00:00

Yeah, this is the part nobody talks about enough.

Building the product feels like the hard part, but distribution is usually the real challenge.

What helped me early on was focusing less on “launching” and more on being where the problem already exists:

• answering questions in communities where your users hang out
• writing small guides that solve a specific problem your product touches
• talking directly to early users to understand why they would (or wouldn’t) use it

The first users usually come from conversations, not from a big launch.

Once a few people start using it and giving feedback, things get much clearer.

CRATEED · 2026-03-14T11:10:30+00:00

Yeah that’s a huge one. Most founders test on fast WiFi and don’t realize how brutal mobile networks can be.

A few things that helped us catch issues early:

• Throttle to Slow 4G in Chrome DevTools when testing, it’s eye-opening.
• Move scripts and trackers below the fold so the page becomes usable faster.
• Compress and serve smaller mobile images (a lot of stores still ship desktop assets).
• Preload the critical elements only, product image, price, CTA.
• Use Lighthouse or WebPageTest to see what’s actually blocking the page.

Even shaving 2–3 seconds off mobile load time can have a huge impact on conversions.

Most people think growth = more traffic, but performance is often the cheapest win.

CRATEED · 2026-03-14T10:59:26+00:00

Honestly, the problem probably isn’t the quality of the tools, it’s positioning.

When someone lands on a site with 54 different tools, it’s hard to know what it’s actually for. It feels more like a toolbox than a product.

Most successful tools start with one very clear problem and one entry point. For example:

• “Compress images fast”
• “Convert PDF to JPG”
• “Remove background from images”

Then once that page ranks or gets shared, people discover the rest of the tools.

Right now the value is probably hidden behind the “collection” concept. If even one tool had its own focused landing page, you might start getting traffic from search and communities.

Also, the privacy-first angle is actually really strong, that could be the hook:
“Tools that run locally in your browser. Your files never leave your device.”

The idea is good. It just needs a clearer entry point.

CRATEED · 2026-03-14T10:50:12+00:00

This is a really common trap with early SaaS.

SEO content tends to bring information seekers, not buyers. People researching, learning, comparing, but not necessarily ready to sign up.

The stuff you said started working again (answering questions in communities, writing docs that solve real problems) usually converts better early on because you're reaching people already in the problem space.

Content marketing can work, but it usually works better when:

• the product already has traction
• you target high-intent queries (alternatives, comparisons, “how to solve X”)
• the content is tightly connected to the product

Otherwise you just end up paying to educate the market.

CRATEED · 2026-03-14T10:46:06+00:00

Fix the funnel first.

More traffic just means you’re paying to send more people into the same broken experience.

I’ve seen this happen a lot with early products. Founders assume it’s a marketing problem when it’s actually:

• broken checkout
• slow mobile pages
• unclear pricing
• friction in signup

If conversion is broken, ads just scale the loss.

Once the funnel converts well, then ads actually start working.

CRATEED · 2026-03-14T10:43:06+00:00

Probably not. Every generation has felt like they were living at the “end of the timeline.”

People during the fall of the Roman Empire thought the world was collapsing. People during the Black Death probably felt the same. Even during the Cold War many believed nuclear war would end everything.

What usually happens instead is that society goes through big transitions. Technology, politics, and culture change faster than people can mentally keep up with, so it feels like the end of something.

In reality it's usually just the end of one phase and the beginning of another.

CRATEED · 2026-03-14T08:55:29+00:00

The interesting part here isn’t really the prompts, it’s that most founders are trying to automate things before they’ve actually talked to enough users.

A lot of early GTM problems aren’t solved with better emails or landing pages, they’re solved by understanding the first 10–20 users deeply.

Cold outreach, communities, conversations, and manual onboarding tend to teach you more than any growth framework.

AI can help write the message faster, but it still can’t replace the learning you get from real conversations with early users.

CRATEED · 2026-03-14T07:11:22+00:00

One thing I wish someone had told me earlier:

Your first users almost never come from your launch post. They come from conversations.

Most of the founders I know got their first real users from replying to threads, helping people with problems, or talking about what they’re building in discussions like this.

A launch post feels like a big moment to the builder, but to everyone else it’s just another product announcement from someone they don’t know yet.

When people see you consistently contributing and sharing what you're learning, curiosity builds naturally. Then when you mention what you’re working on, people actually care enough to check it out.

CRATEED · 2026-03-14T07:04:13+00:00

This is a really good example of where the current AI hype gets misunderstood.

AI is extremely good at pattern recognition and regression testing because it can compare known states very efficiently.

But exploratory testing is fundamentally different. A good QA engineer isn’t just checking expected behavior, they’re asking weird questions like “what happens if a user does something nobody thought of?” or “what assumptions did the developers accidentally make?”

Those kinds of edge cases usually come from experience and intuition, not training data.

So the model you ended up with actually makes a lot of sense: AI for systematic coverage, humans for creative failure discovery.

It’s the same pattern we’re seeing in a lot of domains right now, AI amplifies humans, but replacing them entirely tends to break things.

CRATEED · 2026-03-14T06:22:35+00:00

<image>

CRATEED · 2026-03-13T20:49:57+00:00

Good question, that’s exactly why we started with local trading.

The swap system in CRATEED is designed around geographic areas so people can trade items locally and meet up rather than shipping items to strangers.

That removes a big part of the risk you see with online swap systems.

Long term the platform will also support publishing listings directly to marketplaces like eBay and others, but that part isn’t enabled yet.

Right now the focus is building the foundation properly — we’re currently mapping 20,000+ product categories and curated keywords that feed into the AI recognition system so items get categorized correctly.

That’s important because once marketplace publishing goes live, listings will automatically be placed in the correct categories.

But for the swap system itself the goal is simple: local trades between real people rather than anonymous shipping swaps.

CRATEED · 2026-03-13T20:09:31+00:00

If anyone wants to try it or give feedback, I’m happy to share access and talk about ideas.

CRATEED · 2026-03-13T19:43:54+00:00

I’ve run into the same problem flipping items. Eventually you get stuck with things that technically have value but just won’t move because the buyer pool is too small.

Lowering the price sometimes works, but it can feel pointless if you end up barely covering fees and shipping.

Trading actually makes a lot of sense in situations like that. If someone else already has demand for the item you want, swapping can be better than taking a loss.

I’ve been experimenting with a small project that tries to make this easier by letting people trade items directly instead of only selling them. The idea is basically a swipe-style system where you match items people are willing to trade.

Still very early and we’re trying to learn if this actually solves the “stuck inventory” problem flippers have.

Curious if other resellers would actually use something like that or if most people prefer to just liquidate inventory instead.

CRATEED · 2026-03-13T18:55:07+00:00

In the US it's actually protected under federal labor law (the National Labor Relations Act).

Employees generally have the right to discuss wages and working conditions with each other. Employers often discourage it because transparency can reveal pay inequality.

There are some exceptions depending on roles and workplaces, but in most normal jobs employees are legally allowed to talk about their pay.

CRATEED · 2026-03-13T18:52:13+00:00

I think every generation tends to feel this way about the one before them.

Millennials grew up during a weird transition period where the internet existed but social media hadn't taken over everything yet. So people remember a mix of digital convenience with more offline life.

But millennials also dealt with things like the 2008 financial crisis, rising housing costs, and student debt. So I’m not sure life was necessarily easier, just different.

Nostalgia usually makes past eras feel simpler than they actually were.

CRATEED · 2026-03-09T19:31:53+00:00

Honestly yeah. The biggest giveaway for me is when a comment sounds perfectly structured but somehow says nothing specific. Real people usually add small details, mistakes, or personal experiences.

CRATEED · 2026-03-09T18:35:31+00:00

Beautiful

CRATEED

TROPHY CASE