I started the call by doing the thing I always say I’m not going to do, which is turning a normal catch-up into a screen-share demo.
I had been messing with a voice dictation app on trial, and instead of just saying, “Yeah, it seems good,” I walked him through it live. I talked into my mic, watched the words appear, corrected a couple of awkward phrases, and then immediately started comparing it to the other dictation tool I’d been using. It was very much one of those consultant conversations where we pretend we’re just chatting, but five minutes later we’re deep in pricing models and privacy language.
The part I kept coming back to was where the data goes. One app lets you download the model locally, so your voice and text stay on your machine. The other one has a private mode, but it’s still cloud-based. I could hear myself getting a little too excited about this, like I had discovered fire, but it actually matters for client work. I don’t want to be casually dictating something sensitive into a tool and then realizing later I never really understood where it was being processed.
The lifetime license was tempting. That was the problem. I was still in the trial window, but I had already started doing the math in my head where “expensive” becomes “responsible” if I use it enough. I also sent a note to our internal IT contact because I didn’t want to buy it, fall in love with it, and then find out it was a hard no for corporate use. That would be very on-brand for me: optimize the wrong step first.
After that we moved into actual client work, which had less shiny-new-tool energy and more “please let these numbers tie out before the month ends” energy.
I had sent a client contact a summary of a revenue reconciliation I’d been working through. I used AI to help review the logic, not to magically solve it, just to catch anything dumb I might have missed. The basic problem was still sitting there: recognized revenue on one side, system figures on the other, and a gap that needed source data from the transaction platform before I could say anything cleanly. I hate that stage of a reconciliation, where you’ve done enough to know there’s a real issue but not enough to close the loop. It feels like standing in a doorway with a stack of papers.
There was a little good news mixed in. A former client contact reached out from a new company about possible business software work. Nothing real yet, just a thread that depends on a finance leadership meeting, but still. Those messages hit different when the month is tight. You try not to act hungry, but your brain absolutely starts moving invoices around before the work even exists.
We talked about payment timing too, which is not glamorous but was probably the most honest part of the call. I told him that when client payments land, I’d prefer same-day forwarding if possible. Not because I’m trying to be difficult. Because this month has been heavy. Kids are home for summer, food disappears faster, random expenses keep showing up, and the normal cushion feels thinner than it should. He got it immediately because he’s in the same general boat. There was no big dramatic speech, just two people admitting that timing matters more than we wish it did.
Then the conversation slid into co-parenting logistics, which is its own kind of project management except the stakeholders are tired children and school calendars.
We were looking at overlapping schedules for the kids, games and cheer events landing on the same nights at different schools. On paper it sounds like a simple split: one parent goes here, the other goes there. In real life there are drive times, who wants which parent present, who has gear, who needs to be picked up afterward, and the quiet guilt of knowing somebody is probably going to feel like they got less of you. We landed on an alternate-night plan, or at least the start of one. It wasn’t perfect. It was just the version that didn’t immediately collapse.
By the back half of the call we were talking about cameras for bike content, because apparently my brain needed to spend imaginary money after talking about cash flow pressure. Action cameras, mounts, battery life, whether a 360 camera makes sense, whether used gear is smart or just another way to inherit someone else’s problem. I kept circling the same question: am I actually going to make enough bike content to justify buying something, or do I just like the idea of being the kind of person with a clean little camera setup?
That’s where the call kind of stayed for a while. Work tools, client gaps, possible leads, kid schedules, money timing, camera gear. Nothing got fully solved. A few things got slightly more sorted. A few things just got said out loud, which sometimes is the only progress available on a Tuesday.
