We renamed our SaaS from LinkedCraft to Postessia — here's what forced the decision
We renamed our SaaS from LinkedCraft to Postessia — here's what forced the decision
What I shipped:
Complete rebrand — new name, new domain (postessia.in), updated positioning, new logo assets.
Revenue: Pre-launch. First paid users targeting July 1.
The real reason for the rename:
LinkedCraft had "Linked" in the name.
LinkedIn is a registered trademark. Using it in your product name — even indirectly — puts you in legal grey territory. The risk: a C&D letter that forces you to rebrand under pressure, lose domain authority, confuse early users, and restart from zero.
I didn't want to build a user base on a name I didn't legally own the right to use.
So I made the call at pre-launch stage — the cheapest possible moment to do it.
What I learned:
-
Validate your name legally before you brand anything. Check trademark databases. If your name contains another brand's name — even partially — you're exposed.
-
Pre-launch is the only "free" rebrand window. Post users, post content, post backlinks — every day you wait makes the rebrand more expensive.
-
The name change surfaced deeper product clarity. "Postesia" = posts + ease. The positioning sharpened: we're not a LinkedIn tool. We're a content voice engine that happens to publish to LinkedIn.
What's next:
• July 1 launch with early agency users
• Targeting ₹1L MRR by December 2026
• Stack: Next.js + Supabase + Vercel + Claude Haiku
If you're building a niche SaaS in India — happy to trade notes.
What's one naming/branding decision you wish you'd made earlier?
The part I kept coming back to wasn't the trademark issue.
It was that a naming decision ended up changing how you describe the product.
That feels bigger than a rebrand.