A default, opinionated set of tools we install on day one — and why each one earns its place.
Most growth problems we see in Dubai, Kuwait and Beirut aren't strategy problems. They're plumbing problems. Leads land in a WhatsApp thread, a spreadsheet, and someone's inbox, and nobody can tell you where last month's revenue actually came from. So before we touch campaigns, we build the engine. Here's the stack we reach for, and the thinking behind it.
This is a starting point, not gospel. The principles below matter more than any logo. But if you asked us to set up a brand from zero tomorrow, this is roughly what we'd put in.
The principles before the tools
Pick the tools later. Get these right first, or you'll rebuild in a year.
- Own your data. Your customer list, your pipeline history, your analytics. If a vendor disappears tomorrow, you should still have the asset. Tools that lock your data in and won't export it are a liability, not a stack.
- Integrate, don't silo. Every tool should talk to at least one other tool. A CRM that doesn't know what your ads did, or analytics that can't see your pipeline, just creates more places to look and more numbers that disagree.
- Keep it light enough to actually use. A perfect system nobody updates is worth less than a simple one the team lives in. We'd rather have five clean fields everyone fills in than fifty that rot.
- Pick tools you can hand over. We build the engine, then teach your team to run it, then step back. That only works if the stack is learnable by a normal operator, not just a specialist. If a tool needs a consultant on retainer forever, it fails this test.
Hold those four up against anything below and you'll understand every choice we make.
CRM and pipeline: the source of truth
This is the spine. Everything else plugs into it. We default to HubSpot because it covers marketing, sales and basic service in one place, the free and starter tiers let a small team start without a big commitment, and the learning curve is gentle enough that non-technical staff actually adopt it.
What this layer does:
- Holds every contact and company in one record, so nobody's working off a private spreadsheet.
- Tracks deals through named stages — so "how's the pipeline" has an answer, not a guess.
- Captures the source of each lead — ad, referral, event, inbound — which is the question founders ask most and can rarely answer.
- Triggers follow-up so leads don't die in someone's inbox over a long weekend.
The point isn't HubSpot specifically. Pipedrive, Zoho or others can do the job. The point is that one system, not three, owns the truth about who your customers are and where each deal stands. If you're already deep in another CRM, we'll usually build around it rather than force a migration.
Data and enrichment: knowing who you're talking to
A CRM tells you who's in your pipeline. It doesn't tell you much about them. That gap is where outbound and account targeting fall apart, and it's especially real in the Gulf, where company data is messier and more fragmented than in many Western markets.
We use Clay as the enrichment layer. In plain terms, Clay takes a thin list — a few company names, some emails, a scrape from an event — and fills in the rest: company size, industry, role, and other signals pulled from multiple data sources in one workflow. It connects to your CRM so enriched records flow back in rather than sitting in yet another spreadsheet.
Why it matters for an operator:
- Better targeting. You stop spraying the same message at everyone and start segmenting by who's actually a fit.
- Less manual research. The hours your team spends Googling prospects get automated down to a workflow.
- Cleaner data going in. Enrichment at the point of entry beats cleaning a rotten list later.
A caution we always give: enrichment makes outbound faster, which makes bad outbound faster too. The tool is a multiplier, not a strategy. Get your targeting and message right on a small list before you scale it.
Knowledge, docs and SOPs: the part everyone skips
Here's the layer that decides whether the transfer actually sticks. A growth engine your team can't explain isn't yours — it's ours, parked in your account. So we document it.
We default to Notion as the home for how the system runs:
- SOPs — the step-by-step for the recurring work. How a lead gets qualified. How a campaign goes live. What "done" looks like.
- The stack map — what each tool does, how they connect, and who owns what. So onboarding a new hire takes a day, not a quarter.
- Campaign briefs and a content calendar — one place where the plan lives, instead of scattered docs and chat threads.
- Decisions and playbooks — the reasoning behind choices, so the team doesn't relitigate the same questions every month.
This is the least glamorous layer and the one with the highest payoff. Tools change; the documented thinking is what survives a staff change, an agency change, or us walking away. If you take one habit from this whole post, make it this one.
Automation and glue: connecting the pieces
By now you have a CRM, an enrichment layer and a knowledge base. The risk is that they stay islands and your team becomes the integration — copying data between tabs by hand. That's where the glue comes in.
We use Make (and sometimes Zapier for simpler jobs) to wire tools together. These let you build "when this happens, do that" workflows without writing code.
Typical glue we set up:
- New lead from a form or ad lands directly in the CRM, tagged with its source.
- Enriched data from Clay syncs back to the right contact record.
- A closed deal triggers an internal notification and updates the relevant dashboard.
- A form submission routes to the right owner instead of a shared inbox nobody checks.
Two rules we follow here. First, automate the boring and repetitive, not the judgment calls — a human should still decide who to pursue. Second, document every automation in Notion, because an undocumented workflow that breaks at 2am is worse than no automation at all. Keep it light; a tangle of fragile scenarios is its own kind of debt.
Analytics and tracking: knowing what worked
Last layer, and the one that closes the loop. Without it, you're spending on growth blind.
We set up GA4 for website and conversion tracking, connected back to the CRM so you can trace a path from first click to closed deal — not just traffic, but traffic that became revenue. Where useful, we add a lightweight dashboard (Looker Studio, or a simple view inside the tools themselves) so the numbers that matter are visible without anyone running a report.
What good looks like at this layer:
- One set of numbers the whole team trusts, not three dashboards that disagree.
- Source-to-revenue visibility — which channels bring leads that actually close, not just leads that look busy.
- Few metrics, watched often beats many metrics, watched never.
A regional note: with privacy changes and inconsistent tracking across GCC markets, treat your own first-party data — your CRM, your customer list — as the more reliable source over time. Platform analytics tell you a lot. They shouldn't be the only thing you believe.
The closing take
None of these tools is magic, and the brands don't matter as much as the jobs they do: a source of truth, clean data, documented knowledge, connections between the pieces, and an honest view of what worked. Build those five layers, keep them light, and make sure your team can run them without you.
That last part is the whole game. A stack you can't operate is just a more expensive way to be confused. Build the engine, learn to drive it, and own it.