Start With the Only Question That Survives the Project: Who Owns It?
Before you look at a single design, ask one thing: when this is done, do I own the code, the domain, and the hosting account — or do I own a login to someone else's platform? This is the line that separates a real website from a glorified rental, and most owners in Egypt never ask it until it's too late. A green flag is a clear, written answer: the source code is yours, the domain is registered in your name, and you can move everything to any host on earth without permission. A red flag is anything vague — "we manage all that for you," "it's on our system," or a monthly fee that quietly never ends.
This matters because of a pattern we see every week: an owner builds on a platform he doesn't control, grows for two years, and then discovers that leaving means losing the site, the SEO, and sometimes the domain itself. Ownership isn't a technical detail — it's leverage. The party that holds the code holds the relationship. When YMS ships a project, the code is yours outright on day one; you could fire us the next morning and lose nothing. That's the test. Ask any agency or freelancer to put ownership in writing, and watch how fast the conversation gets honest.
Custom-Built or a Dressed-Up Template? Ask to See the Difference
There is nothing wrong with a template for a five-page brochure site. There is a lot wrong with paying custom-build prices for a Wix or template theme with your logo dropped on top. The honest question is simple: is this built for my business specifically, or am I getting a layout a hundred other companies already use? A green flag is a team that asks about your workflow, your customers, and what the site actually needs to do — booking, orders, a patient portal, a property search. A red flag is a fixed menu of "packages" where the only variable is how many pages you buy.
How do you tell the difference as a non-technical owner? Ask two questions. First: "Can you change this specific thing for my business, even if no template offers it?" If the answer involves shrugging at platform limits, it's a template. Second: "Show me a feature you built from scratch for one client that you couldn't reuse for another." Custom builders have those stories instantly. The IGBS system YMS built — a 17,000-record custom platform for Egypt's largest IP and trademark firm — exists precisely because no template on the market could do what that business needed. That's the line between a website and a tool that runs your operation.
The party that holds the code holds the relationship. Ownership isn't a technical detail — it's leverage.
Who Actually Does the Work — and Will They Still Be There at Launch?
The person who charms you in the first meeting is often not the person who writes your code. In bigger shops, a senior closes the deal and a rotating cast of juniors does the build — or the whole thing gets quietly outsourced to a cheaper team you never meet. That's not automatically bad, but you deserve to know. Ask directly: "Who, by name, is building this, and what's their experience?" A green flag is a straight answer and access to the people doing the work. A red flag is an account manager who becomes a wall between you and anyone technical.
For most Egyptian SMEs, the sweet spot is working directly with a founder or senior who has skin in the game — someone whose reputation is on every line of code, not a junior treating your project as a training exercise. Fewer hands also means fewer handoffs where context gets lost and your site comes out generic. When you talk to a studio, notice whether the person scoping the project clearly understands the technical tradeoffs, or is just reading from a sales sheet. The first kind builds you something that lasts. The second sells you a package and disappears.
Show Me a Real, Still-Live Client — Not a Mockup
Anyone can fill a portfolio with beautiful mockups that were never built, or with sites that went live and quietly died six months later. The only proof that counts is a real client URL you can open right now, on your phone, and see working — ideally one that's been live for years without falling over. Ask: "Give me a link to a site you built that's still running, and tell me how long it's been live." A green flag is an instant, specific answer with a working link. A red flag is a deck full of renders and a sudden change of subject.
Longevity is the underrated signal here. A site that's run four years with zero outages tells you more than ten gorgeous screenshots, because it proves the build was solid, the hosting was set up right, and the team didn't disappear. The IGBS portal YMS built has been live and stable for four years carrying a 17,000+ record system — that's not a design we're showing you, it's a load-bearing piece of a real firm's daily operation. When you evaluate anyone, weight "still working years later" far above "looks pretty in the pitch."
Is It Truly Bilingual AR/EN — Built Natively, Not Translated?
In Egypt and the Gulf, a serious site usually needs to work in both Arabic and English. The trap is that many agencies bolt Arabic on at the end — machine-translated text, broken right-to-left layouts, English fonts forced onto Arabic words, and a language toggle that half-works. Your customers feel that cheapness instantly. Ask: "Is RTL Arabic built into the design from the start, and who writes the Arabic copy?" A green flag is native Arabic handled as a first-class layout, with copy written by a real Egyptian, not run through Google Translate.
This isn't a nice-to-have if any of your customers are in KSA, the UAE, or are Arabic-first inside Egypt. A natively bilingual build means the Arabic version reads like it was written for an Egyptian owner, the layout flips cleanly, and search engines can index both languages properly so you get found in both. When you review samples, open the Arabic version on your phone and read it as a customer would. If it sounds like a robot or the buttons sit on the wrong side, that's your answer about how the rest of the build was done.
Built for Google and Mobile From Day One — or Patched Later?
A beautiful site nobody can find is an expensive business card. SEO and mobile performance have to be designed in from the first line of code, not sprinkled on after launch. Ask: "How is this built for Google search and for mobile speed — and can you show me the Core Web Vitals score?" A green flag is a team that talks specifics: clean code, fast load times, proper structure, mobile-first down to a 375px screen. A red flag is "we'll do SEO as a separate package later," which usually means it was never built to rank in the first place.
Most of your customers in Egypt are on a phone, often on a less-than-perfect connection, and Google now ranks largely on mobile experience. A site that loads slowly or jumps around while loading loses customers and rankings at the same time. When you evaluate a company, open one of their live client sites on mobile data and count the seconds. If their own work is sluggish, yours will be too. Speed and findability aren't decoration — they're the difference between a site that sells while you sleep and one that just sits there.
What Happens After Launch — and Who's Holding You Hostage?
Launch day is the start of the relationship, not the end. The questions that protect you are about the boring afterlife: who hosts it, who fixes it when it breaks, how much a small edit costs, and how fast it gets done. Ask: "After launch, can I host this anywhere and hire anyone to maintain it, or am I locked to you?" A green flag is a clean handover — your code, your accounts, documentation, and the freedom to stay with the team because you want to, not because you're trapped. A red flag is any setup where leaving means losing the site.
The honest model is simple: you own everything, and you choose to keep the team on for maintenance because they're good — not because they hold your business hostage. Get the post-launch terms in writing before you sign: response times, edit costs, and exactly what's handed over. A studio confident in its work doesn't need to lock you in; it earns the next month by being worth it. If a company gets cagey when you ask how to leave, you've learned the most important thing about staying.
Freelancer or Agency — and How Is It Actually Priced?
There's no universal right answer between a freelancer and an agency — there's only the right fit for your risk. A strong freelancer is cheaper and personal but is a single point of failure: if he gets sick, travels, or moves on, your project and your support vanish with him. An agency costs more but gives you continuity and a bench — at the risk of junior hand-offs and you becoming a small account. The studio model sits in between: senior ownership and direct access, with more durability than one freelancer. Ask yourself which failure mode you can live with, then choose accordingly.
On pricing, the rule is: clarity beats cheap. A trustworthy quote is tied to a defined scope — these pages, these features, these revisions, this timeline — so you know exactly what you're buying and what costs extra. A dangerous quote is a single low number with no scope behind it, because the gaps get filled with change-orders later, and the cheap site becomes the expensive one. Don't ask "how much"; ask "what exactly do I get for this, and what triggers more cost?" The company that answers that clearly respects your money. The one that won't is already planning the upsell.
Putting It Together: A 5-Minute Vetting Checklist
You don't need to be technical to protect yourself — you need to ask the same nine questions of everyone you're considering and compare the answers side by side. Do I own the code, domain, and hosting? Is this custom or a template? Who, by name, builds it? Can I see a real client live for years? Is the Arabic native? Is it built for Google and mobile from the start? What happens after launch and can I leave? Freelancer, agency, or studio fit? Is pricing tied to a clear scope? Honest providers welcome these questions. The ones who get defensive are telling you everything.
This is exactly the bar YMS built itself to clear: code you own outright on day one, custom builds for businesses templates can't serve, senior hands on every project, and live proof like the IGBS portal that's run four years without an outage. The smartest first move costs you nothing and tells you a lot — ask for a free, tailored mockup of your own site before any contract. A serious team will happily show you what they'd build, with no obligation. If you want that for your business, that's where the conversation should start.
Frequently asked questions
What is the most important question to ask a web design company in Egypt before hiring?
Ask who owns the code, domain, and hosting when the project is done. If the answer is anything other than "you own all of it outright," you're renting a website, not buying one. Ownership decides whether you can ever leave, move hosts, or hire someone else — get it in writing before you pay anything.
How do I know if a website is custom-built or just a template in Egypt?
Ask the company to change a specific feature your business needs that no template offers. If they shrug at platform limits, it's a template. Also ask to see something they built from scratch for one client that couldn't be reused. Custom builders answer instantly; template sellers change the subject.
Is it better to hire a freelancer or an agency for web design in Egypt?
It depends on the risk you can live with. A freelancer is cheaper and personal but a single point of failure — if he disappears, so does your support. An agency gives continuity but risks junior hand-offs. A senior-led studio sits in between: direct access plus durability. Match the choice to which failure you can survive.
How much should a custom website cost in Egypt?
There's no honest single number without scope — price should be tied to defined pages, features, revisions, and timeline. Be suspicious of one low figure with nothing behind it, because the gaps become paid change-orders later. Ask "what exactly do I get, and what costs extra?" rather than just "how much?"
Why does it matter if a web design agency shows a live client versus a mockup?
A mockup proves nothing — it may never have been built. A real client site you can open right now and that's been live for years proves the build was solid, the hosting was set up right, and the team didn't vanish. Longevity, like the IGBS portal YMS has kept running four years without an outage, beats pretty screenshots every time.