You’ve Already Built the Foundation™

Prefer to listen? The audio version of this post is above.

When I first entered the technology business, I was learning a new language.

I had spent time selling insurance, but I did not have a technical background. I did not know the products, the acronyms, or how the pieces of a technology solution fit together. Suddenly, I was expected to speak with people who understood systems and products far better than I did.

I got an opportunity with IGX Global, a technology reseller, after persistently following up with the VP of Sales even though I had initially been turned down. I had no real technology experience, but I was willing to work, learn, and prove myself.

That did not mean the transition was easy.

I was making calls and trying to earn conversations with customers while learning the products myself. I was surrounded by people who knew more than I did, and there were plenty of moments when I wondered how I was going to catch up.

About six months in, I was frustrated enough to consider quitting.

Then I got an opportunity to work with TippingPoint, a company focused on intrusion prevention.

At a dinner, a challenge was put on the table: generate 15 meetings and win a flat-screen television. I was still learning the technology, but I understood sales. I understood how to pick up the phone, start a conversation, handle rejection, and keep going.

I started calling.

Three days later, I had booked 15 meetings. A week after that, I booked another 15.

I was lucky to have a great mentor during that stretch. He helped me understand the TippingPoint pitch and kept encouraging me to keep my head up. Less than a year later, TippingPoint recruited me to take over their New York City territory. That was a life-changing moment for me.

That experience changed how I thought about my place in the technology industry. I did not suddenly become an engineer. I learned that I did not need to know everything to create value. I needed to understand the problem, learn enough to communicate it clearly, and connect with the people who could benefit from solving it.

As I spent more time working with TippingPoint, I began to understand the technology and, just as importantly, how to explain it.

Intrusion prevention can sound complicated. There are technical details involving network traffic, performance, threat detection, and how a product fits into an existing environment. Those details matter, especially to the engineers responsible for making everything work.

But the person making a business decision also needs a clear answer to a basic question: What does this do for me?

I learned to simplify the message. The technology works inline and at wire speed, with the goal of stopping threats without disrupting legitimate traffic.

That simple explanation opened the door to a deeper conversation. Once someone understood the core value, we could discuss the technical details, the competitive differences, and whether the solution fit their needs.

I began to realize that my job was not to impress people with technical vocabulary. It was to make the value understandable.

The engineers needed to understand the engineering. The customer needed to understand the risk, the business impact, and why the solution was worth considering. My role was to connect those worlds.

That started with listening. The engineer, the product team and the customer each had different motivations, needs and priorities. When I took the time to understand all of them, I could help them connect.

That ability became one of the most valuable skills I developed in my career. I could work with technical people, learn from them, and translate what they were building into language that mattered to executives and customers. It helped me build relationships, create opportunities, and grow in an industry where I had started with very little technical knowledge.

It also changed the way I thought about learning.

You do not have to master an entire field before you can contribute. Start with the fundamentals. Ask the questions you are afraid might sound basic. Listen to how experienced people explain the problem. Learn the terms, but do not hide behind them. Then practice explaining the idea in plain language until someone outside the field can understand why it matters.

I am using that same approach as I build KARSA.

Product development brings together engineering, materials, manufacturing, intellectual property, software, and customer experience. Each area has its own vocabulary and its own set of trade-offs. I have to learn enough to make informed decisions, recognize what I do not know, and work effectively with the people who have deeper expertise.

That means asking manufacturers the right questions, working through design and production challenges with engineers, explaining the opportunity to investors, and listening carefully to the people who might use the product.

But the same principle applies to every conversation about KARSA. I can talk about the product’s components and how it works. Those details matter. But the bigger question is simpler: What problem does it solve for people?

KARSA is being developed to help people sanitize, dry, transport, and store the equipment they use for the activities they love. That can mean a yoga mat, hockey gear, soccer equipment, or other gear that takes time and effort to care for.

The technology enables the experience, but the value is giving people time back and making the routine easier.

No matter what you are selling, you are really selling life’s most precious resource: time. Time back in someone’s day, so they can focus on what truly matters to them.

That is the lesson I keep returning to: learn the technical details, respect the people who know them, and never lose sight of the human problem you are trying to solve. A feature only matters when it makes a meaningful difference to someone.

