I'm Building 11 Products Solo. Here's Why I Refuse to Run 11 Social Media Accounts.

I have a confession: I'm a developer who hates marketing.

Not "mildly dislikes" — genuinely dreads it. The thought of crafting the perfect tweet, building engagement, maintaining a consistent posting schedule across multiple platforms? It makes me want to crawl back into my IDE and never emerge.

But here's the problem: I'm not building one product. I'm building eleven.

AImpactScanner — AI visibility audits
LLMtxt Mastery — llms.txt file generation
PlebTest — customer interview simulation
ModelOptix — LLM cost tracking
Trader-7 — crypto trading system
SoloMarket — Product Hunt alternative for solopreneurs
Evolve-7 — personal evolution tracking
Solo-CMD — CRM for solopreneurs
Socrates — belief testing to keep me honest
ISOTracker — interstellar object tracking
FreeCalcHub — free calculator tools

The conventional wisdom says each product needs its own social presence. Its own X account. Its own LinkedIn page. Its own content calendar. Its own voice.

That's 11 X accounts × daily posts × 2 platforms = me losing my mind.

So I'm trying something different. And I genuinely don't know if it'll work.

The 5-Agent Experiment

Last week, I ran an experiment. I asked five different AI systems — Claude, ChatGPT, Gemini, Perplexity, and Manus — the same question:

"I'm a solopreneur with multiple products. How should I structure my social media presence?"

The consensus was unanimous. 5 out of 5 recommended the same model.

They called it different things:

"Founder First, Product Second"
"Hub and Spoke"
"Personal as Primary Engine"

But the core insight was identical:

Your personal brand is the engine. Product accounts are credibility infrastructure.

How I'm Implementing It

Here's the structure I landed on:

Account Type	Purpose	Activity Level
@Jamie_within (Hub)	Engagement, content, relationships	90% of all activity
@aisearchhq (Spoke)	Credibility, high-intent discovery	Dormant (1 pinned tweet)
@plebtest (Spoke)	Credibility, high-intent discovery	Dormant (1 pinned tweet)
@modeloptix (Spoke)	Credibility, high-intent discovery	Dormant (1 pinned tweet)

The product handles exist for one reason: when someone searches for "AImpactScanner twitter" or "PlebTest", they find an official presence. The bio on each points straight back to my personal account.

The spoke accounts get:

Reserved handle (namespace protection)
Professional bio
One pinned tweet explaining the product
Link to my personal account
That's it. Nothing else. Ever. (Until traction proves otherwise.)

The hub account gets:

All the content
All the engagement
All the relationship building
All the "build in public" storytelling

Why This Might Work

1. People follow people, not logos.

When was the last time you got excited about a brand account? Now think about the founders you follow. @levelsio. @tdinh_me. @marc_louvion. You follow them because they're interesting humans building interesting things — not because they have good product marketing.

2. It's honest about my constraints.

I have maybe 30 minutes a day for marketing. That's it. Running eleven active accounts would mean each gets less than 3 minutes. Running one account means it gets my full attention.

3. Cross-pollination happens naturally.

When I tweet about a PlebTest insight, ModelOptix users see it. When I share an AImpactScanner win, the whole audience benefits. Separate accounts create silos. One account creates serendipity.

4. It matches how discovery actually works.

Most people won't discover my products through my product accounts. They'll discover them through:

A helpful reply I left on someone's thread
A "build in public" post that resonated
A referral from someone who knows my work

The product accounts are safety nets, not growth engines.

Why This Might Fail

I want to be honest about the risks:

1. It might confuse people.

"Wait, is this a personal account or a business account?" Maybe the mixing of product updates with personal observations creates noise instead of signal.

2. It might limit product-specific growth.

Some products might benefit from dedicated communities. A @plebtest account could build a community around customer validation. Am I leaving growth on the table?

3. The "phased activation" escape hatch is tempting.

Claude suggested activating product accounts "once they have traction." But that's a slippery slope. How much traction? When do I pull the trigger? Will I even have the bandwidth then?

4. I might just be rationalizing my introversion.

Let's be real: part of me loves this strategy because it means less marketing work. Is that strategic thinking or sophisticated avoidance?

The Honest Part

Here's what I know for sure:

I am bad at marketing. I am uncomfortable with self-promotion. I would rather build features than write tweets. I am a shy, introverted developer who somehow decided to become a solopreneur.

This strategy might be brilliant. It might be cope. It's probably somewhere in between.

But it's the strategy that I'll actually execute. And a mediocre strategy executed consistently beats a perfect strategy abandoned after two weeks.

What I'd Love to Hear

If you're building multiple products solo, I genuinely want to know:

Does the hub-and-spoke model resonate? Or does it feel like I'm overcomplicating things?
Have you tried running multiple product accounts? How did it go?
What am I missing? What failure modes haven't I considered?
Is there a better way? I'm not attached to this approach — I'm attached to results.

You can find me at @Jamie_within — which, yes, is exactly where this strategy says you should find me.

Current Status

Metric	Status
Products in portfolio	11
Active X accounts	1 (hub)
Dormant X accounts	1 (spoke) — more coming
Strategy tested	No
Strategy proven	Definitely no
Confidence level	Cautiously optimistic

This is Day 1 of the experiment. I'll report back on what actually happens.

Building in public means showing the messy parts. This is one of those.