Why I'm Merging TwitMix Into ReplyWisely (and Building AI Reply Drafting in Your Voice)

I shipped two X tools in the last six months. ReplyWisely picks the right tweets to reply to. TwitMix drafts the replies. They've been living as separate Chrome extensions, separate domains, separate Stripe accounts.

That's about to change. ReplyWisely is absorbing TwitMix. Late May 2026, AI reply drafting ships inside ReplyWisely as a Pro feature, and TwitMix as a standalone product is being retired.

Here's the why and what it means for you.

What each product does today

ReplyWisely lives in your X feed and scores every tweet for visibility potential. Color-coded triangles. Niche keyword highlighting. Reply tracking with green checkmarks. The whole point: stop replying blind to dead threads. Reply where it will get seen.

TwitMix lives in your X compose box. Click a button on any tweet and it drafts replies in your voice — trained on your own past replies via X analytics, not a generic AI persona. Pick a mood (witty, thoughtful, bold, casual, and six more). Polish grammar without rewording. Or remix bookmarked tweets into fresh posts.

Both products are real. Both have paying users. They've been separate because that's how I built them — first ReplyWisely, then TwitMix as an experiment.

Why merge

Because they're two halves of the same loop.

ReplyWisely tells you which tweets to reply to. TwitMix tells you what to say. Without ReplyWisely, TwitMix is drafting replies to dead threads. Without TwitMix, ReplyWisely sends you to draft replies in a vacuum. The product is the loop — pick, reply, learn — and breaking it across two extensions means most users only ever experience half of it.

I also wasn't honest with myself about distribution. Two extensions means two Chrome Web Store listings, two onboarding flows, two pricing pages, two churn funnels, two of everything to maintain. As a solo dev with a full-time job, that's not strategy. That's me keeping things alive that should have been one thing from day one.

So they're becoming one. ReplyWisely keeps the brand. TwitMix's drafting and remix capabilities move inside.

What's shipping late May 2026

• AI reply drafting in your voice. Click a button next to X's native Reply. Pick a mood. Get drafts that sound like you — grounded in your own X analytics (you upload the CSV, we embed each post and retrieve the most relevant ones at draft time). Polish mode for grammar fixes only, no rewording.
• Remix. Turn bookmarked tweets plus your idea into a fresh post in your voice. Five modes: educational, inspirational, informational, CTA, repurpose.
• "Delete my voice data" button in the dashboard. One click hard-deletes everything. No retention, no soft-delete, no grace period.

Drafts are powered by Anthropic's Claude. The prompts are tuned hard against AI tells (em-dashes, "powerful insight", "this resonates" — gone). If a draft still sounds off, regenerate or polish.

What this means for current subscribers

Existing ReplyWisely subscribers at $9.99/mo or $69/yr: nothing changes for you. You stay at your current price forever. When AI drafting ships, you get it included at no extra cost. The new $19.99/mo Pro tier will not apply to you.

Existing TwitMix subscribers: your access carries over to ReplyWisely Pro at no extra cost. I'll email you when the migration is ready — you keep the AI drafting and remix you're paying for, plus get VPS scoring, keyword highlighting, and reply tracking added. Same price, more product.

Existing TwitMix lifetime customers: same. Lifetime access carries over.

What this means for new users

Pricing today is still $9.99/mo or $69/yr ($5.75/mo, save 42%), with a free 7-day trial and no card required to start. When AI drafting ships, the Pro tier moves to $19.99/mo.

If you subscribe now, you stay at $9.99 forever — grandfathered, no expiration. That's not a marketing line. It's how I'm operating the merger. The promise I'm extending to existing subscribers is the same one I'm extending to anyone who signs up before launch.

On privacy

This is the part where I'm being more careful than I have to.

VPS scoring, keyword highlighting, and reply tracking still run locally in your browser. Nothing sensitive leaves your machine for those.

AI reply drafting is different — it has to be. The tweet you're replying to and a slice of your voice training data go to our backend (and through Claude) for generation. Your voice training data sits in our database with row-level security. I don't sell it, share it, train external models on it, or use it for anything other than drafting your replies. The "Delete my voice data" button hard-deletes it forever.

If you've been around for the previous pricing posts, you know I'll publish honest accounting of decisions. Same principle applied to data.

The meta point

I built two products because I wasn't sure which one would land. The market told me: neither, individually. The loop is what people want. Pick, reply, learn — closed and compounding.

Merging is the right call even though it's the harder one. Easier would be to keep both alive, take both subscriptions, and pretend they're different bets. They aren't. They're the same bet split in two, and the product gets stronger by joining them.

Questions or pushback: reply to me on @chams_builds. I read everything.