Pricing a New B2B Software Product in the UAE

A first software price has to survive three conversations. The user needs to see why the product is worth changing their routine. The buyer needs an offer they can approve. The startup needs enough revenue to deliver what it has promised. Work through all three before choosing a subscription price or publishing a tier.

Imagine a Dubai startup selling software that helps small facilities operators track maintenance jobs and prepare client reports. A supervisor uses it daily. An operations director cares about fewer missed jobs and less time assembling reports. Finance needs to know what the annual commitment covers and what it takes to pay the invoice. The price the team can defend depends on the scope of the work, which buyer feels the benefit and how much setup and support each account consumes.

Find the part of the workflow the buyer values

Ask the buyer to walk through a recent example and put numbers beside the work where the records support them. A supervisor might spend time reconciling lists and chasing photographs. The director might be concerned about sending late reports to a client. Keep those effects separate. An hour returned to an employee may create capacity, while fewer late reports might protect a commercial relationship. Use the customer's own operating evidence and check who actually values the change.

Suppose a buyer can document 12 hours a month spent assembling reports and reviewing omissions. If a trial shows that the product frees six hours at an internal planning rate of AED 100 per hour, the time value under those assumptions is AED 600 a month. That figure does not establish a cash saving. Ask whether the hours would avoid paid overtime, move staff to other work or simply give them more time to finish existing duties. If the buyer cares most about fewer corrections, measure that separately and avoid adding overlapping benefits.

Find out what the buyer would do if it did not buy. It may keep its spreadsheet, change the process, hire help or use a feature already available in another system. Understand the cost and limitations of that route before claiming your product is cheaper. A startup may win by addressing a problem the existing tool cannot handle. It can still lose if solving that problem requires a disruptive change for the people doing the work.

Choose a price unit customers can predict

A price unit should make sense to the buyer and reflect how the work grows. A per-user model is easy to explain when named users receive distinct value, but it can discourage the customer from inviting occasional staff. A per-site model can suit a maintenance workflow tied to locations. It can misprice an unusually large site if service effort follows work volume. A usage charge can reflect volume, provided the buyer can understand and verify what was counted.

Stripe's UAE Billing pricing page gives a public example of a supplier offering a volume-linked option and an annual subscription option billed monthly. It helps illustrate the difference between how a supplier measures use and how it sets a commitment. It provides no benchmark for the maintenance product. Apply the distinction to your own offer by stating the unit, the minimum term, the invoice interval and what happens if volume changes. Stripe UAE Billing pricing

Ask buyers to estimate their next bill from a sample. Use their normal situation and one that grows, such as adding two sites or handling a seasonal peak. If the estimate differs from yours, simplify the offer or make the terms clearer before taking payment. For metered billing, decide what happens when a work order is cancelled, reopened or duplicated. A price based on records that the buyer cannot reconcile will generate disputes even if the initial quote is attractive.

Package setup, support and changes explicitly

Write the offer as a service the team can deliver. State the number of sites or users, the relevant workflows, setup steps, expected customer inputs and support coverage. Separate a standard integration from a bespoke one. For the maintenance example, a standard site setup might include importing an agreed file and training a supervisor. A bespoke feed from the customer's existing software could require discovery and ongoing maintenance. If those items are bundled without limits, a reasonable customer may assume both are included.

A paid pilot can have its own defined scope and decision date. Make clear what the pilot delivers, how the customer accepts it and what it would cost to continue on standard terms. If part of the pilot fee would be credited to a later subscription, state the condition and period. A price that the buyer accepts for a short trial provides evidence about that trial. Watch what happens when the buyer has to approve the longer commitment.

Track exceptions as they are offered. A founder may waive setup, travel to the site or provide extra support to win an early buyer. Put those commitments in the commercial record and cost them. If an early account pays a lower price in exchange for a smaller scope or a defined obligation, make that relationship explicit. A discount with no stated end or reason can become the figure both sides expect at renewal.

