Matt Headley

I spent fifteen years in a pulpit.

Five hundred sermons. Week after week, I had to take something true and make it land with a room full of people who had somewhere else to be. You learn fast what plain language does that clever language can't. Clever language impresses. Plain language moves people. I learned that distinction by losing the room — more than once, more than I'd like to admit.

We ran a flower farm on the side. Grew dahlias and zinnias and sunflowers, sold them at markets, learned what it means to build something with your hands and then explain it to strangers. The farm taught me that people don't buy flowers — they buy the story they tell themselves about the flowers. The language was always the thing.

Then things broke. I resigned from the church — abruptly, with a confidence I couldn't fully defend. The farm sold while I was in the hospital. I had to explain both of those things, to neighbors and customers and people who knew me before, in words that were true enough to hold. Not the theological ones. Not the polished ones. The true ones.

I started building software — tools for florists, for pastors, for farmers market managers. Thirty pieces of software, give or take. And at every step, the same problem: I had to explain what I was doing in one sentence to people who didn't care about the architecture. The market manager at a booth at 9am on a Saturday does not care how elegant the code is. She cares whether it works and whether she can tell her vendors about it.

That's the same problem every business owner has. Every day.

The Plainspoken Blueprint is the methodology I built from all of it. Fifteen years of sermons. A flower farm. A hospital. A suite of software products. One page, the true thing, said plainly. It works because it came from situations where it had to work.