How to write your first case study when you have no customer interviews

You write a case study without an interview by starting from the evidence you already hold and then asking the customer to confirm a few specific points in writing. An interview feels like the required first step, but it's really a way to collect two things: the customer's story in their own words and their permission to tell it. For a first case study, you probably have more of the story than you think. The customer explained their problem when they signed up. They told support what wasn't working. They mentioned a result when they renewed or added seats. Some of them have said something about you on LinkedIn, in a review, or on their own website.

Most people stall at this point because the material is scattered across an inbox, a CRM, a few Slack threads, and the open web, and nobody has time to collect it. Interviews also cost the customer an hour, and that's often the ask that never gets scheduled. A confirmation email asking "Can we quote you saying this, is this figure right, and can we use your name?" takes the customer five minutes.

A good first case study tells one customer's story in a clear order: who they are, what they were trying to do, what stood in their way, why they chose you, and what changed. Every quote is something the customer really said, every figure ties to a source, and the customer has agreed in writing to what's published. When you don't have a number, a specific description of the outcome works better than a vague percentage, such as "the team stopped rebuilding the weekly report by hand" instead of "saved countless hours."

No tool on its own does this assembly. Your email, CRM, and review profiles each hold a piece, and a writing tool will happily produce a polished case study from a two-line prompt, invented quotes included. Kite does the assembly honestly. It collects the evidence, keeps track of where each fact came from, writes the draft, and prepares the request that gets the customer's confirmation.

Start by telling Kite which customer you'd like to feature, or ask it to suggest one:

"We don't have any case studies yet. Find the customer with the best story and draft our first one."

Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers. From that research, it already knows what you sell, who your customers are, and how you describe your product, so the case study fits your positioning without a long brief.

Give Kite whatever you have on the customer. You can paste emails into the conversation in the Kite web app, upload PDFs such as a support export or a proposal, or forward email threads to your team's Kite address. If your team uses Kite in Slack, Kite can read files people share there and search the public channels it has joined for earlier conversations with or about the customer. If you've connected a CRM such as HubSpot, Kite reads the customer's company record and the notes your team has added.

Kite shows you the draft and the confirmation email before anything reaches the customer. You don't need to connect any outside account to start, because Kite's research sources, including PredictLeads, are built in.

Kite picks the customer whose story has the clearest before and after and the most evidence behind it. A big logo with nothing on file makes a weaker first case study than a smaller customer who has written you three detailed emails about what changed. When you ask Kite to choose, it looks at the material you've shared and your CRM, if one is connected, and weighs how well each customer matches your ideal customer profile, because a case study works best when prospects see themselves in it.

Kite also checks which customers already talk about you in public. PredictLeads tracks the business connections companies publish, such as the vendors and partners named on a company's own website, along with company news like client wins and partnerships. Kite looks up your domain in PredictLeads to see which companies list you, which tells it who is already comfortable being associated with your brand. That customer is usually the easiest yes.

Kite reads everything you've shared about the customer and pulls out the parts of the story. It looks for five things:

• The starting point. What the customer was doing before, in their own description, such as a spreadsheet they maintained or a tool they replaced.
• The trigger. What made them look for a solution, such as a new hire, a missed target, or a launch.
• The decision. Why they chose you, often stated in a sales email or a sign-up form answer.
• The result. Any outcome they mentioned, with the date and the exact wording they used.
• Their words. Sentences the customer wrote that could stand on their own as quotes.

Kite keeps the customer's wording exactly as written and notes where every line came from, such as "support thread, 14 March" or "renewal email from their head of operations." A sentence a customer wrote to your support team about how much easier the work became is a real quote. Kite treats it that way, and it also marks it as needing the customer's permission before it appears in public.

Kite searches the open web for what the customer and its people have said about your product. That includes reviews on sites like G2, Capterra, and Trustpilot, posts on LinkedIn and X, comments on Hacker News, and any page on the customer's own website that mentions you, such as an integrations page or a blog post about their tools. A public review written by someone at the customer is often the best quote you have, because the customer already chose to say it in public.

Kite also researches the customer as a company, so the case study can describe them accurately. It reads their website for what they do and who they serve, and it uses PredictLeads for recent funding rounds, hiring, and news. That context helps the story. A customer that raised a round or doubled its marketing team since working with you has a growth arc the case study can mention, as long as the draft presents it as context rather than something your product caused.

Before it writes, Kite sorts every claim into what the customer actually said and what Kite is inferring from the evidence. "We used to rebuild this report every Monday" in a customer email is sourced. "The team saves about four hours a week" is an inference unless the customer said it. Kite keeps the two apart because inferred claims are where first case studies go wrong. A customer who reads a figure they never gave is the most likely to say no.

Kite also lists the gaps. A first case study often has a clear story and no hard number, or a strong result with no clear "before." Kite names each gap and decides whether to fill it with a question to the customer or to write around it with a specific, qualitative description.

Kite writes the case study with the customer as the main character. The story follows what the customer was trying to do, what stood in the way, what they decided, and what your product contributed at each point. That order matters because a prospect reading the page identifies with the person who made the decision, not with the vendor describing itself. If the evidence includes a setback, such as a slow first month, Kite keeps it, because a small dip makes the result more believable.

Every quote on the page is a sentence the customer really wrote. Kite never makes up a quote, a number, a job title, or an outcome. Where the story needs a specific detail that the evidence doesn't contain, Kite puts a named placeholder in its place, such as "[number of locations before rollout]," and tells you each one it left. The draft includes a headline, a short summary of the result, the customer's background, the problem, the solution, the outcome, and a pull quote.

The confirmation email does the interview's job in a few minutes of the customer's time. Kite writes a short email that thanks the customer, says what you'd like to publish and where, and lists only the points they need to confirm:

• Each quote, written out in full, so they can approve it or adjust the wording.
• Each figure, with the time period it covers.
• Each inference, so they can confirm or correct it.
• One or two short questions that fill the biggest gaps, such as "Roughly how long did the weekly report take before?"
• Whether you can use their name, their logo, and the names and titles of the people quoted.

The email also offers an anonymous version that describes the customer by industry and size, in case being named is the sticking point. The full draft goes in the body of the email below the list, so the customer can read the story in context and forward it to a manager if they need to.

Once you approve the email, Kite sends it from your team's Kite address, and it arrives under your company's name. If you'd rather send it from your own inbox, Kite gives you the subject line and body to copy. When the customer replies, the reply comes back to the same conversation, and Kite updates the draft with their corrections and answers. Their answers to the gap questions often become the strongest quotes in the piece.

Kite publishes the case study once the customer has confirmed it and you've approved the final version. On a website Kite hosts, it publishes the page and returns the live URL. If your site runs on a supported CMS, such as Webflow or WordPress, Kite publishes through your connected account. Kite can also turn the finished case study into a LinkedIn post or a short section for your homepage, and it can send the customer a thank-you note with the link.

When Kite finishes, you have a first case study built from real evidence and a clear path to the customer's approval.