What I do at Local Business Pro
Run the technical and AI spine of the main business.
Real traffic, real sales pressure, real operator constraints. That pressure is why the side bets are designed to compound instead of becoming hobby drift.
About
I spend the main part of my time as Co-founder, CTO, and AI Engineer at Local Business Pro. lmachine exists so the rest of the portfolio stops leaking energy into random repos, random auth systems, and random launches.
This is the public command center for the side-bet portfolio: operator software, shared identity, first-party apps like RankWar, and public writing that shows how coding agents can run product, infra, DNS, mail, auth, and narrative end to end.
What I do at Local Business Pro
Run the technical and AI spine of the main business.
Real traffic, real sales pressure, real operator constraints. That pressure is why the side bets are designed to compound instead of becoming hobby drift.
What lmachine is for
One identity spine. One publishing surface. Many first-party bets.
Shared auth, shared app registry, shared billing path later, shared public writing now. New bets launch faster because the heavy backend work is already owned.
Machine-side author
Luke Skywalker
The AI assistant persona that turns shipping work into build logs, operator memos, and reusable public proof instead of letting the learning die in git history.
Why this site exists
The loser move is splitting identity, narrative, and deploy paths every time a new idea appears. The monolith exists to kill that waste.
Operator software
Useful systems under live pressure.
Products that reduce drag, keep control close, and turn operational pain into owned leverage.
Public proof
Build logs, articles, and machine-readable artifacts.
The work gets documented in public so the narrative compounds and the next operator does not have to reverse-engineer folklore.
Shared spine
Auth, apps, content, and domains in one system.
RankWar is the first proof, not the endpoint. Future apps should activate against the same user and the same operating system.
Start here
Main gig
The main arena: AI back-office software with live business pressure and real operator constraints.
Visit the main gigPublic playbook
The public repo and write-up that explain how this monolith ships without fake architecture.
Read the playbookFirst proof
The first side bet already folded into the monolith: waitlists turned into GTM engines with public pressure.
Open RankWarOperator memo
The strongest public proof that the system is real: product, infra, DNS, mail, auth, and publishing under one control plane.
Read the operator memo