Questions are easier when the answers are all in one place.

Rexius Lited is a connected business and technology company providing digital systems, websites, business support, commerce, selected lifestyle services and other practical solutions. Our different platforms serve different needs, but they operate as part of one Rexius ecosystem.

No. Rexius Shop is the commerce and ticketing part of the wider Rexius ecosystem. Rexius also works in technology, systems development, business services, digital solutions, selected lifestyle services and Mental Health & Psychosocial Support through a dedicated platform.

Rexius works through a core operating structure supported by specialist collaborators and professional service partners where additional expertise is required. This allows us to remain responsive while assembling the right mix of skills for each engagement.

Yes. Some services are designed for individuals while others are built for businesses, organisations, institutions and project teams. The appropriate process depends on the service being requested.

Rexius operates from Kenya and supports work that can be delivered locally, remotely or through a combination of both, depending on the requirements of the engagement.

Yes. Rexius can design and develop systems around clearly defined workflows, users, permissions, reporting requirements, integrations and operational needs. We usually begin by understanding how the organisation currently works before deciding what should be built.

Yes. Rexius develops websites ranging from business and organisational sites to service portals and more connected digital experiences. The work can include design, development, content structure, integrations, hosting setup and ongoing support depending on scope.

Yes. In many cases improving, restructuring or integrating an existing system is more practical than replacing it. We can review the current setup, identify weaknesses and determine whether the best approach is improvement, migration, integration or a full rebuild.

Where technically possible, yes. Integrations may include payment services, email, authentication, communications platforms, reporting tools, third-party APIs and other systems required by the project.

Hosting, deployment, maintenance and technical support can be included where appropriate. The exact arrangement depends on what has been built, where it is hosted and the level of ongoing support required.

Potentially. We first need to review the available source code, hosting environment, database structure, documentation, access credentials and overall condition of the project before confirming what can safely be supported or improved.

The best starting point for a structured project is the Start with Rexius onboarding form. It gives us enough information to understand the objective, current situation, expected outcome and any important technical or operational requirements.

That is completely fine. You do not need to arrive with a technical specification. Explain the problem, the process you want to improve or the result you want to achieve. We can help determine what kind of solution makes sense.

We review the information provided, identify any major questions and determine whether the request fits the services Rexius can provide. Where appropriate, the next step may be a discussion, clarification of scope, technical review or preparation of a quotation or proposal.

For paid project work, scope and commercial terms should be agreed before substantive implementation begins. Depending on the engagement, this may take the form of a quotation, proposal, statement of work, contract or another appropriate project document.

Yes, but material changes can affect cost, timelines and implementation. Where requirements move beyond the agreed scope, we normally document the change so both sides remain clear about what is being added or altered.

Yes. Rexius can work alongside internal staff, consultants, developers, finance teams, administrators or other providers where responsibilities and access arrangements are clearly defined.

There is no single project timeline because the work varies significantly. A straightforward website and a multi-user operational system, for example, require very different levels of discovery, development, testing and implementation. Timelines are therefore agreed according to scope.

Pricing depends on the work involved, required expertise, complexity, integrations, delivery period and level of ongoing support. For structured engagements, we prefer to understand the requirement before giving a meaningful price.

Payment arrangements depend on the service or project. Larger engagements may be structured around deposits, milestones or agreed payment schedules, while some products and services may require payment at the point of purchase.

Available payment methods depend on the service or platform being used. Rexius Shop provides the payment options available for commerce transactions, while project and business engagements may use separately agreed payment arrangements.

Yes. Business and institutional engagements can be supported with the relevant commercial documentation required for the transaction, subject to the nature of the service and agreed terms.

Products, tickets and other commerce transactions available through Rexius are handled through the dedicated Rexius Shop at shop.rexiuslited.co.ke.

Yes. The Shop is part of Rexius, but it has its own commerce environment because orders, payments, tickets and transaction tracking require different functionality from the corporate website.

Order tracking is handled within the Rexius Shop. Use the tracking tools provided there with the relevant order information supplied during your transaction.

Use the support options provided through Rexius or the Shop and include enough information to identify the transaction, such as the order reference and the contact details used when placing the order. Avoid sending sensitive payment credentials.

Mental Health & Psychosocial Support is provided through the dedicated Rexius MHPSS platform at mhpss.rexiuslited.co.ke.

MHPSS has different service pathways, content and privacy considerations from ordinary business and technology services. Keeping it in a dedicated environment makes the experience clearer and avoids mixing support-related interactions with general commercial enquiries.

For MHPSS-related support, use the dedicated MHPSS platform wherever possible. General Rexius contact channels are better suited to company, technology, commerce, partnership and business enquiries.

Use the communication or support channel established for your project where one exists. For general follow-up, you can also contact Rexius by email or WhatsApp and provide enough information for us to identify the relevant service or project.

Tell us what you were trying to do, what happened instead, which page or system was involved and whether the issue can be reproduced. Screenshots and exact error messages are particularly useful, but passwords and other sensitive credentials should not be sent through ordinary messages.

Yes, where post-launch support is included in the engagement or arranged separately. Support can cover maintenance, technical troubleshooting, improvements, updates and further development depending on the agreed arrangement.

Yes. Many digital products evolve after people begin using them. We can continue improving functionality, usability, workflows and integrations as new needs emerge.

Information required for a project should be used only for legitimate delivery, support and operational purposes associated with the engagement. Where projects involve sensitive organisational data or system access, the necessary access and handling arrangements should be agreed as part of the work.

As a general rule, avoid sending passwords, secret keys, full payment credentials or other highly sensitive access information through ordinary messages. Where credentials are required for technical work, a more appropriate access method should be agreed.

Sometimes. A migration, repair, integration or system review may require temporary access to hosting, databases, administrative panels or third-party services. We only ask for access that is relevant to the work being performed.

Ownership and usage rights depend on the nature of the engagement, third-party software involved and the commercial terms agreed for the project. These matters should be made clear in the relevant quotation, agreement or project documentation.

Yes. Rexius is open to relevant commercial, technical, institutional and service partnerships where the relationship creates a clear benefit and fits the direction of the company.

Yes. Some engagements require specialist skills beyond the core operating team. Rexius may work with independent professionals, technical specialists and service partners according to project requirements.

Current vacancies, consultancy opportunities and other openings are published through the Careers & Opportunities section when available.

It is better to apply through an advertised opportunity where one exists. This makes it easier to match applicants to actual requirements and ensures applications follow the intended process.