Beta
Back to the blog
Product

What your team knows, in the product record: expert notes turned into facts with a source

In every business there's someone who knows the product better than any spec sheet. How to get what your team knows into the product record — by dictating it in a voice note — so it arrives as facts with their source, not as a comment lost in a chat.

3 min readNoobit team

Every catalog has someone who knows more than the spec sheet. The person at the store who has tried the shampoo, the sales rep who knows which hair type each product line is for, the technician who can explain in two sentences why that hair dryer is less tiring on your arm. That knowledge is worth its weight in gold and almost never makes it into the product record: it lives in their head, in a WhatsApp voice message or in a note nobody opens again.

The problem isn't missing information. It's that there's nowhere to put it so it reaches the product record, with the name of the person who said it.

Why what your team knows gets lost

  • Writing takes effort. The people who know the product best rarely have time to write.
  • It stays in conversations. What's said in a hallway or a chat never reaches the catalog.
  • It has no source. If it gets there at all, it arrives mixed in with everything else, and nobody knows where it came from or whether it's still true.

Dictate it instead of writing it

In Noobit, every product has its own expert notes. You press the microphone and talk the way you'd explain it to a customer: who it's for, how it's used, what makes it different. The note transcribes itself and gets cleaned of filler words, and you can correct the text if something wasn't picked up correctly.

Any note can be turned off when it no longer applies, without deleting it. And if you delete it, the audio is deleted too.

From the note to Product Knowledge

A note doesn't go straight into the description. It goes into Product Knowledge, the place where Noobit gathers everything that's known about the product: what the supplier provides, what research finds, the files you upload and what your team says. When it's consolidated, what the note says becomes specific facts, and each fact carries its source: you can see which ones come from an expert note, just as you can see which come from the supplier or the manufacturer's website.

A new note marks Product Knowledge as due for an update, and it's brought up to date before the product page is written again. And that's where you're in charge:

  • You pin a fact and the AI no longer overwrites it: it becomes the basis for the writing.
  • You hide a fact you don't want used, without deleting it.
  • If two sources say different things, the fact is flagged and you choose which one is right.
  • Every change is kept in the Product Knowledge history, with what was there before and what's there now.
What to put in a note
What isn't on any spec sheet: who it's for and who it isn't for, how it's really used, what it goes with, what customers ask. It doesn't have to be long; it has to be true.

What changes on the product page

The description stops sounding like a supplier catalog and starts sounding like someone who knows the product, because it's written from what your team knows. Since every fact has its source, when someone asks where a claim comes from, there's an answer. And what your team knows no longer depends on that person being around: it stays in the catalog.

Put your catalog on autopilot

See Noobit working on your own catalog, with no strings attached.