The first new car I bought had its windshield crack before it hit 1,000 miles.

I can still hear the “tick” sound as the pebble made impact. I can still feel the shock as I glimpsed the tiny starburst imperfection.

If it was up to me, I’d have replaced the whole windshield right then.

I imagined the spot in the low corner of the window turning into a spiderweb of a crack. It would crawl across the view out the front of our brand new car and the only solution was to spend hundreds on an unblemished windshield.

Since we were driving to visit family, cooler heads prevailed. My in-laws had raised four kids on one salary. They’d seen this sort of thing before.

We obtained a special kit that filled in the tiny hole to keep it from spreading. This DIY project took about 30 minutes and cost less than ten bucks.

Years later, that small imperfection looked exactly the same when we traded in that car.

Now I look around the house and see many potential projects. I’ve watched my share of YouTube videos and tackled some DIY fixes. But the truth is… I’m still that “replace the whole window” guy.

That initial instinct is hard to change.

For developers, they’re likely to lean toward DIY. That poses a problem for those of us selling new windshields.

Rather than push against the instinct, roll with it:

• Compare the fix-it stuff to the new window
• Show how to install a windshield yourself
• Highlight the “gotchas” to look out for during installation
  ​

Of course, you’ll want to focus on the DIY aspect of your developer product, not literally windshields.

The D.E.V. Content Framework helps you do that. We use it on every client project to identify content to attract developers, resonate with them, and encourage them to try your product.