Their numbers, not ours.Stories built only from what each customer published.

A customer story here is the customer's own account, and only that: their AppExchange review in full, anything they have published on their own site or in their own press, and the outcomes they chose to attach their name to. If the customer did not publish a number, the story does not have one.

What counts as a customer story here

Most vendor case studies are written by the vendor. The customer approves a draft, the vendor supplies the percentages, and the reader cannot tell which sentences came from whom. These pages work the other way around. Each story is built from three kinds of source, and nothing else:

• The customer's own AppExchange review, reproduced in full and unedited, spelling, punctuation and typos included.
• The customer's own website or press, where they have published something about how they run Kugamon.
• The customer's own published outcomes, each attributed to them in the line where it appears.

That makes them read differently from a case study. There is no challenge-solution-results arc composed after the fact. There is what the customer said they needed, what they say they run, and the numbers they put their name to.

What you will not find

No Kugamon-calculated return on investment. No contract values, deal sizes or invoice amounts for any named customer, ever. No paraphrased quotes. No "up to" or "as much as" wording that stretches a figure past what was published. Where a number appears, it is labeled customer-published, and the customer who published it is named beside it. Where the customer's review includes a criticism, it stays in.

If you would rather start from the raw material, every AppExchange review is quoted verbatim at /customers/reviews/, and the full customer list is at /customers/. The stories below are the customers who have published enough about their own results for a page of their own.