I'm renaming Axtra Planner to just Axtra. Here's why.
Two weeks into building in public, I'm dropping the "Planner" from the name. New home: axtra.app.
Quick context for anyone new: I've been documenting the build of a day-planning app here. Launched May 4. Got my first paying users. Posted daily about what was working and what wasn't.
Then two pieces of feedback landed in the same week.
The first came from another founder commenting on one of my posts here. He pointed out that the people who'd pay for what I'm building don't live in my LinkedIn network. "Pain-shaped users" was the phrase. It reframed everything I was doing wrong with cold DMs.
The second came from a designer who walked me through her use of the product. She didn't want a smarter way to drag blocks around. She wanted the calendar to know that the clinic she scheduled is on lunch break at the time she picked. She wanted location auto-fill on "Trip to airport." She wanted the calendar to know what was happening outside the calendar.
That second piece of feedback is the one I couldn't unsee.
"Planner" describes the substrate. The thing I keep wanting to build is what sits on top of the substrate. A calendar that prepares you. That knows the entities around each event. That warns you when a scheduled event collides with reality.
The first version of that ships next: event location auto-fill, then drive-time-aware buffers, then place-metadata that flags collisions. Each layer adds context the calendar didn't have before.
Dropping "Planner" is just admitting that out loud.
Same product. Same data. Same account if you're already using it. The old URL (planner.axtrastudios.com) keeps redirecting to axtra.app, so existing bookmarks don't break.
If you've been following: thanks for sticking around. The name change is the easy part. The harder part is shipping the thing the new name now describes.
This is the right rename direction. “Planner” made it sound like another manual scheduling tool, but the product you’re describing is closer to contextual calendar intelligence.
The sharpest line here is “a scheduled event collides with reality.” That is much stronger than day planning. It gives the product a real system-level promise: not just helping users plan, but catching the missing context around the plan.
I’d be careful with Axtra though. It is shorter, but it still does not clearly carry the bigger idea yet. If the product keeps moving toward entity-aware scheduling, location context, drive-time buffers, and real-world event intelligence, a cleaner platform name may age better.
Something like Xevoa.com fits that direction more naturally because it sounds less like a planner app and more like an intelligence/workflow layer sitting above the calendar.
Honestly, I had the same worry halfway through today's work.
"Axtra" on its own doesn't telegraph "intelligence layer." Three reasons I held the line on it anyway:
The studio is Axtra Studios. A product name further from the parent creates a gap that has to get resolved later. Going to something like Xevoa means I either rebrand the studio too or live with a permanent mismatch.
Axtra was picked deliberately as a non-descriptive brand. It can carry whatever the product becomes. "Planner" was the part that locked it to one thing. Dropping that gives the brand room to grow without forcing a third rename when the next layer ships.
Two renames in 14 days has its own cost. The first one happened partly because of the line your earlier comment kicked off ("pain-shaped users don't live in your LinkedIn network"). Doing a second one this week trains people that the name isn't stable. That's worse than not having the perfect name on day one.
What's actually coming behind the rename:
Each one is the "catching the missing context around the plan" thing you described, made concrete. Axtra is the platform those features live under.
If 6 months from now the product is fully entity-aware and "Axtra" still feels too planner-y, that's a real conversation. But I'd rather earn the right to rename again by shipping what the rename promises first.
That’s a fair call.
The studio mismatch point is probably the strongest reason not to force another name right now. If Axtra already has parent-brand logic behind it, then the immediate job is making the product promise sharper around the name, not creating more naming instability.
The feature roadmap makes the direction much clearer too. Location auto-fill, traffic-aware buffers, and clinic-hours collision warnings are where it starts feeling less like planning and more like real-world context recovery.
I’d probably judge Axtra by one thing over the next few months:
Do users start understanding it as the layer that catches what the calendar misses?
If yes, the name can carry. If not, then the rebrand conversation becomes much easier because the category will be proven by then.
yeah, that user-language test is the right one. flips the whole question from brand exercise to user-language exercise.
going to start logging how people describe what they're doing in axtra. if the category proves itself, the name follows. if not, the name was the wrong worry anyway.
ping me back on this in 2-3 months.
That’s the right way to frame it.
If users naturally start saying something like “Axtra catches what my calendar misses,” then the name can probably carry because the category is becoming clear through usage.
If they keep calling it a smarter planner or scheduling helper, then the issue may not be the name yet — the product promise still needs to sharpen.
Either way, logging exact user language is the right move.
I’ll check back in 2–3 months once the location/context features are live. That will be a much cleaner time to judge whether Axtra is carrying the platform direction or whether the category needs a stronger name.
Also, happy to stay connected on LinkedIn if easier — this is exactly the kind of naming/category shift that’s worth watching as the product matures.
The framing you're pointing to is a useful distinction. I'd been collapsing those two failure modes into one, and it changes what I'd look for in the user-language data.
Logging starts this week. Probably an Airtable column or similar so I'm working from actual data in 2-3 months, not just my memory of what people said in passing.
Also, LinkedIn works. Let me know your profile and I'll send a request tonight. Way easier to keep this thread alive as the product matures than to start it over every few months.
Here’s my LinkedIn:
https://www.linkedin.com/in/aryan-y-0163b0278/
And yes, happy to stay connected there.
One thought before we wait 2–3 months though: the user-language test is useful, but the brand will also get harder to change the more you ship under Axtra.
So I’d still pressure-test the naming direction lightly now, not necessarily rename now.
The question is simple: if the product becomes “the layer that catches what your calendar misses,” does Axtra feel like the right company/product brand to carry that, or is it just the current studio name doing the job?
That’s probably worth thinking through privately before the next features make the name more fixed.
You're pointing at the distinction I keep blurring: studio name vs product brand. Axtra Studios can stay Axtra Studios. The product doesn't HAVE to share that name. I've been conflating them defensively because the studio name was the easiest reason to give for keeping the product name.
Honest question, since you've been the sharpest voice on this: if you were building this product, what would you actually name it? Not asking for a finished proposal, more curious where your head goes when you separate the company from the product.
I'm genuinely okay with Axtra for now and the user-language test still feels right. But you're correct that the cost of change goes up every week. Worth thinking through while it's still cheap.
LinkedIn request sent btw!
That distinction matters a lot.
If Axtra Studios stays the company layer, then the product name does not need to carry the studio logic. It only needs to carry the user promise.
If I were naming the product, I’d avoid anything that sounds like planner, calendar, schedule, or assistant. Those words pull it back into a crowded category.
The product you’re describing is closer to a context layer above the calendar. It notices the missing reality around an event: location, drive time, opening hours, buffers, friction, and timing risk.
So I’d want a name that feels like a system, not a feature.
That’s why Xevoa.com came to mind first. It feels more like an intelligence/workflow layer than a calendar app, and it gives the product room to grow beyond planning without sounding too abstract or too soft.
I would not rename just to rename. But if the product brand is separate from Axtra Studios, then this is exactly the right moment to compare Axtra against a cleaner product brand before more users attach meaning to it.