Customer stories

Installs you can check

The useful question about a developer platform is not what it claims. It is who runs it in production, what they had to decide, and whether the code holds up when you read it. So these write-ups carry the actual install — and where the customer's SDK bootstrap is served publicly, you can go and read the source yourself rather than take our word for any of it.

  • Lead attribution

    ProLend: the consultant already knows what you read

    A private-lending business with no app and no subscriptions, using identity to hand a human consultant the visitor's whole journey before the call. Vanilla site, no build step, anonymous → named stitching, and a deliberately opt-out consent posture that still enforces a decline.

    Web SDK · identity · consent · Pipedrive

How these are written

One story is not a wall of logos, and we are not going to pretend otherwise. This section starts where it starts and grows as installs are worth writing up. What will not change is the standard:

  • Verifiable over flattering. Facts come from the customer's live code, not from a marketing questionnaire.
  • The decisions, including the awkward ones. Where a customer deliberately went against a Crossdeck default, that is the most useful part of the page, so it is in there with the reasoning.
  • No invented numbers. If a lift has not been measured under conditions worth trusting, no percentage appears. A case study that quotes a figure nobody computed is worth less than one that admits it.

Crossdeck itself is the other install worth knowing about: it is built and operated by Cross Constellation, whose other products run on it in production. The SDK ships into software taking real money before it is recommended to anyone else.

Running Crossdeck in something interesting?

Unusual installs make the best write-ups — especially the ones that do not look like the examples in the docs. If yours is one, we would like to read it.