Enterprise desk
Buying software work inside a large organisation means answering other people's questions: legal, security, finance and the team that will live with the result. This page is the route through them, in the order they usually come up.
We do not publish client names without written permission, and we do not print a service-level table for a contract that has not been written. What we can show is what gets agreed, who signs for it and how you leave if you need to.
Sales conversations can start with our local teams in the UAE and Singapore. The engineering is done in Rajkot and Ahmedabad, India, and you speak to the people doing it.
What the statement of work fixes
These are the items a service-level table would summarise. They are set per engagement, because a support desk and a migration need different answers.
| Item | What gets written down |
|---|---|
| People | The delivery lead by name, the escalation contact above them, and who approves a replacement if someone leaves. You approve the person. |
| Hours | Overlap hours with your team, agreed per client, and the reporting rhythm: a weekly summary, with work tracked in your tools. |
| Response | Response targets and severity tiers for this engagement. |
| Data | Where client data lives. It stays in your environment and region. Any third party that would touch it is listed before it is used. |
| Ownership | Deliverables and source code are assigned to you on final payment. Pre-existing tooling is identified and licensed to you for the deliverable. |
| Assurance | Certification and independent-audit status in writing, and penetration-test summaries for delivered work under NDA with the client’s consent. |
How a large buyer works with us
The same order most procurement teams already follow.
First conversation
With a local sales team or directly with an engineer, under your NDA if you want one first. Nothing confidential is needed yet.
Review
Your reviewers work from the Trust Centre, the security page and the documents they ask for. Dated documents can be requested at no cost.
Working evidence
The readiness check, the demonstrations and, where it helps, a working session with an engineer at agreed rates.
Paper
Your paper or ours. The statement of work names the people and fixes the items above.
A small first task
You meet the named person and judge the work on something small before anything larger is committed.
How an engagement ends
A supplier that is easy to leave is easier to approve. This is the plan from the first day, not a clause to negotiate at the end.
Code is already yours
Work is committed to your repository and accounts as it happens, so there is no handover of files at the end.
Month to month
Engagements run month to month; you can scale up or down at the end of any month, unless your contract sets a different term.
Documentation as you go
Documentation is written during the work and is not invoiced as a separate item, so a new team can pick it up.
Escrow on request
Source-code escrow and professional-indemnity cover are provided on request and agreed per engagement.
Asked by enterprise buyers
Where is the service-level table?
In your statement of work. Response targets and severity tiers are agreed per engagement, so a table here would describe nobody's contract.
Which certifications do you hold?
Certification and independent-audit status is shared in writing during procurement, so that you receive it dated and addressed to you.
Can you give client references?
A reference is arranged per request with that client's written permission. We do not publish client names on this site.
Who do we talk to locally?
There are sales teams in the UAE and Singapore. Use the form below and say where you are; the right person replies within one business day.
How is pricing handled?
Through a request, a person replies with the rate card or a written quotation. Larger engagements are quoted against a scope.
Talk to the enterprise desk
Tell us who needs to be involved on your side and what they will ask first. We reply within one business day.