Exact quota counts,
even at peak traffic.
Turn the agency’s questionnaire around faster, plug straight into your sample suppliers, and keep every quota count exact.
Win the bid on turnaround. Keep the PM in control.
- 01 Quote programming in hours. First preview 5x faster from the client’s spec, so your turnaround is the one that wins. See how ↓
- 02 Supplier-ready from day one. Respondent IDs pass through, and every exit redirects back to the supplier: complete, terminate or quota-full. See how ↓
- 03 Exact counts, fair exits. Completes are counted once under a lock. Full cells screen out at the door, not after 25 minutes. See how ↓
- 04 Launch markets independently. Each language goes Live, Paused or Closed on its own, so one late translation holds nobody up. See how ↓
Quote programming in hours.
Win the bid on the timeline.
Agencies send a questionnaire and a deadline. Fieldbase drafts the whole survey from the Word file, routing notes included, and your programmer reviews and edits it instead of hand-coding it. First preview is 5x faster than programming from scratch.
- From the agency’s own file. Word, PDF or pasted text. No template to fill in first.
- Validated before it goes out. Malformed conditions and broken references are flagged at generation, not on the first test link.
- Late edits in a sentence. Agency changes become tracked changes, logged in the project thread.
Supplier-ready from day one.
IDs in, redirects out.
Live links carry the supplier’s respondent ID into the survey, and every ending sends the respondent back with it: complete, terminate or quota-full. Invite-only studies can use per-respondent entry links instead, and panel ID lists import with de-duplication.
- IDs pass through. The supplier’s respondent ID rides in on the link and back out on the redirect.
- One redirect per ending. Complete, terminate and quota-full each return the respondent to the supplier.
- Per-respondent links. Invite-only studies get one entry link per respondent, with panel imports de-duplicated.
Counted exactly.
Screened at the door, not at the end.
Every complete is recorded in one locked transaction, so a burst of traffic can’t double-count or lose one, and a reload never counts twice. The hard stop sits where it is fair to the respondent: a one-line quota check in the screener, so someone who won’t count leaves in the first minute, not after 25.
- Exact under load. Concurrent completes are serialised, and a retry or reload is never counted twice.
- Screen out early. One line in the screener checks whether the cell is full, before the respondent invests any time.
- Nobody cut off at the end. A respondent already past the screener when a cell fills finishes and is counted. No quota-full after 25 minutes.
Launch markets independently.
And watch every one on one screen.
Each language has its own Test, Live, Paused or Closed status, so English can field while French waits for translation sign-off. The Fieldwork tab shows completes, terminates, in-progress and quota-full counts with IR, CR and LOI underneath, and the PM edits targets there without a programmer.
- Per-language fielding. Launch, pause or close one market without touching the others.
- Live dispositions. Real respondents only. Testers and simulated data stay out of the counts.
- Edit targets in field. Nudge a target or close a cell inline. The programmer’s Quota tab reads the same table.
From test link to close.
What the PM does at each stage, and what they no longer have to ask the programmer for.
- Before launch
Simulate
Run simulated respondents through quotas and routing. Fix anything never reached.
- Soft launch
Open one market
Go live in the first language and watch IR and LOI settle on the Fieldwork tab.
- Mid-field
Adjust without a redeploy
Move targets, close cells, pause a language. Everyone sees the same table.
- Close
Export once
Close the study and export a file whose counts match the cockpit.
Run one live study in parallel.
Same sample source, same quota plan, two platforms. The export decides.
- 1 Pick a quota-heavy study
Nested cells and a tight field window show the difference fastest.
You do this - 2 We programme it with you
Including the quota groups and the exit conventions your sample suppliers expect.
We do this - 3 Field both builds
Send the same sample to both and let them run side by side.
You do this - 4 Compare the files at close
Cell counts against target, interviews wasted, PM hours spent. That comparison is your business case.
You do this
The honest answers.
What happens when a cell fills during a traffic burst?
New arrivals are screened out by a one-line quota check in the screener, so they leave in the first minute. Anyone already past the screener finishes and is counted: we don’t throw away a 25-minute interview on the last page. Counts stay exact throughout, because every complete is recorded in one locked transaction.
Can the PM change targets without the programmer?
Yes. Targets and cell status are editable from the Fieldwork tab while the study is live. The programmer’s Quota tab reads the same table, so there is no second copy to keep in sync.
Does it work with our sample suppliers?
Live links carry respondent IDs in, invite-only studies can use per-respondent entry links, and panel ID lists import with de-duplication. Surveys end on complete, terminate or quota-full exits, and each can send the respondent back to the supplier.
Can we hold one market back?
Yes. Each language has its own fielding status, so English can be live while French waits for translation sign-off.
Where is respondent data hosted?
In the US (San Francisco) today. An EU region in Frankfurt is coming soon and Asia-Pacific is planned. The Trust Center lists every sub-processor.
Don’t take the page’s word for it.
Run your next three projects free.
Up to 5,000 completes over 90 days, hosted in the US (EU coming soon). We programme the first two questionnaires with you; you programme the third with the AI. At day 60 we talk about staying, with a 24-month price lock.