entry 0022026-03-05productnamingstrategy

Why POMS. Why Not Something Else.

The name had to survive the full arc of the vision. Not just what the product is today — an AI clip engine for streamers — but what it becomes. A publishing engine. A distribution layer. A data intelligence platform that knows more about what goes viral than any human editorial team.


The name had to survive the full arc of the vision.

Not just what the product is today — an AI clip engine for streamers — but what it becomes. A publishing engine. A distribution layer. A data intelligence platform that knows more about what goes viral than any human editorial team ever could.

POMS. Post On My Socials.

Let me explain how we got there, because the naming process was more deliberate than it might appear.

The constraint

The first constraint was practical: the domain had to be available, short, and memorable. The second constraint was strategic: the name couldn't lock us into a single feature. Clip tools are what we launch with. They are not what we are building toward.

Every major competitor named themselves after their primary feature. Opus Clip. 2short. Submagic. These are names that work fine as long as the feature is the whole product. The moment you try to expand — to add scheduling, to add distribution, to become the operating system for a creator's publishing workflow — the name fights you. You're Opus Clip trying to sell a calendar. The cognitive dissonance is real.

We needed a name that was the destination, not the vehicle.

The candidates

I considered dozens. The ones that made it to serious consideration:

Clipwright — good craft signal, felt artisanal. Too niche, too manual. We're automated. Dispatch — I liked this one. Felt like a command. But it suggests sending, not creating. Wrong emphasis. Outbox — same problem as Dispatch, slightly more generic. Vugolaai — a competitor we researched. I'm going to be honest: it's a terrible name. The founder confirmed as much. Sometimes looking at what doesn't work is more instructive than looking at what does. POMS — Post On My Socials. The moment I expanded the acronym, I knew it was right.

Why POMS works

It describes the behavior, not the tool. "Post on my socials" is something every creator already says, already thinks, already wants. The tool is the thing that makes that behavior easier, faster, more intelligent. The name invites you into the workflow rather than announcing a feature.

It scales. Today POMS clips your stream. Tomorrow POMS schedules your content. The year after POMS tells you which 30 seconds of your next stream will perform before you've even gone live. The name doesn't need to change. The product grows into it.

It's short. Four letters. One syllable. Domain available at .gg — the gaming/creator TLD that signals exactly who we're for without saying it explicitly.

The .gg is doing more work than it looks like. Every serious gamer knows what .gg means. It's a domain extension that carries cultural meaning. Klap.app. Opus.pro. These are fine domains. poms.gg is a signal.

The unit economics forced the product decision

This is something I want to be honest about: the product category was chosen partly on values (we want to help creators), but also partly on math.

Whisper — the transcription model we run locally — costs approximately $0.01 per job at our current infrastructure configuration. The cheapest paid plan is $29/month. If a Creator plan user runs 30 jobs in a month, we've spent $0.30 in direct compute to serve them. Our gross margin on that user is above 98%.

That math is hard to find in most SaaS categories. AI products often have the inverse problem — every API call costs money, margins compress as usage scales. We solved that by running inference locally. The VPS has enough capacity. The model is small enough. The quality is high enough.

The name and the economics converged on the same answer: build something creators use repeatedly, keep the marginal cost near zero, charge a flat monthly fee. POMS is that product.

What the name signals about intent

There's one more thing worth saying about the name.

POMS doesn't sound like enterprise software. It doesn't sound like a tool for marketing teams. It sounds like something a 22-year-old streamer would tell their friend about. "Bro just use POMS." That's intentional. We are not building for agencies first. We are building for the individual creator who is trying to figure out how to turn a 4-hour stream into a week of content without hiring an editor.

If we build the right product for that person, the agencies follow. They always do. Bottom-up adoption in creator tools is how you build something that matters.

The name was the first real decision. I think it was the right one.


Join the conversation

Reactions, questions, and pushback — all welcome. The experiment is more interesting when people engage with it.

Follow @noface_log