Ralph Dandrea and the 100-page sandwich problem

A sandwich ought to be a manageable proposition. Bread, filling, a customer who would prefer to eat before the afternoon disappears. Ralph Dandrea found enough complexity in the operation to produce a 100-page manual. He co-owned a submarine sandwich shop after college, and he took the training seriously. Perhaps rather more seriously than lunch generally demands.

The detail is funny because it is so specific. It also offers a useful introduction to the founder and CEO of ITX. Dandrea liked processes. He liked understanding how a thing worked and making it work better. By 2010, he could look back on those sandwich instructions with some amusement, acknowledging that he hoped he had tempered the habit at his software company.

A former workplace had supplied a less flattering assessment: “Little Napoleon.” Dandrea volunteered the nickname himself. The capacity to laugh at that earlier version of himself matters to his story. Over the years, the object of his attention widened from specifying the work to understanding the people doing it.

His business education began well before his degrees. His own account puts his first electronics venture at twelve and computer database services at fourteen. He later studied finance at Rochester Institute of Technology, with an emphasis on economics, and earned a law degree and an MBA at the University at Buffalo. He describes himself as an economist at heart. Problems, choices and consequences were familiar territory before ITX had a name.

The $500 exit from an argument

One of his more revealing business lessons involved a purchase in the early 1990s. A computer repair business was closing, and Dandrea agreed to buy its equipment. The departing owner appointed a broker to negotiate. They settled on $3,500. Dandrea paid. Then the owner called, furious about the price and threatening to sue.

Dandrea thought he had followed the agreed process. He was ready to defend himself. His family friend and mentor Al Ferrini listened, then redirected his attention to the business he actually wanted to be in: solving customers’ technology problems. A courtroom victory would be an expensive distraction from that work.

So Dandrea asked the seller which equipment he considered undervalued. The disputed difference amounted to $500. He sent another check and ended the quarrel. Years later, he used the episode to explain his distinction between fairness and workability. He still believed he had acted fairly. He also decided that spending more money to settle the matter was worth it.

The anecdote makes his favored word, workability, unusually concrete. It has a price here. Five hundred dollars bought an end to a dispute and permission to think about something else. There are cheaper ways to be right. There are also much more expensive ones.

A founder learns to leave room

Dandrea founded ITX in 1997. The business began as a two-person consultancy managing telecommunications projects and developed into a custom software company. That description can make the progression sound tidier than any working business feels. It crossed the dot-com boom and bust, changes in customer needs, and changes in the founder’s understanding of his own job.

A formal division of responsibilities arrived in 2012. Fred Beer succeeded Dandrea as president; Dandrea retained the CEO role and became chairman. Beer had joined the executive team in 2009. A company built around one founder’s technical and commercial abilities was giving other people defined authority. The presidency was a job someone else could do.

Dandrea’s writing about mentoring shows the same adjustment at a smaller scale. Asked to mentor for High Tech Rochester’s LaunchPad program in 2013, he stopped to examine what the role required. He had met Techstars co-founder David Cohen at an entrepreneurs’ gathering in Miami and read Cohen’s Mentor Manifesto. But a list of rules did not quite answer his question about how to inhabit the role.

His resulting declaration included a constraint that a founder accustomed to giving instructions might find useful: the mentor has no decision rights over the other person’s venture. The test of success belongs to the person receiving help. Experience is offered without a claim to control.

Two of his stated beliefs were short enough to fit on a card: “I may not know the answer.” And: “Listening is more important than speaking.” The sandwich manual had found an editor.

“Listening is more important than speaking.”

Ralph Dandrea · on mentoring, 2013

Trust has a delivery schedule

Dandrea has a habit of bringing leadership ideas down to ordinary transactions. In his 2015 essay about clarity, he imagines a passenger telling a New York cab driver to go to the airport. There are several possible airports. A brisk departure can be a thoroughly efficient way to head in the wrong direction.

For him, useful leadership means establishing the destination and making the route explicit. At ITX, that extends to agreeing with customers about what a project will include and what it will leave out. Unresolved expectations consume effort later. Clarity earns its keep by reducing that waste.

His companion writing on trust is similarly practical. Trust develops through repeated behavior. A new customer has little history on which to base confidence, so a project manager can start with something modest: send the promised status update at the promised time. Then do it again. Reliability gives the relationship evidence.

