Stories

Why we are building Crossdeck Sales

Cold outbound is miserable because the seller is blind. We were not — we already saw who landed, what they read, and why. So we are building the tool that turns that journey into outreach that lands.

Not yet released Crossdeck

A first look. This one is not live yet — the directive is written, the code exists, and we are building it for our own pipeline first. Here is the why.

Summary

  • Cold outbound is miserable because the seller is blind — you email a stranger and guess at everything: whether they care, what about, and when.
  • We were not blind. We already run Crossdeck, so we could see who landed, what they read, and the journey that brought them. And we were still writing cold email like everyone else.
  • That gap is the whole product. Crossdeck Sales turns the journey you already own into outreach that lands — a note that references what a prospect actually did, honestly.
  • It is coming, and we are dogfooding it on our own funnel before anyone else touches it.

The confession: we sell too, and cold outbound is awful

Every company that builds also sells. And outbound — the cold email, the “just circling back”, the message fired at a stranger who never asked — is the part everyone quietly dreads. Not because selling is bad, but because the seller is working blind.

You do not know if the person cares, what they care about, or whether this is the worst possible moment to land in their inbox. So you guess, you generalise, and the recipient can feel the guess. That is why cold email gets ignored: it is addressed to a category, not a person.

The thing we could not un-see

Here is what made it absurd for us specifically. We run Crossdeck across our own products, which means our own visitors are not anonymous shapes in a funnel — they are journeys. We can see that someone arrived from a particular place, read a particular page, left, and came back. We can see intent as it happens.

And we were still sending cold email. Sitting on the exact signal that makes outreach warm, and writing to people as though we had never met them. The absurdity is the product spec. If you already know why someone showed up, there is no reason on earth to send them a generic note.

Picture the ordinary version of it. A founder at a security company reads one of your pages late on a Tuesday, comes back on Thursday, and spends six minutes on your pricing. In a normal stack that person is a row in an analytics tool nobody will ever connect to your outbound. With the journey in hand, they are the easiest, warmest, most obvious message you will write all week — if something turns that journey into a draft.

What Crossdeck Sales is

Crossdeck Sales is outbound outreach powered by the buyer’s journey you already own. It turns what a prospect actually did on your surfaces into a tailored, honest message that references exactly that. Not a spray of cold templates. A note that lands because it knows why the person is there.

The difference is the difference between guessing and knowing. Everyone else’s outbound tool helps you send more to people you understand less. This inverts it: fewer messages, each one grounded in a real journey, each one obviously worth reading because it speaks to something the recipient actually did.

Why journey-aware beats cold, on every axis

  • Timing. Cold email arrives whenever your sequence fires. Journey-aware outreach can arrive when someone is actually engaged — the day they came back, not a random Tuesday.
  • Relevance. Cold email guesses the topic. Journey-aware outreach knows it: you read the pricing, so let us talk about the pricing.
  • Honesty. A message grounded in real behaviour does not have to pretend. It can simply be specific, which is the most persuasive thing a first message can be.

The line we hold

This only works if it stays honest, and the guardrails are in the directive from the start. It is first-party: the journeys are people arriving on your surfaces, not surveillance of their lives elsewhere. The outreach discloses who it is from and never fabricates a fact about the prospect. And a human sends it — Crossdeck Sales drafts; it does not blast.

Journey-aware is the opposite of spammy. It means writing to fewer people, more truthfully, at a better moment. If it ever felt creepy, we would have built it wrong.

Why we are building it

Because we felt the exact pain while holding the exact fix. That is the most honest reason to build anything, and it is the same pattern behind every product here. Crossdeck already owns the layers that make outreach warm — identity, analytics, the journey — and leaving that power sitting in a dashboard while we wrote cold email was the tell that a product was missing.

So we are building it, and pointing it at our own pipeline first. The best proof that journey-aware outreach works is that it is the only kind we will be sending.

It is not live yet. This is the why. When it is ready you will hear it from us — probably in a message that already knows you read this page.

Want the first message when Crossdeck Sales opens up?

Tell us and we will come back to you when it is ready.

Questions people ask

What is Crossdeck Sales?
Crossdeck Sales is upcoming outbound tooling that turns a prospect’s real journey on your own surfaces — where they arrived from, what they read, when they came back — into a tailored, honest outreach message. Instead of cold templates sent to strangers, it drafts a note grounded in what the person actually did.
How is journey-aware outreach different from cold email?
Cold email is addressed to a category and sent on a fixed schedule, so it guesses at relevance and timing. Journey-aware outreach is grounded in a specific person’s real behaviour — the page they read, the moment they re-engaged — so the message is relevant and well timed because it references something true rather than assumed.
Is using visitor journey data for outreach creepy?
It does not have to be, and it should not be. The honest version uses first-party journeys — people who came to your own surfaces — discloses who the outreach is from, never fabricates facts about the prospect, and keeps a human in charge of sending. It means writing to fewer people more truthfully, which is the opposite of spam.
Is Crossdeck Sales available yet?
Not yet. The concept and guardrails are defined and it is in development, being tested on our own sales pipeline first. This piece is an early look at why we are building it.

Every product named here is built and operated by Cross Constellation.


The reason

We felt the exact pain while holding the exact fix.

Read next

Why we built Crossdeck — and why every product we build helps test it
We thought the App Store Connect wait was the problem. The real problem was fragmentation — the same person scattered across a dozen disconnected tools. So we put one SDK and one customer timeline underneath everything we operate.

Every product is a test environment for the one beneath it
A habit tracker on the App Store, a link-in-bio product carrying anonymous global traffic, and a book catalogue on two platforms. None of them was built to test anything. That is exactly why they work as tests.

The Firebase bill that taught us to see
A runaway Firestore read bill sent us chasing ClickHouse. The real fix was not a new database — it was being able to see where every read came from. What we learned, and why we open-sourced Buckets.

The email address you’re keying on is not the person
Why email is a fragile anchor for user identity, how keying on the wrong id forks one person into many records, and how an identity graph converges every key onto one canonical customer.

We got our connector rejected. It was the best product spec we received all year.
A marketplace review rejected our connector with roughly a dozen findings. Instead of a failure, it read like a spec — the exact definition of a production-grade third-party integration we would never have written ourselves.

The black box blinks: seeing App Review happen in your own data
App Review is a black box. Identity-joined session data reveals when a reviewer starts testing your build, where they connect from, and the exact path they walk — plus the line we will not cross.

Why Biotree needed Crossdeck Trust — and how we stopped the SEO spam farms
Public, indexed link-in-bio pages are a magnet for spam farms and bot signups. The attack Biotree faced, why the obvious defences backfire, and the signup firewall that stopped it without punishing real users.