Stop Answering the Same Question Five Times: How FAQ, Messages, and Private Notes Split the Job

The most expensive part of sourcing natural stone isn't the negotiation. It's typing the same answer over and over. You explain your thickness tolerance to one supplier on Monday, a second one asks on Wednesday, a fifth by Friday. Each version comes out slightly different, and by the end of the week you have five offers on the table, none of them priced against the same spec.

The problem isn't repetition, it's inconsistency

Answering the same question five times is tiring, but the real cost sits elsewhere. An answer written five times in five separate chats is never identical. One supplier gets the tolerance down to the millimeter, another never hears about your packing preference, a third is left guessing about certificates. Every bidder ends up pricing their own private version of your requirement, and the offers that look neatly comparable side by side are, in reality, answers to different questions.

That is why MarbleMap gives buyers three channels with a clear division of labor instead of one inbox: a demand FAQ that every supplier sees, a separate Messages thread per supplier, and a private note that never leaves your side of the screen. The playbook fits in one sentence: decide which information belongs in which channel before the questions start arriving.

In a sealed-bid market, information asymmetry is dangerous

Bids on MarbleMap are sealed. Suppliers cannot see rival offers, rival prices, or even how many offers a demand has received, which is what pushes everyone to submit their genuinely best number. But a sealed system is only fair if information is distributed evenly.

When a supplier asks about your certificate expectations in a private message and the answer stays in that one chat, that company now prices with information the others don't have. The other four bids are prepared blind. You built a competition and then, without noticing, handed one player an edge, and you pay for it later with a comparison that was never apples to apples.

The demand FAQ exists to close exactly that gap. Every question and answer you publish there is visible to every supplier who can access the demand, at the same time and in the same words; the Visible to suppliers label in the interface is a standing reminder that nothing in the FAQ is private. Answers are automatically translated into each reader's language, but translation isn't the point here. Fairness is: one answer, everyone, at once.

If every bidder needs it, write it once in the FAQ

The decision test is simple: does a supplier need this information to price correctly? If yes, it belongs in the FAQ. Thickness tolerances, the certificates you expect, packing preferences, clarifications on loading and delivery terms all pass that test. Even when the question reaches you through a private message, lifting the answer into the FAQ ends the repetition and guarantees that every offer arriving after that moment is built on the same spec.

Only the demand owner can write, edit, or delete FAQ entries; suppliers read them but cannot touch them. The answer field supports headings, lists, and links, so it is built for writing a proper piece of technical specification rather than a hasty chat reply. The practical routine: open the demand with an empty FAQ, watch what comes into Messages, and promote any question the moment it is asked twice.

If it concerns one supplier, keep it in Messages

Negotiation, an alternative block suggestion, a delivery discussion specific to one factory: that traffic belongs in Messages, not the FAQ. On MarbleMap every demand opens a separate conversation with each supplier, and those conversations are fully isolated. Competing suppliers cannot read what you write; they cannot even tell that other suppliers exist on the same demand.

The isolation works in both directions. Going deep into pricing with one supplier leaks nothing to the rest, and in return, anything commercially specific to a single company must never be posted in the FAQ, because everything there reaches every bidder. That is the whole channel discipline: shared facts up top for everyone, private negotiation below with one counterpart at a time.

Your evaluation never crosses the line, your teammate joins the thread

The third channel, My private note, sits on the Offers tab next to each offer and is never shown to the supplier under any circumstance. Weak packing references, ask for a sample, good price but risky lead time: judgments like these live on the offer card instead of in a chat where a slip of the finger could send them to the wrong audience. On comparison day, your notes are the memory of your reasoning.

And here is the step that finally kills the email forward chain: invite your technical teammate directly into the conversation. The Invite teammate control next to the composer lets you pick a colleague from your own company; the thread becomes a group, the header shows the participant count, and everyone can see who is on the buyer side and who is on the supplier side. No more screenshots, no more pasted threads, no more read from the bottom up. Invitations are limited to members of your own company and apply only to that demand's conversation.

Answer once, compare with confidence

Once the three channels settle into their roles, collecting offers becomes a different job: the FAQ equalizes the spec, Messages isolates the negotiation, the private note protects your judgment, and your teammate joins you without a forward chain. Opening a demand on MarbleMap is permanently free for buyers; the platform charges no commission and payments never run through it, while the supplier side runs on a subscription. If you're buying, open your first demand today and put the FAQ to work from the first question. If you're supplying, place sealed bids on verified demands, knowing your offer and your conversations stay strictly between you and the buyer. Find it at marblemap.co