How to choose a software company in Saudi Arabia: the questions to ask, and the answers that should worry you

More clients reach us after being burned by a previous company than reach us from scratch. The story is the same each time: the proposal was attractive, the price was reasonable, and after delivery they discovered the domain was not in their name, nobody knew where the code was, and a small change needed a new contract.

We are a software company, and it is in our interest to say "choose us". This post would work against us if we did any of these things, and we write it anyway, because a client who knows what to ask is easier to work with.

Before you ask anyone, answer this yourself

Many problems start with the client, not the company. Before requesting a proposal, write one page with:

• The problem you want to solve (not "we want a website", but "customers do not know what we offer and call to ask").
• Who the user is and exactly what they will do.
• What success looks like after six months: more orders? Fewer calls? Staff time saved?
• A rough budget. A decent company will not exploit it; it will tell you what fits inside it.

Without that page, every proposal is a guess, and proposals cannot be compared.

The questions to ask

1. "Who owns the code, the domain, the hosting and the accounts?"

The only acceptable answer: you. Everything in your name and on your accounts from day one, with the company holding access, not ownership. If the answer is "we manage it for you and hand it over when you want", that is polite hostage-taking.

2. "What exactly is in scope, and what is out?"

Ask for a written document listing what will be delivered: the number of pages or screens, the features, languages, devices, integrations with other systems. And most importantly, what is not included. A company that does not write down the scope will disagree with you about it later, and you always lose.

3. "How does the project run, and when do I see something?"

The answer you want: milestones, and at each one you see, try and sign off in writing. The worrying answer: "we deliver everything finished after three months". Three months without seeing anything means three months of assumptions.

4. "What happens when I ask for a change?"

Changes inside the scope are free. Changes outside it have a clear price and a clear process. The company that says "anything is possible" in the first meeting is the one that says "that is outside the contract" in month two.

5. "What happens after delivery?"

Who fixes things when they break? Within what time? For how much? And if I am unhappy, can I take the code to another company? (If the answer to the last one is "no", go back to question one.)

6. "Show me a similar project, and let me talk to its owner"

Not screenshots. A live link, and its owner. A company that hesitates here either has no similar projects or their owners would not say nice things.

7. "Who will actually work on my project?"

The person selling to you is not always the person building for you. Ask who the team is, where they are, and whether the work is in-house or passed to a third party. Third parties are not the problem; not knowing is.

8. "How do you make sure the site shows up on Google?"

The honest answer: nobody guarantees rankings, but there is a technical foundation that must be in place (speed, titles, sitemap, structured data, Search Console registration) and it is part of the delivery. The worrying answer: "we guarantee page one". We wrote why websites do not show up on Google so you can check the basics yourself.

The answers that should worry you

• "We do not need a contract, we trust each other." Trust is great; a contract protects the trust.
• "We use a ready template and adapt it." It may suit you, but you must know, and it must show in the price.
• "The price includes everything." Everything is not a scope. Ask for a breakdown.
• "Just start and we will see." Without a scope, "we will see" means "you will pay".
• "It is easier if we register the domain in our name." No.
• "The site will be ready tomorrow." A site ready tomorrow was built before you asked, and not for you.

How to compare two proposals

Do not compare the final number. Compare:

1. The written scope: are both delivering the same thing? Usually not, and that explains the price gap.
2. Ownership: who owns what.
3. The schedule: when you see the first thing.
4. After delivery: support, changes and freedom to leave.
5. Who does the work: the team and their experience with your kind of project.

A more expensive proposal with a clear scope and full ownership is cheaper than a cheap one whose true cost you discover a year later. We explained what drives the price of a website and why quotes differ so much.

What to expect from a serious company

• They ask you more questions than they answer in the first meeting.
• They sometimes say "you do not need this", even when it would raise the invoice.
• They give you a written scope and a fixed price against it.
• They show you their work at least every two weeks.
• They hand everything over in your name and explain how to run it.

The short version

Choosing a software company is an ownership decision before it is a price decision. Ask the eight questions, get the answers in writing, and compare scope rather than the number. A company that is annoyed by the questions has told you everything you need to know.

If you want to run your project, or another company's proposal, past us for a neutral opinion, book a free consultation. We will give you our view even when it is "the other proposal is better for you".