Service providers with a proven capability to design, develop, implement, publish, maintain and support a secure, scalable and user-friendly mobile application

Google Play Store and the Apple App Store. It should support both authenticated and nonauthenticated user journeys, where applicable, and must align with RAF’s business, technology, enterprise architecture, information security, privacy, accessibility, integration and governance requirements.

{"closingTime":"11:00"}

{"name":null,"email":"[email protected]","phone":null,"department":"ies, and support the development of any","address":null}

BIDDER NAME: ___________________________________________________ Please select one of the options below (Tick) OEM (Owner of the technology) Accredited Partner /Reseller

evaluation or future procurement considerations.

evaluation and comparison of submissions.

secure user registration and authentication where required, enable relevant self-service functionality,

• Describe the approach to testing, quality assurance, release management, app store

Describe the core mobile application functionality proposed for RAF, including self-service, information

messaging, alerts, reminders and user consent preferences.

maintenance and ongoing technical support.

3.13. Provide implementation, change management, training, documentation, knowledge transfer

and support services

secure user registration and authentication where required, enable relevant self-service functionality,

provide notifications and alerts where applicable, and integrate securely with RAF back-end systems,

approved third-party services and enabling digital platforms.

RAF is issuing this Request for Information (RFI) to obtain market input from suitably qualified service

providers on available mobile application solution capabilities, delivery models, technology

approaches, integration options, security controls, publishing and release management processes,

support arrangements and relevant implementation experience in comparable environments.

available mobile application development and support options, refining its functional and technical

requirements, validating implementation feasibility, and informing any subsequent procurement

strategy or sourcing approach.

4.1. Identify and assess the availability, maturity and suitability of mobile application solutions,

development approaches and service delivery models that can support RAF’s strategic

objective to modernise digital service access and improve stakeholder engagement through a

secure, scalable and user-friendly mobile application.

4.2. Assess proposed mobile application architectures, technology stacks, development

frameworks, deployment models and integration approaches, including their ability to integrate

securely with RAF’s existing internal systems, approved third-party platforms, identity services,

notification services and analytics platforms.

4.3. Evaluate the extent to which proposed mobile application capabilities can support secure digital

self-service, user registration and authentication, service requests, status updates, document

or media uploads, notifications, in-app communication and other relevant mobile user journeys.

4.4. Assess the capacity, capability and implementation readiness of potential service providers to

design, build, publish, maintain and support the mobile application within a complex, high-

volume and highly regulated public-sector environment, including the ability to deliver through

a phased and controlled implementation approach.

4.5. Obtain sufficiently detailed information on respondents’ mobile application functionality, user

experience approach, security controls, privacy and compliance measures, implementation

methodology, pricing assumptions, support model, app store publishing approach and relevant

reference implementations to enable RAF to assess capability, fit-for-purpose and

implementation readiness.

4.6. Enable RAF to determine whether further market engagement activities, such as

demonstrations, clarification sessions, presentations or technical deep-dive discussions, are

required to validate mobile application capability, delivery approach, user experience, security,

integration and strategic alignment.

4.7. Use the information submitted in response to this RFI to inform RAF’s mobile application

strategy, refine business, functional and technical requirements, validate implementation

assumptions, identify market risks and opportunities, and support the development of any

subsequent procurement strategy or sourcing approach.

5.1. A company profile, including organisational overview, financial standing, mobile application

design, development, deployment, maintenance and support experience, and a minimum of

two contactable client references for comparable mobile application assignments.

5.2. A conceptual overview of the proposed mobile application solution or delivery approach,

including core functionality, Android and iOS support, user experience approach, architecture,

hosting or deployment model, configurability, integration capability, security controls and

alignment to RAF’s stated requirements.

5.3. A presentation, demonstration, prototype, wireframe, application screenshots, reference

application material or other supporting information sufficient to illustrate the maturity, usability,

accessibility, security and key capabilities of the proposed mobile application solution.

5.4. An indicative implementation methodology, high-level delivery timelines, key project phases,

resource assumptions, app store publishing and release management approach, support and

maintenance model, and preliminary costing information to support RAF’s assessment of

implementation feasibility and total cost of ownership.

6.1. The information requested in this section is intended to enable RAF to undertake a structured

assessment of available market offerings, solution capabilities, and service delivery models,

and to determine the extent to which such offerings align with RAF’s preliminary business and

technical requirements.

6.2. The information submitted will assist RAF in refining and validating its business and technical

requirements, identifying functional and implementation gaps, and informing any subsequent

procurement strategy, sourcing approach, or solution design decisions.

6.3. The questions set out below are designed to elicit detailed information on current mobile

application capabilities, proposed delivery approach, user experience, platform support,

integration readiness, scalability, security, support model, future extensibility and innovation

potential relevant to RAF’s mobile application requirements.

6.4. Mobile application knowledge, capacity and experience

or deployment model and rationale for the recommended approach.

dependencies, governance approach and key implementation risks.

solution, implementation approach, hosting model, integration requirements, support arrangements, or long-term sustainability that may affect RAF’s

evaluation or future procurement considerations.

suitability, refining requirements, validating implementation assumptions, or shaping any subsequent procurement or solution design approach.

1. Responses to this RFI must be clear, concise, complete and sufficiently detailed to enable RAF to assess the respondent’s solution capability, implementation

approach and overall suitability.

the borders of the country. The RAF head office is in Centurion and RAF intends to establish Customer

Experience Centres (CEC) in each province in the country.

The Road Accident Fund (RAF) is exploring the market for suitably qualified and experienced service

providers with proven capability to design, develop, implement, publish, maintain and support a secure,

scalable and user-friendly mobile application.

The proposed mobile application is intended to support RAF’s digital modernisation agenda by

improving access to RAF services, enhancing stakeholder engagement, reducing reliance on physical

service channels, and enabling more convenient digital interaction with claimants, road users and other

authorised stakeholders.

capability, technical maturity and relevant implementation experience in the design, development,

deployment, maintenance and support of a secure, scalable and integrated mobile application for the

errors, exceptions and customer experience indicators.

control, monitoring, incident management, maintenance and ongoing support.

integration costs, support and maintenance costs, third-party service costs, app store-related costs and any optional or usage-based charges.

3. Respondents must provide clear pricing assumptions to support RAF’s understanding of the indicative total cost of ownership over a five-year period. At a

minimum, respondents must disclose assumptions relating to the commercial basis of pricing, pricing validity period, user volumes, transaction volumes,

supported mobile platforms, included functionality, integration scope, hosting model, environments, app store publishing, security testing, support levels,

release frequency, third-party services, escalation rates, exclusions and costs that may vary based on usage, scope expansion or changes to RAF

requirements.

Price Y1 Price Y2 Price Y3 Price Y4 Price Y5 Total Price

No specific requirements found

management, vulnerability management and audit logging.

records management and secure handling of personal information.

The Road Accident Fund (RAF) is a schedule 3A public entity established in terms of the Road

Accident Fund Act, 1996 (Act No. ), as amended. Its mandate is the provision of compulsory

social insurance cover to all users of South African roads, to rehabilitate and compensate persons

injured as a result of the negligent driving of motor vehicles in a timely and caring manner, and to

actively promote the safe use of our roads.

Indicate the type of bidding structure by marking with an ‘X’: Individual bidder Joint venture Consortium Using subcontractors Other

Publish date: 18/06/2026 closing date: 10/07//2026 closing time: 11:00 a.M.