Six engagements. All shipping in production.

The problem
A Miami real-estate developer was bleeding hours every week chasing reviewer comments across half a dozen Miami-Dade permits. Manual logins, copy-paste into spreadsheets, drafting responses by hand, chasing consultants. Comments slipped through. Deadlines slipped after them.

What I built
An agent now watches the permit system every business hour. It catches every change, drafts the applicant response, and sends three emails: an instant alert when a comment lands, a morning briefing, and an evening digest. The dashboard rebuilds itself after every check. Multi-permit on one screen.

The problem
A restaurant operator was buried under PDF invoices from a long tail of vendors. No visibility into reorder cadence, vendor concentration, or the prices that quietly crept up between quarters. Stockouts happened. Margins eroded.

What I built
Each PDF lands and parses on arrival into structured rows. A reorder engine watches how often each item normally ships. A pricing engine watches what is creeping up. The kitchen manager runs the whole thing from a phone. Mobile-first, easy enough to learn between services.

The problem
The sales team at a rigging-and-cable distributor was building quotes by hand off inbound RFQ emails across nearly 4,000 SKUs. Wire rope, cable, chain, and rigging hardware come in dozens of variations. Customers send abbreviations, typos, Spanish names, and Outlook mobile messages with broken line breaks. The team was losing deals to faster competitors.

What I built
The agent now reads every inbound RFQ, parses every line item, identifies the right product, prices it against the live ERP, checks live inventory across four warehouses, and drafts a complete quote in minutes. It handles the abbreviations and the typos. The alias table is self-learning and AI-poisoning resistant. Margin alerts fire on lines under 30%. Customer-cycle reports run weekly. Sales managers can approve and reject from inside the email.

The problem
A financial services firm had no real visibility into what was happening inside their 200-plus mailboxes. Forwarding rules, the kind that quietly mail every CFO message to a personal Gmail, are invisible to native security tooling. Nobody had ever looked.

What I built
InboxWatch ran a metadata-only sweep across every mailbox: a hundred checks per inbox, ten threat categories, no message bodies touched. The forty-seven forwarding rules surfaced in the first pass. One of them had been quietly mailing invoices and signed contracts to a personal address outside the firm for the better part of a year. We closed it the same hour and kept the evidence trail the auditor would want.

The problem
A law firm partner's email started behaving strangely on a Sunday. Sent items the partner did not recognize, MFA prompts at 3 AM, mailbox rules that were not there the week before. Client data and active matter correspondence sat in that inbox.

What I built
Live on a call within 30 minutes. Contained inside two hours: every active session revoked, persistent app tokens the attacker had been using to bypass MFA killed, credentials rotated with phishing-resistant authentication. Forensics traced lateral movement to two more accounts and contained both the same hour. Timeline ready for the insurer, the bar, and counsel by Monday.

The problem
An ITAR-registered aerospace manufacturer in Florida had Federal Contract Information flowing through email, customer portals, an ERP, and Dropbox. Their next contract opportunity required a CMMC Level 1 attestation. Seventeen controls across six domains. Zero documentation.

What I built
Complete Level 1 toolkit: gap assessment mapping current state against all 17 controls, five plain-English policies (acceptable use, access control, incident response, media protection, physical security), a system security plan ready to file, a remediation playbook with evidence tracking, and an SPRS self-assessment worksheet. Each policy was written to reflect how the team actually works, not how an auditor wishes they worked. Thirty days of post-delivery support to walk through SPRS submission and answer questions during early implementation.