20 Years, 20 Peaks: How Amexis Grew by Climbing Higher Together

Mar 9
5 min read

Twenty years ago, a small group of engineers started building software. This year, they're climbing 20 mountains.

On March 28, 2026, Amexis Ltd turns twenty. No confetti cannons. No keynote speech. Instead, our team of 20+ engineers will spend the year doing something that feels more like us: lacing up hiking boots, shouldering packs, and summiting 20 mountain peaks together. One for every year we've been in business.

We're calling it #20Peaks20Years. But before we talk about where we're going, let's talk about where we've been.

How It Started

The founding story isn't dramatic. No garage. No eureka moment. Just a handful of experienced engineers who believed they could build software the right way — with senior talent, honest timelines, and a refusal to cut corners. They started Amexis in 2006 with a simple conviction: if you assemble people who genuinely care about their craft, good work follows.

That conviction hasn't changed. Almost everything else has.

Twenty Years in Milestones

Every company has a timeline. Here's ours — not a complete history, but the moments that shaped who we became.

2006–2008: The First Project in Healthcare Industry Early on, we landed a project in healthcare — the kind of work where bugs aren't just inconvenient, they're unacceptable. It set the tone for everything that followed. We learned that the standards we held ourselves to weren't just nice to have. In healthcare, they were non-negotiable. That seriousness became part of our DNA.

2009–2011: Growing Without Diluting The temptation in those years was to hire fast and grow headcount. We didn't. We grew carefully, adding senior engineers who raised the bar rather than people who needed to be carried over it. It was slower. It was also the best decision we ever made.

2012–2014: International Expansion Our work started crossing borders. International clients brought new complexity — different time zones, different expectations, different regulatory landscapes. We adapted, but we didn't bend on what mattered. The code still had to be excellent. The communication still had to be clear. The commitment still had to be real.

2015–2019: The Different Industries Vertical Healthcare taught us to build systems where reliability is everything. The diversity proved we could take that discipline somewhere entirely new. Logistics platforms, fleet systems, real-time data at scale — it stretched us technically and proved that our approach wasn't industry-specific. It was just how good engineering works.

2020–2021: COVID and the Resilience Test The pandemic didn't spare anyone, but it did reveal something about our culture. Because we'd always operated on trust — no micromanagement, no surveillance tools, no mandatory camera-on policies — the shift to remote work wasn't a crisis. It was Tuesday. Our projects didn't skip a beat. Our team didn't fracture. If anything, it proved that the culture we'd been building for 15 years was real, not performative.

2022–2024: Embracing AI (Without the Hype) When the AI wave hit, we didn't pivot our homepage or rebrand as an "AI-first" company. We did what engineers do: we studied it, experimented with it, and started integrating it where it genuinely made our work better. AI-augmented development became part of our toolkit — not a marketing bullet point, but a practical evolution.

2025–2026: 20+ Engineers and Counting Today, Amexis is a team of more than 20 engineers working across healthcare, transportation, and enterprise software. We're bigger than we've ever been, but the principles are the same ones we started with. Senior talent. Honest work. No shortcuts.

The 20 Peaks Initiative

So why mountains?

Because building software for twenty years is a lot like climbing. The summit matters, but what actually gets you there is preparation, teamwork, persistence, and the willingness to turn back when conditions demand it. You don't rush a mountain. You respect it.

#20Peaks20Years is our way of celebrating this anniversary as a team — not at a conference table, but on a trail. Throughout 2026, we'll be climbing 20 peaks together. The exact dates depend on weather and conditions (mountains don't care about your project plan), but the commitment is real.

Each peak represents a year of Amexis. Each climb is a chance for our engineers to do something together that has nothing to do with code — and everything to do with the culture that makes the code possible.

We'll be sharing the journey as we go. The early mornings. The false summits. The views that make it worth it. Follow along at #20Peaks20Years and #ClimbingHigherTogether.

What 20 Years Taught Us

Two decades is long enough to learn some things the hard way. Here are seven lessons we'd pass along to anyone building a company — or a team — that's meant to last.

1. Talent Retention Is Not a Perk Problem

You don't keep great engineers with ping-pong tables and free snacks. You keep them by giving them meaningful work, respecting their expertise, and getting out of their way. Our longest-tenured people didn't stay because of benefits. They stayed because they're trusted to do their best work.

2. Saying No Is a Skill

Not every project is the right project. Not every client is the right fit. Learning to say no — to work that would compromise our standards, to timelines that were fantasies, to engagements that would burn out our people — was one of the hardest and most important things we learned.

3. Principles Over Tech Trends

Technologies come and go. JavaScript frameworks have a half-life of about 18 months. But the principles — clean architecture, tested code, clear communication, engineering rigor — those don't expire. We've always invested in fundamentals over fashions.

4. Trust-Based Culture Can't Be Faked

You can't announce trust in a memo. You build it by actually trusting people. That means no tracking software. No mandatory overtime. No second-guessing senior engineers who've earned the right to make decisions. It takes years to build and seconds to destroy. We've protected it fiercely.

5. Quality Over Speed (Every Time)

The pressure to ship fast is constant. We've never pretended it doesn't exist. But we've also never let it win. Rushing a release to hit an arbitrary deadline and then spending months fixing the fallout isn't fast — it's just expensive. We'd rather be right than first.

6. The Team Is the Product

Our clients don't hire us for a proprietary framework or a secret algorithm. They hire us for the people. The team — their experience, their judgment, their ability to solve hard problems — is the product. Everything else is a delivery mechanism.

7. Climb Together

The best work we've done has never been one person's achievement. It's always been a team effort — people covering for each other, challenging each other, and pushing through hard stretches together. That's true on a codebase. It turns out it's true on a mountain, too.

Looking Ahead

We're not going to pretend we have a five-year plan etched in stone. Twenty years has taught us that the landscape changes too fast for that. But we know where we're headed.

AI-augmented development will continue to reshape how we work — not replacing engineers, but amplifying what they can do. We're investing in understanding these tools deeply, not just adopting them superficially.

Deeper verticals in variety of industries and enterprise mean more specialized expertise, more domain knowledge, and more value for the clients who trust us with their hardest problems.

And above all, investing in people. More senior engineers. More trust. More mountains to climb together. The next twenty years will be built the same way the first twenty were: one good decision at a time, by people who care about getting it right.