If you are entering a new industry, do not let the vocabulary convince you that you do not belong. Learn the language one conversation at a time. You do not need to know everything on day one. You do need the curiosity to keep learning and the humility to ask for help.

Looking back, I am glad I did not quit when technology felt overwhelming. That experience taught me far more than how to sell a technical product. It taught me how to enter an unfamiliar world, learn from people who know more than I do, and make complicated things understandable.

That skill helped me build a career in technology.

Now it is helping me build KARSA.

The goal is not to sound technical. The goal is to understand well enough to make the complicated clear, and to help people see why it matters.

What years in startups taught me about leadership, culture, listening to customers, and remembering the people behind the numbers.

Prefer to listen? The audio version of this post is above.

Over the course of my career, I have worked with a lot of startups, founders, executives, and teams. I have seen talented people build impressive things, and I have seen promising companies struggle for reasons that had little to do with the technology or the market. One pattern has stayed with me: when a leader's ego gets in the way of listening, the whole organization can pay the price.

Ego is not automatically a bad thing. Founders need confidence. They need conviction when the path is uncertain, and they need enough belief in an idea to keep going when other people are skeptical. But there is a difference between believing in your vision and believing that your vision cannot be challenged.

When a leader becomes so attached to being right that they stop hearing other people, confidence turns into a blind spot. Customer feedback becomes an inconvenience. Employees learn to keep their concerns to themselves. Decisions become about defending the original idea instead of solving the problem in front of the company.

Early in my career, I worked at a startup where I was the first person on the go-to-market team. The founder had a strong technical vision for the platform and was determined to build it in a particular way. The technology was designed around advanced, real-time correlation and in-memory processing.

I brought him to New York City to meet with actual customers and buyers. The feedback was consistent. They did not need every part of the system to work in real time. What they wanted was to know about a potential threat or breach before they learned about it from a third party, potentially months after the fact. That need was also consistent with what industry reporting, including the Verizon Data Breach Investigations Report at the time, was highlighting about how breaches were discovered.

I brought that feedback back to the company. I also assembled a customer advisory board and brought those customers to headquarters. They repeated the same message: help us find out sooner. We had room to explore different ways of solving that problem, but the feedback was not getting through. The founder remained committed to the technical approach he had envisioned.

I want to be careful not to pretend I know exactly what was driving his decisions. I cannot know what was in his head. What I could see was the result: the people closest to the customer were telling us what mattered, and the organization was not adapting to what we were hearing.

Ultimately, the company went through roughly $30 million in venture capital without delivering a working product. That outcome was about more than one person's ego, and startups can fail for many reasons. But the experience left a lasting impression on me. Technical ambition is not a substitute for solving a real customer problem. A vision has value only when you are willing to test it against reality.

I have seen another version of the same problem in organizations where leaders seem focused on building layers of hierarchy beneath themselves. An org chart can become a symbol of status rather than a tool for getting work done. As the layers grow, the distance between executives, employees, and customers can grow with them.

Those layers can create silos. Marketing blames sales. Sales blames customer success. Customer success blames renewals. Everyone has a reason the problem belongs to another team, and everyone is busy protecting their own territory. Meanwhile, the customer experiences one company, not a collection of departments.

The customer does not care which team owns the handoff or which executive owns the metric. They care whether the product works, whether the service delivers, and whether the company does what it said it would do. If the teams are not working toward that shared outcome, the org chart may look organized while the customer experience feels fragmented.

Healthy organizations need accountability, clear roles, and good management. The answer is not to eliminate structure. It is to make sure structure serves the mission instead of serving someone's need for status. The best leaders reduce unnecessary barriers between the people building the product, the people selling it, the people supporting it, and the people using it.

Culture is not just a set of values printed on a wall or a slide in an onboarding deck. It is what happens when someone raises a concern, challenges a decision, admits a mistake, or brings difficult customer feedback into a meeting.

If people believe they will be dismissed or punished for speaking honestly, they will eventually stop doing it. The leader may still receive updates and dashboards, but the information becomes less useful because people are filtering what they say. Silence can look like agreement from the top of the organization. Often, it is simply a sign that people no longer believe speaking up will make a difference.