This approach suits a software services business, where much of the work is invisible to the buyer until someone demonstrates it. A customer cannot inspect every technical decision. They can notice whether the person managing the project keeps a small promise. Dandrea treats those moments as part of the product relationship, with consequences for how comfortably the next decision gets made.

The contrast with a hundred pages of sandwich instructions is useful. A procedure can specify what should happen. A working relationship also needs repeated evidence that people will follow through, acknowledge problems and repair commitments. The manual and the status email serve different parts of the same practical concern.

Everyone gets a place at the toast

By 2014, Dandrea was already writing about the complications of a distributed workforce. ITX had people working as far away as Argentina, Romania and Spain. Access to talent beyond the neighborhood was an advantage; keeping those colleagues part of the company required deliberate effort.

His list of difficulties was specific: accountability, location and coordinating across time zones. Office colleagues could exchange information without realizing that someone remote had been excluded. A person attending through a screen could miss the casual exchanges that help a team feel like a team. Technology provided a connection, but habits determined who belonged in the conversation.

After attending the Office Optional conference in San Francisco, he described practices ITX had adopted. Team conversations belonged in shared chat, including the informal remarks. Celebrations could include virtual toasts over video. It is a pleasingly ungrand detail: an organizational philosophy occasionally needs a beverage and a working microphone.

His thinking about the physical office also left room for employees’ preferences. Before ITX’s 2019 move into downtown Rochester’s Metropolitan building, the company surveyed its team. Most non-management employees who regularly used the office preferred a city location. Dandrea cited that preference when explaining the decision.

Rochester competed with other possible locations, including Portland, Oregon. Talent, quality of life, retention and business costs helped make the case. Dandrea’s description of a thriving downtown included homes, workplaces, food, theater and shopping within easy reach. The interests of a software company extended past the office door and into the city around it.

The customer was never another Ralph

At ITX’s twenty-fifth anniversary in 2022, Dandrea described another correction in perspective. Earlier software work had too often treated the developer as a substitute for the eventual user. That left real-world situations and unfamiliar needs outside the design process. Product thinking gave the team a way to examine the product separately from themselves.

It is a recognizable temptation for someone who understands a system deeply. Familiarity makes the next step obvious. The person using the software may have a different task, a different level of knowledge, or a reason to approach it that the builder has never considered. Dandrea’s account of ITX’s evolution makes room for those differences.

The anniversary conversation also gave luck a place in the company’s history. He credited family introductions, early mentors, partners and the opportunities that happened to arrive. Sean Flaherty, his colleague and longtime partner, recalled their encounter on a Y2K project. The company’s origin had relationships in it as well as technical ability.

Recognition followed along the way. Dandrea was included in the Rochester Business Journal’s Power 50 Technology list in 2022. His profile that year described approximately 250 people at ITX and a preference for calculated risks, shaped by watching entrepreneurship succeed and fail in his own family. He also marked employees’ length of service with annual awards. Longevity was something to acknowledge in public.

In 2023, ITX acquired Philadelphia-based SUMO Heavy, adding e-commerce expertise. The move extended the company’s range of problems to solve. It also illustrates the sort of growth Dandrea described: bringing in people with knowledge the existing organization could use, and making that knowledge available to clients.

What survives when the code gets cheaper?

The questions have acquired a new setting. In June 2026, Dandrea and ITX vice president of technology Michael Lesher published two essays about AI and the changing value of software work. The vocabulary included economic moats, but the concern was familiar: what does a customer have reason to trust?

Their business argument places weight on service, guarantees, expertise and human accountability as software becomes easier to produce. They argue that a feature set alone offers less protection when comparable tools can be created quickly. Someone still has to stand behind what the system promises and take responsibility when it disappoints. This is their forecast of where durable value will sit.

The second essay follows that argument into individual careers. Dandrea and Lesher expect more value to concentrate in identifying problems, understanding business context, validating systems and owning outcomes. Engineers retain responsibility for architecture and the soundness of production software. Faster execution enlarges the importance of deciding what deserves to be built.

For a founder whose early instincts produced an exhaustive lunch manual, this is an interesting place to arrive. Better tools make more activity possible. Judgment determines which activity helps. Across his writing, Dandrea keeps returning to the person on the other side of the work: the entrepreneur receiving advice, the distant teammate, the customer waiting for an update.

A hundred pages can explain how to make a sandwich. Someone still has to listen to the order.