About Jeremy Goldsborough & Spirelight Web

In 2006 I was handed the responsibility of my local church's website because I was "good with computers."

The person who had built the church website was moving away, and was more than happy to pass me their digital hot potato.

I didn't know how websites worked, and I received no training. There was no plan or roadmap to follow. No content management system, and nobody to call. Just me, the "computer guy", with a login and the directive to "make it great, brother."

What unfolded over the next several years was the beginning of what would ultimately become Spirelight Web.

Over the past 20 years, I have had countless conversations with pastors, church staff, and volunteers who had been handed the responsibility of the church website with little to no knowledge of what to do with it, and no time to do it in.

After completing a thousand "church website projects" it became obvious that what churches really needed was a plan, not just another project.

So often I would finish a new church website build, launch it, and turn the keys over to a church volunteer.

6 months down the road I'd come back to visit that same church website, and it would be in total disarray. Perhaps the original volunteer was replaced or left, and the new volunteer was the "artsy" type and "over-edited" the website.

Dozens of other scenarios contribute to the decline of a church's internet presence, but they all point to the root problem: there's no plan, and no consistency.

Moving forward, I'm here to help your church fix that with the Bulletproof Church Website System.