External opportunity

Request for Proposal WAZZII Platform Feature Development and Service Design

GirleffectPosted 29/10/2026

CareerCraft Connections does not place you into this role

This is a listing we found and linked to. The employer screens, interviews and hires; there is no CareerCraft Connections assessment, no reservation and no placement fee. Our own placements are at Attachments.

About this role

<h2>Who We Are</h2> Girl Effect is an international non-profit that builds media and technology girls choose, use and trust. Across Africa and South Asia, our youth brands — including Wazzii and Tuki in Kenya, Big Sis in South Africa, Chhaa Jaa and Bol Behen in India, and Yegna in Ethiopia — reach millions of adolescent girls and young women (AGYW) with content and digital tools that support the decisions shaping their lives, from sexual and reproductive health (SRH) to wellbeing, education and work. Our approach is girl-centred by design: girls co-create our products, our evidence teams measure what actually changes for them, and our safeguarding architecture treats their safety as a design constraint, never an afterthought. Girl Effect has spent a decade building conversational products for young people, and several years deliberately and publicly charting what responsible technology for girls looks like.  <h2>What is WAZZII</h2> Today. WAZZII is Girl Effect’s WhatsApp-based chatbot for AGYW in Kenya, offering confidential SRH information, signposting and human help desk support in English and Sheng. It draws on a decade-deep corpus of more than 50 million questions young people have asked our chatbots — one of the richest datasets in existence on what girls actually want to know. Human help desk operators, working on the RapidPro help desk, remain central to the experience. The next evolution of its design. Over the coming two years, WAZZII will evolve from a conversational companion into a trusted service-navigation platform: girls will move from a conversation to finding a real, vetted, youth-friendly provider nearby; prepare for the visit with confidence; access services using codes issued in the chat; and be supported to continue afterwards — with verified loops confirming a girl was actually served. Tens of thousands of girls are expected to use these capabilities directly, and the learning will shape Girl Effect’s chatbot portfolio globally. This tender selects the partner for the service design and platform engineering behind that evolution. <h2>The Girl Effect Tech Stack</h2> Girl Effect has built an ecosystem of technologies which underpin its user-facing solutions. By using the existing tech stack, we ensure our in-country teams can focus their time and budget on delivering impact. The stack consists of: <ul> <li>RapidPro: Low-code chatbot building platform through which we connect to instant messaging platforms, build out user engagement pathways including informational content, quizzes and surveys, and connect to other tools via API. Hosted on partner org’s multi-tenant AWS infrastructure</li> </ul> Wagtail: Python-based CMS, used to build our user-facing websites. Connects to RapidPro via API to provide structured content such as service directories. Self-hosted on AWSIntelligence Module: GE’s self-built tool to manage connectivity with LLMs. Connects via API to RapidPro to build user-facing GenAI workflows.Self-hosted on AzureAPIs: Manage connections between the different tools in the system. Self-hosted on AWS We are open to suggestions of changes that could be made to the stack which would provide tangible benefits to our programmatic output, whether through improved functionality or cost efficiencies. Objective  To appoint an experienced technology and service-design partner to design, build, test, deploy and support the next phase of WAZZII as a safe, accessible and measurable service-navigation platform for adolescent girls and young women in Kenya. The engagement will follow a service-design-led approach, with user needs, safeguarding requirements and tested service journeys informing the final technical build. <h2>What You will do</h2> Girl Effect is seeking an experienced partner to deliver WAZZII’s next evolution through a human-centred design approach: service design leads, and engineering follows. The partner’s senior service designer works with girls, operators and the Girl Effect team to understand needs, shape journeys and define the feature requirements — and the build then delivers against those requirements. The partner will build on WAZZII’s existing stack and be onboarded to current systems and documentation at inception. AI functionality is not in scope of this TOR. Service design. Key activities include: <ul> <li>Co-creation workshops with young people — multiple rounds across the engagement, designed and facilitated with Girl Effect — shaping the finder, the redemption moment, visit preparation and continuation support around how girls actually live, move and pay</li> <li>Design sprints with the Girl Effect team — per feature cluster, turning co-creation insight and programme requirements into tested, buildable designs before engineering begins</li> <li>End-to-end journey mapping — from first conversation to provider visit to continuation, kept current as the build evolves</li> <li>Escalation flow design — with Girl Effect’s safeguarding team, so every journey has a safe, human path out</li> <li>Service blueprint for the redemption moment — the seconds at the pharmacy counter where the whole service succeeds or fails for a girl</li> <li>Feature requirements definition — workflow maps and functional requirement packs per feature cluster — the outputs that define what gets built, for this engagement and for future platform capabilities</li> <li>Design QA — on every girl-facing feature, including accessibility and low-bandwidth performance</li> </ul> Feature development. Many of the features likely to be built as part of these requirements include, but are not limited to: <ul> <li>Code redemption system — girls receive single-use codes in the chat that unlock services at participating pharmacies and clinics. The partner builds the full lifecycle: secure code generation, delivery in-chat, validation at the counter, and reconciliation — with anti-fraud controls (single-use enforcement, expiry, anomaly detection) and reliable performance on low-end devices and patchy connectivity</li> <li>Provider dashboard — a simple web dashboard for participating pharmacies and clinics: validate a girl’s code in seconds at the counter, track stock of supported products, view redemption history and reconciliation status, and access basic reporting. Designed for busy counter staff with minimal training, on the devices providers actually have</li> <li>Geolocation & provider finder — a girl shares her area in the chat and receives the nearest vetted youth-friendly providers — services offered, opening hours, indicative pricing, and simple directions. Provider records are managed by Girl Effect through an admin interface; the directory exposes open APIs so future partner services can be surfaced</li> <li>Structured chat journeys — new structured flows in Sheng and English — method exploration, visit preparation, follow-up scheduling — authored by Girl Effect, implemented and instrumented by the partner so every journey step is measurable</li> <li>Cost comparison tool — a lightweight in-chat calculator letting girls compare the costs of methods and services across provider types, supporting informed choice before a visit</li> <li>Help desk enhancements — workflow improvements on the existing RapidPro help desk — routing, tagging, queue management and reporting for operators.</li> <li>Code generation tools — bulk and offline code generation for on-ground activations and community events, with attribution so redemptions can be traced back to the channel that issued them</li> <li>Quality, security & operations — QA throughout; security audit and penetration test before any girl-facing launch; hosting and infrastructure; maintenance and bug-fix support through the engagement</li> </ul> <h2>Scope Confirmation and Change Control</h2> The feature descriptions above represent the anticipated scope. The final feature requirements will be confirmed through the inception and service-design stages. To control scope and cost: <ul> <li>Each feature cluster must have an approved requirements pack and acceptance criteria before development begins.</li> <li>No material change to the agreed scope, cost or timeline may proceed without written approval from Girl Effect.</li> <li>Proposed changes must document the rationale, impact on costs, timeline, security, dependencies and other deliverables.</li> <li>Work completed without the required written approval may not be eligible for payment.</li> <li>Girl Effect may prioritise, defer or remove features based on user evidence, technical feasibility, available budget or programme priorities.</li> <li>Girl Effect may commission optional or future features through separately approved work orders or contract amendments.</li> </ul> <h2> Deliverables</h2> Service design <table> <tbody> <tr> <td> Deliverable </td> <td> Description </td> </tr> <tr> <td> Co-creation workshop rounds </td> <td> A minimum of three rounds with young people across the engagement, each with documented outputs feeding directly into design decisions </td> </tr> <tr> <td> Design sprint outputs </td> <td> Sprint per feature cluster with the Girl Effect team: tested prototypes, decisions log, and buildable specifications </td> </tr> <tr> <td> Journey maps </td> <td> End-to-end maps maintained across the engagement </td> </tr> <tr> <td> Escalation flow designs </td> <td> Safeguarding-approved designs for every journey </td> </tr> <tr> <td> Redemption service blueprint </td> <td> Counter-moment blueprint validated with providers and girls </td> </tr> <tr> <td> Feature requirements packs </td> <td> Workflow maps and functional requirements defining each feature cluster before build </td> </tr> <tr> <td> Design QA reports </td> <td> Per release, covering accessibility and low-bandwidth performance </td> </tr> </tbody> </table> Development features The final feature set is confirmed through the service design process; the deliverables below reflect the features currently anticipated. <table> <tbody> <tr> <td> Deliverable </td> <td> Description </td> </tr> <tr> <td> Code redemption system live </td> <td> End-to-end generation, delivery, validation and reconciliation in production, with anti-fraud controls and monitoring </td> </tr> <tr> <td> Provider dashboard live </td> <td> Deployed to participating facilities with onboarding materials and admin tooling </td> </tr> <tr> <td> Provider finder live </td> <td> Geo-located directory in the chat experience, with the admin interface and open APIs documented </td> </tr> <tr> <td> Structured chat journeys live </td> <td> Agreed RapidPro Flow journeys set implemented, instrumented and released </td> </tr> <tr> <td> Cost comparison tool live </td> <td> In-chat calculator released </td> </tr> <tr> <td> Help desk enhancements live </td> <td> RapidPro workflow improvements deployed to the operator team </td> </tr> <tr> <td> Code generation tools live </td> <td> Bulk/offline generation with channel attribution, in the hands of the on-ground team </td> </tr> <tr> <td> Security & launch readiness </td> <td> Security audit and penetration test passed; QA reports; release briefs to operators and content team per deployment </td> </tr> <tr> <td> Operations </td> <td> Hosting live; maintenance and bug-fix support; documentation and handover materials </td> </tr> </tbody> </table>   <h2>Technical and Operational Requirements</h2> The proposed solution should: <ul> <li>Be secure, scalable, maintainable and suitable for future expansion.</li> <li>Work effectively on low-end devices and under limited connectivity conditions.</li> <li>Apply privacy-by-design and data-minimisation principles.</li> <li>Use documented and supportable technologies.</li> <li>Integrate with Girl Effect’s approved systems and interfaces.</li> <li>Provide appropriate audit logs, access controls and administrative permissions.</li> <li>Support secure backup, restoration and business-continuity arrangements.</li> <li>Avoid unnecessary collection or exposure of personal and sensitive information.</li> <li>Meet agreed accessibility and usability standards.</li> <li>Provide clear operational monitoring and error reporting.</li> <li>Avoid unreasonable dependency on proprietary tools or a single supplier.</li> </ul> Bidders must identify all third-party software, services, licences and recurring costs required for the proposed solution. <h2>Project Management and Working Arrangements</h2> The engagement will be managed by Girl Effect’s Product and Delivery Lead. The successful partner will: <ul> <li>Work through two-week delivery sprints.</li> <li>Use Girl Effect’s agreed Jira or programme management environment.</li> <li>Participate in weekly delivery meetings.</li> <li>Maintain an updated delivery plan, risk register, issues log and decisions log.</li> <li>Provide concise sprint and monthly progress reports.</li> <li>Demonstrate completed work at agreed sprint reviews.</li> <li>Escalate material delays, dependencies, security risks and safeguarding concerns promptly.</li> <li>Ensure that each production release is supported by appropriate technical and operational documentation.</li> </ul> <h2>Who You Are</h2> <ul> <li>Relevant experience delivering large-scale digital platforms, chatbot services, dashboards, system integrations or comparable solutions.</li> <li>Strong service design and participatory design capability.</li> <li>Experience designing digital services for young people or users in sensitive contexts.</li> <li>Experience with WhatsApp, RapidPro or comparable conversational platforms.</li> <li>Strong software engineering, quality assurance, security and deployment practices.</li> <li>Ability to integrate with and improve an existing technology environment.</li> <li>Capacity to provide implementation and post-launch support in Kenya.</li> <li>Appropriate safeguarding, data-protection and information-security controls.</li> <li>Financial and operational capacity to deliver the assignment.</li> </ul> <h2>Proposal Submission Requirements</h2> Bidders must submit separate technical and financial proposals (Max 10 pages). <h3>Technical Proposal</h3> The technical proposal should include: <ul> <li>Understanding of the assignment and proposed solution.</li> <li>Service-design and participatory-research approach.</li> <li>Proposed technical architecture and integration approach.</li> <li>Delivery methodology, workplan, sprint structure and key milestones.</li> <li>Quality-assurance, testing and release-management approach.</li> <li>Safeguarding, data-protection and security approach.</li> <li>Hosting, maintenance and support model.</li> <li>Proposed project team, roles, CVs and level of effort.</li> <li>Relevant organisational experience and at least three comparable assignments.</li> <li>At least three client references.</li> <li>Key assumptions, dependencies, risks and exclusions</li> </ul> <h3>Financial Proposal</h3> The financial proposal must be submitted in USD and include: <ul> <li>A fixed price by deliverable and implementation phase.</li> <li>Personnel roles, professional rates and level of effort.</li> <li>Hosting, infrastructure and recurring costs.</li> <li>Third-party licence and service costs.</li> <li>Maintenance and support costs.</li> <li>Applicable taxes shown separately.</li> <li>Proposed reimbursable expenses shown separately.</li> <li>Optional feature or enhancement rates, where relevant.</li> <li>Clear assumptions, dependencies, exclusions and pricing conditions.</li> </ul> <h1>Evaluation</h1> Proposals will be evaluated in the following order: <ul> <li>Pre-screening;</li> <li>Technical evaluation;</li> <li>Pitch, demonstration or clarification stage, where required; and</li> <li>Financial evaluation.</li> </ul> Evaluation Criterion <ul> <li>Relevant organisational experience and comparable platform delivery 15%</li> <li>Service-design and participatory-design capability 15%</li> <li>Quality and feasibility of the technical approach 20%</li> <li>Security, data protection, safeguarding and quality assurance 10%</li> <li>Proposed team, delivery plan and Kenya support model 10%</li> </ul> Technical Total 70% <ul> <li>Financial proposal and overall value for money 30%</li> </ul> Total 100% Girl Effect may: <ul> <li>Request written clarifications;</li> <li> Invite shortlisted bidders to a pitch or technical demonstration;</li> <li>Conduct reference checks and due diligence;</li> <li>Request a best-and-final offer; or</li> <li>Negotiate the final scope, work plan and commercial proposal with the preferred bidder.</li> </ul> The lowest-priced proposal will not necessarily be selected. <h1>Project Timelines</h1> <ul> <li>Terms of reference published: 29th October 2026</li> <li>Questions/Clarification Deadline: 4th November 2026</li> <li>Consolidated FAQ shared with all prospective bidders: 6th November 2026</li> <li>Deadline for proposal submission: 13th November 2026</li> <li>Inception: onboarding to existing stack; interfaces defined; design sprint 1 and co-creation round 1- Months 1–2 post-contract</li> <li>Build releases (redemption system, dashboard, finder first)- Months 2–6</li> <li>Co-creation rounds 2–3; design sprints per feature cluster- Months 2–5</li> <li>Security audit and launch readiness-Month 6</li> <li>Operations, maintenance and iteration- Month 7 onward</li> </ul>   Timings are indicative and will be finalised at contracting; deliverable acceptance, not elapsed time, triggers payment milestones. <h2>Clarification Process</h2> Bidders may submit clarification questions to suppliers@girleffect.org by 4th November 2026 The email subject should state: Clarification Question – WAZZII Platform Tender To ensure a fair and transparent open-tender process: <ul> <li>Girl Effect will not provide substantive answers to all bidders.</li> <li>All relevant questions and responses will be compiled into a consolidated FAQ.</li> <li>The FAQ will not identify the organisation that submitted each question.</li> <li>The consolidated FAQ will be shared with all prospective bidders through the same publication or communication channels used for the RFP.</li> <li>Bidders are responsible for reviewing the FAQ and any formal tender updates before submitting their proposals.</li> <li>Verbal information or guidance will not amend the RFP unless confirmed by Girl Effect in writing.</li> </ul> Girl Effect may decline to answer questions received after the clarification deadline. <h2>How to Apply</h2> Submit the technical and financial proposals as separate attachments to: suppliers@girleffect.org Applications must be received by 13 November 2026 Use the email subject: WAZZII Platform Feature Development and Service Design – Kenya Late, incomplete or incorrectly submitted proposals may not be evaluated. Girl Effect may contact only shortlisted bidders. Unsuccessful bidders will be notified following completion of the procurement process. <h2>General and Commercial Terms</h2> <ul> <li>Contracting: The successful bidder will sign Girl Effect’s standard services agreement, statement of work and applicable data-processing and information-security documentation.</li> <li>Payment: Payments will be linked to the satisfactory completion and written acceptance of agreed deliverables. Girl Effect may withhold payment for incomplete, defective or unapproved work.</li> <li>Pricing: The agreed implementation pricing will remain fixed unless a change is approved through the formal written change-control process.</li> <li>Expenses: Only reasonable expenses approved in writing in advance will be reimbursable. Reimbursable expenses must be supported by appropriate documentation.</li> <li>Intellectual Property: Girl Effect will own all foreground intellectual property, deliverables, source code, configurations, designs and documentation created specifically under the engagement, subject to agreed treatment of pre-existing tools and third-party materials.</li> <li>Source Code and Access: The partner must maintain current source code and documentation in repositories approved by Girl Effect and provide Girl Effect with appropriate administrative access throughout the engagement.</li> <li>Open-Source and Third-Party Components: All open-source and third-party components must be disclosed, appropriately licensed, maintained and approved for use.</li> <li>Confidentiality and Data Protection: The partner must protect Girl Effect’s confidential information and personal data and comply with applicable data-protection requirements.</li> <li>Safeguarding and Conduct: Appointment is subject to satisfactory due diligence, reference, safeguarding, information-security and compliance checks. The successful bidder must comply with Girl Effect’s code of conduct, safeguarding and anti-fraud requirements.</li> <li>Subcontracting: No material part of the assignment may be subcontracted without Girl Effect’s prior written approval. The lead bidder remains responsible for all subcontracted work.</li> <li>Warranties and Defects: Bidders should propose a warranty period during which defects in accepted deliverables will be corrected at no additional cost.</li> <li>Conflicts of Interest: Bidders must disclose any actual, potential or perceived conflict of interest.</li> <li>Tender Costs: Girl Effect will not reimburse costs incurred in preparing or submitting a proposal or participating in clarification, pitch or negotiation stages.</li> <li>Right to Award: Girl Effect may clarify, negotiate, amend, suspend or cancel the procurement; reject any or all proposals; award the full or partial scope; award in phases; or make no award.</li> <li>No Commitment: Publication of this RFP does not constitute a commitment to enter into a contract.</li> <li>Equal Opportunity: Girl Effect welcomes submissions from qualified organisations that meet the stated regulatory, technical and service requirements.</li> <li>Proposal Validity: Proposals must remain valid for 90 days from the submission deadline.</li> </ul>