When people feel heard and valued, they are more likely to bring forward ideas, identify problems early, and care about the outcome beyond their individual job description. That commitment can be contagious. People who believe in the mission often bring more energy to the work, and customers can feel the difference in how a company treats them.

A positive culture does not mean everyone agrees all the time. It means people can disagree constructively, challenge assumptions, and remain focused on the shared goal. A leader should not need to be the smartest person in every room. A leader needs to make it possible for the best thinking in the room to be heard.

Unchecked ego can damage more than a company's results. It can affect the people who work there and the leader's own career. People remember whether they were listened to, whether their contributions were respected, and whether a leader took responsibility when things went wrong.

Over time, patterns become reputations. If someone repeatedly creates toxic cultures, dismisses feedback, or treats colleagues as pieces on a chessboard, changing companies does not necessarily change the pattern. Different logos on a résumé do not erase the experiences people have had working with you. A reputation can arrive before you do.

That is one reason humility matters. Humility is not a lack of confidence or the absence of strong opinions. It is the willingness to recognize that your perspective is incomplete, that other people have expertise you do not, and that the mission matters more than your need to win an argument.

I understand why leaders focus on numbers. Revenue, growth, retention, pipeline, and profitability matter. They tell us whether the business is healthy and where attention is needed. But the numbers are the result of people doing work together. They are not a replacement for those people.

Every company is made up of human beings with strengths, blind spots, ambitions, pressures, and room to grow. People want to know that their work matters, that they can be honest, and that they are contributing to something bigger than a departmental scorecard. Leaders have to make time for those conversations, especially when the demands of running a business make it tempting to stay buried in the spreadsheet.

As I continue building KARSA, I keep coming back to how much a company depends on people working toward a shared purpose. We are building wellness technology intended to make it easier to sanitize, dry, transport, and store the gear people depend on. The product matters, but so do the people who design it, build it, support it, and help customers understand its value. No founder can do all of that alone.

The work of leadership is not just setting the vision or tracking the numbers. It is creating the conditions for people to do their best work together, to be honest about what is not working, and to stay connected to the people the company exists to serve.

Ego can help a founder take the first step. It can provide the confidence to pursue an idea that does not yet exist. But when ego becomes more important than curiosity, listening, and respect, it can turn into a barrier between the company and the people who could help it succeed.

Customers are telling you something. Employees are telling you something. The market is telling you something. The question is whether you are willing to hear it, especially when it challenges what you wanted to believe.

A founder's job is not simply to build a business. It is to build an environment where people believe in what they are building together. That starts with remembering that titles and org charts do not make anyone more or less human. We all have strengths. We all have flaws. We all have something to learn.

So take a beat. Look up from the spreadsheet. Talk to the people doing the work and the people using what you make. Listen without preparing your rebuttal. Make it safe for someone to tell you something you may not want to hear.

The best leaders are not the ones who never get it wrong. They are the ones who stay approachable enough to learn, humble enough to change, and focused enough to remember what matters most: the people, the culture, and the value the company creates for its customers.

Prefer to listen? The audio version of this post is above.

For a long time, I did not have a clear plan for where my life was going.

I grew up in a small town in northeastern Connecticut. Money was tight, family life was complicated, and I took on responsibility young. School was not where I found my confidence. I struggled academically, and I was not the kid who had everything figured out or a straight line mapped out for the future.

I was mostly reacting to what was happening around me. I knew I wanted a different life, but wanting something different and knowing how to get there are two very different things.

One of the jobs I took was working overnight at a printing press. There is something about working through the night, watching the hours pass, that can make you think hard about where you are headed. I started to see a version of my future that I did not want to accept as inevitable. If I wanted a different outcome, I was going to have to change how I approached my life.

I needed structure. I needed to learn how to prepare, follow through, and do things that were difficult even when I did not feel like doing them. That was part of what led me toward military training.

My path through the Marines and the National Guard was not a perfectly straight line, but the experience helped me understand the value of discipline and preparation. I began to see that progress was not about waiting until I felt motivated or confident. It was about doing what needed to be done, even when I did not feel ready.

Discipline gets talked about as if it is some special trait that certain people are born with. I have come to see it differently.

Discipline is a decision you keep making.

It is showing up when you would rather stay home. It is doing the next useful thing when the bigger goal still feels far away. It is being accountable for your choices, including the choices nobody else sees.

