The data we capture.
How data capture works.
Brief
You bring the capability gap. We turn it into a data spec.
Design & screen
We design the task and screen the right people, credentials checked where it matters.
Capture
Facilitated, instrumented sessions. Consent and provenance recorded at the source.
QC & adjudicate
Sessions are reviewed; weak or off-brief ones are rejected and re-run.
Deliver
Schema-conformant to your pipeline, with the full provenance chain.
What a deliverable looks like.
A conversational voice dataset: five speakers across three accent profiles, paired negotiations and solo speech, word-aligned and diarised. Every clip carries interaction metrics and a signed consent chain.
Per-speaker Opus/OGG · word-aligned manifest · Annature consent envelopes · IP assigned at capture · checksummed. Identities redacted.
Built on eight years of Askable infrastructure.
Recruitment, consent, capture, transcription, and delivery run inside one audited platform: one identity system, one consent ledger, one audit log. Provenance and consent are captured at the source, not reconstructed after.
One platform, one audit trail. Granular consent, attribution chains, and audit logs on every artifact. Independent: not owned by, or exclusive to, any lab.
See the audit postureTell us the capability you're trying to move.
Bring the model behaviour you want to improve. We'll scope the data, run a validated pilot, and deliver it ingestion-ready.