Trust as an Operating System: A Kuwait Startup's Approach

How a Kuwait Startup Replaced Surveillance with Structure

Three months into building Dallal, I noticed one of our team members drifting. In no way would a timesheet catch. He showed up. He sat at his desk. But the questions he was asking were about the edges of the job, not the centre of it. He was present without being invested.

In most companies, this goes unnoticed for months. The employee badges in on time, files the right forms, and the system confirms everything is fine. The system is measuring attendance. Nobody is measuring engagement.

We don’t have that system. Dallal has no fingerprint machines. No time tracking. No HR department. No sick leave forms. Twenty-nine people, thirteen in Kuwait and sixteen developers working remotely, and not a single mechanism designed to monitor whether someone is at their desk.

So when this team member started drifting, there was nothing to hide behind. No green light on a dashboard saying he’d clocked in at 8:57. Just the work, and what was visibly not happening.

I sat with him. Not in a meeting room with a written warning. Just a conversation. I told him what I saw. I told him he had a choice: commit to growing with us, or find somewhere that fits him better. No threat, no HR process, no performance improvement plan. Just honesty.

He stayed. And the change was immediate.

That conversation could not have happened in a system built on compliance. It happened because we built something different.

The Decision

When I started hiring for Dallal, I knew what I didn’t want. I’d spent twenty years seeing organisations where the infrastructure of control was treated as the infrastructure of management. Fingerprint scanners at the entrance. Security cameras as productivity tools. Annual leave systems that require three approvals. Sick leave policies that assumed you were lying.

These systems don’t create accountability. They create performance. People learn to look busy. They learn the minimum threshold. They learn to game the metric because the metric is present, and presence is easy to fake.

I wanted to build Dallal on a different foundation. Not because I’m idealistic about it. Because I think it’s faster.

Here is what we did instead:

No fingerprint machines. No time tracking. No formal HR function. Work from home is allowed. Sick leave is not policed. There is no annual leave bureaucracy. If you need a day, you say so.

In place of all that, we built a structure. Clear project management through Asana. Every team member has defined responsibilities, documented and visible. An operations manual that the team writes collectively, updated as we go. Productivity is measured by output, not hours. And I keep an open door, available to anyone, any time.

The trade is simple: I will not watch you. But I will see your work. And if the work isn’t there, we’ll both know.

What I Hired For

The system only works if you hire for it. A trust-based operating system with the wrong people is not enlightened management. It’s chaos.

I was looking for specific traits from the beginning. Not credentials or years of experience. I wanted people who are easy to talk to. Listeners. People with creative instincts who can act on their own without waiting for permission. People who take ownership naturally, not because a KPI tells them to.

These are hard calls. I turned down candidates who were technically strong but wouldn’t thrive without supervision. I hired people who might need development but had the disposition to grow inside an open system. You are not just hiring for skill. You are hiring for a way of operating.

Then I made a second decision that most founders in this market would not make: I told the team their professional identities matter. I encouraged everyone to associate themselves with Dallal on LinkedIn. I encouraged participation on social media. I wanted them visible, not hidden behind a company account.

This makes some founders nervous. Visible employees can be poached. My view is the opposite. If someone stays only because they’re invisible to the market, they’re not staying because of you. They’re staying because they have no options. That is not loyalty. That is captivity.

Three Months In

I am writing this ninety days after we started operating. That is not a long time. I am not going to claim we have proven a model. But I can tell you what I see.

Development is moving faster than the timeline projected. The remote team of sixteen developers, spread across different time zones, is delivering consistently without daily standups or surveillance software. They have clear ownership. They ship.

Research is progressing. Our market intelligence work, which requires initiative and curiosity that no checklist can manufacture, is producing material I did not have to request. People are finding things because they’re looking, not because they were told to look.

Operations are being documented in real time. The manual is growing because the team is writing it, not because I mandated a deadline. It lives on Asana, open to everyone, and people add to it when they discover something that needs to be recorded. The manual is a living reflection of how we actually work, not a compliance document that sits in a drawer.

Marketing is ticking. Our designer is building the brand identity with a level of ownership I did not have to assign. The sales team is already meeting people, building relationships, laying groundwork.

And people come to work smiling. I know that sounds soft. It is not. A team that wants to be there moves faster than a team that has to be there. That gap compounds over time.

None of this happened because we gave people freedom. It happened because we gave people freedom inside structure. That distinction matters, and it is the one most critics of trust-based management miss.

The Thing About Control

Kuwait’s business culture, like much of the GCC, tends to default to control. This is not a criticism. It is a description. Most companies in this market install attendance systems early because they equate structure with surveillance. The assumption is that without monitoring, people will slack. That discipline requires a mechanism.

I understand the instinct. When you are spending seed money, every hour feels expensive. The impulse is to tighten, to track, to make sure you are getting what you paid for.

But control has a cost that rarely appears on the P&L; it tells your team you do not trust them. And people who feel untrusted behave accordingly. They do exactly what is required, nothing more. They wait for instructions instead of taking initiative. They optimise for visibility rather than impact. They protect themselves rather than solve problems.

I saw this repeatedly during my years. I worked with companies that had installed tracking software on every manager’s laptop and required a photographic check-in at the start of each shift. Turnover was brutal. The best people left first, because they had options and refused to be treated like suspects. The ones who stayed learned to comply: photos taken, reports filed, and boxes ticked, while the guest experience quietly deteriorated. The system was measuring everything except what mattered.

When every action is tracked, the safest action is the minimum. Innovation requires risk. Risk requires trust. You cannot surveil your way to creativity.

Kindness as Infrastructure

There is a phrase I keep coming back to: kindness as infrastructure. Most companies treat kindness as a personality trait. You hire nice people and hope for the best. That is backwards.

Kindness is what happens when a system gives people the room and the authority to be human. When there is no HR department standing between a founder and a struggling team member, the conversation happens directly. When there is no sick leave form requiring a doctor’s note, people feel trusted enough to say they need a day without performing illness. When responsibilities are clear, and ownership is real, people help each other because the work is shared, not because a values poster tells them to.

The infrastructure comes first. The kindness follows.

At Dallal, we did not run workshops on company culture. We did not write a values statement and pin it to the wall. We built systems that made trust the default, and trust made kindness inevitable. When someone needs time off, nobody fills out a form. They say so. When a developer has an idea that falls outside their brief, they raise it because the system does not punish initiative.

That is not softness. It is designed.

The Bet

Dallal is a bet on a few things at once. It is a bet on Kuwait’s real estate market needing transparency and trust. It is a bet that verified listings and honest information can beat the chaos that buyers and renters currently navigate. But underneath all of that, it is a bet on a way of working.

Twenty-nine people. No fingerprint machines. No HR. No time tracking. Clear ownership, shared documentation, and a founder who would rather have a difficult conversation today than a disciplinary process next quarter.

In a system with no attendance tracking, there is nowhere to hide. You cannot badge in at nine and coast. The work either happens or it does not, and everyone can see which it is. Accountability is not reduced by the absence of surveillance. It is sharpened by it.

Ninety days is not proof. But ninety days of a team that delivers, documents, creates, and shows up because they choose to is enough to tell me the operating system is holding.

I will report back.

Ali Bahbahani is the Founder and Managing Partner of Ali Bahbahani & Partners, a strategic advisory firm specializing in customer experience, hospitality consulting, and brand strategy across the GCC.

‍

‍