Make the research useful, protect the integrity of the evidence, create a professional asset and keep your editable files safe. This manual is about operating the actual released software.
Customer Detective is your private investigation desk. Save its project JSON to preserve buyer files, notes and evidence entries. Export a buyer dossier HTML to read or archive one candidate. Do not publish confidential research without checking it.
Buyer Questions Studio creates a public-facing page from facts and answers you are comfortable sharing. Its project JSON is editable; the exported HTML is the functioning public asset. The builder does not host the file, collect leads or guarantee rankings.
Open Customer Detective. Use New file for one segment. Enter a specific group, present problem, triggering situation, desired outcome, possible objections and access hypotheses. The tool does not require all fields to be completed at once.
Choose Load example only to learn the workflow. It replaces the current project and is explicitly labelled fictional.
The Signals tab records firsthand observations, external signals and untested assumptions. Firsthand and external entries require a source description. Keep identifying personal information out of export files where possible.
Record disagreement and missing data; evidence quality matters more than the raw number of entries.
The Triage tab displays four self-rating sliders: urgency, reachability, offer fit and viability. Each is scored 1–5 by you. Their sum reaches a maximum of 20; it is neither market size nor a statistical confidence percentage.
Compare the evidence list beside the ratings. A well-researched modest score can be more actionable than a high score built only from guesses.
In Debrief, enter the fact you most need to verify, a realistic small test and what happened. Use Download Buyer Dossier for a readable independent HTML record; use Copy investigation brief to carry your notes to another tool or research process.
Write actual observations rather than invented campaign outcomes.
Add multiple buyer files if two situations involve different events, problems or buyers. Each maintains its own evidence and ratings. The comparison table makes your own choices transparent, not automatic. Current limits are 30 buyer files and 80 signals per file.
The active selection remains inside its separate editable project JSON.
Save JSON creates a portable project file. Open JSON validates the matching product and schema before replacing the editor state. A local browser autosave is a convenience only, not cloud backup or cross-device synchronisation.
Keep a dated JSON file before major edits and never rely on one browser profile as your only archive.
Open Buyer Questions Studio. In Content set the truthful business name, useful headline, introduction and optional CTA. In Answers, write complete questions and practical answers. Move questions up/down, remove weak ones and add up to 40.
Do not use testimonial-like proof you cannot verify. Its demonstration is fictional and is marked as such in the exported page.
The Design tab has eight palettes, independent background, text, accent and card colours, typography, alignment, card corners and three presentation patterns: Cards, Editorial and Accordion. The editor theme button changes only the editing environment.
Export checks text contrast against both the page and card background. Choose a different palette or refine colours if readability fails.
The builder's preview uses the same output HTML generator as the download. Test Desktop and Mobile at minimum. Use Open full preview to inspect the complete page and its click targets. For accordions, open and close answers before exporting.
Preview contains temporary placeholder text only when fields are empty. Export requires a real title, name and at least one complete question/answer.
Download finished HTML saves an independent responsive webpage without Ghost or ProductDyno authentication. Upload it using the static hosting or site platform you control and test all destination links. If you supply an external logo URL, the logo needs that URL to stay available.
The tool does not create a live URL, submit web forms, host analytics or promise search placement.
The generated file includes a title, description, semantic content structure, accessible links and viewport settings. Search engines can only encounter the page after you publish it publicly and allow ordinary crawling. Real expertise, accurate content, internal navigation and relevant links remain essential.
No fabricated AI-discoverability scores, ranking guarantees or auto-generated endorsements are added.
If the export refuses to download, read the message beneath the download buttons; it identifies missing required content, unsupported URLs or low contrast. If an import fails, verify you are opening the correct product's JSON rather than the final public HTML.
If a page works locally but not after publication, test the file path, uploaded filename, image URL and hosting permissions. Browser-local saving cannot repair hosting configuration.
Start with a customer situation, verify a genuinely useful question, publish a clear explanation, then choose an appropriate acquisition route. If more advanced work is needed, use ACCESS to investigate where the buyer actually spends attention.