AI where it helps.
Operator judgment where it matters.
Boring software where the answer can't be wrong.
Yes, there is value in embracing AI for almost any business. My job is helping you get the shape right: what should be automated, what should stay human, where the facts need to be deterministic, and what kind of system the team will actually trust and use. Where that work usually breaks out:
AI WHERE IT HELPS
Language, ambiguity, and judgment support.
Use the model for the things models are weirdly good at: classifying messy messages, drafting vendor replies, interpreting ambiguous memos, searching policy docs, summarizing legal news, proposing mappings, or explaining why something looks off.
- classification and triage
- drafting and summarization
- semantic search and RAG
- edge-case review and anomaly flags
OPERATOR JUDGMENT
the boundary is the work.
Decide what to automate, what to keep human, what needs source-of-truth data, and where review belongs before the system reaches a customer, a partner, or a decision-maker.
BORING SOFTWARE WHERE IT HAS TO WORK
what needs to be boring, deterministic, and right.
Facts. State. Permissions. Proof. Payment status comes from Stripe — not from a model that's pretty sure. Customer state comes from Salesforce. Access comes from your permissions system. The output ties back to source data. Use code for the parts that can't be fluently wrong.
- API lookups and source-of-truth data
- structured workflows and review queues
- retries, idempotency, audit logs
- dashboards, exports, and handoff docs