Star four: Connection. Clients don't buy code.

Seven Years. Seven Stars. Chapter four of seven.

In our fourth year, we didn't stay in one lane.

We moved from one industry to the next and solved problems for very different customers. It worked because of how we work: every project starts with understanding the domain. That's in our DNA.

Four worlds in one year In a single stretch, our teams built for four very different worlds:

Demand management for a global pharmaceutical company, built as a Microsoft Teams bot so its people could raise and track demand where they already work. Contract lifecycle management for the same company: a separate application built on Salesforce. Enterprise risk, where a specialist firm taught us how organisations see risk before it arrives. Ethics reviews in clinical research, as the nano-GCC behind a global company's electronic IRB platform. An IRB, or institutional review board, is the committee that reviews research involving people, to protect the people taking part.

Four domains. Four vocabularies. And in each one, people who used the software every day, with their own idea of what "done" meant.

Domain first, every time A demand planner, a contract manager, a risk officer and an ethics reviewer don't just want different features. They see the same screen differently. What one calls a delay, another calls a risk. What looks like an extra step to an engineer is the step that protects someone.

We don't treat that as a hurdle. It's where every project starts. Before we design anything, we sit with the people who will use it, learn their words, and ask why each step exists.

That habit is what let one small team say yes to four different industries in a single year.

What the year taught us Clients don't buy code. They buy understanding. Every domain has its own language. Learn it before you build in it. Flexibility comes from method. When understanding the domain is always the first step, a new industry is a new conversation, not a new risk. The buyer and the user are rarely the same person. The person who signs the contract and the person who uses the software every day often need different things. Build for both.

The Pragmatiq Way, principle 4 Learn by teaching.

Last Thursday, Archana showed what it looks like inside our teams. That year, our clients were our teachers. Four domains taught us more than any course could have.

The star: Atri Atri is the star the West calls Megrez. It is the faintest of the seven, and it sits exactly where the bowl of the Big Dipper meets the handle. Without it, the two halves don't connect.

That was our fourth year: the quiet work of connecting technology to the world it serves.