What I learned rebranding Famvoy to Krewva

The day we decided to kill the name “Famvoy,” I had four investor decks, two pitch videos, a domain we’d paid $4,800 for, an Apple Developer account, two AWS accounts, three Stripe entities, a trademark filing, and somewhere around six hundred references to “Famvoy” scattered across the codebase, the marketing site, the App Store metadata, and our outbound email signatures. None of it was wrong. All of it had to change.

We changed it in fourteen days. This post is about what I learned in those fourteen days, and what I wish I’d known eighteen months earlier.

Why Famvoy was wrong

The name “Famvoy” was a portmanteau of “family” and “envoy.” When we started the company in late 2024, our hypothesis was that the most underserved messaging surface was family communication. Parents talking to kids. Grandparents who couldn’t keep up with group chats. Adult children managing care for aging parents. We thought there was a real product to be built around AI that handles family messaging specifically, translating tone, setting reminders, mediating cross-generational miscommunications.

That hypothesis wasn’t wrong. It was just narrow.

Within six months of building, two things became obvious.

First, the family use case is real but small. Most users wanted the AI for all their messaging, not just family. They had work threads, friend threads, customer threads, group chats with hobby clubs, project channels, neighborhood groups. Limiting the brand to “family” meant we were building a feature, not a product.

Second, the family framing scared off our biggest segment, solo professionals and small business owners. When we started running landing-page tests, the conversion rate for users who self-identified as “small business owner” was dramatically lower than for users who self-identified as “parent.” The post-test interviews told us why: business users heard “Famvoy” and assumed the product was a family chat app, not a productivity tool. The brand was actively excluding our best customers.

We had a naming problem. The naming problem was actually a positioning problem. “Family + envoy” had positioned us as a niche family product. The real product was an AI agent crew for all personal communication.

I sat with this for about a month before I admitted it out loud. Founders sit with naming problems too long because the cost of changing is so visibly high. The cost of not changing is invisible, every prospect who bounces, every investor who passes, every story you can’t quite tell because the name doesn’t match the pitch.

The fourteen-day plan

When I finally accepted the name had to change, I gave us fourteen days. The reasoning was: the longer we live with two names internally, the more split brain we get. Faster is cheaper.

Day one was naming. Haiyang and I sat in the office for six hours with a whiteboard. We listed criteria:

1. Pronounceable in English, Spanish, Mandarin (our three biggest target geographies).
2. Available as a .com domain we could afford.
3. No conflicts in the App Store or Trademark Office.
4. Suggests “crew” or “team” without saying it literally.
5. Not a family-coded word.

We generated about a hundred candidates. We narrowed to twenty by checking domain availability with cheap auto-tools. We narrowed to five by saying them out loud at each other. We picked Krewva over the other four because:

• It rhymes with “crew” without being “crew.”
• The first syllable is sharp (“Krew”) and the second is soft (“va”). That phonetic shape is memorable.
• It looked good in the lockup we sketched.
• The .com was available for a reasonable price.

Day two was domain acquisition and trademark filing. We registered krewva.com that morning and filed the USPTO trademark application that afternoon.

Day three through day seven was the codebase migration. The repo was full of Famvoy references, class names, env vars, comment blocks, log statements, push notification topics, schema columns. We did a globally-scoped find-and-replace, then a manual review of every file, then a full local rebuild and smoke test. The bulk of the work landed in a single PR that touched something like four hundred files. The CI pipeline became Famvoy-CI to Krewva-CI and we had to update GitHub Actions secrets, AWS resource tags, Cognito user pool names, every infrastructure label.

Day eight through day eleven was the marketing surface. New logo (Haiyang did the lockup). New landing page (we kept the layout, swapped the brand). New social handles (Twitter let us re-grab the name; LinkedIn was painful and required filing a name-change form with documentation). New App Store listing, TestFlight needed a fresh build with the new bundle identifier. New favicon. New OG images.

Day twelve was the investor email. I sent a single message to every investor and advisor who’d seen the company under the old name: “We’re now called Krewva. Same product, sharper positioning, broader market. Here’s the new deck. Sorry for the confusion.” About 80% of the replies were “love it” and the remaining 20% were “smart move.” Nobody said “what were you thinking before?”

Day thirteen was paid launch, we ran a small announcement campaign on the social channels we’d already built, explicitly framing the rebrand as a positioning sharpening, not a pivot.

Day fourteen was cleanup. Final pass through internal docs, Slack workspace name, Notion workspace name, the dashboard the team uses every day. By the end of day fourteen, “Famvoy” survived only as a historical note in our git history and a few investor decks that lived on people’s hard drives.

What it cost

I want to be honest about the cost, because the founders I talk to about this consistently underestimate it.

Direct cash cost: about $9,000. Domain ($4,800 because the seller had it parked), trademark filing fees ($1,200 for the USPTO application), new logo design (we did most of it in-house but paid a designer for one round of polish, $1,500), new landing page assets ($800 for stock photography and Figma library), App Store name-change costs ($350 for the Apple Developer paperwork), miscellaneous ($350, printed business cards, new envelopes, signage).

Indirect time cost: about 110 person-hours across the team over two weeks. That’s mostly engineering time on the codebase migration. Could have shipped two real product features in the same window. Did not.

Trust cost: zero, surprisingly. I expected investors to read the rebrand as a wobble, “they don’t know what they’re building.” None of them did. Founders who’d been through their own rebrands explicitly said the move was a positive signal. Investors who hadn’t been through a rebrand were briefly confused but recovered quickly. The story we told (“we outgrew the family framing, this is the real product”) was honest and crisp and people believed it.

Brand-equity cost: real but smaller than expected. We lost some inbound search traffic that had been building under “Famvoy.” We lost some social mentions that didn’t get migrated. A few people who’d told their friends about us under the old name had to re-explain it. That’s a few weeks of slightly slower growth, not a permanent setback.

What I’d tell a founder considering this

If you’re sitting on a name that doesn’t fit anymore, three thoughts.

First, the cost of changing is real but bounded. It’s measured in days and tens of thousands of dollars. The cost of not changing is unbounded, every customer you don’t acquire because the brand confused them, every investor who passes because the pitch and the name don’t match, every internal moment where you have to apologize for the name in a sales call. Compounded over years, the cost of not changing dwarfs the cost of changing.

Second, the change itself is mostly mechanical. I had been imagining the rebrand as some kind of artistic process, where we’d agonize over names for months. The artistic process was one day. The other thirteen days were find-and-replace, paperwork, and emails. If you’ve decided to change the name, decide fast and execute fast. Lingering is the expensive part.

Third, the right time to rebrand is exactly the moment you realize the name is wrong, not later. Every month you spend with a name you’ve outgrown is a month of customers and investors absorbing the wrong signal about your company. There is no “wait until we have more traction” strategy that beats “fix it now.” The rebrand gets harder the bigger the company is. We had eighteen months of equity in “Famvoy.” A startup with three years of equity has six times the migration cost.

I’m sometimes asked whether we wish we’d named the company Krewva from the start. The answer is yes, obviously. But the path here was useful, Famvoy was the version we built when we thought the product was narrower, and the experience of running into the brand’s limits is what taught us what the product actually is. You don’t always know what you’re building when you name it. Sometimes you have to build it for a year before you understand it well enough to name it correctly.

The only failure mode is realizing you’ve outgrown the name and not acting on it.

— Zeming Liang, Founder & CEO of Wuvov