Let me set the scene.

It is June 10th. I have just purchased IBM Bob Pro — a $16/month subscription — to support my consulting work. Simple enough, right? Except within minutes, I cannot log in. The system tells me my account is not provisioned. I opened a support case with IBM. And what follows is six days of back-and-forth with first-level support that, frankly, goes nowhere.

Not because the IBM support team was not trying. Maria was genuinely helpful. Pierre did some real digging. But here is the problem with integrated systems: when something breaks at the seams between them, first-level support often cannot see what you can see — especially if you know how those seams work.

I do.

---

The Runaround

The ticket trail tells the story well. On Day One, IBM’s Entitlement Exception Handling team told me my issue was not technical — it was a subscription matter. Call sales. On Day Two, same message, different agent. By Day Three, Pierre from the backend team confirmed the subscription was active and properly provisioned. So why could I not log in?

That is where it started to get interesting.

Maria’s instinct was good: she suspected the email used to purchase the subscription did not match my IBMid. That is a common integration fault. I updated my IBMid profile, confirmed that my primary email (perry@VogelConsultingLLC.com) matched my login — and still nothing. We scheduled a Teams call. I sat available until 5 PM CDT. IBM tried to schedule me at 5 PM. I had to correct that. Small thing, but it added to the friction.

---

What I Knew That They Did Not

Here is where my background in integrated systems kicked in.

I know that when two systems share an identity layer — in this case, IBM’s subscription platform and the Bob application — account associations do not always sync cleanly. The question is not just “does the email match?” It is which account owns the relationship?

I started mapping it out. I had two email addresses in play: my IBMid (perry@VogelConsultingLLC.com) and a personal Google account (pvogel@gra.midco.net). The Bob application had been originally associated with the Google account — not the IBMid. When I purchased Bob Pro while logged in under my IBMid, the order went through successfully. But the system then told me I needed an IBMid. Which was strange, because I already had one.

That is a classic integration symptom: the order system and the application system had different answers to the question “who is this user?”

---

The Fix — And the Calculated Risk

I could not create a new IBMid using my Google email address — the system rejected it. So, I did the next logical thing: I authenticated using the Google account itself. And when I did, the Bob Pro subscription appeared in the settings, right where it should be.

The account association was not broken. It was just pointed at the wrong identity anchor.

But here is the part worth spelling out. To get to that conclusion, I had to take a calculated risk. I purchased a second IBM Bob Pro subscription — knowingly — to test my theory. I only needed one. I knew I only needed one. But after six days of support going in circles, the fastest way to prove where the identity association problem lived was to place a fresh order and watch how the system responded. That second $16 charge was not a mistake. It was a diagnostic tool.

It worked.

To clean things up fully, I deleted the IBM Cloud Console tied to my IBMid, which severed the orphaned trial subscription that had been causing the license assignment conflict. Once that was gone, the paid subscription was clean, uncontested, and properly accessible. I have asked IBM to confirm the first order is canceled and that no recurring charges will stem from it. That is the last loose end.

I wrote it all up and sent it to Maria. Her response: “Your detailed investigation was very helpful.”

I appreciate that. But I will be honest — IBM’s first-level support did not have the tools or the visibility to trace that path. The escalation to the backend team would have taken days more. Instead, I spent an evening thinking through how the system was supposed to work, found where it had drifted from that design, and walked it back.

---

The Bigger Point

This is what modernization consulting is about. Not just the shiny new tools — it is the integration points. It is the place where System A hands off to System B and assumes the other side is ready. Those assumptions are where outages live. Where access failures hide. Where a $16 subscription turns into a six-day support saga — and where a second $16 subscription becomes the most efficient diagnostic move available.

Sometimes figuring it out costs a little something. In this case, it cost $16 and the willingness to think like the system instead of waiting for the system to explain itself.

That is a trade I will make every time.