March 12, 2026
Updates from Tim Dietrich
In my last message, I shared an interview I did with Tim Dietrich.
Even though I just published it, we recorded back in October of 2025.
In the intervening five months, a lot has happened at the intersection of software development and AI.
Tim replied to the announcement email with an update that I think will be of interest, especially to the devs here on the daily list (shared with permission):
Jonathan -
Wow - thank you so much. For the opportunity to be on the podcast, for the time you gave me as we worked through the challenge I was facing, and for the years of friendship, even as we’ve passed like ships in the night.
A lot has changed since October...
I released my first digital product - an AI prompt library for NetSuite - and it has done very, very well. More libraries are on the way.
Oracle also reached out and contracted me to write a white paper and host a webinar on NetSuite AI and financial analysis. It was a great way to build authority - and it paid well, too.
I’ve been heavily using Claude Code lately, and it’s completely reshaped how I think about my work. As you know, I’ve always loved writing code, but I’ve realized I’m far more fulfilled - and a lot less frustrated - when I focus on solving expensive problems rather than writing every line myself. Not something I ever expected to say!!
A couple of posts on that, if you’re curious:
- A Prompt That Turns Any AI Into a Senior SuiteScript Developer
- I Assigned a NetSuite / Shopify Integration Project to My Virtual SuiteScript Developer. Here’s What Happened.
I’m still a solopreneur, but I now have a virtual team of 60+ agents working alongside me - and the roster grows almost daily. (And no, I’m not using OpenClaw.)
- I Built a Virtual AI Team Instead of Deploying OpenClaw. Here’s Why.
- 9 Prompts Aren’t a Team. Here’s What Made Them One.
Something interesting happened yesterday. A NetSuite client came to me with an urgent SuiteScript update. I was slammed, so I handed it off to my virtual developer - gave it the script, the client’s request / requirement, and let it run.
A few minutes later: updated script, thorough deployment notes, the works. The client was thrilled, and genuinely excited when I told them who did it.
Now I’m faced with the awkward part: how do I bill for this?
It was a rush job for a client I’ve always billed by the hour, so this time I charged for my time. But it’s pushed me back to rethinking how I price things entirely.
If there’s ever been a case for value-based pricing, I think this is it.
If you ever want to do a follow-up to the October episode - or just chat about how AI is reshaping authority, solopreneurship, and the business of expertise - I’d love that.
Thanks again, truly.
Tim
Thanks to Tim for allowing me to share this with the mailing list.
Here’s the thing...
Even if you’re not a software developer, the line that jumped out the most to me was:
If there’s ever been a case for value-based pricing, I think this is it.
Yup.
Yours,
—J