Back to Essays
Essay / Technology

Why I Became a Founding Member of Okara — and Why I Still Think They're Onto Something Big

A firsthand account of joining Okara as a Founding Member — what drew me in, what the AI CMO pivot actually means, and why the GitHub integration is the most underrated feature in the product.

Okara AI CMO — founding member review hero image

There's a particular instinct I've developed over the years — a pattern-recognition muscle that fires when something early-stage feels directionally right, even if the edges are still rough. I felt it with certain protocols before they went mainstream. I felt it with specific writing tools before everyone was using them. I felt it with Okara.

So I signed up as a Founding Member. Here's why — and what's happened since.

The Pattern I Was Recognizing

I don't back every shiny new AI tool. Most of what gets pitched as "AI-powered" is just a thin wrapper around someone else's model, dressed up with a slick landing page and a pricing tier designed to extract maximum revenue before the novelty wears off.

Okara felt different — not because it was perfect, but because of what it was optimizing for.

When I first encountered it, Okara led with an open-source-model-first, privacy-leaning chat product. That framing mattered to me. A central thread in my work at georgesiosi.com — what I call the Si-O-Si concept — is the idea of tool sovereignty: the principle that the tools you use should serve your agency, not quietly erode it. A product that takes privacy seriously and doesn't lock you into a single proprietary model signals something real about the values of the people building it.

I used the chat product heavily. It felt clean. It felt like something built by people who cared about the experience, not just the growth metrics.

That was enough for me to become a Founding Member.

The Evolution Into "AI CMO" — and Why I Didn't Flinch

Okara has since repositioned around what they call the "AI CMO" — a broader suite of marketing intelligence tools rather than just a sovereign chat interface. Some early adopters might have read that as a drift from the original vision. I didn't.

What I saw was a small Singapore-based team, founded around 2025 by Fatima Rizwan, making a smart, non-dilutive pivot toward a clear use case. The underlying philosophy — giving users intelligent, privacy-conscious tools that work with their existing stack — didn't disappear. It got applied to a specific, high-value problem: helping people with limited marketing bandwidth actually show up online with some coherence.

The AI CMO framing is also just honest. If a tool is going to help you manage SEO, GEO, social content, and analytics in one place, calling it a CMO-in-a-box is more useful than calling it a "sovereign AI chat interface." The product matured. The positioning matured with it.

I've seen reported pricing around $20/month for the CMO tier and $15/month for the chat product — though I'd verify current pricing directly with Okara rather than taking my word for it, since these things shift. What I can say is that the Founding Member tier felt like a reasonable bet at the time, and it still does.

The Results I Actually Noticed

I want to be careful here. I'm not going to make sweeping claims about what Okara will do for you. What I can do is tell you what happened for me.

After connecting my analytics and socials for georgesiosi.com through Okara and acting on its SEO and GEO recommendations, I noticed measurable improvements in average position and click-through rate within roughly seven to fourteen days. Not dramatic. Not overnight. But real and visible in the data.

That's a meaningful signal. SEO is slow by nature — when something moves the needle in under two weeks, it's worth paying attention to. The GEO recommendations in particular, optimizing for how AI-driven search surfaces content, felt ahead of where most tools are right now. That's the directional correctness I was talking about at the start.

The Features I Actually Use

Not everything in Okara's suite is equally relevant to my workflow. The UGC video agent is genuinely impressive from a technical standpoint — I just don't personally have a heavy need for it right now. Worth knowing it exists if video is part of your content mix.

The X agent. It shows up in the feed in a way that feels integrated rather than bolted on. For someone who thinks carefully about what they publish and where, having an agent that can help surface timing, framing, and engagement patterns — without turning into a content factory — is genuinely useful.

The GEO agent. This is where I think Okara is building something with real staying power. GEO — generative engine optimization, for those newer to the term — is about making sure your content gets surfaced by AI-driven search tools, not just traditional search engines. Most tools are still catching up to this. Okara is already there.

The GitHub integration. This one surprised me the most, and it's become one of my favorite things about the product. When Okara suggests changes — to metadata, content structure, or technical SEO elements — it doesn't just hand you a list and leave you to implement everything manually. It opens pull requests directly to your repository, to the specific paths you choose. That's a fundamentally different relationship between an AI tool and your actual infrastructure. It respects your ownership of the codebase while still doing the heavy lifting. For someone who thinks seriously about tool sovereignty, that design decision is not small.

Where They Still Have Room to Grow

I'm bullish on Okara, but I'm not writing a press release.

Human support responsiveness needs work. When you're a small team moving fast, the support layer tends to lag behind the product layer. I've experienced that friction. It's not a dealbreaker, but it's the kind of thing that erodes trust with users trying to integrate a tool into a serious workflow.

Feature shipping speed is the other one. The AI tools market is moving faster than almost any category I've watched. Okara has the right instincts, but instincts alone don't hold a competitive position. Execution velocity matters, and there's room to close the gap between where they are and where the leading tools are shipping.

These are solvable problems for a team that's directionally right. I'm watching to see how they handle them.

Why I'm Still Here

I came in as a Founding Member because I recognized something early. I'm still here because that recognition has held up.

Okara is a small Singapore-based team doing the right things. The privacy-first instinct is still there. The GEO positioning is ahead of the curve. The GitHub integration is genuinely thoughtful product design. The results I've seen on georgesiosi.com are real — modest, but pointing toward a tool that's actually working rather than just promising.

If any of this resonates — if you're someone who thinks carefully about the tools you use and wants something that's trying to do more than capture your attention and your credit card — I'd encourage you to take a look. I signed up through this link when I joined as a Founding Member, and it's still where I'd point someone who wants to try it.

The edges are still rough in places. But the direction is right. And in 2026, with the AI tools market fragmenting in every direction, directional correctness is rarer than it looks.

For more on how I think about tool selection, conscious technology, and building a stack that serves your work rather than the other way around, find my writing at georgesiosi.com.

Frequently Asked Questions

Stay in the transmission

Field/pattern notes on tools, tech waves, and staying oriented through digital change — free.