Trusted Voice Research Infrastructure for NGOs, Governments & Global Development Partners
How we work

Not every organisation wants to operate a research platform.

Some want the evidence delivered. Some want to run collection themselves with our infrastructure behind it. Some want the platform as institutional capability. Start with which of those you are.

Three ways to work with us

These are engagement models, not product tiers. The capability groups you licence are a separate decision, set out on the procurement page.

Managed research delivery

We run the study

For an organisation that needs the evidence, not the software. You bring the question and the programme context; we design the instrument, run collection through our field network and channels, apply the quality controls, and hand you the analysis and the publications.

Who it suits
Programme teams with a deadline and no field operation of their own; donors and foundations commissioning an evaluation; ministries needing an independent read.
What VoiceInsights does
Instrument design, translation of the instrument into the collection languages, enumerator arrangement and training, collection, quality review, analysis, and the governed publication.
What your team does
Defines the question, approves the instrument, reviews findings, and makes the decisions. No platform administration.
Typical deliverables
An executive report (PDF), an editable working document (DOCX), a presentation (PPTX), a statistical workbook (XLSX), and the governed dataset export.
How it starts
A scoping conversation, then a written proposal with the design, the sample, the channels and the timeline.

Technology-enabled delivery

Your team runs it, with us alongside

For an organisation with its own M&E or research team that wants the instrument, the field workflow and the evidence chain to be somebody else's engineering problem. Your staff operate the workspace; we stay on the study with you.

Who it suits
INGOs and research firms with field capacity; national programmes with M&E officers; consortia running the same design across several countries.
What VoiceInsights does
Implementation and configuration, training for each role, design review, channel setup where a communications provider is used, and support through the collection window.
What your team does
Builds and launches the campaign, manages contacts and audiences, runs the enumerators, reviews quality, and authors the findings.
Typical deliverables
Your own governed publications and exports, produced by your team inside the workspace, plus the implementation and training record.
How it starts
An implementation scope, then configuration and role training before the first campaign.

Enterprise platform

You operate it

For an institution running continuous research across programmes, countries or agencies, where the platform becomes part of the operating estate rather than a project tool. Organisation-level governance, geographic scope, and role-aware access across every team that touches the evidence.

Who it suits
Multi-country programmes, government agencies with several departments, and organisations whose reporting obligations recur.
What VoiceInsights does
Platform operation, governance configuration, identity and access setup, upgrades, and the assurance evidence a procurement review asks for.
What your team does
Everything operational — designs, contacts, audiences, campaigns, field teams, quality, analysis and publication — under your own permissions and scopes.
Typical deliverables
A continuously operating evidence estate: governed publications, datasets, and an audit trail that survives staff turnover.
How it starts
A procurement conversation. The evidence pack states what is implemented, what is configurable and what is not yet assured.

What does not change between them

The evidence chain is the same in all three. So are its boundaries.

The same collection routes
A web link and the offline field application work wherever the platform is deployed. Phone, WhatsApp and SMS are connected once a communications provider is configured for your organisation — one account covers all three. How an answer reaches you.
The same evidence rules
Consent is recorded with the response. A publication that cannot resolve its evidence is refused rather than produced. Quality and review.
The same language architecture
The language a respondent speaks, the language your team works in and the language a report ships in are three separate decisions. Language capabilities.
Access is invitation-controlled
There is no public sign-up. Accounts are created for named people by an administrator in your organisation, and what each person sees follows the permissions they hold.
What is not included
We do not operate a call centre on your behalf, we do not hold certifications we have not earned, and we do not sign data processing agreements retrospectively. The Trust Center states the assurance position as it is.
Choose your context

Compare bundles by operating model.

For government, NGOs, UN agencies, donors, universities and public programmes.

Scope components

What can be included

Each bundle is tailored during discovery; cards describe scope, not fixed prices or quotas.

Designed for research delivery

Research & Evaluation

Best for: surveys, baselines, endlines, evaluations and mixed-method research.

Workflow
Design → collect → analyze → publish
Products
Dataset, dashboard, technical report, publication, methodology, evidence pack
Onboarding
Study configuration and research-team training
Governance
Research review and evidence traceability
Support
Delivery and publication support
Discuss your implementation
Accountability-focused

Community Voice & Accountability

Best for: citizen and beneficiary feedback, scorecards, complaints and safeguarding channels.

