Business operations can look like a discipline of models, systems, and planning. Ian Lazarus learned many of its most important lessons earlier, inside his family's hospitality businesses.
Restaurants make operating quality immediate. Service is visible, work arrives in real time, and a missed handoff affects a customer within minutes. Ian carried that foundation through finance, high-growth technology companies, founder advising, and business operations leadership.
Hospitality teaches ownership early
Growing up around restaurants exposed Ian to pace, customer expectations, and the need to solve problems without waiting for perfect conditions.
Hospitality also makes interdependence obvious. Front-of-house service depends on preparation, staffing, inventory, communication, and dozens of small operational decisions. The customer experiences the combined result, not the internal explanation for a failure.
That is useful preparation for business operations. Customers and employees experience the whole company even when the company organizes work into separate functions.
Finance revealed how software businesses work
Ian later moved into investment banking and private credit. That path developed analytical rigor and exposed him to software transactions and private-equity activity.
Finance teaches a particular form of discipline: connect operating choices to economic consequences. Growth, retention, margin, and capital are not separate stories.
The experience also pulled Ian toward operating roles. Evaluating a company from outside can sharpen judgment, but building inside one reveals the constraints hidden in the model.
Career pivots can build operating range
Ian's career includes moves across startups, roles, and company stages, including QuadPay and Klarna. Each environment created different lessons about timing, scale, and product-market conditions.
A broad operator learns that the same playbook will not work everywhere. An early company may need speed and direct founder involvement. A larger organization may need clearer ownership, documentation, and coordination.
Range is valuable when it produces better diagnosis rather than a larger library of generic advice.
Service is a useful test for internal systems
Operations teams can become focused on internal efficiency. Hospitality provides a simple counterweight: does the change improve the experience of the person being served?
That person might be a customer, seller, manager, or partner. A workflow that saves time for one function while creating confusion for another is not automatically an improvement.
Strong operators trace changes through the full service chain. They consider who benefits, who absorbs new work, and what the end user will actually notice.
AI should create practical operating leverage
Ian sees AI as a meaningful tool for building playbooks, improving processes, and helping teams engage customers more effectively.
The important word is practical. AI should shorten the path from problem to useful action. It can organize existing knowledge, draft repeatable procedures, prepare account context, and help teams inspect workflows.
The operator still needs to verify the output and define the standard. Faster production of an unclear process is not leverage.
The practical lesson for business operators
Ian's path suggests a simple operating model:
- Learn the customer experience, not only the internal process.
- Connect operational decisions to economic outcomes.
- Adapt the playbook to the company's stage.
- Evaluate efficiency across the entire handoff.
- Use AI where it removes real work or improves a decision.
Business operations is strongest when analytical rigor and service instinct reinforce each other.
About the guest
Ian Lazarus is VP of Business Operations at Zippy. His background spans hospitality, investment banking, private credit, high-growth technology companies, startup advising, and business operations.
