Useful answers.
Before the call.

The lower band is a focused business website: a defined set of pages, a CMS and analytics. The higher band covers content architecture, integrations into systems you already run, and editorial workflows. Page count, content volume and the number of integrations are what move a project between them.

A focused business website is typically four to six weeks from approved scope. Corporate builds, storefronts and portals run longer, and the pace is usually set by content and review cycles on your side rather than by engineering.

Yes. On final payment the source code, design files and any accounts created for the project transfer to you. Nothing is withheld to keep you on a retainer.

Often. We audit what is already there first and say plainly whether extending it costs less than replacing it. A rebuild is the right answer less often than agencies suggest.

You get a handover pack, a warranty window for defects in what we built, and an optional support arrangement. Hosting, licences and third-party subscriptions are billed separately or held in your own accounts.

Structure and guidance from us, words from you by default, because you know your business better than we will. Copywriting can be quoted in if you would rather not, and for most sites it is money well spent.

Yes. Every build ships with a CMS and a handover session. If you cannot change your own opening hours without calling an agency, the build has failed.

Held in your own accounts wherever possible so you are never locked to us. We recommend and configure it; the bill goes to you at cost rather than through us with a margin on top.

No. Provider consumption and licence fees are always separate, and wherever possible they are billed to your own account so the running cost stays visible to you rather than marked up through us.

We plan a controlled cutover, usually outside business hours, and every migration carries a documented rollback path agreed before the first workload moves. Any unavoidable window is named in the plan, not discovered on the day.

A workload inventory, a dependency and risk map, a cost direction, and a sequenced migration roadmap. It is a document you can act on with or without us, which is the point of buying it separately.

Yes. Email and file storage first is a common and sensible starting point. Applications and infrastructure are scoped separately once dependency analysis shows what they actually rely on.

Either your team, working from the handover documentation, or us under a managed arrangement. Both options are priced before the migration starts so the decision is not made under pressure at the end.

No. We assess against the workload. Most UAE small and mid-size businesses land on Microsoft 365 because of licensing they already hold, but that is a finding, not the starting assumption.

They keep running in parallel until the migration is verified, then are decommissioned to a plan you approve. Data retention obligations are agreed before anything is wiped.

Yes, and it is often the quickest win available. Right-sizing, reserved capacity and removing orphaned resources typically recover more in the first year than the review costs.

Often just automation. We map the inputs, approvals and exceptions first, and if a rules-based workflow is cheaper and more predictable we will say so. A model is a cost and a dependency, not a default.

Process mapping, the built automation, testing, the controls and approvals around it, and handover to your team. Model usage, messaging fees, licences, data preparation and complex governance are separate.

Only where you decide it should. Human approval stays in the path by default, and every workflow has a defined fallback for the cases it cannot complete rather than failing quietly.

Into the systems you already run wherever the workflow allows it. Where a third-party model is involved we tell you which one, what it receives and what is retained, before anything is built.

Workflows are built to be edited, and documented so someone other than the original author can edit them. The optimisation retainer covers tuning and new workflows; one-off changes are quoted against the existing build.

Not by us, and we select providers and settings where it is not used for training by them either. Which provider, what it receives and what it retains is written down before anything is built.

Every workflow has a defined exception path and a human review point. Failures raise an alert and stop rather than passing quietly down the line, which is the failure mode that actually costs money.

Your team using the documentation, or us on the optimisation retainer. We do not build automations that only their author can read.

A person, not a device. The plans cover up to ten and up to twenty-five users respectively. Servers, shared machines and unattended systems are counted separately because they carry different work.

Response priorities are written into your proposal against issue severity rather than promised as a single generic number. Priority response is part of the Business plan; the Small team plan is next-business-day for non-critical issues.

Remote help desk is included in every plan. Onsite visits are bundled into some agreements and charged per visit in others. Abu Dhabi is the standard service area; travel beyond it is quoted.

Usually not. An annual maintenance contract suits environments that need scheduled preventive visits rather than continuous coverage — a server room checked quarterly, say. We will tell you which one fits rather than selling both.

Yes, and it is a common arrangement. We take monitoring, patching and escalation while your own person keeps the business knowledge and the internal relationships. The split is written down so nothing falls between us.

Business hours across the UAE working week by default, with extended and out-of-hours cover priced separately. The exact window is written into your proposal rather than assumed.

Email, phone or WhatsApp, all landing in the same queue so nothing depends on catching one particular person. Severity sets the priority, not who asks most loudly.

You get your documentation, credentials and asset register, and we help hand over to whoever comes next. No exit fee, and nothing held back to make leaving harder.

A managed plan is continuous coverage billed monthly. A maintenance contract is scheduled preventive work billed yearly, with an agreed number of call-outs. If your environment is stable and mostly needs looking after rather than watching, the contract is the cheaper and more honest fit.

Rarely worth it. The two overlap, and we will tell you which one covers what you actually need instead of selling both. The exception is a monthly plan for users plus a server contract for infrastructure nobody touches day to day.

Each contract carries a defined number of call-outs with a stated response time. Beyond that allowance, attendance is charged at the on-demand rate, and you are told when you are approaching the limit rather than after you pass it.

Yes. The server contract includes a documented restore test, because a backup you have never restored from is a scheduled task rather than a backup. The report tells you what was restored and how long it took.

Replacement parts, new hardware, licence and subscription renewals, cabling works, and project work such as migrations or new deployments. Those are quoted separately so the contract fee stays predictable.

Set with you and written in. Commonly quarterly for IT and network contracts and more frequently for servers. Visits are scheduled ahead so they do not land in the middle of your busiest week.

