Insights
Ideas that change how the work moves.
Notes from what we're building, testing, and learning inside real businesses — distilled into things you can actually use.
From current builds
The work is the source material.
These notes came directly out of systems under active development or operation. Current-work framing reviewed September 28, 2026.
A Passing Test Is Not Production Proof
A green test proves something specific happened in a controlled environment. It does not prove a design was approved, a deployment gate passed, or production is behaving the same way.
Read the note →We Stopped Designing the App Around the Database
Leasing, maintenance, accounting, and admin all touch the same operation. That does not mean they should see the same software.
Read the note →Not Confirmed Is a Real Outcome
A write can leave your system, time out, and still succeed. Treating that as a failure can create the duplicate you were trying to prevent.
Read the note →Explore
Ideas, systems, and signals.
Browse by topic or search for exactly what you need.
From Messy Data to Trusted Data
The four-step process that turns conflicting records from email, accounting, banking, and operations into one answer the company can actually trust.
→Your Company Needs Memory
AI gets dramatically more useful when it can reason over a structured, time-stamped history of how the company actually works.
→Your agent can read the file. Should it forward the contents?
Before an assistant sends an update, check the purpose, recipient, and allowed fields. Accurate information can still belong in the wrong place.
→Giving an agent search does not give it evidence
Cloudflare’s Web Search API makes retrieval easier to wire in. A useful research workflow still needs claim-level sources, dates, and an honest unresolved state.
→When AI writes faster, the review queue becomes the product
Anthropic’s source-control rebuild exposes a practical bottleneck: how quickly your team can accept a change, prove it works, and recover when it doesn’t.
→AI Inbox found the follow-up. Who owns it now?
Suggested to-dos help you notice the work. A source link, one owner, and a completion rule turn a suggestion into an accountable commitment.
→Stop your AI search from quoting retired instructions
A source link can point to a real procedure that no longer applies. Test current answers, historical answers, and the transition between them.
→Your browser agent needs a receipt for every finished task
A new WebArena-Lite audit shows why an agent’s final answer and an evaluator’s score both need checking against the actual task outcome.
→Deleting an exposed API key does not revoke its access
A clean source file is only one part of the response. Track invalidated access, restored operation, exposure cleanup, and the evidence for each.
→Before you add another agent, freeze the facts
Cloudflare’s security operations design offers a useful pattern for business reviews: collect a versioned evidence snapshot before asking agents to interpret it.
→What breaks when the model in your workflow retires?
A deprecation notice is a dependency change with a deadline. Identify the affected jobs, test the replacement, and choose a visible fallback.
→Your AI playbook needs one current version
A shared document and an agent's installed instructions can drift apart. Make the approved revision, installed copy, and run history traceable.
→Your preview link should never surprise a real customer
A separate URL does not choose safe external connections. Verify the database, CRM, notifications, and calendar behind the rehearsal.
→More reported conversions can still mean the same number of customers
Google’s October measurement updates make one distinction more useful: an event your ad platform records and a customer outcome your business can verify.
→Can you restore the system you just decided to own?
Source code and a backup are a starting point. A witnessed recovery test shows whether the business can resume the work.
→Trace the missing handoff before buying another dashboard
Follow one quote request from submission to callback. Find the first missing receipt before changing the wrong part of the workflow.
→A voice note and a document disagree. What should your AI save?
Multimodal input makes conflict handling more important. Preserve each source observation before accepting a change to the working record.
→10 Jobs That Don't Exist Yet
A 2046 thought experiment: if AI agents make intelligence cheap, what kinds of work become valuable next?
→Your Agent Says Everything Worked. That’s the Problem.
The business knows something broke. The agent’s health checks say otherwise.
→Your AI Assistant Works. Until Someone Else Uses It.
The person who built it may be doing invisible work that makes it look smarter than it is.
→A Passing Test Is Not Production Proof
A green test proves something specific happened in a controlled environment. It does not prove a design was approved, a deployment gate passed, or production is behaving the same way.
→Inside Xovion Books: Why We Built a Flight Recorder
Xovion Books automates real accounting work. Once it could make decisions and attempt writes, ordinary logs were not enough — so we built a read-only Flight Recorder that shows what Books saw, decided, tried, skipped, changed, verified, and why.
→Not Confirmed Is a Real Outcome
A write can leave your system, time out, and still succeed. Treating that as a failure can create the duplicate you were trying to prevent.
→The Best First Commit Was Almost Empty
When we started a financial system from scratch, the first meaningful milestone was not a dashboard or a ledger. It was a database harness that proved what had not been built yet.
→We Stopped Designing the App Around the Database
Leasing, maintenance, accounting, and admin all touch the same operation. That does not mean they should see the same software.
→Your Accounting Team Should Review Exceptions. Not Hunt for Them.
Property-management accounting teams still spend too much time proving that their systems agree. Continuous financial control changes the job from finding problems to reviewing evidence-backed exceptions.
→Build Log: The Test Suite Was Green and the Numbers Were Still Wrong
We had an AI agent build a market data query layer in a day. Every test passed. Two of the six metrics were empty stubs, one overstated sales volume by $783,500, and twenty test files had never run at all. Here is what we found and what it taught us about verifying AI-written code.
→The Sioux Falls apartment signal hiding in plain sight
We’re building a market-intelligence engine that looks for changes beneath headline real-estate statistics. One early Sioux Falls signal shows why the data needs to be connected, not just collected.
→An Update on the Property Management Operating System I'm Building
Two real fixes this week. The morning data sync was breaking in a way I had wrong, and I wired up the cause-and-effect link in the event log only to find out the other end of the chain isn't built yet. Where the operator OS stands today, and what ships next. Part 3 of a build log.
→The Moat Is the Event Log, Not the Database
Most of what you call 'owning your data' is just renting it from yourself. Spent a day inside the data layer of the property management OS and realized the rent roll and the GL aren't the moat. They're a cache. The event log is the only thing that disappears if you don't capture it. Part 2 of a build log series.
→The Moat Isn't the Model. It's What Trained It.
Almost everyone building 'with AI' right now is renting model weights they don't own. Here's the line between a real AI business and a ChatGPT wrapper with branding, and the questions every operator should be able to answer.
→Why I'm Building a Property Management Operating System (and Where I Am Today)
Tool sprawl is the operator's tax. Here's the four-layer system I'm building — data, dashboard, action, AI in the loop — to stitch AppFolio, ClickUp, and the rest into one operating system for a small property management portfolio. Part 1 of a build log series.
→The Compute Is Coming Home
NVIDIA wants to bolt a half-million-dollar AI data center onto the side of your house. I'm building the same thing in my backyard — except I'll own all of it. The case for local AI, privacy, and why ownership beats hosting.
→What an Agentic Operator Does With a Messy CRM
Cleaning up a CRM isn't a button. It's reading the threads, fixing the tools that produce the mess, sending with safety architecture, and writing the rules down so the mess can't form again. The five moves of an agentic operator.
→Why Underwriting Breaks
Most acquisitions teams rebuild the same Excel model for every deal — and every deal arrives with broken formulas, drifted assumptions, and recipients who can't read it. There's a better way: engine in code, Sheet as the rendering layer, the build automated, and the whole pipeline wrapped in a skill so the next deal takes 15 minutes.
→Everything Is an Event
A business is just a stream of things that happened — sales, money, field, team, software. Almost none of it gets tracked, and that blind spot is where cash and time quietly leak. The operator's case for making your whole operation visible before you automate any of it.
→Agent Swarms vs. Agent Teams: When 300 Agents Beats 6 (and When It Doesn't)
One AI system now fans out to 300 agents at once. Another runs a tight team of six. The headline number isn't the point — and if you're an operator, picking the wrong model wastes more than money. Here's the honest breakdown.
→The Two Files That Turn Claude Into a Coworker
Most people use AI like a vending machine — punch in a question, take the answer, walk away. Two plain text files turn it into a colleague that actually knows you. No code. Here's the setup.
→Stop Re-Explaining Yourself to Your AI
Most people pay a hidden tax every week: re-typing the same instructions to an AI for the same recurring job. A Skill is the fix — a saved set of instructions Claude runs on demand. Here's when to build one, when to just prompt, and two easy ones you could write today.
→Stop Babysitting Your AI. Build a Team Instead.
For a year I used AI like a vending machine — type a request, get an answer, repeat. Then I learned the difference between a chatbot and an agent, that an agent is really only four simple pieces, and that you can build a whole team of them in Cowork without writing a line of code.
→Boris Runs Thousands of Agents While He Sleeps. The Whole Trick Is One Command: /loop
The engineer who built Claude Code casually mentioned he has a few hundred AI agents running during the day and a few thousand doing deeper work every night. The mechanism behind it isn't exotic. It's one command — /loop — and it changes how operators should think about recurring work.
→Anthropic Just Put Claude Inside Small Business. The Opportunity Isn't the Tool.
Anthropic launched Claude for Small Business: 15 ready-to-run workflows wired into QuickBooks, PayPal, HubSpot, and the rest of the stack owners already pay for. Here's what it actually is, and the implementation gap it just exposed.
→Google I/O 2026: The 5 AI Updates That Actually Matter for Operators
Google shipped Gemini 3.5 Flash, an agentic Search, Gemini Spark, Ask YouTube, and the Omni world model at I/O 2026. Here is the operator's read on what each one means for your workday.
→Build Log: The After-Hours Calls Our Property Management Company Was Quietly Losing
Our own multifamily operation was sending leasing and maintenance calls to voicemail every night. Here's the problem we hit, what we built to fix it, and what changed.
→I Told It To Write a Blog Post. 10 Minutes Later I Had a Content Team.
Yesterday I dictated one sentence to Claude. What came back was a blog post, 5 designed social visuals, captions for 5 platforms, a video script, an organized Drive folder, and an open pull request to my live site. Here's the receipt — and the 200-line file behind it.
→Wispr Flow — I Don't Think I'm Going to Type Again
I started using Wispr Flow yesterday. I thought it was another voice-to-AI tool. It's not. It's voice-to-everything — email, Slack, Claude, the address bar, a Google Doc, a CRM note. Two days in and I'm questioning why I've been typing for 20 years.
→Google's New AI Search Guide: What It Actually Means for Your Business
Google just published the official playbook for ranking in AI Overviews and AI Mode. Most of the SEO industry is panicking. Most of it shouldn't be. Here's the operator translation.
→Google Has a Hidden Approval Gate on the Business Profile API — Here's How to Get Through It
Most local businesses pay $300/month for software that automates Google Business Profile. The API to do it yourself is free — but Google won't tell you it requires manual approval. Here's the full playbook.
→You Can't Learn AI By Watching Videos About It
18 months of playing with every AI tool I could get my hands on, and one realization that finally connected everything. Why most people are still using AI like a smarter Google — and what the real shift actually looks like.
→They're Spending $500 Billion on AI Infrastructure. Here's What That Means for Your Business.
The biggest infrastructure buildout in tech history is underway. Microsoft, Google, Amazon, and Meta are pouring hundreds of billions into AI data centers. Operators who understand why will be positioned to take advantage. Everyone else will just be surprised.
→Codex vs. Claude Code: I Build Production Systems With Both. Here's the Honest Breakdown.
OpenAI's Codex agent and Anthropic's Claude Code are both trying to be your AI coding partner. I've used both to build real production systems. The differences matter more than the benchmarks suggest.
→Local LLMs Are Coming. Here's What That Means for Operators.
There's a viral take on r/LocalLLM that local models are 12-24 months from taking over. The developer case is real. The operator case is different — and the move you make this year matters either way.
→What an AI Phone Receptionist Actually Does (In Plain English)
Not a robot voice reading from a script. Not a phone tree that makes people want to hang up. Here's what a real AI receptionist does — and what it means for a business that's tired of missing calls.
→Beyond the Chat Box: The Operational Waste of AI "Conversations"
If your AI strategy relies on copying and pasting text into a browser tab, you don't have an automation system. You have an advanced, expensive typewriter. Here's how to build true autonomous infrastructure.
→Build Log: We Let AI Pick Our Tech Stack. Here's What Happened.
We didn't plan the architecture for this build. We just started prompting. Then we had to figure out how to fly the plane.
→Six Months Ago Google Changed the AI Game — Most People Still Haven't Noticed
I was a ChatGPT user until Gemini's context window update changed how I thought about what AI could actually do for real business operations.
→MCP Servers Explained: How AI Goes From Chatbot to Digital Employee
Most people using AI for business are stuck in copy-paste mode. MCP is what fixes that — here's what it is and why it matters for operators.
→How to Set Up Close CRM So Leads Stop Falling Through the Cracks
Wholesaling is chaotic by default. Here's the exact Close CRM setup — pipeline structure, smart views, and AI integration — that keeps deals from disappearing.
→How I Built a Business Website in a Day — Without an Agency, Without a Website Builder
When I tell people I built a production website in under four hours, they assume I used Wix or Squarespace. I didn't. Here's what I actually did, explained in plain English.
→Keep looking
Read what helps. Skip what doesn't.
Insights are here to be useful on their own. When an article genuinely connects to a Build, Solution, Tool, or series, you'll see that relationship inside the article.