Valerium ∇

What was the first thing you charged for in your SaaS?

SaaS founders today are basically: 90% shipping 5% talking to customers 5% hoping the launch post finds buyers If you're building in #tech, let's #connect!!!

Show annual pricing upfront. Hiding it makes the monthly option harder to compare.

What happened to the first AI feature you shipped?

Founders should write the first version of the sales page themselves. You learn what customers actually buy before you hand the story to someone else. If you're building in #buildinpublic, let's #connect!!

Which SaaS metric is hardest to improve? - activation - retention - expansion

Founder problem: You can ship fixes so quickly that the onboarding screenshots are outdated before a new user sees them. If you're building in #tech, let's #connect!!

Claude drafts the feature spec. I spend an hour removing features it confidently invented.

I would not call an AI feature defensible just because it uses a strong model. If another SaaS can add the same prompt and API, customers have little reason to stay with yours. The edge has to come from the workflow, context, or distribution around the model.

Nobody warns you what building in public leads to. - Drafting launch posts - Explaining a rollback - Screenshot archaeology Very public. The changelog needs a changelog. If you're building in #buildinpublic, let's #connect!!

When runway gets tight, what do you cut first? - Paid ads - Contractors - Your own pay

You copy a competitor's AI feature. Your roadmap gets longer. Your product gets harder to explain. The feature may be useful, but if you can't name the customer problem it solves, you've added complexity without giving buyers a reason to choose you.

A SaaS feature flag should have an expiry date. Permanent flags turn every release into a second product to maintain. If you're building in #tech, let's #connect!!

If you only post wins, you're not building in public. You're running a launch campaign. If you're building in #buildinpublic, let's #connect!

You post the launch. The wrong people show up. A broad announcement can bring attention from people who like the idea but will never use the product. Then you mistake replies for demand and build for an audience that won't become customers.

I'd rather lose a SaaS customer in one click than keep them through a cancellation maze. A trapped customer isn't retained. If you're building in #tech, let's #connect!!

You ship the feature users requested. Support tickets go up. They wanted the result, not another screen to manage. Before adding a new control, ask what they were trying to finish.

Build in public works better when you share the decision you changed, not just the feature you shipped. If you're building in #buildinpublic, let's #connect!!

The brutal truth about SaaS onboarding: Users don't explore. They guess. They get stuck. Design for that.

The fastest way to mistake a waitlist for demand: count signups instead of follow-through. People will leave an email for a product they may never try. Ask them to take one real next step. If nobody does, you have interest, not a business.