Yes. Additional sites are priced per site because travel and time are real costs, and you see that as its own line rather than having it averaged into a single number.

Usually yes, after an initial survey. Kit already at end of life or no longer supported by its vendor may be excluded, and we tell you which items those are before you sign.

No. The retainer covers strategy, execution, content and reporting. Media spend, creator fees, premium tooling and third-party placements are separate and passed through at cost.

Paid channels produce usable data within weeks. Search and content compound over months. We report against qualified enquiries rather than impressions, which makes the early months look slower and the honest picture clearer.

Three months. Anything shorter cannot generate enough data to make a defensible decision about what is working, so it wastes your budget and our time equally.

You do. Accounts are created in your name and we work inside them. If the engagement ends you keep the history, the audiences and the learning.

Whatever you define it as, agreed before the first campaign runs. Without that definition reporting measures our activity instead of your pipeline, which suits agencies and nobody else.

Yes, and splitting channels is common. We agree who owns what in writing at the start, so neither side ends up optimising against the other.

Yes, with native review rather than machine translation. Bilingual campaigns are priced with the additional production shown explicitly rather than absorbed.

A monthly report against qualified enquiries and cost per enquiry, plus a live dashboard you can open any time. Impressions and reach are in there, but they are not the headline.

Hardware pricing moves with model, memory, storage, warranty term, quantity and current availability. A published shelf price would be out of date or misleading within weeks, so we quote the exact bill of materials instead.

Yes. Send the model numbers and quantities and you get a straight quote. The specification service exists for when you do not know, not as a condition of buying.

We state the warranty term explicitly in the quote, and whether it is onsite or return-to-base, because regionally grey-imported stock is frequently not covered locally even when the manufacturer badge suggests it is.

Yes, quoted as a separate line. Imaging, account setup, data transfer and asset tagging can come with the hardware or be handled by your own team — it should be a visible cost either way.

No. We specify against the requirement. Where a manufacturer logo appears anywhere on this site it describes technology we work with, not a reseller agreement, certification or endorsement.

Common configurations are usually days. Specific builds and enterprise kit run to weeks depending on regional stock. The quote carries a lead time rather than a guess.

We can arrange secure disposal with data destruction certificates. Trade-in value depends on age and condition and is quoted separately so it never disguises the price of the new kit.

We can phase a rollout so the cost lands across quarters. We are not a finance provider, so formal leasing goes through your own facility.

Cable routes, coverage, mounting points, power availability, civil works and local approvals change both the design and the cost materially. A number quoted without seeing the site is a guess, and it is usually the wrong one.

Repeatable starting points for assessment and design work. Equipment, complex cable routes, civil works, permits and multi-site rollouts are quoted after the survey, against what the survey found.

Often. We test and document what is there before recommending anything. Reusing sound infrastructure is usually cheaper than replacing it, and we will tell you clearly on the occasions when it is not.

We identify what is required for your premises and coordinate with the building management or authority. The fees themselves are passed through at cost rather than marked up.

A documented topology, the addressing and VLAN scheme, a device inventory, credentials and test results. An undocumented network is cheap to install and expensive to own.

Yes. Cabling and cutovers are normally done outside business hours or at weekends, and that is priced in from the start rather than added as a surprise later.

Either. If you supply it we check compatibility and licensing first, and tell you plainly if something on the list will cause problems rather than installing it and letting you find out.

Workmanship is warranted for twelve months. Equipment carries its manufacturer warranty, stated per item in the quote so you know what is covered by whom.

Usually fewer than a camera-count quote suggests. Coverage is designed around entry points, blind spots and what you would realistically need to prove afterwards — not around filling a quote with hardware.

Retention is a specification decision driven by storage and any requirement that applies to your premises, and it is agreed before purchase. Longer retention means more storage, and that cost is shown rather than buried.

Yes, with secured access set up deliberately. A recorder exposed straight to the internet is a liability rather than a security control, so remote viewing is designed rather than switched on.

We identify what applies to your premises and design to it from the start. Authority fees, approvals and any required certified equipment are quoted separately and passed through at cost.

Recording health checks, storage verification, lens cleaning and firmware updates. A system nobody checks is normally discovered to be broken on the day the footage was needed.

Often, if they are IP and reasonably current. Mixing generations limits some features, and we will tell you exactly what you lose before recommending it.

You do. Access is granted per person with a named account rather than one shared password, so the log actually shows who viewed what and when.

Coverage is designed to avoid areas where recording is inappropriate, and we advise on signage and retention. The legal obligation remains yours; the design is built to support it rather than complicate it.

Labour and diagnosis. Screens, batteries, storage, memory, boards and other replacement components are quoted by exact device model once the fault has been confirmed, not estimated in advance.

No. You get the fault, the part, the price and the timeline, and nothing is ordered until you approve it. That is the whole point of separating diagnosis from repair.

We assess recoverability first and tell you honestly what the odds are before you spend anything. The assessment is quoted separately from any recovery attempt, so a poor prognosis does not cost you the full price.

Common repairs are usually same or next day once the parts are in hand. Board-level work and ordered components take longer, and you get a date rather than a vague estimate.

Yes, within the normal Abu Dhabi service area. Offices with several devices are handled as a scheduled pickup rather than one trip per machine.

Yes for common repairs, upgrades and diagnostics. Some Apple work requires authorised-service parts, and we will tell you when that is genuinely the better route rather than attempting it anyway.

Devices are held securely and we access only what the repair requires. If we need to sign in we ask; we do not want your password sitting on file.

Ninety days on workmanship. Replacement parts carry their own supplier warranty, stated on the invoice so there is no ambiguity about who covers what.