What Crash taught me about the architecture I didn’t know I was missing.

After a year of nonstop weekly releases spread across six series and several short stories, I was mentally done. It felt like an endless cycle of trying to stay ahead of a monster chasing me through a dark forest. We were between series, and I asked Sean if I could write a book I’d been thinking about for decades. He said yes. That book was Crash.

It derailed me.

Crash is about Thomas Witt, a photographer who loses his daughter in a car accident that also takes his last month of memories before the crash. Six months later, he’s obsessed with recovering those memories, driving for hours searching for accidents to photograph, hoping something triggers what he lost. His marriage is dissolving. A book he’s supposed to be writing sits untouched. Then one night, he’s going through his photos, and he sees something. A man in black. At multiple scenes. Across several weeks and towns.

Staring straight at Tom.

That man in the photos creeped me out so much that I couldn’t wait to start the story.

I thought Crash would serve as a reset. Seven months on a relatively short book, then back fresh and ready for whatever was next. Why it took seven months instead of one is a story for another Dispatch. The short version is that the book was more personal than I realized. When I finally came up for air, Sean told me our sales had collapsed. All the momentum we’d built with readers had evaporated. We’d stepped off the hamster wheel, and it had stopped caring about us entirely.

Crash was a good book. In fact, it wound up being the first movie script we ever sold to Hollywood. But it wasn’t built with anything else in our catalog in mind. It was a standalone when we were known for series and serials. And while I spent months on it, readers had nothing new from us. Our success until then had been built on the fact that we never stopped. We released something new every week for a year. Something had to give.

In this case, it was me.

At the time we released Crash, we had six other series spread out among several horror subgenres: post-apocalyptic, sci-fi, young adult, and urban fantasy.

Now, let’s say in the best scenario, a reader LOVED Crash. It was the best thing they ever read. They might’ve just found their favorite new authors. They want to see what else we’ve got. Well, guess what. That reader who loved our haunting ghost story had nowhere to go for something along those lines.

There was still a good chance they’d dig our other stuff. Like Stephen King and Dean Koontz, our genres blend like a Reese’s Cup, and there’s a good chance they’d like something else we had.

If only we’d thought to mention those other books.

We made no mention of them. We wrote a Call to Action to join our mailing list. It thanked them for reading the book. It said something along the lines of “sign up for the latest news and freebies.” No meaningful cookie at all.

But wait, it gets worse.

We thanked them for reading the wrong book. Somehow, the CTA page from the other standalone Sean was writing at the time, Threshold, wound up in the back of Crash.

Clearly, the sort of ineptitude that screams, “Hey, I’ll give THESE idiots my email!”

That was the architecture we’d built. Or hadn’t.

Sean has a line I’ve heard a hundred times and only recently started actually hearing: stop publishing, start building IP. What I finally understand now is that the hamster wheel was never a system. It was just motion. And motion without architecture stops the second you do.

There was nothing in place to keep compounding while I took the detour. No reader journey that continued without me running it manually every single day.

When Sean told me sales had collapsed, I was devastated. I spent months convinced that writing Crash was the worst decision I’d made in my publishing career. Months blaming one book for the poor sales across everything else we’d built.

Crash wasn’t the mistake. It wasn’t even in the top five mistakes I’ve made in publishing.

The mistake was that we had a mountain of books behind us, and none of them knew each other.

Instead of looking at one book’s performance and wondering what you did wrong, look at the architecture around all of your books.

The architecture is what holds everything together. It’s the difference between a catalog and a pile of books. Without it, a reader who finds you has no idea where to go. They’re dropped into your catalog with no map. Most creators never build the map. They just keep adding territory and wondering why nobody’s exploring it.

The Shift

Find the book that most readers discover you through. Then trace the path forward. Where does it send them next? If the answer is nowhere, that’s your first architecture problem. Fix that one book this week. Just that one.

In Closing

This is a real-time experiment. Sean has spent years using this method to help clients drive millions in sales. We never applied it to our own work. The cobbler’s kids, barefoot in the snow. He’s rebuilding our fiction catalog now, using the same architecture we’re building the Smarter Artist series on from day one. Two different problems, same method. I’ll be posting what works and what doesn’t every Friday. Steal what you can.

This Week’s Podcast

The moment we’ve been teasing for weeks is finally here.

Along with the upgraded newsletter (this very Dispatch), and more in-depth blog posts, check out my post on writing your darkness:

​https://smarterartist.net/the-stuff-youd-rather-not-think-about-is-the-most-valuable-ip-youll-ever-own/​

We’re ALSO delivering our first USEFUL episode of The Smarter Artist Show.

After 14 episodes of screwing around, we’re finally bringing a more structured approach to the show.

Did we succeed? Or did the show devolve into insanity?

Well, you’ll just have to watch or listen.

But, c’mon. I think you know the answer.

Check it out here:

​https://smarterartist.net/podcast/15-the-smarter-artist-method/​

One More Thing…

​The Smarter Artist Method is free HERE.

Sean wrote it as the foundation for everything else we’re doing, and the Dispatch tends to assume you’ve got the framework in your head. Read it when you can. Friday’s Dispatch will still make sense if you haven’t, but it’ll hit harder if you have.

And because you’re here on day one, I’ve got one more One More Thing for you: the original conversation Sean and I had that the book is based on. It’s not advertised anywhere. Consider it a welcome gift.

​The Smarter Artist Method: The Conversation​

Thank you for reading,
Dave

P.S. Have you looked at your entry point book yet? Hit reply and tell me how bad the architecture was. I’ll tell you where I’m at.

​
​