Technology Business Valuation in Dubai

By classifying revenue into contracted recurring, repeatable and one-off components, rebuilding retention from customer-level data, decomposing gross margin by revenue line, and normalising for accounting positions such as capitalised development. Methodology is then applied to that base — typically forward-looking approaches supported by market evidence where comparable data exists.

There is no reliable universal figure. The answer depends on revenue composition, retention, gross margin, growth rate and concentration. A business with contracted recurring revenue and strong net retention is treated very differently from one with the same turnover from project work. Any multiple quoted before examining that composition is a number rather than a valuation.

The components are separated and assessed on their own economics. Software revenue with high gross margin that scales without proportionate headcount is treated differently from implementation and support revenue carrying staff cost against every dirham. Blended gross margin conceals the difference, so it is decomposed by revenue line before any conclusion is reached.

It measures revenue retained from existing customers including expansion, upgrades and additional usage. It matters because it shows whether the customer base grows on its own without new acquisition. Where expansion offsets churn, growth is far less dependent on marketing spend — which materially changes the risk attaching to a forecast.

It is examined rather than accepted. Where development costs sit on the balance sheet rather than reducing profit, reported earnings can be materially flattered without any change in the cash the business consumes. The analysis considers how much is capitalised, whether the basis is consistent, amortisation periods, and what earnings look like with development expensed in full.

No. Subscriptions billed annually in advance produce cash before the service is delivered, creating an obligation that unwinds across the term. It is a liability a buyer inherits, not surplus available to them, and is separated from cash in the transaction bridge. Companies billing annually upfront often appear more liquid than their underlying position supports.

Often less completely than assumed. Code written by contractors, offshore developers or founders before the company was incorporated may not have been properly assigned, and open-source components carry licence obligations affecting commercial use. A buyer's legal and technical diligence will establish this, and an unresolved position found late can stall a transaction. Assignment and licensing are matters for qualified legal advisors.

Significantly, where the core system is understood by one or two people and documentation is thin. A buyer is then acquiring a dependency rather than a self-sustaining asset, and typically responds with retention arrangements, deferred consideration or a lower price. Broadening system knowledge and improving documentation are among the most improvable factors before a sale.

Because reselling third-party software, hardware or infrastructure at gross can substantially overstate economic scale. Where the company acts as agent rather than principal, only the margin is genuinely its revenue. Applying a multiple to gross figures in such cases produces a value the underlying economics do not support, which diligence quickly exposes.

As concentration risk, reflected explicitly rather than absorbed into a multiple. The extent depends on contract terms and duration, renewal history, how embedded the product is in the client's operations, switching costs, and how readily lost revenue could be replaced. Where clients are government-related, strong credit quality coexists with tender and renewal risk.

On fee income rather than gross billings, with media pass-through separated. Retainer revenue is distinguished from project work, client concentration assessed, and the key question examined: whether relationships attach to the agency or to specific individuals. Agencies with institutional relationships and retained clients transfer considerably more readily.

On net revenue — the take rate — rather than gross merchandise value, which is not revenue. Analysis covers transaction volume and frequency, both sides of the network, retention on each side, take rate sustainability, and dependency on any single supply or demand partner.

Only if prepared for that purpose. Tax provisions generally require market value between unconnected parties at a prescribed date with supporting documentation — particularly relevant where intellectual property is transferred between group entities or licensed intra-group, which attracts transfer pricing considerations. Current requirements should be confirmed against Federal Tax Authority guidance.

Typically: converting repeatable revenue into contracted revenue, improving retention and reducing churn, separating and documenting software margin from services margin, resolving IP assignment gaps, broadening system knowledge beyond key engineers, and producing customer-level data a buyer can verify. Most take a year or more to demonstrate.

Fees reflect the purpose, the complexity of the revenue model, the number of entities, the quality of customer-level data, and whether specialist technical or IP input is required. Businesses with clean cohort and contract data proceed faster than those where retention must be reconstructed. KGRN provides a fee proposal after an initial discussion.