How I Would Redesign Contract Review as an AI-Native Workflow
The old route for contract review is email, PDFs, and Word track changes. Here's how I'd design an AI-native system that compares against a playbook and keeps judgment calls human.
Tag archive
#workflow automation
How I Would Redesign Employee Onboarding as an AI-Native Workflow
A teardown of why onboarding stays slow across HR, IT, and payroll, and how a coordination layer, not a chatbot, would fix the handoff.
How I Would Redesign Vendor Onboarding as an AI-Native Workflow
A system teardown of vendor onboarding: why chasing tax forms, insurance certificates, and bank details still takes weeks, and what an AI-native intake and risk-tiering system would automate versus keep human.
Why Adding an AI Agent to a Broken Workflow Usually Fails
Adding an AI agent to a broken workflow rarely fixes it. Here's why the failure is usually the process, not the model and what to map before you automate.
How I Would Redesign Expense Report Reconciliation as an AI-Native Workflow
A system teardown of expense report reconciliation: why the old route of receipts, card statements and spreadsheets persists, and what an AI-native coordination layer would look like.
How I Would Redesign Invoice Processing If We Started From Zero
A system teardown of accounts payable: why three-way matching is still manual, and what an AI-native invoice processing route would automate and keep human.
How I Would Build an AI-Native Insurance Claims System
The 1995 insurance claims workflow is a document relay between six people. Here's how I'd redesign it as an AI-native intake, triage, and settlement route.
AI Automation vs Manual Work: Where the Handoff Should Actually Move
Where the AI-to-human handoff should actually sit in a workflow, using refund and return approval as the worked example.
How I Would Build a Bookkeeping System That Hides the Ledger
A designed teardown of the coordination layer under Greek bookkeeping: inbox invoices, classification, myDATA transmission, rejections, and the accountant who still signs. A model, not a client build.
How I Would Build a CE Marking System That Keeps a Product File Alive
A designed teardown of the coordination layer under CE marking: product intake, requirement mapping, evidence gap analysis, test coordination, technical file generation, and the engineer who signs. A model from the lab, not a client build.