Quant Became IPMATHics. Intelligence Became Strata.
For a surprisingly long time, two of the three products were basically named after what they were.
Verbal.
Quants.
Intelligence.
Useful while building.
Not exactly unforgettable.
Eventually the products had enough personality that the placeholder names started feeling wrong.
So Quant became:
IPMATHics.
And Intelligence became:
Strata.
The rename sounds cosmetic.
It ended up being a useful product-design exercise.
A name changes what you notice
"Quant" tells you the subject.
That is useful.
It also makes the product sound like a section of a larger app.
IPMATHics feels more like its own thing.
It still clearly belongs to IPMAT.
It also gives the product permission to have a stronger identity than:
Green app, but maths.
That mattered because the Quant product had already grown into a large system of its own.
Practice.
Review.
Formula work.
Drills.
Tests.
Analytics.
Achievements.
Evidence.
It deserved a name that felt like a product rather than a folder.
"Intelligence" was even more awkward
Calling the third product "Intelligence" was descriptive.
Maybe too descriptive.
It sounded like an internal architecture layer.
Worse, it sounded like a claim.
This is the intelligent app.
Okay.
Prove it.
Strata fits the actual idea better.
Preparation has layers.
Performance.
Retention.
Timing.
Confidence.
Coverage.
Mocks.
Verbal.
Quant.
Recent behaviour.
Long-term patterns.
Strata exists to interpret those layers together.
The name does not promise magic.
It describes structure.
I like that much more.
The visual identities could finally separate properly
Verbal already had a clear personality.
IPMATHics needed one too.
Precise.
Analytical.
Fast.
Focused on solving.
Strata needed something else.
Darker.
Richer.
More interpretive.
Less like a practice tool.
The naming made those differences easier to design around.
Three products can belong to one ecosystem without looking like recoloured copies of each other.
That became the goal.
The logos got simpler, not louder
There is an easy trap when naming software products.
Make a futuristic gradient logo.
Add a sparkle.
Add a glowing orbit.
Add an abstract AI star.
Done.
I did not want that.
The products already have enough visual depth inside them.
The marks should be flatter.
Cleaner.
Recognisable at small sizes.
Usable as favicons.
Usable in app headers.
Usable on Android later.
A logo is not where the product needs to prove that it has AI.
Tiny details suddenly mattered
Once the names became real, little inconsistencies became much more visible.
Header spacing.
Logo sizing.
The Pro button.
The status dot.
Favicon scale.
Mobile breathing room.
Internal engineering copy accidentally appearing in public UI.
"Get Pro" in one place and "Pro" in another.
None of those deserve a product strategy meeting.
Together they decide whether the ecosystem feels finished.
Shared elements needed actual consistency
One of the best examples was the Pro treatment.
If Verbal has one premium control, IPMATHics has another and Strata has a third, the ecosystem feels assembled.
So we moved toward one consistent Pro language.
Same basic control.
Same hierarchy.
Small product-specific accents.
That creates family resemblance without making the products identical.
The same applied to header spacing and sync treatment.
Consistency should live where the user's mental model should be shared.
I did not want the rename to break the architecture
This is where branding becomes engineering.
A public product name can change relatively easily.
Internal identifiers are much more dangerous.
Routes.
Database product keys.
Entitlement names.
Event contracts.
Migration references.
API assumptions.
If I recklessly rename every internal "quant" identifier to "ipmathics" because the logo changed, I create risk for no user benefit.
So the public name and internal identity do not have to change at the same speed.
That felt like an important maturity step.
Users can see IPMATHics.
The backend can still use stable product keys where changing them would be pointless or dangerous.
Branding should not force data migration unless there is a real reason.
Strata had the same constraint
"Intelligence" still appears in some internal concepts because it describes the system role.
That is fine.
The product can be Strata.
The architecture can still contain intelligence snapshots, workers or model state.
Public language and implementation language serve different audiences.
Trying to make them perfectly identical can actually make both worse.
Naming also clarified the ecosystem story
The relationship now feels cleaner to me.
Verbal helps with Verbal.
IPMATHics handles Quant practice and performance.
Strata interprets the learner across both.
That sentence is easier to remember.
It also avoids making Strata sound like a generic AI chatbot.
It is not.
It is the interpretation layer for the preparation happening inside the subject products.
The brand is still less important than the product
I do not want to overstate this milestone.
Renaming software is easy compared with content, reliability, integration, real users and learning outcomes.
The name does not make the product better.
But a good name can stop getting in the way.
And once the products are serious enough to be shown publicly, clarity matters.
The ecosystem finally stopped sounding like my file system
That is probably the funniest way to put it.
"Verbal project."
"Quants project."
"Intelligence project."
Those are development labels.
Now the products are starting to feel like products.
Verbal.
IPMATHics.
Strata.
The architecture underneath is becoming more shared.
The identities above it are becoming more distinct.
That is exactly the balance I wanted.
One learner.
One ecosystem.
Three tools with different jobs.
And finally, names that sound like they belong there.