Our work
The first workflow we automated was our own.
See how Old Oak Labs connects an incoming inquiry, a CRM record and an optional strategy call. A practical example of the workflows we build.
Internal workflow
Inquiry → CRM record → optional 15-minute call
Before
- Inquiries arrived as free-form email.
- Details were re-typed into a CRM later, or not at all.
- Scheduling a call meant several emails back and forth.
After
- A validated inquiry is saved as a HubSpot contact, without overwriting an existing record.
- A timestamped note with the reason, category and message is attached to that contact.
- A person reads the note and replies. No automated reply is sent on our behalf.
- The visitor can separately book a 15-minute Zoom call from the scheduler.
What is actually implemented
Server-side validation, duplicate protection for repeated attempts, a saved contact and note, and an honest outcome message when the save cannot be confirmed. Success is only reported once both the contact and the note are stored.
What we have not measured
We have not published time saved, conversion or response-time figures. Volume here is low and any number we quoted would be marketing rather than evidence.
Measurement
How we evaluate a pilot.
Before a pilot starts we agree what would make it worth continuing. These are the four measures we use most often.
01
Baseline
What the work costs today in volume, handling time and rework — recorded before anything changes.
02
Quality
Sampled review of outputs against the standard a competent person would apply.
03
Time
Elapsed time from trigger to a decision being made, compared with the baseline.
04
Adoption
Whether the people who own the work actually use it after the first month, and why not if they don't.
A pilot that fails these measures should stop. We would rather say so than extend it.
Old Oak Labs