web11 Technologies · Nairobi, Kenya
How SME Onboarding Works with web11
A simple, transparent onboarding process helps a business bring its websites, apps and technical requests into a manageable working relationship.
1. Create your business account
Start by creating an account on the web11 platform with a business email and the requested account details. Use an address the company can continue to access if a staff member changes role. Keep recovery methods and account ownership under business control, and do not send passwords in a public form or an unsecured message.
After registration, add the business information that helps us understand who is requesting work and how to follow up. Account setup does not itself transfer ownership of your domain, hosting or software. Those remain under your control unless a separate, authorized change is agreed with the relevant provider.
2. Add your business and describe the systems
List the website, mobile app, hosting, database or business software you want help with. For each system, note its purpose, who currently manages it, where it is hosted if known, and any recurring issue or planned change. If something is unknown, say so; discovering missing access is a normal part of onboarding.
You can also explain which systems are most important to day-to-day operations and what would happen if they were unavailable. This helps the team prioritize review and identify dependencies before maintenance work begins. Avoid sharing sensitive credentials in a request; we can agree an appropriate access method for the work.
3. Confirm ownership and authorized access
Before taking responsibility for a system, confirm that the business owns or is authorized to administer the domain, source code, hosting plan, app-store account and connected services. If a previous developer or employee controls an account, use the provider’s official transfer and recovery process. A contractor should receive only the access required for agreed duties.
We review the access available, backups, environment configuration and any useful documentation. This step protects continuity and helps distinguish a simple content change from a system that needs technical remediation. If access cannot be confirmed, we explain what is needed and what work should wait until ownership is clear.
4. Review the current state and agree priorities
web11 discusses the business goals, existing risks and near-term requests with the people who know the systems. We identify what can be verified, what should be investigated and which tasks have the greatest user or operational impact. The output is a practical next-step list, not an assumption that every system must be replaced.
We then agree how requests will be submitted, how work is estimated, who approves changes and what support expectations apply. The service scope, communication channel and any third-party costs should be clear before ongoing work is scheduled. A gradual handover can start with one website or application and expand as each system is understood.
5. Manage requests and keep improving
Once onboarding is agreed, use the account to share updates, context and priorities. A request might be to correct a website page, investigate an app issue, add a feature or plan an infrastructure change. The team can ask questions, estimate the work and agree a sequence that reflects urgency and dependencies.
Regular reviews help ensure the arrangement still fits the business. New staff, services, regulations and software changes can alter priorities. Keep a current list of systems and owners, review access periodically and raise changes early when they affect important customer or staff workflows. The goal is a clear partnership in which the SME remains informed and in control.
Frequently asked questions
Does creating an account automatically transfer our IT systems?
No. Account creation starts the working relationship. Ownership and provider access change only through a separate authorized process.
What should I prepare before onboarding?
Gather a list of important websites and apps, business owners, known hosting providers, key issues and upcoming priorities. Do not send passwords in a public form.
Can web11 take over from an old developer?
Yes, after the business confirms ownership and arranges authorized access. We review code, accounts, backups and deployment before agreeing a takeover plan.
Can we start with one website and add other services later?
Yes. A phased onboarding can begin with one system and expand as access, condition and priorities are understood.
Who decides which requests web11 works on?
The business sets priorities and approves scope. web11 provides technical input, estimates and recommendations for an informed decision.
Need a dependable technology partner?
Tell web11 what your business needs. We’ll help you choose a practical next step.