Issue No. 02 - June 16, 2026

Sometimes the answer is to stop tryng to connect everything.

I spent the better part of last week trying to solve a problem that turned out not to be the problem I thought it was.

Here's what happened.

At JB Sales, we run two separate platforms that both touch our members. UScreen is our membership portal where our pre-recorded sales training content lives and where members access it. Kit is where our newsletter and subscriber base live. When someone becomes a UScreen member, they also become a Kit subscriber.

We recently started a project to segment our Kit subscriber base by role. Individual contributor, sales manager, or VP/executive. The reason matters: what we offer each of those roles is different. The shift to add advisory services targeting the VP and executive level is actually the same business problem that started this whole journey. So getting the segmentation right in Kit wasn't just a data hygiene project. It was tied to something real.

Here's where it got complicated.

When we onboard a corporate group account into UScreen, we don't just hand them a link. We provide personalized instructions. Where to start. Which programs apply to their team. What to focus on first. Every group is different. And we wanted to capture the role of each person registering so we could keep our Kit data current and serve them better over time.

So I started asking: can we capture role data in UScreen and pass it back to Kit?

The short answer is no. Not in the way I needed.

UScreen's group subscription functionality requires a custom self-registration link. It tracks user counts, access terms, and usage analytics, all things that are non-negotiable for how we manage corporate accounts. The moment you try to route registration through an external system like Kit first and then pass the user into UScreen, you lose that functionality.

I found two options.

Option one: build a custom Kit landing page for each client. Capture the information we want there. When they submit the form, the confirmation email includes the UScreen self-registration link. Clean from a data perspective. But it means the user enters their name and email twice, once in Kit and once in UScreen. Not a dealbreaker, but not a great first experience for a paying client.

Option two: leave the onboarding process as it is. Send the group contact everything they need by email. Have users register directly in UScreen and answer three custom questions during signup. The role data stays in UScreen and would need to be manually entered into Kit afterward.

Neither option was clean. So I did something I should have done earlier.

I stopped trying to make the platforms talk to each other and started asking what we were actually trying to accomplish with each project.

The Kit segmentation project exists to provide value to subscribers and serve them relevant offers based on where they are in their career. The UScreen onboarding project exists to give clients a better experience when they join.

And through my thought process, and discussions with John on this, here's what surfaced: UScreen users are already clients. They've already bought. The segmentation logic we were building in Kit was designed for people who hadn't become clients yet, to nurture them toward the right offering. Trying to apply that same framework to people already inside the product was mixing up two different stages of the customer relationship.

It's still worth capturing role data for UScreen members. Particularly as we tailor or messaging and provide continued value to ALL subscribers, regardless of whether they have purchased something or not. But the urgency and the process didn't need to be the same.

So we decided to keep the two projects separate. At least for now. Each one gets to be what it actually is, instead of being forced to solve for the other.

Sometimes the clearest path forward is realizing you were trying to solve two problems at once and treating that as a feature instead of a flaw.

Where this lands in the three buckets

Immediately actionable: Before you connect two platforms, map out what data you need to move, in which direction, and whether losing any of it would break something. A 15-minute whiteboard exercise before you build saves hours of backtracking.

Start thinking about: How you're segmenting your audience and whether that segmentation logic makes sense at every stage of the customer relationship, not just at the top of the funnel.

Next phase: Building a clean data flow between your membership platform and your email platform. It's worth doing eventually. It just needs to be its own project with its own defined outcome, not a side requirement of two other projects running at the same time.

Meghan Brenner is COO at JB Sales and founder of The Operator's Notebook. The Muddy Middle publishes every Tuesday.