For more than two decades, I've been designing and building technology for nonprofits, schools, associations, startups, and small businesses. Today, I focus on creating systems that are easier to operate, easier to maintain, and more useful to the people who depend on them.
About Ben Downey
I build software that helps communities thrive.
How I Got Here
I started writing software in 1997 and have been building production systems since 2008.
Many organizations are trying to accomplish important work with processes that have grown complicated over time. Seeing those challenges firsthand changed how I think about technology.
Today, I focus on building practical software that reduces complexity instead of adding to it.
Technology works best when it fades into the background and lets people focus on the work that matters.
-20260606130114889%2F800.webp?alt=media&token=1bc7e47e-4f6e-44a6-b5f9-0c408755195c)
Community Matters
After moving to Spokane, I became deeply involved in local organizations and community initiatives.
Today I serve as manage fundraising for Hutton Elementary and Sacajawea Middle. I help gather support for the programs, events, and initiatives that benefit students and families.
I'm also involved with Startup Spokane and have built projects that help connect entrepreneurs, businesses, and community organizations across the region.
Those experiences shape how I think about technology. The best systems aren't the most sophisticated—they're the ones that help people accomplish meaningful work together.
What I Believe
Good People Shouldn't Need Workarounds
Most organizations aren't limited by effort. They're limited by processes that have become harder than the work itself.
Every New Tool Creates New Work
Most organizations don't need more technology. They need fewer systems that work better together. I've seen teams spend more time managing software than doing the work they set out to accomplish.
Simple Beats Clever
The best systems aren't the ones with the most features. They're the ones people actually use six months later. If a solution requires constant training, documentation, and workarounds, it probably isn't simple enough.
Let's Build Something That Works
Whether you're launching a new idea, improving an existing system, or trying to untangle a complicated process, I'd be happy to help.