Structure did not magically solve every problem in my life. It did give me a foundation. Instead of feeling like everything was happening to me, I began to understand that my actions could influence what happened next. Every time I followed through on a commitment, I had another piece of evidence that I could trust myself.

That lesson followed me into my career.

Sales requires discipline long before it produces results. You make calls when people do not answer. You follow up when it would be easier to move on. You prepare for meetings, learn your product, listen to customers, and keep going through rejection. You cannot control every outcome, but you can control whether you do the work that gives you a chance.

Over time, those small actions compound. They build skills, confidence, relationships, and a reputation. Eventually, the work you put in behind the scenes creates opportunities that might look like luck to someone who did not see the preparation.

Years later, I would need that same discipline as I moved from a career in technology into building KARSA.

The founder journey has no shortage of uncertainty. There are engineering questions, manufacturing decisions, intellectual property, supply chains, fundraising, customer conversations, and days when progress seems painfully slow. Nobody is coming to organize every part of it for you. You have to create structure and keep moving, even when the finish line is not in sight.

Building a company is not one heroic act. It is thousands of ordinary decisions made consistently.

Make the call. Ask the question. Review the prototype. Follow up with the potential partner. Admit what you do not know. Then come back tomorrow and do it again.

I still have plenty to learn. Discipline does not mean having everything under control. It means creating enough consistency to keep making progress when life is not under control.

If you are looking at your life and feeling behind, do not confuse your starting point with your destination. You do not need to fix everything at once. Pick one promise you can keep today. Build a little structure around it. Repeat it tomorrow. Let those small commitments become evidence that you are capable of change.

I did not start with a perfect plan, perfect grades, or a clear path. I had to build the habits that helped me move forward. Those habits became part of the foundation for my career, and now they are part of the foundation for KARSA.

You are not defined by the grades you got, the job you started in, or the circumstances you came from.

You are shaped by what you choose to do next.

Discipline is how you begin turning that choice into a different future.

Prefer to listen? The audio version of this post is above.

One of the most powerful things I have learned throughout my career is that you are rarely starting from scratch.

You may feel like you are. You may be walking away from a job, starting a company, changing careers or recovering from a failure. You may be entering an industry you do not understand, or standing in front of an opportunity that feels bigger than you.

But you are not starting from scratch. You are standing on everything you have already built.

I think about my own career that way. In my early twenties, I was an independent contractor for Aflac, with no salary, no benefits and no safety net. I had become one of the top producers in the country, selling voluntary benefits to nurses and CNAs at nursing homes throughout New Jersey. Then one of my biggest accounts accidentally paid only half of an invoice, and Aflac cancelled every policy I had written through that account. I was hit with a massive chargeback. For nearly a year, I went back into those nursing homes, shift by shift, to rebuild trust and get people signed back up, while foreclosure notices arrived on my small condo. That year taught me resilience. It also taught me what it feels like to have something you worked for suddenly become uncertain.

IGX Global taught me how to learn a completely new industry. TippingPoint taught me how to sell. New York City taught me how to build relationships and create a territory from the ground up.

Difficult bosses taught me what kind of leader I did not want to become, and great mentors taught me what was possible. Failures taught me humility. Success taught me confidence.

Every experience became another brick. Eventually, those bricks became a foundation, and that foundation is what I am standing on today as I build KARSA.

That is why I have become less afraid of the unknown. I do not know exactly what the future holds. No founder does. There will be challenges and setbacks. There will be days when the product does not work the way we want it to, deals we lose and people who say no. There will be moments when I question whether the whole thing is going to work.

But I have been through uncertainty before. I have learned before, rebuilt before and taken risks before. And I have succeeded before.

So I do not need to start from scratch.

Neither do you.

If you are leaving a job that has drained you, you are not starting over. You are taking the experience with you. If you are changing careers, you are bringing transferable skills with you. If you are starting a company, you are not starting from zero. You are bringing every relationship, mistake, lesson and success you have accumulated along the way.

If you are simply trying to figure out what comes next, remember this: you already know more than you did yesterday. You have already survived things you once thought you could not survive. You have already built relationships, learned and grown.

Take a deep breath. Exhale. Look at what you have built. Then take the next step.

You are not starting from scratch. The foundation is already there.