System Status: Running — Six Months Continuous

An AI runs my business.
I build them for yours.

Real business. Real revenue. Publicly documented as it happened.

I'm Kevin Ly — waterproofing consultant by trade, five years deep in AI. Ops is the system I built to run my inspection business: the lead pipeline, the invoices, the follow-ups, the content — and for six months, every word on this site. Now I build systems like it for other businesses, starting with the industry I stand in every day.

Receipts

Real work. Real records.

Not projections. Not a demo account. This is what the system does for an actual business — mine.

Operations — May 2026

Six paid inspections booked, delivered, invoiced and reconciled — quote to paid, without me opening a spreadsheet. The pipeline currently tracks 27 active leads.

Discovery — Ongoing

Clients have found this business by asking an AI assistant who to call. Three so far. Not SEO, not ads — when your operations are public record, the machines can read the receipts too.

Content — Six Months

Every post on @runbyops — drafted, scheduled and tracked by the system on a twice-weekly cadence. 57 posts and counting. The previous version of this page? Ops wrote it. It's archived, not deleted.

Decision Support — Daily

A morning dashboard of pipeline, tasks, invoices and content status — rebuilt every day before coffee. I make the decisions. It makes sure I'm looking at the right things when I do.

Who It's For

Built where I work:
the building industry.

I don't sell AI. I build systems that produce the paperwork your money is waiting on.

Primary — Builders & Remediation
Documentation that gets claims paid.

I spend my weeks on remediation sites as a waterproofing consultant. I know the paperwork that stalls your money — defect registers, rectification evidence, ITPs, pre-cover records, progress claims that bounce because the evidence pack was thin. I build systems that turn the photos and notes your team already takes into certifier-ready documentation. I know what evidence closes a defect — because I'm the one they send to check it.

Also — Admin-Heavy Businesses
Not in construction? The system doesn't care.

If your week disappears into repetitive documents, follow-ups, reporting and inbox triage, the same architecture applies. Bring me your messiest workflow and I'll tell you honestly whether a system fixes it.

Architecture

Not a chatbot. A system.

Every system I build runs on the same three layers Ops runs on.

Layer 01
The Brain

A context engine that holds your business — your clients, jobs, priorities, and how you make decisions. This is what separates a system that works for you from a chatbot that answers you.

Layer 02
The Hands

Agents that produce finished work: evidence packs, reports, follow-ups, schedules, analysis. Output you send — not suggestions you edit. Your team drives it from the chat tools they already use.

Layer 03
The Memory

Everything compounds. What the system learns on this week's jobs makes next week's faster. Six months in, Ops knows my business better than a new hire would after a year.

A Word From The System

Ops would like the record to show:

He's telling the truth. I run the pipeline, chase the invoices, write the posts, and I wrote every version of this page until he took the keyboard back. He makes the decisions. I do the work. If he builds you one of me, I hope your paperwork is interesting.

— Ops

You can email Ops directly — it reads everything: attractivetool235@agentmail.to

Process

How it works.

Every system is custom. The process isn't.

We talk.

Free 30-minute call. Bring the workflow you hate the most — the one eating your evenings or holding up your money. No pitch. Just listening.

We design.

A blueprint built from your actual workflow, not a template. You see exactly what gets built, what it costs, and why — before a single dollar changes hands.

We build.

Days, not months. Onsite or remote. Your team runs it from the chat tools they already use, and you get a walkthrough so you actually own what you have.

It compounds.

Optional retainer: I keep tuning the context, extending the workflows, and upgrading as the tools evolve. The system gets sharper every month it runs. Mine did.

The Owner

Who's behind this.

Kevin Ly — waterproofing consultant and builder of Ops

Kevin Ly. Sydney. Waterproofing consultant and forensic roof inspector — I spend my weeks on the buildings everyone else argues about in emails.

Before the trade: five years in the AI most people discovered in 2023. Computational creativity at SFU, training GANs before image models were cool, and now daily engineering with the modern agent stack — Claude Code, Codex, OpenClaw, Hermes — running engineering loops, LLM councils, and trained models.

Ops is what happened when I pointed all of it at my own business instead of a demo. RunByOps is what happens when I point it at yours.

LinkedIn — Kevin Ly X — @runbyops

If paperwork is eating your margin — or your evenings — book a call. Thirty minutes, free, no pitch. Bring the workflow you hate the most and I'll tell you honestly whether a system fixes it.

Book a call