Most coding problems are really codebook problems. Codes get invented mid-pass, definitions drift, two similar codes end up meaning the same thing, and by the end nobody can say precisely why a given extract sits where it does. The analysis may still be right — but you cannot demonstrate that it is, which in a viva or a peer review amounts to the same thing.
We start by agreeing the approach: inductive coding where the codes come from the data, deductive where an existing framework or theory drives them, or the hybrid most applied projects actually need. Then we build the codebook properly — each code with a definition, inclusion and exclusion criteria, and an anchor quote that shows what a clear instance looks like.
Where reliability matters — funded work, multi-coder teams, anything heading for a journal — we run a second coder over a sample and report Cohen's kappa, with the disagreements documented and resolved rather than quietly averaged away.
What you receive
- A documented codebook: definitions, criteria, anchor quotes
- The full dataset coded in your chosen software
- The native project file (NVivo .nvp, ATLAS.ti, MAXQDA)
- Coded extracts exported and organised by code
- Inter-coder reliability testing with a reported kappa
- Analytic memos recording why the codebook changed as it did
How this service runs
- Send the brief — Email us the data type, the volume (audio hours or cases), your method if you have one, and the deadline. No form-filling marathon.
- Scope call & fixed quote — We come back with clarifying questions, then a written scope and a fixed price. NDA signed first if you'd rather talk under one.
- Analysis with checkpoints — You see the codebook or the analysis plan before we run the whole dataset — so the direction is agreed while it's still cheap to change.
- Delivery & walkthrough — Files, project files, syntax and write-up delivered together, plus a call to walk you through the reasoning. Revisions included.
Doctoral coding chapters, funded studies needing reliability evidence, and teams who started coding and lost the thread.
Services that usually run alongside this one
Transcription & translation
Verbatim or intelligent-verbatim transcripts with speaker labels and timestamps, from interviews, focus groups and field recordings. Translation into English with the source retained alongside.
Thematic & content analysis
Themes derived from your data with the trail intact — Braun & Clarke's six phases, framework analysis, or quantitative content analysis with frequency counts where you need numbers.
Quantitative & statistical analysis
From cleaning and assumption checks through to the model your design actually calls for — with the syntax file, so a reviewer or supervisor can reproduce every number.
Send us the brief. Get a price.
One email with your data type, volume and deadline is enough for a fixed written quote — back with you within 1 business day, NDA first if you prefer.
Quote for coding & codebook development
Email us a paragraph, or fill the brief on the right. Either way a real analyst reads it and replies within 1 business day — no sales sequence.