DEV Community: Chad Dyar

Eight days after launch: zero purchases, and what I am changing

Chad Dyar — Tue, 18 Aug 2026 14:23:04 +0000

I shipped a self-serve product two Mondays ago. Sales page tested clean on two devices. Checkout works. Monitoring is quiet. Eight days later: zero people have finished the free assessment that is supposed to be the front door, and zero purchases.

That is not a soft launch story with a happy ending yet. It might still turn into one. The honest version of this post is the one where I tell you what I actually know eight days in, not the one where I dress a flat line up as a slow build.

What the product is

A twelve week self-serve kit for sales orgs that want to build coaching infrastructure with their own people, no consultant, no calls with me, ever, by design. The whole point is that it works whether I am paying attention to it or not, which shaped the marketing too: it cannot rely on me showing up either.

What I instrumented, and what I did not

PostHog tracks every step of the assessment: started, completed, email submitted, results viewed. That part is solid. The sales page only fires a pageview. There is no buy-click event, so I currently cannot see whether people reach the page and bounce before checkout, or never reach the page at all. That gap should have shipped with the funnel instead of after it, and it is the first fix.

The real number

Zero assessment completions in eight days reads like a conversion problem. It is a traffic problem. A one time batch of launch posts went out the day the page went live, most of it lost to a platform gate I had already decided on before launch and knew would apply, and little went out after that. Traffic that never arrived cannot convert.

What changes this week

The fix is not a better landing page. It is putting this product into the same weekly content rhythm everything else I market runs on, instead of treating launch week as the whole campaign: one assessment link, repeated weekly, across the platforms actually live for me.

If the number still has not moved after a real month of real traffic, that is a more useful piece of information than the one I have now, because it moves the conversation back to strategy instead of tactics. Right now there is not enough traffic yet to know which conversation this is.

Free assessment, if you run coaching for a sales team: chadtdyar.com/coaching-score.

Bring Your Best Self To Work

Chad Dyar — Fri, 07 Aug 2026 14:45:07 +0000

You Built Something. Now Build Yourself.

If you're a developer, you know the feeling. You've shipped features that scale. You've debugged code at 2 AM. You've learned languages, frameworks, databases, and architectural patterns. You've invested thousands of hours becoming better at your craft.

Then why do you feel like you're holding yourself back at work?

The gap isn't technical. It's personal. And it's not something a conference talk or a new tool will close.

Most of us treat personal development like optional content. We'll spend a weekend learning a new stack, but we won't spend an hour understanding how we show up in meetings, how we communicate under pressure, or why we sabotage ourselves right when something matters. We optimize our code but run our lives on default settings.

I wrote "Bring Your Best Self to Work" after watching this pattern repeat across hundreds of people in technical roles. Smart, capable developers who were genuinely stuck. Not because they couldn't solve technical problems. Because they couldn't see the personal problems that were actually in their way.

Here's what I found: the people who moved fastest weren't the ones with the biggest brains or the best certifications. They were the ones who could recognize their own patterns, adjust their approach based on feedback, and show up differently depending on what the moment required. They treated themselves like a system worth optimizing.

That sounds basic until you realize most of us don't do it. We coast on raw talent, blame external circumstances when things don't work out, and then wonder why the same problems keep happening.

The book moves through five core areas: how you think about yourself, how you handle pressure, how you communicate what you know, how you show up in relationships with people who can't code, and how you recover when you stumble.

Each section is built around a real problem I watched developers face. Not hypothetical problems. The actual moments where capability wasn't enough. Where knowing the right answer wasn't the same as saying it in a way people believed. Where confidence became arrogance, or humility became invisibility.

You get frameworks that actually work (not flowery metaphors that sound nice and do nothing). You get permission to be imperfect. You get a realistic path from where you are to where you want to be.

This is for people who want to lead without changing jobs. For people who want to influence projects without formal authority. For people who got hired because they're brilliant at their craft and realized that's not actually enough.

Bring Your Best Self to Work is the book I wish I'd read earlier. Not because I was broken. But because I was capable and underutilized, and I didn't know why until I looked at the personal side of the equation.

If that resonates, the book is here: https://www.chadtdyar.com/books/bring-your-best-self-to-work?utm_source=devto&utm_medium=community&utm_campaign=devto-20260807-bringyourbestse

The Deliberate Breath

Chad Dyar — Fri, 07 Aug 2026 01:01:30 +0000

The Debug You Can't Find in Your Code

You've been staring at the same function for twenty minutes. The logic is sound. The tests pass. But something feels off, and you can't name it. So you keep reading the same lines over and over, hoping the answer will suddenly appear between the curly braces.

It won't.

What you're actually dealing with is not a bug in the code. It's a bug in your nervous system. Your attention has fractured. Your breathing is shallow. Your body is in a low-grade fight-or-flight state, and from that place, your brain cannot generate the kind of relaxed clarity that debugging demands.

This is not poetic. This is physiology.

The Deliberate Breath is not a productivity book wrapped in meditation language. It's a practical guide to understanding how your breath connects to your cognitive load, your attention span, and your ability to solve problems under pressure. For developers specifically, it matters because debugging is not just a technical skill. It's a neurological one. The best debuggers are not necessarily the smartest people in the room. They're the ones who can stay calm enough to see the pattern everyone else is missing.

