Information security for software delivery

ISO/IEC 27001
ISO/IEC 27001 certified
What you are actually choosing
The demo is the easiest part of the job to get right
We do not have an office in Saudi Arabia
We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.
A sales demo and a slide of past logos tell you a team can present, not that it can deliver. Both are prepared under ideal conditions with the best examples selected, and every supplier you shortlist will do them well. The information you need is about the ordinary state of a project — the week a requirement changes, the release that has to go out with a known issue, the production bug found on a Thursday evening — because that is where the difference between suppliers is enormous and where none of them volunteers the truth.
So the whole task of choosing well is turning an unknowable question — will this team be good to work with — into checkable ones. How do they handle a change to scope. Who exactly will you speak to, and how often. What do they test, and how would you know if they stopped. And if the relationship ended tomorrow, could another team take the code and run it. None of these is answered by a portfolio, and all of them can be verified before you sign. The rest of this guide is those checks.
The verification
What to actually verify before you sign anything
Each row is a claim every supplier will make and a way to test whether it is true. The good answer is specific and checkable; a vague one is the finding.
A portfolio of shipped, maintained work
Ask to speak to a client whose project is still running, not just launched, and ask that client what happened after go-live rather than during the build.
What a good answer looks like: A reference who talks about years of support, not a highlight reel of a launch, and a team comfortable putting you in touch.
A process you can see, not just hear about
Ask how a change to scope mid-project is handled, what they test and how, and to see a real example — a change log, a test suite, a release process — rather than a description.
What a good answer looks like: A concrete answer with an artefact behind it, and a change process that neither freezes scope nor waves it through without a conversation.
Communication you can rely on
Establish who specifically you will speak to week to week, how often, and whether that is the person doing the work or an account layer relaying to them.
What a good answer looks like: A named point of contact close to the work, a regular cadence, and a plain answer about what happens in the buyer's language and time zone.
Code and ownership you keep
Confirm in writing who owns the code and the intellectual property, where it lives, and whether a different team could deploy it from the repository without the original supplier.
What a good answer looks like: You own the code and the IP, it lives in a repository you control, and it is documented enough to hand over — proof there is a way out that is not a rebuild.
The team that will actually do the work
Ask who is assigned to your project by name and seniority, and whether the people in the pitch are the people who will write the code.
What a good answer looks like: The people you met are the people you get, or an honest account of who joins and when — not a senior pitch followed by a junior delivery.
When to walk
The warning signs worth walking away over
None of these is about capability; every one is about how the relationship will actually run. A supplier can be genuinely skilled and still fail you on these.
A quote given before the scope is understood
A firm figure produced after a single call, before anyone has understood the integrations or the backend, is not confidence — it is a number that will be defended by cutting corners when the real work appears. A supplier who asks harder questions before quoting is showing you how they will behave later.
No one will name who does the work
A pitch led by senior people who then hand delivery to a team you never met, and a refusal to name that team, means you are buying a brand and receiving whoever is free. Insist on knowing the people, and treat evasion as the answer.
Vague answers on code ownership
If who owns the code, where it lives and whether you can redeploy it are met with reassurance instead of a written answer, assume the exit is expensive by design. Ownership is cheap to settle at contract time and costly to discover at year two.
A process that only exists in the pitch
When you ask to see a real change log, a test suite or a release process and get a diagram instead of an example, the process is aspirational. Teams that work this way can show you the last time they did, not a slide about how they would.
Our role
Where we fit, and how to hold us to the same test
- 01
Ask us these questions first
The checks in this guide are the ones we would want a buyer to run on us — who does the work, what we test, who owns the code, how a change is handled. We would rather answer them plainly at the start than have them surface as surprises later.
- 02
A way out that is not a rebuild
You own the code and the IP, it sits in a repository you control, and we document and hand over enough that another team could run it — because a partner worth choosing makes leaving possible rather than expensive.
- 03
The honest no
Where the work is not something we are the right team for, we say so and say who might be a better fit by capability, without ranking named firms — because a partner who only ever says yes has told you nothing about their judgement.
Which partner is right is your judgement to make; we would rather be chosen because you tested us on process, communication and ownership and the answers held up, than because a demo went well and the harder questions were never asked.
Common questions
What buyers ask
Should we simply choose the cheapest bid?+
Not on price alone, and not by assuming the cheapest is the weakest either. A lower bid can be real efficiency — a team with reusable tooling and lower overheads doing the same work for less — or it can be a smaller scope in disguise, where the number is low because integrations, testing and maintenance were quietly left out. The way to tell is to make the bids comparable: confirm each covers the same scope, the same platforms, the same backend and the same handover. Once they describe the same work, price is a fair input. Before that, comparing the numbers compares two different things.
How do we check a portfolio we can't independently verify?+
Shift from the artefact to the reference. A screenshot proves nothing you can rely on; a conversation with a client whose system the supplier still supports proves a great deal. Ask for a reference on a project that is a year or more past launch, and ask that client the unglamorous questions — how the team handled a change they did not expect, how bugs after go-live were dealt with, whether the estimate held. A supplier confident in its work makes that introduction easily. One that offers only logos and testimonials it wrote itself is showing you the limit of what it can stand behind.
How should a local partner weigh against an offshore one?+
By what the project actually needs from proximity, not by a rule. Closeness in time zone and language matters most when the work needs frequent, high-bandwidth conversation — an evolving product, tight collaboration with your own team, or a domain that takes time to explain. Cost and access to specific skills often favour an offshore or blended team, and a well-run one closes the distance with overlap hours and a named point of contact who works in your time zone. We serve Saudi organisations without claiming a local office there, and what makes that work is the same thing that makes any arrangement work: a person close to the code you can reach in your working day. Judge the setup by whether the communication is reliable, not by the postal address.
In this cluster
Talk to us, and test us on this
A first conversation you can run this guide against — asking us the same process, communication and ownership questions you would ask any supplier, and judging the answers rather than the pitch.
Start the conversation