Workflow
Listen → triage → respond → close the loop
Products
Feedback dashboard, issue dataset, accountability report, evidence pack
Onboarding
Channel, language and safeguarding design
Governance
Controlled access and escalation
Support
Field and response-workflow support
Discuss your implementation
Knowledge-product delivery

Publications & Knowledge

Best for: reports, publications, datasets, policy briefs and controlled dissemination.

Workflow
Review → approve → publish → share
Products
Publication, policy brief, presentation, dataset, metadata, evidence pack
Onboarding
Editorial and Knowledge Ecosystem configuration
Governance
Publisher control and versioning
Support
Publication-quality assurance
Request procurement pack
Best for national programmes

Government & Multi-Agency

Best for: ministries, agencies, local government and multi-region programmes.

Workflow
Coordinate → govern → monitor → publish
Products
Portfolio dashboards, agency reports, national publications and datasets
Onboarding
Organizational and regional configuration
Governance
Multi-level roles and publication control
Support
Phased implementation and training
Request procurement pack
Executive operating context

Enterprise Decision Intelligence

Best for: integrated data, executive dashboards, board reporting and risk visibility.

Workflow
Integrate → analyze → decide → track
Products
Executive dashboard, decision brief, board publication and action register
Onboarding
Data-source and decision-workflow design
Governance
Executive access and auditability
Support
Custom implementation and review
Schedule a demonstration

These are scope components, not products to choose between. The final scope is shaped around your programme, evidence needs and procurement requirements.

Bundle comparison

Compare capability groups without implying unsupported features.

Enterprise service bundle capability comparison
CapabilityResearchMonitoringCommunityKnowledgeGovernmentEnterprise
Collection channels
Voice, web and field collectionConfigurableConfigurableIncludedOptionalCustom scopeOptional
Offline and field operations
Offline assignments and synchronizationIncludedConfigurableIncludedNot applicableCustom scopeOptional
Quality and processing
Validation, review and approvalIncludedIncludedConfigurableIncludedCustom scopeConfigurable
Analytics and dashboards
Role-specific dashboardsIncludedIncludedIncludedOptionalCustom scopeCustom scope
Reports and publications
Governed editorial productsIncludedIncludedConfigurableIncludedCustom scopeIncluded
Datasets and evidence
Versioned datasets and evidence packsIncludedIncludedIncludedIncludedCustom scopeConfigurable
Collaboration and governance
Roles, review and publication controlIncludedIncludedIncludedIncludedCustom scopeCustom scope
Integrations and API
External systemsOptionalOptionalConfigurableOptionalCustom scopeCustom scope
Security and compliance
Security and retention configurationConfigurableConfigurableConfigurableConfigurableCustom scopeCustom scope
Implementation
Structured onboardingIncludedIncludedIncludedIncludedCustom scopeCustom scope
Training
Role-based enablementIncludedIncludedIncludedIncludedCustom scopeCustom scope
Support
Operational support modelConfigurableIncludedIncludedConfigurableCustom scopeCustom scope
Customer success
Review and expansion planningOptionalIncludedConfigurableOptionalCustom scopeCustom scope
Inside a research engagement

What happens between a research question and a finding somebody can act on.

Eight stages, each with a named owner and a reviewable output. Open this if you are assessing delivery method; skip it if you are still deciding whether to talk to us.

Show the eight stages

The eight stages

Whether your team runs these or we run them for you is the question the engagement models answer. The stages themselves do not change.

1 · Design

Before anything is asked

The research question becomes an instrument: the questions, their order and their logic, the languages the instrument will be administered in, and the consent statement a respondent hears before any of it. The design is registered, so the analysis later runs against what was actually planned rather than what was remembered.

Research designs supported
Structured survey, facility assessment, citizen feedback and qualitative work run as live designs. Mixed methods, observation and longitudinal panels are supported on the same structures. The seven registered modes.
Qualitative formats
Key informant interviews, in-depth interviews and focus group discussions are recorded as formats within qualitative work, with participant counts — not as separate research modes.

2 · Field preparation

Who and where

Contacts are loaded — from a spreadsheet, a workbook or typed in one at a time — and normalised into one unambiguous form so a number is never dialled twice or dialled wrong. An audience is then a rule over those people, and its size is counted from your own respondents when you ask for it.

