Zach was already running a successful company and proactively adding AI across it. Hook’s board wanted to lower expenses, operate more efficiently and create new revenue opportunities.
The work moved over several months, at a pace people could absorb. Zach led innovation and selected the projects, his team executed them, and Adam remained a sounding board as board chair.
Business goals
→
Useful changes
→
Everyday use
→
Next decision
The realization
Building something is only part of the job. People have to use it in their daily work, and the change has to help the business. Zach kept those two things together as adoption grew.
What happened next
01
Choose what could help the business
The board goals were clear: lower expenses, improve operating efficiency and find new revenue opportunities. Zach led innovation and selected the projects; his team executed them.
02
Put each change into real work
The team introduced changes inside the company and for customers, learning from everyday use instead of treating delivery as the finish line.
03
Keep the owner in charge
Zach kept choosing what moved forward. Adam served as board chair and sounding board in monthly conversations and as needed between them.
What changed, and what to measure next
Hook reported these initiatives in use or shipped. The measures below are ways to judge their business payoff, not claimed financial improvements.
Find answers without interrupting colleagues
The team built an internal assistant that answered course and content questions from shared knowledge sources. Staff could look things up without repeatedly relying on a single colleague.
Measure next: Time spent finding answers, accuracy and interruptions, after tool and support costs.
Bring the operating picture together
A daily Morning Brief assembled the calendar, cash, pipeline and open follow-ups. A twice-weekly leadership report brought information from several systems into one place and was reviewed before distribution.
Measure next: Time preparing updates, missed follow-ups and how any released capacity is used.
Make collections work easier
A collections assistant identified past-due invoices, matched payment history and prepared follow-up emails. People reviewed and sent the drafts; it did not independently contact customers.
Measure next: Collection effort, overdue balances and time to payment. Faster collection frees cash; it is not new revenue.
Reduce customer administration
Hook shipped Autopilot to run customer training programs with less manual administration, extending the product beyond individual tasks toward managing the program itself.
Measure next: Customer setup and administration effort, program adoption, retention and delivery and support cost.
Give customers more useful product features
The team shipped a read-only assistant for plain-language questions about a customer’s own training and phishing data, plus AI-assisted improvements and variations to phishing-simulation templates.
Measure next: Feature use, paid adoption, retention and incremental gross profit after delivery costs.
Keep support accountable
The support assistant answered tickets with citations to Hook’s documentation and handed the conversation to a person when it could not verify an answer. Customer-facing work used bounded actions, visible explanations and human review when an action required it.
Measure next: Cost per resolved contact, resolution time, answer accuracy and customer satisfaction.
The transferable lesson
Useful progress comes from choosing changes for a business reason, giving people time to adopt them and using what happens next to guide the following decision.
What could a worthwhile next step look like in your company?
We can start with the outcome you want, look across the business and decide which change deserves attention now.