I Built It to Last. Someone Else Bought It to Scale.
The story of building Nemra, selling it in nine months, and learning the difference between being a founder and being an operator.
The dinner table at the Ritz-Carlton in Riyadh has a certain weight to it. The kind of place where deals are made quietly, where the lighting is soft enough to hide whatever is happening on your face.
I remember looking at the papers in front of me and feeling two things at once - pride so sharp it almost hurt, and something else I didn't have a name for yet. In nine months, an idea I had sketched out had become a real product, with real clients, and someone was now willing to pay to own it entirely. That should feel like winning. And it did. Just not cleanly.
I signed. We shook hands. And somewhere in the middle of the congratulations, I realized I was already grieving something.
That was the exit of Nemra - my first company, sold via buyout to a mid-size accounting firm in Saudi Arabia. This is the story of how we built it, why we sold it, and what it cost me personally to understand the difference between being a founder and being an operator.
The Problem No One Was Talking About Loudly Enough
Every accounting firm - whether it's a boutique shop or an in-house finance team at a large corporation - has the same dirty secret: their data is a mess.
Client documents scattered across emails, shared drives, WhatsApp threads, printed invoices photographed with a phone. When tax season arrives or an audit looms, accountants spend the first week just finding things. Not analyzing them. Not flagging issues. Just hunting for documents that should have been organized months ago.
Nemra started as an answer to that problem. We built a data aggregation layer: a system that could pull financial documents from wherever they lived, extract the relevant data, and centralize it into a structured, searchable format. The goal was simple - make the data findable before the deadline, not during it.
But as we went deeper, we found the more interesting problem underneath. It wasn't just that data was scattered. It was that nobody was watching it. Errors, inconsistencies, anomalies - they only surfaced when an accountant manually reviewed everything. Which meant they often didn't surface at all until it was too late.
So Nemra evolved. What started as a data aggregation tool became a fiscal compliance layer - a system that not only collected and structured financial data, but actively monitored it. Flagging anomalies. Catching things before the accountant ever had to look. A silent co-worker that never got tired and never missed a line item.
That evolution wasn't planned on a whiteboard. It came from listening to users and following the problem wherever it went.
The Saudi Bet
I want to be honest about something: choosing Saudi Arabia as the primary market was a deliberate bet, not a default.
I arrived at LEAP 2025 - one of the largest tech events in the region - with a working product and a clear thesis: Saudi Arabia under Vision 2030 is a country investing heavily in its own infrastructure, including the infrastructure of compliance. ZATCA, the tax authority, had been on an aggressive digitization push. The fintech sandbox they ran was genuinely open to builders. Regulators were reachable. The market was moving.
At LEAP, I met the person who would become my co-founder on the commercial side. He understood the local landscape in ways I couldn't navigate alone - not because I was incapable, but because not having a Saudi co-founder would have cost us months of friction in sales cycles and trust-building. With him, doors opened faster. That is just the reality of operating in regional markets.
We also made a deliberate choice to stay close to the regulators. Not just tracking ZATCA updates from a distance, but engaging with the fintech sandbox directly. That proximity was a competitive advantage we didn't fully appreciate until later - it meant our compliance checks were always current, and clients trusted that.
The Saudi market rewarded focus. We didn't try to serve everyone. We went deep on one vertical: accounting firms and internal finance teams dealing with high-volume document processing. That decision - to go narrow and go deep - turned out to be the most important one we made.
How We Built It
The technical architecture of Nemra was designed around one principle: financial data is sensitive, and leakage is not an option.
We built a pipeline that moved from extraction to audit to secure storage, with each layer isolated. The OCR and LLM components handled document parsing - turning unstructured financial documents into structured, queryable data. The anomaly detection layer sat on top of that, running rule-based and model-assisted checks. And the storage layer was built with the assumption that what goes in stays in, with full audit trails.
We weren't building features. We were building infrastructure that happened to have a user interface.
By the time we reached what I'd call 80% completion - the core pipeline solid, the first clients onboarded, the anomaly engine running reliably - we had something that was defensible. Not just useful, but hard to replicate quickly. That distinction matters more than I understood at the time.
The Offer We Didn't Go Looking For
We weren't running a sale process. We weren't talking to investors about an exit. We were heads-down, finishing the product.
Then our first serious client - a mid-size accounting firm that had been using Nemra for several months - made an offer. They wanted to acquire the whole thing. Exclusive use, full ownership, the team's knowledge included.
My co-founder came to me with the news carefully. He had hesitated before telling me, because he knew how much Nemra meant to me - and because he genuinely believed the product could grow into something larger. He wasn't wrong. But he also couldn't continue. Personal reasons, the kind that aren't anybody's business to detail publicly. The kind that are real and legitimate and end conversations quickly.
I sat with the decision longer than I probably should have.
Here is what I kept coming back to: the tech was solid. The financial offer covered everything we had put in and gave us something meaningful on top. My co-founder needed to move on. And I - if I'm honest - missed home.
There is something clarifying about being in a foreign country, building something hard, watching another country invest in its own future at scale. Saudi Arabia under Vision 2030 is doing exactly that: deliberately, systematically building itself. And I remember thinking - I want to go do that at home. Algeria has the same raw material. It just needs people willing to stay and build.
The Ideacrafters invitation arrived around the same time. The timing felt less like coincidence and more like a signal.
I signed the papers at the Ritz-Carlton. I flew home.
From Founder to Operator: What Nobody Warns You About
The hardest part of becoming a Venture Lead at a startup studio wasn't the workload. It was learning to be what I now call an atheist when it comes to judging projects.
As a founder, you are allowed - even required - to be irrational about your own work. You believe in your product when the data doesn't support it. You push through when a rational person would stop. That irrationality is the fuel.
As an operator, that same quality will destroy your judgment.
At Ideacrafters, I work across multiple products and multiple founders simultaneously. My job is not to fall in love with ideas. It is to assess them clearly, quickly, and without the distortion of personal attachment. Founders sometimes think I'm brutal - killing ideas that haven't been validated, pushing back hard on assumptions, refusing to move forward without research. I'm not being cruel. I'm being honest in a way that their own attachment to the idea doesn't allow them to be yet.
The shift from one to the other - from the person who builds one thing with obsessive focus, to the person who evaluates many things with deliberate detachment - is not a skill upgrade. It's closer to an identity replacement.
I went from building one thing to building many, on purpose. Nemra taught me what a well-built product looks like from the inside. Ideacrafters is where I get to use that knowledge at scale, across different founders, different markets, different problems.
The studio model suited something I had learned but couldn't yet name while I was at Nemra: the real skill isn't building a product. It's building the conditions in which good products get built.
What I'd Tell a First-Time Founder
Build to be acquired, not just to grow.
Those two things sound like the same thing. They are not.
Building to grow means optimizing for scale - more users, more revenue, more features, bigger market. Building to be acquired means making deliberate choices early that make your company legible, defensible, and transferable to someone else.
What does that look like in practice?
It means going deep on one niche rather than spreading thin across several. An acquirer doesn't want a product that does many things adequately. They want one that does one thing better than anyone else.
It means building clean, documented systems - not because you plan to hand them over, but because a product that only works because you're running it isn't really a product. It's a job. And nobody buys a job.
It means staying close to your regulatory environment if you're in a compliance-adjacent space. The proximity itself becomes a moat. We had a relationship with Saudi regulators that an acquirer couldn't replicate in six months.
And it means knowing when the conditions for a good exit are present - not waiting for perfect, which doesn't exist - but recognizing when the offer, the timing, and the personal circumstances align in a way that won't repeat.
Nine months from idea to signed deal. I'm proud of that. Not because it was fast, but because when the moment came, we had something worth buying.
Where It Led
I'm writing this from Algiers, where I spend most of my time now as Venture Lead at Ideacrafters.
The studio works with founders across Algeria, Morocco, Tunisia, France, and the Gulf. Every week I'm either building a product directly or helping someone else build one. The Nemra experience lives in everything I do - in how I think about technical architecture, in how I approach market selection, in how I evaluate an idea's acquirability before I evaluate its ambition.
Exiting a company is a strange kind of education. You learn things you couldn't have learned any other way. Things about value, about timing, about the difference between what a product means to you personally and what it means to the market.
The Ritz-Carlton dinner was heavy because it was real. That weight was the point.