Fieldwork that goes out under your brand

An agency’s client did not commission a survey from us, and a company’s employees have no reason to trust a name they have never heard. So the surface a respondent actually opens leads with your identity — and it is set from configuration, which is why it takes minutes rather than a release.

• Your logo, your name, your line — on the page a respondent opens.

  The invitation lands on a page that leads with your mark and your organisation’s name, with an optional line of your own underneath. To the person answering, this is your study, run by you, in a language they chose.

• Configuration, never a per-client build.

  Every co-branding value is a setting on the workspace, resolved when the link is opened. Nobody forks a codebase for a client, nobody ships a release to change a tagline, and a fifth client costs the same as the first.

• For an agency, one workspace per end client.

  Each study you run for a different client gets its own workspace with its own branding, its own respondents and its own reports. Data does not cross between them, which is the part your own client’s procurement will ask about first.

Co-branding is the visible half. The other half is that a platform which already holds the relationship — an HR system, a patient app, a lender’s portal — can drive fieldwork without anyone logging into ours.

• A partner API for the platform that already knows who to ask.

  Create a campaign, register respondents, launch it, poll its status and pull results over REST — authenticated by an API key with scopes and quotas, and idempotent, so a retried request cannot double-invite anyone. Your product decides who is surveyed and when; ours runs the conversation.

• Signed webhooks, retried, replayable.

  Subscribe your own systems to events — a conversation completed, results ready — delivered with an HMAC signature you verify, retried on failure from a durable queue, and replayable when your endpoint was down. You configure them yourself in the client portal; nobody has to open a ticket with us.

• Anything the screens can do, the API can do.

  A standing rule rather than a roadmap item: an action that exists only in the interface cannot be automated, and one that exists only in the API is invisible. If you can do it in the client portal, it is callable — which is what makes this embeddable rather than merely integrable.

Both of these come up in the first conversation with an agency, so they are here rather than in a third meeting.

• The WTN line stays unless you ask us to remove it.

  Your brand leads; by default a small line says the conversation runs on WTN. Removing it is not a switch you can flip and not something on the price list — it is a deliberate change we make for you, recorded against the person who asked and the reason they gave. What it never removes is the processor disclosure: the respondent is always told which company is actually handling and storing what they say, and no branding setting reaches that line.

• Creating a new client workspace is still done by us.

  Everything inside a workspace is callable. Provisioning a brand-new one over the API is not yet possible, so onboarding your next end client is a short conversation with us rather than a request your own system makes.

Pricing is one published ceiling for everyone, and volume is discussed with us directly. There is no branding tier and no surcharge for any of the above.

None of these are available to a study today; they are named so that what is live above can be read literally.

• Your own domain on the respondent page — coming soon

  The respondent page carries your brand today; serving it from an address of yours is coming soon. Until then, the link a respondent opens is a WTN address.

• An embeddable component inside your own product — coming soon

  A button or panel you drop into your own application that starts the conversation in place, instead of sending the person to a link. Coming soon.

• A parent agency account over its client workspaces — coming soon

  One agency view across every end-client workspace, with one bill and one set of people. Today each workspace stands alone, which works and is simply more clicks.

When you run a study for your own client, they are the organisation the data belongs to, you are running it on their behalf, and WTN is processing it on yours. That chain has to be written down rather than styled away: a data-processing agreement, a named register of every outside company that touches personal data, encryption before storage, and hosting and the database in India.