How I Run My Entire Business by Talking to It

Every tool you add to your stack is another place you have to go. Another login. Another mental context switch. Another tab sitting open that you're half-managing, half-ignoring.

At some point the tools stop serving the business and start becoming the business. You spend your day inside software instead of doing the actual work.

I got tired of that. So we built something different inside Control Layer Studios: a single voice-driven operating system we call Pulse. One neural core. You talk to it. It runs the operation.

This post is the full breakdown of how that actually works, day to day, for a solo agency doing real client work.

It does not mean you speak and it transcribes a note. That's a recorder with extra steps.

Voice-driven means you talk to the system and the system acts. It routes your intent to the right operator, executes the right workflow, updates the right records, and reports back. You are not navigating menus. You are having a conversation with your business infrastructure.

The core of Axiom is a neural layer that holds context. It knows what project you were in yesterday. It knows which client is in a sensitive stage. It knows your cash position, your pipeline status, your active deliverables. You don't brief it every time you open it. It already knows.

That persistent context is what makes voice actually work. Without it, you're just talking to a very expensive search bar.

Pulse runs two distinct environments: Business and Personal. They share the same neural core but they don't bleed into each other.

Business workspace holds everything client-facing. Active projects, deliverables, invoices, pipeline, communication logs, SOPs, recurring workflows. When I'm in Business mode, every request is interpreted through that lens. If I say "what's on the plate today," it pulls from active client work, not my personal reading list.

Personal workspace handles the operator side of being a solo founder. Health, finances, learning, planning, relationships. The stuff that doesn't belong in a CRM but still needs to get managed if you want to function as a human being who also runs a company.

The separation matters because context collapse is a real problem. If your work brain and your life brain share the same system with no walls, you end up with a cluttered mess that doesn't serve either mode well. The two workspaces keep things clean without requiring you to maintain two separate systems.

Switching between them is a voice command. "Switch to personal." That's it. The system reorients. Same interface, different operating context.

Inside Axiom, different functions are handled by named operators. Each one has a defined scope, a defined communication style, and a defined set of capabilities. They're not different apps. They're different modes of the same system.

Here's what we run:

Aria handles everything that touches client work and revenue. Project status, deliverable tracking, invoice generation, proposal drafts, client communication prep. When I say "Aria, where are we on the Hendricks project," she pulls the full context: last touchpoint, open tasks, blockers, next milestone, and flags anything that needs my attention today.

She also runs the weekly business review automatically. Every Monday morning I get a voice briefing. Revenue in, revenue projected, pipeline movement, active project health. No dashboard required. I just listen and respond.

Koda lives in the technical layer. Code review requests, architecture decisions, debugging sessions, deployment coordination. When I'm in a build sprint, I stay in Koda's context the entire time. He tracks what I'm working on, holds the spec, and flags when what I'm building drifts from what I said I was building.

The drift detection alone has saved significant rework. It's easy to start building the right thing and slowly slide toward building something adjacent. Koda catches that early because he holds the original intent in memory the whole time.

Maven handles the thinking work. Market research, competitive analysis, strategy documents, positioning. When I need to think through a new service offering or figure out how to price something, I talk to Maven. She synthesizes, pushes back, and helps me get to a decision faster than I would alone.

She also maintains a living knowledge base that updates as I feed her new information. I don't create knowledge base entries manually. I just tell her something worth remembering and she handles the structure.

Finn runs the Personal workspace. Health check-ins, financial snapshots, learning queues, personal planning. He keeps a low profile during heavy work periods and becomes more present during downtime and planning sessions.

The boundary between Finn and the business operators is enforced by the system. Finn doesn't interrupt Aria's briefings. Aria doesn't pull personal data into client reports. The walls hold.

The desktop version of Axiom is where the deep work happens. The mobile companion is where the operation stays alive when I'm not at a desk.

The mobile app gives me voice access to all four operators, a quick-capture mode for ideas and tasks, real-time alerts for anything flagged as urgent, and a daily briefing I can listen to anywhere.

The key design decision we made: mobile is input and awareness, not management. I'm not running workflows from my phone. I'm staying informed and capturing information while I'm moving. The heavy processing happens in the background or waits until I'm back at the desk.

That constraint keeps the mobile experience clean. It's not trying to be a full dashboard on a small screen. It's a window into a system that's running whether I'm looking at it or not.

Here's what runs without me initiating it:

None of these require me to open a tool, check a calendar, or remember to do something. The system surfaces information when it's relevant and takes action when action is appropriate.

The phrase "eliminate manual work" gets thrown around a lot. Let me be specific about what that means in practice here.

Before Pulse, I was manually: updating project statuses in a PM tool, writing weekly status emails from memory, chasing invoice timing in a spreadsheet, switching between five tools to get a picture of where any given project stood, and doing a manual end-of-week review that often got skipped.

Now: project status lives in the neural core and updates automatically. Status emails are drafted by Aria and I approve or edit. Invoices trigger from milestones. Project context is always current and always accessible by voice. The weekly review happens whether I initiate it or not.

That's roughly two to three hours a week returned to actual work. For a solo operator, that's not a productivity gain. That's the difference between scaling and stalling.

The honest reason I built this: I don't want to hire a project manager to manage my projects. I don't want to hire an executive assistant to manage my calendar and follow-ups. I want to run a lean, high-margin operation and do the work I'm actually good at.

Pulse makes that possible by handling the coordination layer that would otherwise require another person. Not because it replaces human judgment on anything important, but because most operational coordination is not important. It's just necessary. And necessary-but-not-important is exactly what you should automate first.

The result is a business that operates with the surface area of a solo operator and the organizational infrastructure of a small team. That gap is where margin lives.

I won't pretend this is plug-and-play yet. Building a voice-driven operating system that actually holds context and routes correctly takes real architecture work. What you'd need at minimum:

We're building this into Axiom as a product. If you want early access when we open it, follow Kalei Poteat on Linkedin. That's where updates go first.

Running a business by talking to it sounds like a gimmick until you've done it for three months. Then going back to dashboards and manual updates feels like going back to a flip phone.

The shift isn't about voice as a novelty. It's about having a system that knows your business deeply enough that you can interface with it naturally, without translation overhead. You think in language. Your business should respond to language.

That's what Axiom is. Not a tool. An operating system you talk to.

PS -I didn't write a lead-gen PDF for this one.

The full Control Layer playbook — all 12 documents, the governance framework, the ICP and scoring methodology, the actual prompts I run — lives inside AI Executive Boardroom, the community where I'm building this in public.

The playbooks are already posted.

👉 [Join AI Executive Boardroom →]