An inquiry arrives. Someone copies the contact into a CRM, checks a calendar, asks for missing details, updates a spreadsheet, and tells the sales team what happened. Each step is familiar. Together, they can turn a promising lead into a coordination project.
In Sync Or Swim: Bridging The Gap With Automation at the Northwest Event Show 2026, Loophole’s Noah Latsch and Sean Sakaguchi examined that gap between having software and having a business that runs well. Their central framework was straightforward: standardize the work, connect the systems, and then automate the repeatable steps.
The session was part of NWES’s April 2026 gathering at the Seattle Convention Center. In an industry built around human connection, its practical question was how to stop spending so much human effort keeping disconnected tools in sync.
Diagnose The Work Before Buying Another Tool
A missed handoff can look like a performance problem. A delayed response can look like a capacity problem. Before adding another person or another platform, look at what the team must do to complete the work.
Noah and Sean described the less visible infrastructure of a business: the applications, spreadsheets, messages, and informal notes through which information travels. When that infrastructure is fragmented, capable people become the connection between systems. They remember exceptions, reconcile conflicting records, and manually move work forward.
That makes the first diagnostic question surprisingly simple: where are people compensating for a process that the business has never clearly defined or connected?
Start With One Bottleneck
Choose a point where valuable work waits: an unqualified inquiry, an approval, a staffing response, or a missing event detail. Write down what must happen to move it forward. That gives you a specific process to improve and a result to measure.
Standardize, Connect, Automate
1. Standardize The Decisions And Inputs
Standardization starts with understanding how work gets done today. What information does an inquiry need? What makes it qualified? Who owns the next step? Which exceptions require a different response?
The goal is to make the repeatable parts explicit. Consistent client information, clear checklists, and agreed handoffs reduce the number of details a person must remember. They also give software something dependable to work with.
This can protect a high-touch experience. Your team still decides what the client needs and how to deliver it; they spend less time reconstructing the routine steps around that decision.
2. Connect The Systems That Hold The Information
Once the process is clear, follow the data. A contact record, event date, qualification status, and internal notification may belong in different tools. The connection should move the right information to the right place without asking someone to copy it repeatedly.
The presenters used an inquiry moving into a CRM, a calendar, and a team notification as an example. The useful question is not how many integrations you can add. It is which manual handoffs can disappear while the team retains a reliable view of the work.
3. Automate Work With A Defined Next Step
Only then is there a stable process to automate. Reminders, task creation, routing, draft responses, and status updates can follow the rules the business has established.
Skipping the first two steps leaves software acting on inconsistent inputs or incomplete context. A faster process is not an improvement if it produces the wrong result more quickly.
From An Incomplete Inquiry To A Useful Sales Handoff
Noah and Sean demonstrated an automated inquiry workflow for Suite Dreams, a fictional hotel, and its sales manager, Lucy. Starting with an incomplete wedding inquiry, they walked through how the system gathered missing details, checked the venue’s requirements, and prepared a useful handoff for the sales team.
The workflow divided the work among four agents, each with a specific role:
- Intake: read and summarize the incoming inquiry.
- Qualification: identify missing information and request the details needed to evaluate the lead.
- Booking: consult connected operational information to check fit and possible conflicts.
- Reply: assemble the result into a concise response to the prospective client.
Sean played the prospective client. His initial wedding inquiry omitted the details needed to qualify the request. The system asked for a date, start and end times, guest count, and budget.
When the response specified a budget below the ballroom’s minimum spend, the demonstration suggested another space instead of treating the inquiry as a dead end. After Sean accepted that alternative, the workflow showed updates in the connected calendar, spreadsheet, CRM, and team communication channel.
The handoff kept the sales team informed. The team could see the lead’s status, the information collected, and the activity behind the response. The demonstration also retained the existing email inbox. The new workflow coordinated with the tools around it.
Give AI The Context You Would Give A Colleague
The presenters compared an AI tool without context to a new employee asked to respond to a client without knowing the event, the business, or the prior conversation. Even a capable colleague would be poorly equipped to answer.
In the demonstration, useful context included qualification criteria, venue constraints, availability, and the conversation itself. The system had specific work to perform and information against which to evaluate it.
For your own business, define that context before asking an AI tool to act. Write down which facts it must use, which decisions it may make, and when it should hand the work back to a person. Review the output against the same standards you would use for a team member.
Turn The Framework Into A Small, Testable Plan
The session returned repeatedly to the difficulty of taking action. A broad intention to improve operations is easy to postpone. A clearly owned process with an observable outcome is easier to move forward.
Use this short exercise with your team:
- Pick a recurring delay. Choose one workflow, such as qualifying an event inquiry.
- Follow a real example. List the decisions, tools, people, and missing information involved.
- Define the desired handoff. Describe what the next person should receive and what “ready” means.
- Choose a measure. Track time to a useful response, manual touches, or incomplete handoffs before and after the change.
- Test a narrow improvement. Review ordinary cases and exceptions before expanding the workflow.
That process may reveal a configuration change in a tool you already own. It may call for an integration or a custom application. The framework helps you make that choice based on the work your business needs to do.
For examples of how these changes feel in daily operations, read the companion panel recap, There Is Finally A Better Way: Automation For The Events Industry.