I wrote this book after watching engineers with junior-level coding skills outpace senior engineers with vastly more technical knowledge. The difference was not intelligence. It was regulation. The juniors had learned (or stumbled into) ways of managing their own nervous systems that kept them functional when the pressure mounted. The seniors had not.

Most technical books teach you what to think. The Deliberate Breath teaches you how to think when the stakes are high and your brain is threatening to shut down on you. That is a different skill entirely.

The book does three things. It explains the mechanics of how breath and nervous system regulation connect to focus and problem-solving. It gives you specific techniques that work in real time, not techniques you have to practice for six months before they become useful. And it addresses the particular pressure points that developers face, whether that's the 2 a.m. deploy that went sideways, the code review where you feel attacked, or the architecture decision you're not confident about.

You do not need to become a meditation expert. You do not need to sit cross-legged for an hour. You need about ninety seconds of deliberate practice to shift your nervous system into a state where your actual skills can show up.

The reason this matters now: we are all working in higher-stress environments than we were five years ago. Remote work, context switching, on-call rotations, the constant flow of Slack, the pressure to ship faster. Your technical skills are the same as they were. Your bandwidth is not. Most engineers I know are not struggling because they forgot how to code. They are struggling because they cannot access the cognitive resources they need because their nervous system is dysregulated.

That is fixable. Not through willpower or discipline, but through understanding how your body works and using that understanding deliberately.

The book is short. It does not waste time on theory that does not connect to your actual work. Every technique in it came from watching engineers use it, fail with it, refine it, and eventually make it their own. Some of those engineers now use it before stepping into a difficult conversation. Some use it when they feel their focus splintering. Some use it when the error message makes no sense and frustration is creeping in.

The goal is not enlightenment. The goal is getting your own best thinking back online when you need it most.

You can find it here: https://www.chadtdyar.com/books/the-deliberate-breath?utm_source=devto&utm_medium=community&utm_campaign=devto-20260807-thedeliberatebr

The Sales Call Version of "Micro Workouts"

Chad Dyar — Tue, 28 Jul 2026 22:11:13 +0000

My trainer told me last week that she's seeing better results from clients doing three ten-minute sessions throughout the day than grinding through one brutal hour at the gym. Something about consistency mattering more than intensity. Cortisol, recovery, sustainability, the usual science.

She wasn't trying to make a business analogy. But I heard one anyway.

I've been tracking my prospect conversations for the past quarter, and the pattern is obvious now. The deals that close aren't coming from the marathon discovery calls where I try to unpack their entire business model in sixty minutes. They're coming from the quick fifteen-minute check-ins where we tackle one specific objection or walk through one part of the pricing model.

The micro workout principle applies to sales execution in ways that feel almost embarrassingly obvious once you see it. Your prospect's attention span works like muscle recovery. You can't force understanding or trust into a single exhausting session. You build both through repeated, focused contact. Three short calls over two weeks will always beat one comprehensive call that leaves everyone drained.

The practical shift is smaller than it sounds. I started blocking my calendar differently. Instead of holding slots for hour-long discovery calls, I book three twenty-minute conversations spread across the week. First call covers their current process. Second call explores one pain point we identified. Third call introduces how we'd solve that specific problem.

The conversion rate difference showed up in under a month. Not because my pitch improved, but because prospects actually remembered our previous conversations. They'd done the thinking between calls. They'd talked to their team. They came back with real questions instead of polite objections.

This maps directly to what I cover in Think On Your Feet, Land On Your Numbers, particularly around call preparation and question sequencing. The temptation in sales is always to pack everything into one interaction. More features, more case studies, more proof points. But that's training for exhaustion, not results.

Micro workouts work because they respect recovery time. Micro calls work because they respect processing time. Both require you to trust the compound effect of showing up consistently instead of trying to earn everything in one session.

Your prospects aren't avoiding your follow-up because they're not interested. They're avoiding it because the last call left them tired.

The newest Presswright title is live on Amazon: Large Print Word Search for Nostalgic Minds: 45 Cherished Themes, Vol...

Chad Dyar — Fri, 24 Jul 2026 22:11:09 +0000

Presswright is a small agent system that takes a puzzle book from theme list to print-ready interior: one agent drafts themed word lists, one validates every grid for solvability and overlap rules, one typesets the large print interior, and a final gate rejects anything that fails a checklist before the PDF ever reaches KDP. The lesson so far: generation was the easy half. The real work lives in the validation gates. When a grid fails, the pipeline logs the defect and regenerates instead of shipping a broken puzzle to a paying reader.

The book that came out the other end is here: https://www.amazon.com/dp/B0H9G4PMW2

Shipping a paperback with an agent pipeline

Chad Dyar — Fri, 24 Jul 2026 21:00:02 +0000

The newest Presswright title is live on Amazon: Large Print Word Search for Nostalgic Minds: 45 Cherished Themes, Volume 4. It is a large print word search book for seniors, and the book is ordinary on purpose. The pipeline is the project. Presswright is a small agent system that takes a puzzle book from theme list to print-ready interior: one agent drafts themed word lists, one validates every grid for solvability and overlap rules, one typesets the large print interior, and a final gate rejects anything that fails a checklist before the PDF ever reaches KDP. The lesson so far: generation was the easy half. The real work lives in the validation gates. When a grid fails, the pipeline logs the defect and regenerates instead of shipping a broken puzzle to a paying reader.

Performance Amplified

Chad Dyar — Thu, 23 Jul 2026 14:00:03 +0000

Performance Amplified