From event work
to a clearer operating system.

I started working with my uncle immediately after high school and continued through SUNY Oswego. We operate an Audio & Visual company in Central New York, with a focus on Syracuse and the surrounding markets. For the first four years, the business grew the reliable way: excellent work, professional service, and a network of venues and event coordinators who knew they could trust us.

That kind of growth creates a particular kind of problem. The relationships are strong, the work is real, and the business is moving—but the information behind the work starts to scatter. Spreadsheets, QuickBooks, documents, email threads, and conversations each served a purpose. Together, they made it hard to see the current state of a client, event, referral, or next action.

The idea that exposed the real problem

My uncle proposed a way to make our venue relationships more valuable. When a venue referred a client who hired us for AV, we could share an agreed-upon margin from the equipment rental or related service. The venue would create an additional revenue opportunity, the client would have a trusted technical partner, and we would have a stronger path to qualified work.

The idea was sound. The administration was not. To make the program reliable, we needed to connect the referring venue, the client, the event, the selected services, the equipment, the labor, the invoice, and the final margin. Without that chain, a discount or referral program could create more confusion than value.

That incentive became the forcing function for a larger realization: we did not need another isolated spreadsheet. We needed a clearer operating system.

The commercial idea only becomes useful when the operational chain can be seen and reconciled.

Building close to the work

During my final year at SUNY Oswego, I started investing heavily in AI tools, full-stack development, and systems architecture. I had considered studying both business and software engineering, but ultimately chose Software Engineering. The degree gave me a technical foundation; working inside the AV company gave me the operational context needed to use it well.

The arrival of ChatGPT and other GPT-3-era tools 4 years ago, halfway into my freshman year, it sparked the beginning of a few new ways to approach Software Engineering. Over the course of those 4 years, significant advancements have been made in not only the LLM's capabilities, but so too the tool-kit of entire AI-accelerated workflows and systems. I saw how quickly software could be explored, prototyped, tested, and improved with an AI assistant in the development loop.

AI accelerated the implementation. It did not replace the need to understand the business, define the rules, or test the result.

That distinction matters. AI can produce sloppy code, but it can also help a developer produce sound, maintainable software when the foundation is deliberate: clear requirements, sensible data relationships, security boundaries, and testing appropriate to the work.

From a public front door to private operations

The first four years had little online presence. The website and Google Business Profile changed that by giving prospective clients and venues a place to validate the work before starting a conversation.

The website works as the front door to the operating system. A person can discover the company through search, understand the services and quality of work, submit an inquiry, and share more useful project information through a structured form. That inquiry can then enter the same follow-up process as every other opportunity.

This is the shift from a website as a brochure to a website as an acquisition system. The marketing activity does not end when someone fills out a form. The form starts a business action.

What changed in the ordinary work

A project can now be understood as a connected record rather than a trail through separate tools. The venue, coordinator, client, event details, services, inventory, labor, files, messages, schedule, contract, invoice, and next action all belong to the same operational story.

That visibility is especially valuable because events change constantly. Guest counts shift, rooms move, schedules change, equipment needs evolve, and clients add or remove services. A shared event record makes it easier to see what changed, when it changed, who needs to know, and whether the change affects equipment, labor, pricing, or timing.

The most expensive mistake is often not a dramatic technical failure. It is a small uncommunicated detail that reaches the event floor too late. Better records reduce that risk while also making handoffs safer when one person is unavailable.

Where the value compounds

The strongest result is not a single automation. It is the capacity recovered when people spend less time searching, re-entering, and reconstructing the work. The system makes the strengths that built the business easier to see, repeat, and improve.

The value can be measured in time recovered per event, qualified opportunities that no longer go cold, fewer preventable corrections, clearer invoice and margin visibility, and stronger venue partnerships. The exact figures should be filled in from operating records as the implementation matures.

The best part of the deal

The most valuable outcome is not simply that we have a website or that business information can live in one place. It is that the company has a path to grow without letting operational complexity grow at the same rate.

The original venue incentive was a commercial idea. The system turned it into something the business can manage, measure, and improve. The website creates more opportunities to be discovered. The backend helps us respond and deliver more consistently. The shared records make it easier to build trust with clients, venues, and event coordinators.

In other words, the technology strengthened the relationships that built the business in the first place.