- ModulesFunding readiness, programmes, M&E
- LocalisationCountry evidence mapping
- ReportingQuarterly · donor format
- IntegrationsSAP B1 · DocuSign · Workday
Built for institutional deployment, not one-size-fits-all subscriptions.
Mothusi deployments are priced around the reality of your programme, country, sector, or institution: SME volume, modules required, localisation, reporting, integrations, support, data governance, and sector depth. A 100-business pilot, a national funding-readiness platform, an agriculture field-support programme, and a multi-country DFI deployment should not be priced the same way.
Scoped with the partner, not sold from a price list.
A deployment-pricing conversation usually covers seven things.
After scoping, partners receive a deployment model, implementation assumptions, pricing structure, and recommended rollout path.
- 01SME volume and expected growth
- 02Programme or institutional scope
- 03Modules required
- 04Localisation and sector configuration
- 05Data, reporting, and M&E requirements
- 06Integration and governance needs
- 07Implementation support and SLA model
Five deployment models, structured around how partners actually buy, test, scale, and govern Mothusi.
Many partners begin with a pilot and expand into programme, institutional, sector, or multi-country deployment.
01 Design a pilotPilot Deployment
Test the MGS model with a focused cohort.
Institutions that want to validate MGS with a defined group of SMEs, sector, region, or programme before scaling.
Use cases- SME readiness pilot
- Funding-readiness cohort
- Agriculture programme pilot
- Youth or women enterprise cohort
- Supplier-development test deployment
- DFI innovation or proof-of-concept programme
Includes- Mothusi access for participating SMEs
- MGS baseline assessments
- SME cockpit and journey
- Programme dashboard
- Basic evidence tracking
- Light localisation
- Admin onboarding
- Pilot impact summary
Best suited for- 50 to 500 SMEs
- 3 to 6 month pilots
- Single country, region, sector, or cohort
02 Price a programme deploymentProgramme Deployment
Run targeted programmes around measurable SME movement.
Accelerators, ESD programmes, supplier-readiness initiatives, funding-readiness programmes, agriculture development programmes, and cohort-based interventions.
Use cases- Bankability programme
- Supplier readiness programme
- Agriculture commercialisation programme
- Women-owned SME programme
- Youth enterprise programme
- MSME formalisation programme
- Learning-to-action programme
Includes- Programme setup and cohort onboarding
- MGS diagnostics and baseline scoring
- Issue-cluster identification
- Contextual intervention mapping
- Learning, mentor, funding, and network routing
- Monthly or periodic reporting
- Programme dashboards
- Evidence outputs and impact reporting
Programme design maps to- MGS stage
- Target transition
- Issue clusters
- Target levers
- Required evidence outputs
- Funding-readiness goals
- Sector-specific outcomes
Best suited for- 500 to 5,000 SMEs
- Programme-duration deployments
- Single or multiple cohorts
- Institution-led SME support programmes
03 Request institutional pricingInstitutional Platform Licence
Deploy MGS as SME growth infrastructure.
Governments, DFIs, SME agencies, national entrepreneurship platforms, enterprise-development institutions, banks, and ecosystem partners supporting SMEs across multiple programmes, regions, or sectors.
Use cases- National SME readiness platform
- DFI portfolio support platform
- Multi-programme SME development infrastructure
- Bank or fintech SME preparation ecosystem
- Government enterprise-development platform
- Large-scale ESD or supplier-development infrastructure
Includes- Multi-programme management
- Multi-cohort dashboards
- Role-based institutional access
- Advanced reporting and M&E
- Country evidence mappings
- Funding-readiness workflows
- Localisation and configuration
- Data governance support
- Integrations and API access
- Implementation support
- Training and capacity building
- Support and SLA options
Best suited for- 5,000 to 100,000+ SMEs
- Multi-year deployments
- National, institutional, or multi-region platforms
- Large ecosystem partners
04 Explore sector deploymentSector-Specialised Deployment
Add sector intelligence on top of the MGS framework.
Sectors where generic SME support is not enough. Agriculture is the flagship example; other sector modules can be configured per partner.
Sector workflows- Commodity Diagnostics
- Farm Visits
- Vet Dispatch
- Production and seasonality tracking
- Offtake and buyer evidence
- Input planning
- Agri-funding readiness
- Field programme reporting
- Climate and production risk tracking
Other sector modules- Manufacturing
- Construction
- Retail
- Tourism
- Services
- Technology
- Creative industries
Pricing depends on- Sector module selected
- Number of SMEs or producers
- Number of field users
- Workflow complexity
- Specialist roles required
- Reporting requirements
- Integration needs
- Country and sector localisation
05 Discuss a multi-country partnershipMulti-Country Partnership
Scale a common SME growth framework across countries.
Development institutions, regional programmes, DFIs, foundations, and ecosystem partners operating across multiple markets.
Use cases- Cross-border cohort coordination
- Shared evidence framework with local adapters
- Multi-country donor reporting on common indicators
- Comparative outcome analysis across markets
Includes- Shared MGS methodology
- Country-specific evidence mappings
- Local programme configuration
- Multi-country dashboards
- Comparative impact reporting
- Local language and currency support
- Sector adaptations
- Governance and data-model alignment
Best suited for- Regional development programmes
- Multi-country DFI initiatives
- Global SME support partnerships
- International donor-funded deployments
Pricing is shaped by your real deployment requirements.
Mothusi deployment pricing is not based on a generic per-seat model. It is shaped by the operating requirements of your SME ecosystem. Below are the factors we discuss during scoping, the components most deployments include, and the public-sector structuring options.
- 01Number of SMEs supported
- 02Number of programmes or cohorts
- 03Number of countries or regions
- 04Modules required
- 05Sector specialisations
- 06Mothusi usage requirements
- 07Evidence and verification depth
- 08Learning and programme configuration
- 09Mentor, funding, and network workflows
- 10Reporting and M&E requirements
- 11Data governance requirements
- 12Integrations and API access
- 13Support and SLA level
- 14Implementation and localisation scope
- 01Platform access
- 02Implementation and configuration
- 03SME volume band
- 04Module access
- 05Mothusi AI usage
- 06Sector-specialised workflows
- 07Reporting and dashboards
- 08Training and capacity building
- 09Integrations
- 10Support and success management
For public-sector and development partners, deployments can also be structured around pilot phases, technical assistance components, programme implementation budgets, M&E requirements, multi-year partnership agreements, and country or sector expansion phases.
A deployment should reflect the programme it is supporting.
A 100-SME pilot, a 2,000-SME funding-readiness programme, a national SME development platform, an agriculture field-support deployment, and a multi-country DFI partnership have different requirements.
We scope each deployment with the partner so the commercial model reflects the actual size, purpose, complexity, localisation, reporting, support, and impact requirements of the work.
The result is a deployment model that fits the operating reality, not a generic subscription price.
SMEs are usually supported through institutional deployments.
For most programmes, SMEs do not pay directly. Access is sponsored or enabled by a government agency, funder, lender, enterprise partner, DFI, NGO, or development programme. This lets partners support inclusion while still building a trusted, measurable SME development record.
- Fully sponsored SME access
- Subsidised SME access
- Programme-funded cohort access
- Institutional platform access
Designed for institutional procurement and programme delivery.
Mothusi deployments can be structured to support institutional requirements. Our team works with partners to define scope, success metrics, implementation timeline, reporting outputs, and the commercial model that fits the deployment.
- Pilot design
- Technical assistance
- Capacity building
- Implementation support
- Monitoring and evaluation
- Data governance
- Country localisation
- Sector configuration
- Impact reporting
- Multi-year scaling
Pricing questions, answered honestly.
The questions partners ask most often during early scoping conversations.
01Do SMEs pay directly?
In most institutional deployments, SME access is sponsored by a programme, funder, government agency, enterprise partner, lender, or development institution. Self-service SME access may be available in selected contexts.02Can we start with a pilot?
Yes. Many partners start with a focused pilot to validate the MGS model with a defined cohort, sector, or programme before scaling. Pilot Deployment is the first model on this page.03Can MGS support national or multi-country deployments?
Yes. MGS is designed as a global framework with local evidence mappings, country-specific configuration, sector modules, and multi-programme reporting. See Institutional Platform Licence and Multi-Country Partnership above.04Is Agriculture priced separately?
Agriculture is deployed as a sector-specialised module because it includes additional workflows: Commodity Diagnostics, Farm Visits, Vet Dispatch, production tracking, and agri-funding readiness. The sector layer is priced alongside the underlying programme or institutional deployment.05What affects pricing most?
The main factors are SME volume, number of programmes or countries, modules required, localisation depth, Mothusi AI usage, integrations, reporting requirements, sector workflows, and support level. The full factor list is in the section above.06Do you support implementation and training?
Yes. Deployments can include configuration, onboarding, administrator training, Mothusi setup, programme design support, reporting setup, and capacity building. Procurement-friendly scope is one of our defaults.07Can MGS integrate with existing systems?
Yes, depending on the deployment scope. Integrations can include CRM systems, LMS tools, funding platforms, document systems, banking and open-finance providers, programme databases, and reporting environments.08Can we use MGS only for one programme?
Yes. MGS can be deployed for a single programme, cohort, or sector use case, then expanded over time. Programme Deployment is the model that fits this scope.09Can pricing be structured for donor-funded or public-sector programmes?
Yes. Pricing can be aligned to pilot phases, programme budgets, technical assistance components, M&E requirements, and multi-year implementation plans. We work with procurement teams to structure terms that fit institutional rules.
Ready to scope your deployment?
Whether you are designing a pilot, running a national SME programme, preparing SMEs for funding, supporting supplier development, or building a sector-specific platform, we can help structure the right MGS deployment. Tell us about your programme, country, sector, SME volume, and goals.
Mothusi deployment pricing follows deployment design, configured around your programmes, sectors, countries, and impact goals.