What I Worked On in July 2026: Payments Content and a Slow Demand Gen Month

Last month was about simplification. I spent most of June untangling dense payments concepts and finding clearer ways to explain them.

July asked something different of me: help audiences see payments not as a launch to celebrate, but as a business discipline to keep running.

That idea shaped almost everything I worked on this month, from our latest podcast episodes to our monthly newsletter and the small conversation starters we handed off to sales.

At the same time, July was also a humbling month from a demand generation perspective. Despite launching meaningful campaigns and putting a lot of thought into the work, I reached the final stretch of the month without generating a single marketing-qualified lead.

That was disappointing.

It also forced me to hold two things at once: I could be proud of the quality and strategic direction of the work while still being honest that the results had missed my expectations.

So in addition to talking about content and messaging, this month’s recap is also about what happens when the work feels strong, the effort is real, and the outcome still falls short.

Payments Models and Payments Maturity Are Not the Same Thing

The main idea of July's theme came out of our Payment Pulse Podcast episode titled, "Payments Models vs. Payments Maturity." The episode made a point I keep coming back to: two software companies can run the same payments model, process similar volume, and still operate at completely different levels of maturity.

Picking a model is one decision. Becoming mature in payments takes ongoing attention to things like merchant adoption, operational processes, customer support, reporting, revenue optimization, and ever-changing customer needs. None of that shows up in a launch announcement.

It’s also worth noting that the payments model you chose in the beginning doesn’t have to be the one that you stick with as your company grows. It’s definitely okay to pause and ask if your current model fits the stage your company is at today. I wrote a blog article diving into this topic as a companion to Xplor Pay’s Flex Framework: Why Great SaaS Companies Outgrow Their Payments Strategy

What I'm taking from this: a payments model describes how a program is built. Payments maturity describes how well the business keeps operating, improving, and growing them. If you're only measuring the first one, you're missing the story that actually determines whether the program succeeds.

Turning Our Podcast Into a Connected Content Program

July also pushed me to think harder about repurposing. For our latest episodes, I built out social captions, meta descriptions, YouTube and Spotify descriptions, TL;DR points, FAQs, short promotional copy for video clips, and newsletter promotion. I also took a short scripted exchange from an insights clip and turned it into tight social copy.

None of this was new work, exactly, but it felt different than it has in past months. The content system we’re building is getting more mature in its own right. The episode is still the source material, but the surrounding assets each create their own entry point for a different kind of reader or listener.

The lesson I'd pass along: repurposing works best when every asset has a distinct job. A video clip should spark curiosity. An FAQ should resolve one specific question. A newsletter blurb should give someone a reason to keep reading. Trying to make one piece do all three usually means it does none of them particularly well.

Building a Newsletter Around Growth After Launch

The July Payment Pulse newsletter pulled together chargeback management, payments maturity, growth plateaus, whether a payments model still fits the business, and how to build long-term value once the initial launch excitement fades. I also shared an older article about the limits of static payments models that was refreshed with a new angle, all without touching the core argument.

Pulling those pieces together took more editorial judgment than I expected going in. A newsletter lands better when the resources inside it feel like they're in conversation with each other, rather than a list of links that happen to share a topic. In July, the through-line was simple: launching payments is the beginning of the story, and the more valuable work happens in everything that comes after.

Connecting Payments Content to Sales Conversations

The highlight that mattered most to me this month was less about any single asset and more about where the content pointed. Across the podcast, newsletter, and outbound work, I kept translating payments topics into questions a sales rep could actually use in a live conversation: Is your payments program still maturing? Where does a static payments strategy start holding back growth? How do you follow up around an event or resource without it feeling like a form email?

This makes me realize that content shouldn’t just fill a calendar; it should give the sales team a better way to talk to a prospect. July reminded me that demand generation work is judged less by the volume produced and more by whether it changes the conversations happening downstream.

Sitting With a Month That Missed Expectations

As mentioned at the beginning of this blog, July brought a result I was disappointed to see: I generated zero marketing-qualified leads in the first three weeks of the month, and the last week isn’t looking any different.

That was difficult to sit with, especially because the month did not feel inactive. I had launched two larger campaigns: an event management vertical nurture reaching 350+ contacts and a Tap on Phone campaign reaching 650+ contacts. I had put real thought and effort into the audiences, messaging, resources, and follow-up.

But effort and outcomes do not always move in a straight line.

July also had a slower summer rhythm. I only had two trade show campaigns running, compared with busier periods of the year when event outreach creates more opportunities for sales conversations. Fewer campaigns in market meant fewer chances for prospects to raise their hands.

That context matters, but it does not make the result less disappointing.

This is the part of demand generation that does not always make it into the highlight reel. You can follow the process, launch meaningful work, and still miss the outcome you expected. When that happens, it’s tempting to treat one slow month as proof that the entire strategy has stopped working.

I’m trying to resist that instinct.

One bad month is a data point, not a verdict. It doesn’t erase the progress that came before it, and it doesn’t automatically mean the campaigns were wasted. But it does mean I need to look more closely at what the month is telling me.

Were the audiences right?
Did the messaging create enough urgency?
Were there clear enough opportunities to respond?
Did the campaigns need stronger follow-up messaging?
How much did seasonality affect the available demand?

I don’t have every answer yet. What I do have is a clearer reminder that demand generation requires both confidence and humility. You need enough confidence to keep building when the results are slow, and enough humility to examine the work honestly when expectations are missed.

What July Taught Me

The TL;DRs are:

Payments content has a life after the launch story. So much of the messaging around embedded payments focuses on the moment a program goes live. The more interesting questions come later: how adoption is growing, where operations are creating friction, whether the current model still fits, and what's standing between the program and its next stage. That's a bigger, more strategic story than "we launched."

Content programs need both depth and accessibility. A full podcast episode can sit with nuance. An FAQ can answer a search-driven question in two sentences. A short clip can introduce a single insight. A newsletter can connect several resources under one theme. Each format is doing something the others can't, and each one meets someone at a different point in their journey.

Repetition earns its keep when the framing changes. I came back to payments maturity, static models, and post-launch growth more than once this month. That repetition builds positioning, but only because each version of the idea carried a slightly different application than the last.

A slow month is information. Missing a target should lead to reflection and adjustment, without erasing the progress that came before it.

Looking back, I’m still proud of the work I’ve accomplished despite having a slower month. See you back here for next month’s learnings.