Consent is not assumed
A contact can only be dialled where consent was recorded. A blank consent column is treated as unknown, never as permission, and somebody who has asked not to be contacted stays that way through a re-import.
Enumerators and assignments
Field staff receive assignments with their own area and due dates, and a supervisor can see what has been given out and what is outstanding.
Offline packages
Where a team is going somewhere without a network, the instrument and its language pack are prepared on the device before they leave.

3 · Collection

Five routes

A person replies however suits them. A web link and the offline field application work wherever the platform is deployed. Phone, WhatsApp and SMS are connected once a communications provider is configured for your organisation — one account covers all three.

Voice, in any registered language
Recording someone's voice does not depend on which language they speak, so a respondent can answer aloud in any of the 57 African languages the platform registers, and the recording is kept as the evidence of what they said.
What that does not mean
Capturing speech is not understanding it. Automatic transcription reaches 15 of those languages on the published list of the speech provider we route to, and none of the 57 has been accuracy-validated by VoiceInsights against African field audio. The registry, language by language.

4 · Getting the work back

Often the longest

Work collected with no connection sits on the device until it is confirmed received. An interrupted interview resumes at the question it reached. A device that is running out of room says so, and refuses a new interview rather than silently failing to save one. If a confirmation is lost on the way back, the device sends again and the server recognises what it already holds instead of storing it twice.

A supervisor can see what has not arrived
Devices report the shape of their queue — how much is waiting, how long it has been waiting, and whether the last attempt was refused.
And what silence means
Those figures come from devices that reached the server. A device with no connection cannot report that it has no connection, so an absent device is unknown rather than healthy — and the platform says so rather than showing a reassuring zero.

5 · Evidence management

The record

Every response carries its consent status, its origin and its lineage. The original audio is retained — including a recording with no discernible speech, which is stored as evidence rather than discarded, because a refusal to answer is a finding and the recording is the proof of what happened.

6 · Quality control

A person decides

Responses are checked for completeness, duration, consent validity and duplication, and flagged where something does not hold. Double entry compares two independent records of the same interview. A supervisor decides; the platform records who decided and when.

Where AI is involved
Analysis assistance is separated from observation and from human interpretation, and is presented as suggestion rather than conclusion. Responsible AI.

7 · Analysis

Against the design

Descriptive results, frequencies and dispersion, with the cautions that belong to them. Qualitative coding keeps themes, contradictions and minority views rather than averaging them away. Findings reference registered evidence, so a claim can be traced back to the responses behind it.

8 · Reporting and decision support

Five formats

A governed publication is produced in the formats an institution actually circulates, and a publication whose evidence cannot be resolved is refused rather than produced.

PDF
The executive report, for circulation and for the record.
DOCX
An editable working document, for a team that will add its own programme context.
PPTX
A presentation, for the meeting where the decision is taken.
XLSX
A statistical workbook, for an analyst who wants the figures behind the finding.
CSV
The governed dataset export, for a data team or a donor's own pipeline.
Who can export what
Export is a permission, not a button everyone has. A role that may read a publication is not automatically a role that may compose or export one.

What this process does not do

Worth stating plainly, because each of these is something research software is routinely assumed to do.

It does not translate automatically
Translation is a governed artefact with a recorded reviewer, not something generated in the pipeline.
It does not detect a language for you
The platform performs no automatic language detection. The collection language is a decision that is recorded.
It does not identify who spoke in a group discussion
Focus group audio is preserved and attributed at the level a researcher can defend, not split by speaker automatically.
It does not let an operator message a respondent back
Collection is not a conversation channel. There is no reply surface, and there is no cross-channel message thread.
It does not decide anything on its own
Quality is scored; a person adjudicates. Safeguarding indicators, where configured, are raised for trained human review and replace no protocol or referral pathway.
What shapes a proposal

Scope follows the operating reality.

OrganizationsProjectsUsers & rolesCollectorsChannelsLanguagesResponse volumeAudio processingStorageData productsIntegrationsHostingSecurityTrainingSupport & SLAGeography
Procurement assurance

Evaluate institutional controls directly.

Procurement teams can review the governing assurance evidence without relying on a separate Resources destination.

Implementation journey

A controlled route from need to operating service.

  1. DiscoveryOutcomes and context
  2. Solution designScope and controls
  3. ProposalBundle and options
  4. ProcurementEvidence and terms
  5. ConfigureWorkspace and products
  6. PilotTrain, test, launch

Bring us the decision you have to defend.

We will come back with scope, method and what it takes to run it — shaped around your programme rather than a price list.