DemandBolt
Start your 7-day trial
← All resourcesCase study / DemandBolt field notes

Rae: researching a different buyer without mixing the evidence.

Learning case study. Experiment record: 1 September 2026. Rae tested whether tutors and educator-builders valued retrieval-first, correction-aware practice. This reports the research setup and its evidence limits.

A learning product has more than one buyer

Rae helps learners work with real schoolwork. Learners, parents, tutors, and institutions can have different problems and reasons to pay. A message about convenience for a tutor is not automatically a useful offer for a student.

The recorded research experiment focused on tutors and educator-builders interested in retrieval-first, correction-aware practice without setting up every unit manually. Keeping that audience explicit made it possible to select sources and prepare a relevant question.

Combine source types, then inspect each candidate

The September 1 report used public tutor and student discussions alongside primary product feature and bug reports. These sources reveal different kinds of friction: repeated manual work, uncertainty about learning outcomes, or a missing workflow.

A feature request does not establish buying intent. The candidate’s observed problem and commercial inference stayed separate, with an original source for review. No private contact details were collected in this staging experiment.

Recorded on 1 September 2026Result
New candidates staged5
Existing candidates refreshed0
Prior review decisions changed0
Outreach in the staging recordNone sent
Paid outcomes demonstratedNot established

Keep evidence and success measures specific to the product

The five candidates entered Rae’s own project review queue. They did not become PyInvesting leads, and prior hypotheses were retained. This matters when a founder operates products with different buyers.

For a learning workflow, activation should show learning value: a corrected error, a successful independent question, or a return to practice. A channel click helps explain arrival, but it is not the same as a useful learning outcome.

What is known, and what must be tested next

The documented outcome is a structured, reviewable shortlist. The seven-day experiment aimed for three substantive conversations and one explicit design-partner commitment. The record does not demonstrate those commercial results.

The next step is to inspect the sources, approve appropriate candidates, ask the narrow question, and record replies and product use. If the audience values a different task, change the brief before expanding the shortlist.

The reusable lesson is to tie each acquisition motion to its buyer and activation event. A shared workspace is useful only when it preserves those distinctions.

Source notes

These public product pages provide context. The experiment results above describe our dated internal record, not an independent customer testimonial.

From reading to doing

Put one customer hypothesis to work.

Create a project, review real evidence, and keep an honest record of what happens next.

Start 7-day trial View plans and limits