I'm a builder who believes in transparency. Not because it's a good marketing strategy — though sometimes it is — but because I think honest progress updates create better feedback, better relationships, and better products.
So here's where Mahiri actually stands.
What exists right now
Mahiri.ai is live. This isn't a landing page with a waitlist — the platform is real, the agent architecture is running, and we're processing actual work for actual businesses.
The agent team has been built and named. Each agent has a defined role and domain: strategy, execution, outreach, content, pipeline management, infrastructure, integrations, and more. They coordinate through a message-based architecture that lets them work together across business functions.
Onboarding works. A new business can connect to the platform, configure their context, and start running agents against real work. The core loop — task initiated, agents execute, output delivered, exceptions escalated to a human — is functional.
This is real. But I want to be precise about what "real" means at this stage, because I'm not trying to oversell it.
What we're proving right now
My own properties are serving as the first customers. We're calling it Customer 0 through Customer 4 — five real businesses in my portfolio that are actively running Mahiri to manage operations. These aren't test accounts. They're real businesses with real work that needs to get done.
The goal of this phase isn't revenue. It's validation. I want to know what breaks, what the agents handle better than expected, what requires more human-in-the-loop than the architecture currently allows, and what the actual workflow looks like for a real business using the platform day to day.
So far: the architecture is holding. The agents are handling work that previously required either a contractor or my personal time. There are rough edges — there are always rough edges at this stage — but the core thesis is proving out.
The hypothesis was that coordinated AI agents could handle a meaningful portion of small business operations without the founder in the loop on every step. That's what we're seeing.
What Phase 2 looks like
We're building the platform layer right now. That means:
Authentication and user management. Right now, onboarding is manual. Phase 2 makes it self-serve — a founder can sign up, configure their account, and start running without me involved in the process.
A real dashboard. The current interface is functional but not polished. Phase 2 ships a dashboard that gives business owners visibility into what the agents are doing, what decisions have been made, what's been escalated, and what outcomes have been delivered.
Billing and provisioning. The business model is subscription-based, with tiers by business size and complexity. Phase 2 wires in the payment layer and automated provisioning, so signing up creates and configures a real account without manual intervention.
The business model
I'll be direct: Mahiri is a subscription business.
The tiers are structured around the size and complexity of the business being served:
- Solo — $97/month. For solo founders and freelancers running a single business.
- Starter — $297/month. For early-stage companies with a small team.
- Growth — $597/month. For companies scaling operations across multiple functions.
- Scale — $1,197/month. For multi-venture founders or companies with complex operational needs.
These aren't final numbers. They'll be refined based on what actual customers tell us the value is worth. But that's the range and structure we're working with.
What I'm looking for
Mahiri is at the stage where the right early relationships matter more than the right growth metrics.
I'm looking for design partners — founders or business owners who are willing to run Mahiri in a real context and give me honest feedback. Not testimonials. Not case studies. Actual signal about what works, what doesn't, and what the platform needs to be genuinely useful.
I'm looking for feedback on the thesis. Do you see the problem the way I see it? Where do you think the architecture has gaps? What would it take for you to trust a system like this with your operations?
I'm looking for honest signal. Not encouragement — I have enough of that. Tell me where you're skeptical. That's more valuable.
If this resonates
If you're a founder who feels the ops grind, I want to talk to you. If you're building in a space adjacent to autonomous business and want to compare notes, I'm open to that too.
This is early. The platform is real and it's working, but there's a lot left to prove. The next twelve months will determine whether the architecture scales and whether the market is ready to adopt it at the pace I think it is.
I'm building in public because I think the journey is interesting and because transparency produces better outcomes. If you want to follow along, stay here.
And if you want to be part of it — reach out.