Who do you need to reach? What should they do? What would count as a useful result?
A course completion, a project submission, a product test and a specialist hire each need a different delivery plan.
One process for every engagement. The final stage changes with the work: a research brief may end with accepted outputs, while a learning or adoption programme continues.
Agree who you need, what they should do and how success will be measured.
Map relevant communities, then confirm identity, skills and experience against the brief.
Onboarding, learning, technical sessions and day-to-day coordination while the work runs.
Check submissions, data and feedback against the standard your team sets.
Accepted outputs for research. Follow-up support and agreed usage tracking for everything else.
The relationships that connect the brief to people with relevant interests, experience and skills.
Curriculum, facilitation and assessment support where the programme involves skill development.
The practical arrangements that make participation and delivery possible in each market.
Participant coordination, programme workflows and records of progress and work delivered.
The mix changes with the brief. Propel's role is to make those parts work together.
We keep what we have delivered, where we have relationships and what we would assess first clearly separate, so you can judge what we can run in your market.
Mastercard Foundation in Nigeria and Kenya. Hedera across 20+ African cities. Google AI Skills Training in Portugal.
Specialised communities across 30 countries in the Propel ecosystem. Relationships are not the same as completed programmes.
Assessed on request. Tell us the market and the audience, and we will say what looks realistic before you commit.
Your objective, audience requirements, product or programme knowledge, and the access participants need to take part. For learning programmes, that may include curriculum. For testing, it includes the product and scenarios to explore.
A scoped programme, participant recruitment, coordination and support, agreed outputs and reporting. Roles, approvals and responsibilities are set before the programme begins.
Responsibilities are agreed per brief
| Compare | A focused project | A complete programme | Continuing activation |
|---|---|---|---|
| The work | A specific research question, test cycle, recruitment need or activation brief with a defined finish. | A coordinated learning pathway, developer initiative or multi-market activation with several stages. | A planned series of activities that supports community participation and product engagement over time. |
| Planning approach | Planned around one defined finish | Planned across several coordinated stages | Planned as a recurring series of activities |
| Example | A product test or a practitioner workflow pilot. | Supported AI learning for a defined audience and market. | Recurring clinics, champion support and participation reviews. |
| You receive | Recruited participants, completed tasks and a findings summary. | A recruited, supported cohort, progress reporting and a final report. | An activity calendar, participant coordination and a report each cycle. |
| Your team supplies | Product access, the questions to answer and review criteria. | Curriculum or product content, access and review standards. | Priorities, expert time and a named lead. |
| Next phase | Review the findings together and decide whether to extend. | Agreed at review: scale to new markets or move to ongoing support. | Reviewed each cycle, with scope adjusted by agreement. |
Pricing is scoped to the work. We agree delivery, responsibilities and measurement before launch.
Depending on the programme, reporting can cover recruitment, participation, completion, project output, user feedback, certification or work matches.
Each participant gets a clear task with a clear finish: test a workflow, complete a learning module, review documentation or submit structured feedback. Your team sees progress and gets the work back in a consistent format.
The participant submits a task record, observations and supporting screenshots. Your team receives feedback tied to a specific workflow, organised for review.
“Create an account and complete your first project. Record where you hesitate, capture any error and explain what you expected to happen.”
{{ q.a }}
