Syrup — survey collection for insights teams
Design, host, and quota-manage studies from one place. Every response goes straight from the respondent's browser to your infrastructure — never ours.
// Signed by a secret only you and Syrup hold { "response_id": "3f6c2a9e-8d41-4b7a-…", "survey": { "slug": "brand-tracker", … }, "disposition": "complete", "meta": { "pid": "abc123", "src": "fieldline" }, "answers": { "q_gender": { "questionType": "single_select", "selectedValues": ["Woman"], "selectedCodes": ["2"] }, … } }
Why it matters
Every vendor that holds respondent data triggers a review: the security questionnaire, the data processing agreement, data residency sign-off, a privacy impact assessment, and the same again at renewal. A team of three waits two quarters to field a study that takes four days.
A platform that never receives the answers changes the shape of that review. There is no respondent data to put in a DPA. The questionnaire gets short. Data residency is already settled — the data is wherever you put it.
What Syrup does
Everything between the brief and the data landing in your warehouse — and nothing after it.
Surveys are written in SRP, a small plain-text language. Review them in a pull request, diff them between waves, and let any AI assistant draft or translate them.
Publish a survey as numbered waves. Each wave has its own link and a frozen copy of the questionnaire, so the survey stays editable for the next one.
Define cells on your quota variables and set targets. When a respondent's cell is full, they're sent back to the panel as over quota.
Keep your sample vendors. Their entry parameters pass through to your data, and respondents go back to the vendor's complete, screen-out or over-quota URL.
Shared links for panel and customer studies.
answers → your endpointEmbeddable forms. With direct delivery, submissions post straight to you.
answers → your endpointA tablet app for fieldwork without a signal. It syncs through Syrup when back online.
answers → SyrupWhat Syrup doesn't do
Each of these is something you already have, or that's better kept out of a collection platform.
| Store responses | No respondent answers on our servers means nothing to breach, nothing to negotiate, and nothing to review every year. |
|---|---|
| Analytics & dashboards | Responses land in your warehouse, where your BI tools, your definitions and your data team already are. You don't need a second, weaker analytics product. |
| Sample & panel sourcing | You keep your panel relationships and your negotiated CPIs. We don't mark up respondents. |
| Data processing | No weighting, tabbing or open-end coding. Your team or your existing vendor does that downstream, the way they already do. |
A team of one
Your engineers stand up one HTTPS endpoint and store one secret. From then on, a single researcher takes a study from brief to data in the warehouse without convening anybody.
IT runs a webhook and keeps the secret.
Write the questionnaire in SRP, or have an assistant draft it.
Publish a wave, set quota targets, hand the link to the panel.
Follow completes, incidence and cell fill live.
Edit, publish wave 2. The data is already where you work.
For your engineers and reviewers
The delivery contract is public: the request, the signed token, how to verify it, and exactly what we keep.
The webhook request, JWT verification with receiver examples, retry behaviour, and what we keep about each session.
The plain-text survey language Syrup runs on. Small enough to learn in an afternoon.
Write a survey, validate it and preview how it renders. No sign-up.
See it run
We'll field a live study to an endpoint you control, watch quotas fill, and publish the next wave — and show you what your security team would review.