Every company asks people to work hard just to exist. The odds explain some of that urgency. U.S. Bureau of Labor Statistics data show that only about half of start-ups survive their first five years.
Deadlines tighten. Customers need answers. Products break in ways nobody predicted. A promising idea becomes a long list of details that still have to be carried by someone. Even good growth creates new responsibility faster than it creates certainty.
The effort is real whether a company has named its purpose or not. Survival explains the pressure. It does not create a North Star.
The question is what the effort is for.
Revenue matters. A company that cannot sustain itself cannot keep its promises to customers or employees. Growth can create opportunity, fund better work, and give a team room to think beyond the next emergency. But numbers alone rarely explain why people should bring care, imagination, and years of their lives to the work.
A company needs a reason to work hard that can survive a difficult Tuesday. It needs a North Star.
The company grew around a project
Enhancesoft did not begin with a polished company plan. It grew around the work required to support osTicket and the people who depended on it.
Hurricane Katrina had pushed me out of New Orleans, out of my job, and eventually into consulting and entrepreneurship in Alexandria. For a time, I was working from a trailer home while trying to understand whether an open-source project could become the foundation of a durable company.
The early years were practical. Solve the problem in front of us. Answer the customer. Keep the product working. Find people who cared about the details. Earn enough trust to continue.
Money mattered because the company had to survive, but it was never my North Star. At some point, it stopped being a meaningful reason to keep going. That is part of why Enhancesoft has remained bootstrapped and why I have not taken venture capital. Outside investment is not inherently wrong. I have simply valued the freedom to let usefulness, the team, and a long horizon determine the pace of the work.
Over time, the question changed. We were no longer asking only whether we could build software. We were asking what kind of organization should exist behind it.
Software can begin with one person. A company cannot mature that way.
The team is part of the product
The visible product is the software. The deeper product is the organization’s ability to keep learning, make sound decisions, and care for the work after the original excitement has passed.
That ability lives in people.
The Enhancesoft team came together piece by piece. Some people carried years of experience with osTicket and its community. Others arrived with fresh questions, new technical instincts, and no obligation to defend the way things had always been done. The work became stronger when accumulated knowledge and new perspective could challenge one another without either being treated as a threat.
Growing the company across Alexandria, Louisiana and Eldoret, Kenya made that principle more important.
Enhancesoft is a flat organization. Alexandria may be where the company began, but it is not a command center with Eldoret as an outpost. We have no outposts. Each city contains people with judgment, context, and ambition. Knowledge should travel in both directions. Important decisions should be made by the people closest to the work, not reserved for the geography where the company began.
A distributed team becomes real when responsibility is distributed with it.
That asks more of everyone. Trust cannot mean abandonment. Leadership cannot mean collecting every hard decision back at the founder’s desk. People need consequential work, room to develop judgment, honest feedback, and the confidence that their growth matters to the future of the company.
Purpose has to reach ordinary work
Purpose is easy to write at a distance from operations. It is harder to recognize in a product review, a hiring decision, or the way a team responds when a customer is frustrated.
I founded Enhancesoft around a practical belief: useful products begin with real problems and improve when the people behind them keep listening.
If that belief is real, it should change ordinary decisions:
- We listen before deciding what a customer ought to need.
- We value reliability after the excitement of building has passed.
- We create room for people to learn by trusting them with meaningful work.
- We build teams capable of carrying decisions beyond the founder.
- We measure progress by usefulness, not activity alone.
Purpose becomes credible when it costs the organization a convenient choice.
A statement that never changes a decision is decoration. A useful purpose narrows some options and strengthens others.
Work should leave capacity behind
I have also come to believe that a company’s work should create more than the product it sells.
The Rotich Foundation is funded by me and supported by Enhancesoft. It bears my name, but the reason behind it belongs to a wider team. At Enhancesoft, we see the Foundation as part of why the company should become more capable. The harder we work and the better we build, the more capacity we have to invest in education, health and wellness, mentorship, and technology in our communities.
This is not a charitable message attached to the side of the company. It is a relationship between effort and responsibility.
The company creates products, jobs, knowledge, and resources. The Foundation turns part of that capacity toward communities and young people whose opportunities should not be limited by where they began.
The relationship also keeps us honest. Community impact cannot excuse a weak product or a poorly run company. The product must serve customers. The company must treat people well. The Foundation must listen to communities and do disciplined work of its own.
Purpose raises the standard. It does not lower it.
A reason larger than a quarter
Some seasons in a company are exciting. Others are maintenance, correction, rebuilding, and patience. A team cannot live on launch energy forever. It needs a reason to care when progress is slower and the work is less visible.
For me, that reason has become clearer.
We are building useful products that help other teams serve people well. We are growing talent in places often overlooked by the usual geography of technology. We are building an organization whose knowledge and judgment can outlast its founder. We are using part of what that organization creates to widen opportunity for others.
These ideas do not remove the difficulty of the work. They make the difficulty worth meeting with care.
A company should know what success allows it to do next. Otherwise growth becomes a larger version of the same question.
The reason to work hard is not to prove how hard we can work.
It is to build enough capacity, trust, and usefulness that the effort continues to matter beyond us.