Most Mauritian business owners look for a web developer after they've been burned — pushed into an expensive custom build when WordPress would have done, or locked out of their own .mu domain when the developer vanished. Whether you're starting from scratch or redoing website development in Mauritius, choosing a web developer is less about portfolios than about infrastructure, compliance, and control. Here are the four decisions to make before you talk to anyone, the six questions to ask, and the red flags to walk away from.
Who should build your site: freelancer, agency, or offshore
The first decision is not what to build but who builds it. The three options in Mauritius carry different risks.
| Factor | Local freelancer | Local agency | Offshore developer |
|---|---|---|---|
| Cost | Lower. Often MUR 15,000 to 60,000 for a standard site. | Higher. MUR 60,000 and up, but more hands on the work. | Lowest, but you carry compliance and communication risk. |
| MRA e-invoicing knowledge | Varies. Ask explicitly for a past project. | More likely to have handled VAT-registered builds. | Rarely. You will need a local EBS partner regardless. |
| DPA 2017 and local data handling | Usually familiar. | Usually familiar, with documented policy. | Often unfamiliar. Extra coordination required. |
| MCB / SBM payment integration | If they've done it before. | Usually yes. | Rare without a local integration partner. |
| Handover and accountability | Single point of failure. If they vanish, you're stuck. | Team continuity, written handover, easier to enforce. | Harder to enforce handover across time zones and jurisdictions. |
| Communication | Direct, WhatsApp and phone, English and French. | Project manager as a layer, slower but more reliable. | Async, email and chat, possible language friction. |
The pattern I see: a freelancer is fine for a brochure site you'll run yourself. An agency earns its premium the moment MRA e-invoicing, MCB payment rails, or a handover to a team matters. Offshore works for pure build work where you, the owner, own the compliance and the integration locally. The cheapest quote is usually the one that quietly skips one of those three.
1. Decide the build type: WordPress or custom
Before you look at a portfolio, know what platform you need. A CMS like WordPress or Shopify is a different animal from a custom web application.
A custom app built on React, Laravel, or Node.js makes sense only if your business logic is genuinely unique. If you run a standard service business, an e-commerce store, or a corporate site, a CMS is faster to build, cheaper, and easier to maintain. Be wary of developers pushing a custom build for a brochure site or a run-of-the-mill online store. That is the most common route to vendor lock-in. WordPress runs 43% of all websites (W3Techs, 2024) for a reason: for a brochure, a shop, or a blog, someone has already built the thing you need.
| Factor | WordPress / Shopify (CMS) | Custom build |
|---|---|---|
| You don't code yourself | The UI is usable without a developer. | A developer for almost every change. |
| Budget and deadlines | Faster and cheaper to build. | Expensive and time-consuming to scope. |
| Specific integrations | Thousands of plugins for booking, forms, payments. | Every integration coded from scratch. |
| Long-term maintenance | Lower initial cost, regular plugin updates. | Higher initial cost, stable core architecture. |
| Custom layouts and logic | Restrictive for unconventional layouts. | Limitless; if you can design it, it can be coded. |
| Database complexity | Fine for standard forms, blogs, profiles. | Essential for complex or heavy logic systems. |
The honest split: WordPress for the marketing site, the blog, anything content-heavy. Custom only for the one part of the business that genuinely needs it, a booking flow with rules WordPress can't model, a member portal, a product configurator. Don't pay someone to custom-build what a free plugin already does. Don't run your whole operation on WordPress if one custom screen would save you hours every week.
2. Register the .mu domain in your name before any work starts
This is the single most common lock-in I see, and it is entirely avoidable. The developer registers the .mu domain and the hosting in their name, builds the site, and two years later when the relationship sours you find out you don't own your own web address.
The .mu country-code domain is administered by the Mauritius Network Information Centre (MUNIC) and has no registration restrictions. You can register at the second level (yourbusiness.mu) or under labels like .com.mu and .org.mu. Any accredited registrar can sell you one. Standard registration runs roughly MUR 2,800 per year through local resellers like cloud.mu and register.mu. Register it in your company's name, with your company email as the admin contact, before a single line of code gets written. Control stays with you, and no one can overcharge you for the renewal or hold the domain hostage.
3. Hosting: where is your audience, actually?
Don't blindly buy whatever hosting package your developer recommends. Ask where they'd host your site and listen to how they answer. "Local is best" is a weak answer. The strong answer sounds like "your audience is mostly European tourists planning trips, so I'd host in Frankfurt with a CDN edge close to Mauritius for the domestic traffic." A reasoned answer means they've thought about who loads the site and where.
If your audience is strictly in Mauritius, hosting locally with providers like cloud.mu or Mauritius Telecom can reduce latency, because what matters is peering into the Mauritius Telecom and Emtel networks. For a diaspora or tourism audience, a European host fronted by a CDN often serves them faster than a domestic one. International cloud providers like AWS, Google Cloud, or DigitalOcean are more reliable and scalable if your traffic is global. Mauritius had 1.01 million internet users and an internet penetration of 79.5% at the start of 2024 (DataReportal, Digital 2024: Mauritius), and Google's mobile page-speed research found bounce probability jumps 32% as load time goes from 1 to 3 seconds and 90% as it goes from 1 to 5 seconds (Google/SOASTA, 2017). Where you host changes whether that first mobile load keeps the visitor.
One compliance note: the Data Protection Act 2017 (DPA 2017) governs personal data processing in Mauritius and is broadly modelled on the EU's GDPR. If your site collects names, emails, or booking details, it applies to you. Any credible developer should talk through cookie consent, a privacy policy, and where visitor data is stored. If they can't, treat that as a yellow flag regardless of how good their portfolio looks.
4. Address MRA e-invoicing before, not after, you build
If you sell online in Mauritius, e-invoicing is no longer optional. The Mauritius Revenue Authority (MRA) is rolling out a national e-invoicing system for VAT-registered businesses, and depending on your turnover band, invoices your site generates must conform to a structured format the MRA can receive, not just a PDF that looks right to a customer.
The rollout is phased by turnover. Mandatory phases began on May 15, 2024 for businesses with annual turnover above MUR 100 million. It extends to businesses above MUR 80 million by June 30, 2026, and above MUR 40 million by September 1, 2026. Confirm what applies to you against the MRA's current e-invoicing guidance before you scope any invoicing feature.
On the technical side, your developer can't just install a standard checkout plugin and walk away. Your store must integrate with an MRA-certified Electronic Billing System (EBS). The system has to generate structured JSON invoices, transmit them in real time to the MRA's Invoice Fiscalisation Platform (IFP) for validation, and produce a unique Invoice Reference Number (IRN) and QR code for the customer. Retrofitting this into a site built to email pretty PDFs is expensive and annoying. If you're VAT-registered and your site issues invoices, it should produce them in the right shape from day one.
What this means for picking a developer: ask explicitly whether they've built invoicing flows that comply with current Mauritian tax rules, and whether they can integrate your store with an MRA-compliant EBS before writing a single line of code. A wave-off like "we'll add it later" tells you they don't know the cost of retrofitting. Get your accountant and your developer in the same thread before scope closes. The cheapest time to get this right is at build time.
Six questions to ask a web developer in Mauritius
Once the four decisions are made, the developer shortlist shrinks to these checks.
- Portfolio of comparable scope. Restaurant booking experience doesn't transfer to B2B services. Ask for two projects that match your shape, and one that didn't work out. Test those live sites on your phone to see how fast they load.
- Communication speed. If they take five days to answer an email, that's how long they'll take to fix a broken payment gateway. Hire someone who communicates proactively.
- Ownership terms in writing. The contract states: on final payment you get all source files, hosting and domain are in your name, you're free to leave. Verbal versions of these terms are worth nothing.
- A maintenance plan. Every site needs upkeep. Ask what they charge monthly or quarterly, what's included (patching, backups, uptime monitoring), and what happens if they're unavailable. WordPress in particular needs a defined cadence. No answer means you'll discover the cost on your own later.
- Development stack. If they're pitching a custom build, what languages and frameworks are they using? Avoid obscure or outdated stacks, so you can transition to a new developer later if you need to.
- Local payment fit. Can they wire up MCB or SBM rails if you need online payment? Do they work in the language and channels you actually use, WhatsApp, email, phone, in English or French?
Red flags when choosing a web developer
- The developer wants to register the
.mudomain in their own name. - They push a custom build for a standard brochure site or a simple online store.
- "We'll add MRA e-invoicing later." Retrofitting costs more than building it right.
- No written ownership terms. "Don't worry, you'll own it" is not a contract.
- They take five days to reply to an email during the sales process.
- No handover session. If they resist one, walk away.
- Their own portfolio site loads slowly on your phone over mobile data.
- They can't name the EBS they'd integrate, or can't explain the IRN and QR code flow.
- They quote a price with no mention of hosting, domain, maintenance, or compliance.
FAQ: choosing a web developer in Mauritius
Do I need to hire a web developer based in Mauritius?
No, but local knowledge matters for three things: MRA e-invoicing integration, the Data Protection Act 2017, and wiring up MCB or SBM payment rails. An offshore developer can do the build, but you need someone who understands Mauritian tax and compliance, or you will retrofit it at double the cost. A common workable split is offshore build plus a local integrator for the EBS and payment rails.
How much does a website cost in Mauritius?
A standard WordPress brochure site runs MUR 15,000 to 60,000. A custom build with booking logic, a member portal, or MRA e-invoicing integration starts around MUR 150,000 and scales with scope. The .mu domain runs about MUR 2,800 a year, and ongoing maintenance is typically MUR 1,500 to 5,000 a month depending on what's included. The cheapest quote is usually the one that skips domain ownership, hosting, handover, or compliance.
WordPress or a custom build for my business?
WordPress for marketing sites, blogs, and content-heavy pages. A custom build only for the one part of your business that WordPress cannot model: a booking flow with rules, a member portal, a product configurator. Do not pay someone to custom-build what a free plugin already does, and do not run your whole operation on WordPress if one custom screen would save you hours every week.
What is MRA e-invoicing and does my site need it?
The Mauritius Revenue Authority is phasing in mandatory e-invoicing for VAT-registered businesses by turnover band. Mandatory phases began May 15, 2024 for turnover above MUR 100 million, extending to above MUR 80 million by June 30, 2026 and above MUR 40 million by September 1, 2026. If you are VAT-registered and your site issues invoices, it must integrate an MRA-certified Electronic Billing System that generates structured JSON invoices, sends them to the MRA platform in real time, and returns an Invoice Reference Number and QR code. Confirm your band against the MRA's current guidance before you scope any invoicing feature.
Who should own my .mu domain?
You, in your company's name, with your company email as the admin contact. The .mu domain is administered by the Mauritius Network Information Centre with no registration restrictions, and costs roughly MUR 2,800 per year through accredited resellers. Register it before any work starts. The most common lock-in is a developer who registers the domain in their own name and disappears.
5. Handover is where most projects actually fail
The launch isn't the finish line. Projects go wrong in the three months after, when the developer moves on and the business finds out nobody explained how to change the menu, update the phone number, add a post, or restore from backup.
Before final payment, require a handover session, recorded, with you and whoever will run the site present. It should cover how to edit each content type, where backups live and how to restore one, where the domain and hosting accounts are, what the monthly maintenance cost and cadence is, and who to call if the site is down on a Friday night. You should walk away with full administrative access, not an "editor" role, clear documentation on hosting and domain renewal dates, and a training session so your team can process orders and make minor text edits. If the developer resists a handover, that resistance tells you more about the whole engagement than anything in their portfolio.
Get the four pre-decisions right, get the ownership terms in writing, and get the handover recorded. Almost everything else is negotiable. Once your site is live, the next visibility win is structured data and microdata — the checklist I run on every WordPress build.