Customer interview transcripts go into Claude with one question: what do these buyers actually care about? The answer arrives in seconds. Three themes, five benefit statements, ready to paste into the launch deck. It reads like the work of a strategist who spent a week with those customers. What you can't see is which parts came from the transcripts and which the model invented to fill the gaps. It's fast, but not accurate...
It's 18:40 on a Tuesday and Sara is still at her desk. Frustrated. Listening to call recording 9 of 14. Five to go. That's two hours if it goes well. Maybe three.
The launch messaging is due Thursday, and she knows everything she needs is already in these recordings. Real buyers, in their own words, saying why they bought, what almost stopped them, which phrase made it click. It's in there. Somewhere. So she keeps going, because she doesn't want to base her new messaging on nothing. Or on the opinion of the CEO.
So she digs. And digs. And digs. Finds a good quote, pastes it into a doc. Finds another one, adds that too. By call eleven the doc is a pile of quotes and she's lost the thread. Who said this one? A best-fit customer, or someone who churned? Those two point at opposite messaging. She doesn't know anymore. She'll sort it out later.
Later is Thursday. The messaging has to go live. So it goes live, and it's probably fine (is it?). She just can't say why.
Sara is not a real person. She is also not invented. She is assembled from our own buyer research: interviews with product marketers and product managers, all describing the same Tuesday. She is a senior product marketer at a mid-sized B2B SaaS company that inherited customer research without a background in qualitative research and without inheriting a research team. Her company can tell you the exact drop-off rate on step three of onboarding, to two decimal places, in a dashboard. It cannot tell you why a single customer bought and how they talk about a certain product.
If you have "product" in your job title, product marketer, product manager, or something close, you know her Tuesday because it is probably yours: listening to sales calls, running customer interviews, building the roadmap or the messaging from "what customers told us." That is qualitative data analysis, even when nobody calls it that.
And what Sara wants is not complicated. She wants to be fast and accurate, not one at the cost of the other: messaging she can ship this week and still defend when someone with budget authority asks how she knows.
Which is exactly the problem. So on Wednesday morning, she does the reasonable thing.
She pastes four transcripts into Claude and asks what her buyers care about.
The answer arrives in seconds. Fluent, structured, confident: three themes, five benefit statements, ready to paste into the deck. It reads like the work of a strategist who spent a week with her customers.
Then she looks for the seam: the line between what the model actually found in her transcripts and what it invented to fill the gaps. There isn't one.
One of the five benefit statements reads "cut reporting time in half." It is the sharpest line in the set for messaging, the one she would lead the launch deck with. She goes back through the transcripts. Nobody said half. One buyer said reporting used to eat most of her Friday and now it doesn't. That became a number, and the number arrived in the same confident sentence as everything else on the page. Somewhere in those nine seconds the model also decided two offhand remarks were a theme, and it did not mention that it had decided anything.
There are precise names for what she is looking at. Fluent fabrication: a plausible-sounding claim the data does not support. Silent interpretation: a judgment call the model makes without telling you. A general-purpose AI assistant commits both daily, and neither leaves a mark on the output.
Polished and true are not the same thing.
The people we interviewed felt feel it too. One product manager described his own do-it-yourself AI setup as "a bit of confirmation bias... writing a prompt from the product's hypothesis." The tool was answering the question his prompt implied. That is the villain of this story.
Sara also knows what is riding on the difference. In a previous article we told the story of a campaign built on one ungrounded positioning call: clean launch, sharp creative, almost zero pipeline, well into six figures gone. That was the human-speed version of the failure. The agentic era scales your bad execution exactly as fast as your good execution. We argued then that agents are already deciding, and the open question is what they decide on. For Sara, that question is not abstract. It is due Thursday.
The fix is not to stop using AI. She will not, and she should not. The fix is to ground the AI in verified customer truth, and to make its uncertainty visible instead of hidden.
So we built the colleague Sara needed. And we packaged her so you can run her yourself.
Amy is a senior product marketing manager you run inside Claude or Gemini. You set her up once, tell her where your company context, and from then on she works with you on positioning, messaging, pricing, launches, sales enablement, and measurement. She is direct, she gives you a clear recommendation with the reasoning behind it, and she does not let weak strategy through.
Plenty of AI assistants/agents will do those tasks. What makes Amy different is what she refuses to do while doing them:
Sara's first session with her sounds like this. 👇🏻
Sara: Should we lead the launch messaging with the integration story?
Amy: HYPOTHESIS, and I would not lead with it yet. The March win/loss report supports speed-to-first-value as the decision driver (said by 6 of 9 interviewed buyers: "we picked the one that was live before the pilot ended"). Integrations came up twice, both times as a checklist item, not a reason. If you want integrations to lead, that is a research question, and I can scope it.
None of this discipline is a personality quirk. It is build on the Bubble Research Methodology, the same method our product runs on, shipped inside Amy as part of her operating instructions: how research is planned, what counts as evidence, how findings get analyzed and reported. Not a promise in a README. The doctrine the rest of her behaviour hangs on.
Sara's problem this week is messaging. Yours might be pricing, a launch, or the battle card sales keeps asking for. Nine capability areas ship with her:
Step 1: Add her to your Claude or Gemini. We wrote step-by-step setup guides for both. You create a project, paste her instructions, upload her knowledge files. One-time setup, about 15 minutes, in the browser, nothing to install.
Step 2: Bring her your reality. A short State doc tells her your company, your ICP, your positioning, your open bets. That is her memory between chats. Then feed her the real material you already have: research reports, call transcripts, the objection a rep heard yesterday. She treats every one as data and routes it into messaging, ICP, and enablement.
Step 3: Let her keep getting better. Amy improves through a feedback loop: we ship regular updates to her instructions and knowledge, announced in our newsletter. Download the changed files, replace them in your project, and she is current.
That is the whole plan. No procurement, no integration project, no new tool to learn ,and no invoice: Amy is free, included the moment you sign up for Bubble's free plan. She lives inside the LLM app you already use.
Everything above works standalone. Paste or upload a research report and Amy reads it the way the methodology demands: she audits the evidence behind the findings she is about to build on, and she surfaces the report's flagged assumptions for you to confirm instead of letting them slide through.
If you run your research on Bubble, one more step makes her better. Connect your Bubble account through the bubble connector in Claude and Amy reaches your company's Bubble workspace (where your research lives) directly: she can list, search, fetch, and verify reports herself, citations included, read-only. Ask her to fetch the latest win/loss report and tell you what it changes in your messaging, and she comes back with the answer, the quotes, and the counts, without you shuffling files.
Same Amy. Shorter distance between a question and the evidence.
One honest boundary either way: Amy does not run your customer interviews (yet). When the research she needs does not exist, she does not guess. She drafts the research request that would close the gap: the decision that is blocked, the current hypothesis, and what result would change the recommendation.
Everything Amy does traces back to the Bubble Research Methodology, and the shape of it is worth thirty seconds, because it is also the answer to the question someone with budget authority will eventually ask: how do you know?
Why it exists. Most people who do research at work were never trained for it, and you should not need a research degree to defend a finding. The methodology gives product (marketing) people just enough foundation to do genuinely good research, and to survive scrutiny when real money is on the line.
How it works. Codebook thematic analysis with semantic coding: a fixed framework decides the shelves, and the codes are built from your transcripts, in your customers' own words, each anchored to a verbatim quote. AI does the mechanical passes. A human stays in the loop at exactly two checkpoints: audit the evidence, resolve the flagged assumptions.
What it produces. Findings you can defend. Every theme traces down to real quotes, every citation is checked against its source, and belief is kept separate from evidence with confidence labels.
The full methodology is a 52-page whitepaper, and we distribute it for free. If you want the foundation under Amy, or under your own research practice, download it here.
Version one. She ships the nine-second messaging answer. The deck is clean, the meeting goes fine, the campaign runs. The cost arrives quarters later, in a budget review, when someone asks which of those confident guesses actually came from customers, and the room goes quiet. We wrote last time about what that silence is: it is what a failed launch sounds like.
Version two. She walks in with three messages, and under each one: the claim, the customer's own words, the count, the confidence label. Someone with budget authority asks how she knows. She opens the quote. The debate moves from whose opinion wins to what the evidence says, and that is a debate she now runs. Nobody in that room calls what she does a supporting role.
The people in our research describe that second version in their own words. The professional one: "from sharing hearsay to presenting data." And the quieter, personal one: "I did my research, it's not just I was coming up with random ideas."
That second Thursday is the point of all of this. The person with "product" in their job title stops producing opinions and starts owning the customer truth their team runs on, for the humans deciding today and the agents deciding tomorrow.
The agents are already deciding. Amy is how your corner of the business decides on truth.