Put the offer through the actual approval and payment path

Find out who holds the budget, who signs and what the buyer needs to open a supplier record. Ask whether the budget is set per site, across operations or centrally for technology. One buyer might approve a pilot from operating spend but require a separate review for a year of software. Another might require a purchase order before any work starts. Get those details before interpreting a delayed approval as a price objection.

Present a quote with the scope, total, payment dates, commitment and applicable tax treatment checked for the actual supply. The Federal Tax Authority publishes VAT registration information and tax invoice guidance. The Ministry of Finance separately describes UAE eInvoicing as structured data exchanged and reported electronically. A PDF sent by email does not meet that programme's definition of an eInvoice. Check the latest requirements and timing for the actual entity and transaction. A buyer's internal approval, the invoice format and receipt of payment are separate steps. FTA VAT registration · FTA tax invoice guidance · Ministry of Finance eInvoicing portal

A UAE Ministry of Finance Instagram post introduces business registration for eInvoicing. Use the example to prompt a concrete question for the buyer and the finance team about which invoicing process they expect. Keep the answer with the quote so a seller can identify whether an order is waiting on approval, supplier setup or an invoice correction.

Calculate contribution and cash at the same scope

Suppose the Dubai maintenance startup offers an illustrative AED 1,200 monthly subscription and a separate AED 1,500 setup fee. It estimates direct setup at AED 1,800 and monthly direct delivery costs at AED 420, including the assumed hosting and support for that account. The subscription leaves AED 780 per month after those stated direct costs. The setup fee falls AED 300 short of the specified setup cost. Over six paid months, the offer leaves AED 4,380 after those costs and before items such as sales, fixed overhead and tax. Change the assumptions if payment fees, support or infrastructure vary with actual use.

Cash timing changes what the founders have to fund. If the team spends AED 1,800 on setup before collecting the fee, it must carry that outlay even if the account later contributes as planned. Add the dates for setup, subscription billing and expected receipt to the cash view. Use the payment terms and acceptance conditions in the actual quote. A forecast with a profitable account and no cash to start the next installation needs a different decision from one with predictable collections.

Stress the part of the cost base that can move. If monthly support takes an extra AED 300 per account, monthly contribution under the example drops to AED 480. Across six paid months, after the same setup shortfall, it falls to AED 2,580. Investigate whether that support comes from a temporary learning curve, a product defect or a requirement every comparable customer will have. The answer affects whether to change the price, the scope or the product.

Test comparable offers and read the objections

Keep a record of each quote, including customer type, trigger, scope, price unit, direct cost estimate and decision date. Ask the buyer what happened at the next approval step. If a budget owner says the offer is expensive, find out which part is difficult to approve. It might be the total, the up-front charge, an unpredictable usage bill or a scope that includes work the team already pays for. Changing the price without diagnosing the objection can leave the real issue untouched.

Test one meaningful change at a time where possible. If the first few buyers need predictable spend, compare a fixed site package with the same scope and a clear allowance. If the blocker is the initial payment, test a different schedule and account for the extra cash the startup has to carry. If the buyer doubts the benefit, collect better evidence from a narrowly scoped pilot before offering a discount. Give comparable accounts time to make a decision and keep open quotes separate from declines.

Review what happens after the buyer says yes. A package that repeatedly sells but requires a new report template for every site has a delivery problem the quote may have hidden. Compare actual setup and support with the estimate, and ask which parts of the scope the customer used. At renewal, record whether they paid the standard price, reduced scope or needed a new concession. A series of comparable decisions gives the founders a firmer basis for setting the next price than a collection of verbal reactions.

Use the review to choose the next version of the offer. A clear first price is one a comparable buyer can understand, approve and pay, with a scope the startup can deliver repeatedly. In the Dubai example, the first good decision could be to standardise one site package, charge separately for custom integrations and track support through renewal. Put the price, limits and review date in writing, then see whether the next customers buy and use the same thing.