A live spec of the AI operations layer I would build inside Impact Clients in my first ninety days as Executive Operations. Three systems shipped in week one. Twelve in total. All running against the stack you are already on.
Prepared for Richard Yu & the Impact Clients leadership team. Companion to the Loom video attached to the Workable application.
The first three are not chosen because they are easy. Each one removes an hour a day from a founder's calendar and gives it back to high-leverage work. Built on the existing stack. No new tooling required.
Audits the founder calendar weekly against a documented list of company-forwarding priorities. Flags meetings that do not move the company forward. Suggests cuts with reasoning. Proposes the cleanest replacement use of that block.
Reads from Google Calendar via a permissioned integration. Cross-references against a quarterly priorities doc maintained by the Exec Ops seat. Outputs a Friday review with a kill, keep, or compress call on every recurring meeting.
Important-Person-Slack inbox. AI sorts inbound messages from Richard's network into three buckets: needs Richard, can be delegated, can be archived without reply. Drafts replies for the second and third buckets so the human work is review and send.
Slack integration plus a language model trained on a small library of Richard's prior replies. Tone, length, what he says yes to, what he says no to. Updates priority of inbound based on relationship history and current company priorities.
Tracks open requisitions, candidate pipeline velocity, time-to-hire, and stage-by-stage drop-off. Auto-flags stalled processes against a documented SLA. Surfaces the one or two roles where a single intervention from leadership unblocks throughput for the rest of the funnel.
Reads from Workable. Builds a simple dashboard the leadership team checks weekly. Layered on top: a model that drafts the next-best-action against any stalled candidate, so the recruiter never has to write a status update from scratch.
Three of these ship in week one. The rest fill out across the ninety days, sequenced against where the next operational fire is burning. Each one is a layer on the stack the team is already on, not a parallel build.
Three checkpoints. Each with a specific deliverable. By Day 90 you have evidence the bet was right or evidence to make a fast cut.
Calendar Sentinel, IPS Inbox, and Hiring Throughput Engine running in production. Auditable by leadership. No black boxes.
Hours returned to the founder calendar quantified against the company priorities doc. Comp cost compared. Number sits on the Smokejumper Pipeline board for everyone to see.
If the numbers are not material, you fire me on the same Slack message you used to onboard me. You keep two months of payroll you would have paid the wrong hire for the equivalent six.
The downside is yours to take, not mine. The asymmetry is the entire pitch.
"This page is the receipt. The Loom is the voice. Mochary's playbook says years do not matter. I am here to test that line."