Published November 2026 · 10 min read

AI Verbatim Coding Software for Research Agencies: A Practical Comparison

Coding open ends used to mean a coding department, or a freelancer and a two-day turnaround. AI has changed the economics, and now every text analytics vendor claims to do "AI coding". For an agency, the question is not whether the AI can read verbatims. It is whether the tool fits how agency work is actually delivered: client codeframes, multi-coded nets, banner tables, tight turnarounds and per-project budgets. This guide sets out the criteria that matter, compares the main types of tool, and shows how to cost a study before you commit.

What Agencies Need From Verbatim Coding Software

Score any tool you are evaluating against these eight criteria. Most demos only show the first one.

1. Coding quality on your data. Run a past study you have already hand-coded and compare. Expect agreement in the range of 85–95% agreement with human coders for well-defined codeframes. Be wary of anyone promising 99%.
2. Codeframe control. Can you start from a client's codeframe, edit AI suggestions, and lock the final list before anything is coded? If the model decides the codes, you cannot defend them in a debrief.
3. Multi-coding. Real verbatims mention several things. One code per answer understates every theme.
4. Output format. You need codes as data: 0/1 columns or code lists that drop into your tab software, SPSS or Excel without someone rebuilding them. A dashboard alone is not a deliverable for most agency work.
5. Consistency across waves. Trackers need the same codeframe applied the same way every wave, with versioned changes.
6. Turnaround. Minutes to hours, not days. Fieldwork always closes late.
7. Pricing that maps to projects. Agencies bill per project. An annual seat licence that sits idle between studies is a cost you cannot pass on.
8. Client data handling. Where does the data go, how long is it kept, and is it used for training? Your client contracts will ask.

The Main Types of Tool

1. Dedicated verbatim coding platforms

Tools such as Ascribe and Codeit grew up serving coding departments at research agencies and fieldwork houses, and have added machine learning and AI assistance over time. Their strengths are workflow depth: coder assignment, review queues, hierarchical nets, and integrations with survey and tabulation platforms. They are built to be used every day by people whose job is coding. Pricing is typically licence-based and quoted on request.

Best fit: agencies with a dedicated coding team and steady, high volume.

1b. AI-first coding tools for agencies

Newer tools such as Survey Coder Pro are built AI-first for agency coding: the AI drafts the codebook and codes every answer, and the team reviews flagged answers in a shared inbox. Survey Coder Pro adds hierarchical nets and banner tables, and sells published one-time credit packs (from $100 for 750 coded responses as of November 2026). We compare it with SurveyCat in detail in SurveyCat vs. Survey Coder Pro.

Best fit: agency teams that want AI-first coding with a multi-person review workflow.

2. AI text analytics platforms

Platforms such as Caplena and Thematic focus on finding and tracking themes in feedback, with dashboards, trend views and integrations for continuous sources like NPS programmes and reviews. They can produce coded data too, but the product centre of gravity is ongoing insight rather than a coded file for a one-off project. Pricing is subscription-based; check each vendor for current plans.

Best fit: CX programmes and agencies running always-on feedback work for a client.

3. Survey and analysis suites with text features

Qualtrics Text iQ and Displayr include text coding inside a wider survey or analysis product. That is convenient when your data already lives there, and limiting when it does not: you code where the data is, on that platform's terms. We compare these in more depth in Qualtrics Text iQ alternatives and Displayr alternatives for verbatim coding.

Best fit: teams already standardised on that suite.

4. General-purpose chatbots

Pasting verbatims into ChatGPT or a similar assistant is how many researchers first try AI coding, and it is fine for exploration. For deliverables it breaks down: long files must be chunked by hand, the codeframe drifts between chunks, results change if you re-run, and getting clean 0/1 columns back into a dataset is manual work. You also need to check what the product does with pasted client data.

Best fit: quick exploration of a small sample, not client deliverables.

5. Self-serve, file-in/file-out coding tools

This is the category SurveyCat sits in. You upload the data file, the AI proposes a codeframe, a researcher edits and approves it, every answer is coded against it, and you download the same file with 0/1 columns appended. There is no platform to adopt, no licence to keep busy between projects, and nothing to learn beyond the upload screen.

Best fit: agencies and consultants whose coding volume comes in project-shaped bursts.

Side-by-Side

Based on public vendor information as of November 2026. Products change, so confirm details with each vendor.

Costing a Typical Agency Study

Take a common brief: 1,000 completes, three open-ended questions, about 2,700 non-blank answers once you allow for skips.

• Manual coding: at 50 to 100 answers per coder-hour, plus building the codeframe, that is roughly 27 to 54 hours of coding time.
• SurveyCat on credit packs: 2,700 credits to classify plus 15 for AI codeframe suggestions on three questions. The Growth pack (2,750 credits, $75) covers it, and unused credits never expire.
• SurveyCat on a plan: Research Starter gives 4,000 credits a month for $100, with codeframe suggestions included. Agencies running several studies a month usually land on Research Monthly or Research Pro, which add crosstabs and, on Pro, saved codebooks for trackers.

Researcher time does not go to zero. Someone still reviews the codeframe and spot-checks the output, but that is 20 to 40 minutes rather than days, and it is the senior judgment the client is paying for anyway.

Where SurveyCat Fits, and Where It Doesn't

A good fit if you:

• deliver coded data files, not dashboards;
• work in SPSS, Stata, Excel or CSV. Files come back in the same format with labels intact (see our SPSS guide);
• want a researcher to approve every codeframe before coding runs, then check the codes (low-confidence answers flagged, bulk recoding, review log);
• run trackers and need the same codeframe each wave (how that works);
• prefer published, per-answer pricing to an annual contract.

Probably not the right fit if you need:

• a multi-coder workflow with assignment, review queues and per-coder audit;
• hierarchical nets and sub-nets managed inside the tool (SurveyCat codeframes are flat lists; build nets in your tab software from the 0/1 columns);
• live connectors that code feedback continuously as it arrives.

Questions to Ask Any Vendor

1. Can I code a past, hand-coded study in a trial and see the agreement rate?
2. Can I import my own codeframe, and is anything coded before I approve it?
3. Does an answer get multiple codes?
4. What exactly do I download, and in which formats? Are SPSS labels preserved?
5. How do I apply last wave's codeframe to this wave, and how are changes versioned?
6. What does a 3,000-answer study cost, all in, at my expected annual volume?
7. How long is response text retained, and is it used to train models?

SurveyCat's answers, for comparison: yes (80 free credits, no card); yes, type your codeframe in and nothing runs until you confirm; yes, and after coding you can review flagged answers and recode one response or a whole group, with a downloadable review log; the same file with 0/1 columns, with labels preserved for SPSS and Stata; saved, versioned codebooks on Research Pro; 1 credit = one classified response to one question, published on the pricing page; uploads are deleted within 30 minutes and results within an hour, and response text is not stored.