What Happens When Your Web Developer Disappears (A Nigerian Business Reality)
A Lagos business owner needed to update her payment gateway last month. Her developer had moved to Canada six months earlier. She had no login credentials, no hosting details, nothing. She couldn’t even confirm where the domain was registered.
For three weeks, her business was unable to process online payments. The recovery bill matched what the original website cost.
When your website developer stops responding, this is what happens. Developers relocate abroad. Agencies close when economic pressures hit. Freelancers take full-time jobs and stop responding. It’s more common than most businesses expect.
When your developer disappears, you discover an uncomfortable truth: you might not actually control your own website. No access to the code you paid for. No way to log into hosting. No clue where your domain is registered.
Here’s what’s at stake and how to protect yourself.
Why This Keeps Happening in Nigeria
Understanding why developer disappearances are common helps you plan more effectively and avoid taking it personally.
The Japa Effect is Real
Nigerian tech talent is leaving in large numbers. When a developer gets a Canadian PR or a UK visa, they often have weeks to relocate. Projects that were “almost done” become impossible to complete. Handovers don’t happen. It’s overwhelming, not malicious.
Economic Pressure Closes Agencies
Small development agencies struggle when clients delay payments for months or when the naira crashes and hosting bills triple overnight. Some close quietly, without proper client handovers.
Sudden Life and Job Changes
A developer working on your site as a side project lands a banking job that prohibits freelance work. They take it, your project becomes a liability, and communication stops. Health emergencies and family crises happen. Informal projects get dropped first.
Intent Matters (But Doesn’t Solve Your Problem)
Most disappearances aren’t malicious. Developers get overwhelmed by circumstances. Understanding intent doesn’t solve your problem, but it matters for how you respond.
The Structural Reality
Nigeria’s informal tech contracting culture grew faster than governance structures. Fast-moving arrangements without formal processes became the norm. Our rapid growth compressed years of learning into months. Result: thousands of businesses discover they don’t control their digital infrastructure.
The Two Models: Why Structure Matters More Than Access
The risk isn’t “someone else managing my infrastructure.” The real risk is informal arrangements without institutional accountability. Some freelancers run tight processes, and some companies don’t. The difference is structure, not business size.
| Factor | Informal Arrangements (High Risk) | Professional Managed Services (Recommended) |
|---|---|---|
| Account Ownership | Personal accounts tied to an individual | Company accounts (institutional) |
| Documentation | Verbal promises, “trust me” | Written SLA with exit procedures |
| Continuity | Single-person dependency | Multiple staff, documented processes |
| Domain Management | Personal name, personal renewal | Client-owned, provider-administered |
| Hosting | Personal account | Reseller account with documented exit procedures |
| WordPress Access | Varies/ad-hoc | Role-based (Editor/Author for clients) |
| Recoverability | No plan, no guarantees | Contractual guarantees, documented backups |
| When it Fails | Everything stops | Team continuity, escalation paths |
Model 1: Informal Arrangements (High Risk)
A freelancer manages your infrastructure through personal accounts with no written SLA, verbal commitments only, and no documented handover procedures.
This isn’t about freelancers being careless. It’s about what happens when the entire setup depends on one person. When that individual leaves Nigeria, gets a new job, or simply disappears, everything stops.
Model 2: Professional Managed Services (Recommended)
A professional IT services company manages your infrastructure under a written SLA defining ownership and exit rights, with multiple staff, documented procedures, and transparent handover processes.
As the table shows, provider-administered domains, reseller hosting, and role-based WordPress access are normal here. You’re not dependent on any individual. The company has institutional accountability. Multiple team members can support you. If your primary contact leaves, someone else steps in. The SLA guarantees your recoverability.
In practice: Domain registered in your name (even if the provider manages it), you can retrieve all files/databases on exit, backups documented, handover procedures contractually defined, and you can request an ownership/exit pack at any time.
Which Model Do Most Nigerian Businesses Need?
For many Nigerian businesses, professional managed services are the better choice. You get expertise without in-house technical knowledge, don’t track renewals, and have team backing with built-in continuity.
If your website drives revenue, handles customer data, or supports payments, you need continuity baked in. Direct infrastructure management makes sense if you have in-house IT teams. For everyone else, the risk outweighs the value.
At PlanetWeb, we manage infrastructure for most clients through our managed IT services. They don’t operate infrastructure daily, but retain ownership rights and access on request.
What You Risk With Informal Arrangements
When you work through informal arrangements – freelancers with personal accounts, verbal agreements, no SLA – you lose control of business-critical assets when they disappear.
Important: Professional managed services handle these same functions on your behalf. That’s not the risk. The risk is informal setups without documentation, institutional backing, or guaranteed recoverability.
Your Source Code
Source code is the foundation of your website. Without it, any new developer must reverse-engineer everything or rebuild from scratch. Custom functionality you paid for? You’ll pay again.
Your Design Files
Original Photoshop, Figma, or Illustrator files contain your brand in editable form. Screenshots aren’t replacements. Recreating professional design files costs β¦300,000 to β¦1,500,000.
Hosting and Domain Access
In informal arrangements, domain and hosting control become a critical vulnerability. If a freelancer registered your domain under their personal Gmail and manages hosting through their personal account, you’re at risk. When they disappear, you can’t renew, can’t update DNS, can’t migrate.
In managed services environments, providers typically administer domains and hosting on your behalf. This is normal and often safer than DIY management. What matters isn’t who logs into the registrar daily – it’s whether:
- The domain is registered in your company’s name
- Renewal responsibility is documented
- You can retrieve your website files and database
- Transfer procedures are guaranteed if the relationship ends
Without these guarantees – whether from an individual or a company – your domain can expire, your site can go offline, and your business emails can stop working. (Read our guide on choosing web hosting in Nigeria.)
Your Email Infrastructure
Company email accounts, forwarding rules, autoresponders, CRM integration – all in a configuration you can’t access. Historical data may be unrecoverable. New email means new addresses and broken customer chains.
Third-Party Integrations
Payment gateways like Paystack or Flutterwave. Google Analytics. Social media tools. API connections. Your developer set up each integration. Now each one is a black box to you – you don’t know how it works or where credentials are.
Platform Account Access
Beyond integrations, there are critical platform accounts you need visibility into: WordPress or CMS access for content updates;Β Cloudflare or CDN configuration for security; Google Search Console for SEO monitoring; Google Business Profile for local presence;Β and backup systems.
A Note on WordPress Access Levels
In managed WordPress environments, clients typically receive Editor or Author access, not Administrator. This is proper security practice. Providers retain administrator access to prevent site breakage, manage updates safely, and maintain security. What matters is content ownership and guaranteed access on exit, not admin permissions.
If these accounts were set up under your developer’s personal email in an informal arrangement, you can’t manage your own presence.
Documentation (Usually Missing)
How does inventory sync with your website? Where are database backups? Who do you call if something breaks? If this knowledge lived only in your developer’s head, it’s gone.
The Legal Side You’re Ignoring
This is also a compliance problem. Expired SSL certificates drive customers away. Without access to customer data systems, you can’t manage consent, respond to access requests, or handle breach notifications properly. You have obligations under Nigeria’s data protection requirements and PCI DSS requirements if you process payments. This is governance risk. Learn more about business continuity planning.
What This Actually Costs
Rebuilding: β¦800,000 to β¦2,500,000. (Website costs guide.) Migration: β¦500,000 to β¦3,000,000. Emergency work adds a 50-100% premium. Plus ongoing costs: plugin renewals, SSL, domain privacy, CDN, email licenses.
Biggest cost: time. Lost revenue, missed opportunities, damaged reputation.
What a Good SLA Should Cover
For many Nigerian businesses, professional IT services with institutional accountability provide better protection than DIY management.
What Should Be in Your IT Service Level Agreement
Your IT service level agreement should include:
Ownership and Recoverability: You own content, code, and domain. Documented backups, data extraction rights, exit procedures (typically 30 days), and migration assistance.
Service Standards: Response times, uptime guarantees, security updates, multiple contact points, and escalation paths.
Administrative Clarity: Who handles domain renewals, hosting responsibilities, WordPress access levels, and emergency access if the provider is unavailable?
Notice what’s NOT listed: daily operational access to hosting panels, registrars, or WordPress admin. In managed services, the provider handles operations. Client retains ownership and recoverability. If you want day-to-day access, that can be arranged, but it isn’t the core safety mechanism.
Why This Model Works Better
When a managed services provider handles infrastructure, they manage renewals, security, backups, and technical issues. Clients don’t track SSL expiry or manage DNS.
Critical distinction: Managed services don’t mean losing ownership. The domain remains in your company’s name. Your content and data remain yours. You can retrieve everything if the relationship ends. What changes is who handles operational work, not who owns assets.
What makes this safer: company-owned accounts (not tied to individuals), support isn’t dependent on one person, work is documented, escalation paths are clear, and exit rights are protected in writing.
When Managed Services Make Sense
Professional managed IT services are right if you don’t have in-house technical expertise, your team’s time is better spent on core business, or business continuity matters. The investment typically costs less than one emergency recovery.
If You’re Managing Infrastructure Directly
Some businesses prefer direct management. This makes sense if you have in-house IT teams or technical founders. Here’s what you need to do it safely.
When Direct Management Makes Sense (And What It Requires)
If you have in-house IT teams, direct management gives complete operational control. Requirements: A domain in the company name with secure credential storage. Hosting account under company billing with multiple login access. Email hosting is separate from web hosting. Code in GitHub, GitLab, or Bitbucket with company admin access. Documentation tied to milestones. Knowledge transfer sessions and exit procedures in writing.
Minimum Non-Negotiables
Before you launch any website, ensure you have:
A. Ownership & Recoverability (must-have):
- Domain registered to your company entity
- Documented renewal responsibility
- Backup policy with retention periods
- Exit process with timelines
- Data handover format (files/database export)
- List of critical third-party accounts and who owns them
B. Operational Access (role-based, as needed):
- WordPress Editor access for content updates
- Emergency access available on request
- Transparent process for DNS changes or updates
The first list ensures recoverability. The second list varies by management model: direct management requires more, while managed services handle operations on your behalf.
During the Project
Schedule quarterly documentation updates. Run credentials audits every six months. Verify repository access regularly. Proper website maintenance includes access audits.
Watch for warning signs: the developer resists sharing access, uses personal email for business tools, or provides no documentation.
If Your Website Developer Stops Responding: What to Do Now
You’re reading this section because it’s already happened. Your developer stopped responding, and you need to regain control.
Here’s how to approach recovery methodically, even when you’re stressed.
Start with Damage Control
Assess What You Have: Is your site live? Try password recovery. Search for documentation – emails, notes, automated messages.
Find Backup Contacts: Did your developer mention colleagues? They might help reach them.
Run Forensic Recovery: Use browser tools to identify the hosting provider. Contact them with proof of ownership.
What Proof You’ll Need: When contacting registrars or hosting companies, you’ll need documents proving that your business owns the website: company registration, business email matching the domain, payment records or invoices, if available, and trademark registration, if applicable. If the domain registrant is the developer’s name and the payment records are in their name, recovery becomes much harder. This is why proper ownership documentation from the start matters.
Capture Current State: Before changes, document everything – screenshot pages, export catalogs, download media, record DNS. Ask your new provider to produce a short ‘asset recovery report’ before touching anything – this creates a baseline of what exists and what’s accessible.
Choose Your Recovery Path
Option 1: Rebuild from Live Site – Extract content/design with scraping tools. Faster and cheaper. Best for simpler sites.
Option 2: Complete Migration – New hosting, full control, fresh build. More expensive but clean infrastructure you control. Best for complex sites or modernization.
Option 3: Hybrid – Preserve what works, rebuild problem areas, gradual transition. Most practical middle ground.
Secure Your Access Immediately
Once you regain control, take these security steps immediately: reset all passwords, rotate API keys and tokens, remove any old admin accounts you don’t recognize, confirm that backup systems are working, and enable two-factor authentication where possible. Don’t wait – secure your recovered access before the next crisis. Learn more about WordPress security in Nigeria.
Don’t Make Decisions Under Panic
Emergencies create urgency that leads to poor decisions: rushing into rebuilds, overpaying for “emergency” services, and choosing insecure shortcuts. Take 48 hours to assess properly. Get second opinions from two different developers.
Timeline: Simple recovery: 2-4 weeks. Complex migrations: 6-12 weeks. Complete rebuilds: 3-6 months.
Costs: Recovery assessment: β¦100,000 – β¦300,000. Migration: β¦500,000 – β¦3,000,000. Emergency premiums: 50-100%.
Warning Signs You Need to Act Now
These apply to informal arrangements with freelancers or small operators without formal SLAs. The table below helps you diagnose your current situation:
| Scenario | Red Flag (Informal Setup) | Standard (Managed Services) |
|---|---|---|
| Domain Registration | Under developer’s personal name | Provider administers, client owns |
| Hosting Billing | Developer’s personal credit card | Provider’s reseller/company account |
| WordPress Access | No clear policy, everyone admin or arbitrary | Role-based access (security-driven) |
| Documentation | “It’s in my head” | Written procedures, SLA |
| Continuity Plan | No answer to “what if you’re gone?” | Multiple team members, documented escalation |
| Account Ownership | Personal Gmail, PayPal | Company accounts (institutional) |
Red Flags in Informal Setups
Beyond what the table shows, watch for these patterns:
Access & Documentation:
- No documentation on where things are hosted or how to recover access
- Business infrastructure managed entirely through personal accounts with no company backing
- No recovery plan when asked, “What happens if you’re not available?”
Process & Structure:
- “Trust me” responses to reasonable access requests
- Everything verbal – no contracts, no SLA, no documented exit procedures
- Only personal contact methods with no business alternatives
- No backup person who knows anything about your infrastructure
What’s Normal in Professional Managed Services
The table above shows standard managed services practices. Key point: The difference is documentation, SLAs, institutional backing, and guaranteed recoverability – not who has daily operational access.
What Good Actually Looks Like
In managed services environments:
- Company-owned accounts (not personal)
- Written SLA with exit procedures
- Documented backup and recovery processes
- Multiple team members can support your account
- Clear ownership documentation
- Role-based access appropriate to your needs
- Responsive communication through business channels
In direct management setups:
- Domain and hosting under your company’s control
- Multiple people in your organization have credentials
- Password manager for secure storage
- Regular documentation updates
- Clear contracts with developers
- Repository access for custom code
Both models can be professional. The key is to match the structure to your needs and ensure accountability through documentation.
Choose the Right Model for Your Business
Developer disappearance is predictable in Nigeria: japa pressure, economic volatility, and informal arrangements without institutional backing.
Two paths: Informal arrangements (personal accounts, single points of failure, verbal promises, high risk) vs. Managed services (institutional accountability, documented procedures, contractual guarantees).
Not sure which fits? Start with an access and ownership audit.
At PlanetWeb, our managed IT services include documented processes, multiple support staff, and SLAs that protect ownership and exit rights. Reach out for consultation.
Frequently Asked Questions
Related Reading:
