# Marcus Tello, RevOps Manager at Bonlook Commerce (82 people) — read of Customer Data Platform, May 13 2026 > Nine years in ops and revenue tooling, currently the person accountable for a Frankenstein stack of HubSpot, Klaviyo, Shopify, Stripe, and a Zapier workflow I built in 2022 that I am afraid to touch. --- ## How I got here Searched "unify shopify klaviyo customer data no engineers" on a Tuesday afternoon because I had just spent 45 minutes explaining to our head of growth why the LTV numbers in HubSpot and the LTV numbers in Klaviyo are different numbers from the same customers. A Reddit thread in r/revops mentioned "a Wishdeal page about a CDP that was actually honest about what it costs." I clicked. That is how low my bar for "honest" has gotten. --- ## What I clicked first The comparison table. Specifically the "Connector rot policy" row. "We monitor and fix / You monitor / You monitor / You monitor." That is the first time I have seen a vendor name the thing that actually kills these deployments. We had a Segment connector to HubSpot silently stop syncing for 11 days in January. Nobody noticed until a campaign went out to people who had already churned. So yes, that row got my attention. The "Five minutes to connect the first integration, two weeks to a full unified profile" headline also landed. It is specific. It is a promise with a shape. I can argue with it. --- ## Where I paused The pricing block. I had to read it three times. "Browse Free. Unlock the dossier, $5. Adopt the build, $99 to $199. Operator partnership, custom." I stopped because I realized I did not know what I was looking at anymore. I came here thinking this was a SaaS product I could try. But "adopt the build" sounds like I am buying... the idea? The code starter? The "adopt this idea" framing at the bottom confirmed it: "The dossier maps a realistic path; whether it works is up to you, your taste, and your distribution." So this is not a CDP. This is a blueprint for building a CDP. That is a completely different product. I had to go back and reread the whole page knowing that, which changed everything. --- ## What I distrusted Two things, one small, one big. Small: the header block lists "SOC 2 Type II Certified" as a procurement detail. Then further down, the security section says "We are pre-launch and pre-SOC 2." Those two things cannot both be true in the same page. I noticed it and it made me check everything else twice. Big: the "Trusted by Salesforce Stripe HubSpot Snowflake Shopify Klaviyo Intercom" section. That is a logos row. It implies these companies are customers or partners. But the honest disclosure says "we don't have live customers on this idea yet." So what does "trusted by" mean here? That the integrations exist in theory? That the founders have used those tools? It is the most misleading line on the page, and it sits right next to the section I was starting to trust. Also: "One pilot operator connected four platforms in under 20 minutes." If this is a pre-launch idea with no live customers, who is the pilot operator? --- ## What would convince me If this is a blueprint product, I want to see the actual code starter. Not a screenshot, not a feature list, a GitHub link to the repo with real commits and real schema decisions. Show me the identity resolution logic. Show me what a "connector health monitor" actually looks like in code. That would tell me whether the builder has actually solved the problem or just described solving it. If this is somehow a real product hiding behind confusing copy, I want one customer, named, who will get on a 20-minute call with me. Not a case study. A call. Someone who ran the Shopify-Klaviyo-Stripe unification and can tell me what broke on week three. The Fermi math showing negative year-one take-home ($-56,700) is oddly compelling as a trust signal, but it also confirms I am not buying a product. I am buying a research package on whether to build a product. That is fine but it should be the headline. --- ## What I'd ask in an email reply 1. The page says "one pilot operator connected four platforms in under 20 minutes." You also say you have no live customers. Who was the pilot operator and what does "pilot" mean in that context? 2. If I buy the $99 adopt tier and the code starter, what stack is it? Node, Python, something else? And how close is it to production-ready for someone running on AWS without a dedicated data engineer? 3. The comparison table shows your starting price at $380/mo. Is that the price for the SaaS you are planning to build, or the ongoing cost for the operator partnership model? I genuinely cannot tell. --- ## Verdict: on-the-fence The connector rot insight is real and I have lived it. But I arrived thinking I was evaluating a product and left realizing I had read a pitch deck for a product that does not exist yet, formatted to look like a product homepage. That is not dishonest exactly, but it is disorienting, and disorientation is not a feeling that converts me. --- *Memo by skeptic persona, generated 2026-05-13. Studio breaks own self-grading loop.*