Case study participation form

A case study invitation needs to ask a satisfied customer three things: will they describe how they use the product, will they share specific results, and will they put their name on it. This form collects those essentials — company, usage, metrics, quotability, availability for an interview — so your team knows what they are getting into before a writer starts. The same shape works for a software case study, a consulting case study or a nonprofit impact story.

The form beside this text is live. Fill it in and submit it — it validates exactly as it would for a real respondent, and saves nothing.

Radio buttons for quotability are clearer than text

A radio group "Yes, quote me" or "No, anonymous" leaves no ambiguity. Free text like "maybe" or "ask first" puts the burden on your team to follow up.

Collecting results in the form saves back-and-forth

An optional textarea for metrics — "We cut processing time from 2 hours to 10 minutes" — gives your writer a head start. Not every customer will fill it, but those who do spare a follow-up email.

No card required.

Case Study Participation Form

Live preview

How to build this form

6 steps in the editor. Nothing here needs a paid plan.

  1. Add text fields for the customer contact's name and their company name, so you know who you are talking to.
  2. Add a long text field asking how they use your product. This is their starting narrative; the actual case study gets written with them afterward.
  3. Add an optional textarea for results and metrics they are willing to share — revenue increase, time saved, adoption by team size.
  4. Add a radio group asking "May we quote you by name?" with Yes and No. Radio is cleaner than a checkbox here because the answer is binary.
  5. Add a second radio group asking "Would you be willing to do a short interview?" so the team knows whether to schedule a call.
  6. Export the roster to CSV. Follow up with participants outside the form — interview scheduling, draft approval, publication timeline.

Fields in this form

7 fields, using 4 of the 19 field types available.

QuestionField typeRequired
Your nameShort textYes
Company or organizationShort textYes
EmailEmailYes
How does your team use our product?Long textYes
Results or metrics you are willing to share (optional)Long textOptional
May we use your name and company in the case study?Radio buttonsYes
Would you be willing to do a short interview?Radio buttonsYes

What goes wrong with this form

Specific to a case study participation form, not general advice about forms.

Asking for metrics the customer might not have

Make the metrics field optional. Not every customer tracks ROI or measures time saved. Ask for results if they have them; let them skip it otherwise.

Using a checkbox instead of a radio for quotability

A checkbox says "I agree to be quoted" but does not say "I do not want to be quoted". A radio group with Yes and No makes the choice explicit and leaves no ambiguity.

Treating the form as the case study

The form collects permission and initial info. The actual case study is written in conversation with the customer — interviews, draft reviews, final approval. That happens outside the form.

Questions about this form

Should you ask a customer to do a case study via a form?

Yes, if the customer already has a relationship with you. A form is the structured way to ask permission, collect their story outline, and find out if they will do an interview. The actual case study — interviewing, writing, approving — happens afterward.

Can you write the case study from the form data alone?

Rarely. The form collects permission and basic facts, but a real case study needs a conversation with the customer. Use the interview radio button to schedule a call where you ask follow-up questions the form could not anticipate.

What if a customer wants to stay anonymous?

Use a radio group with "Yes, quote me by name" and "No, keep it anonymous". Anonymous customer stories are less valuable but still worth publishing. The form makes the preference explicit.