I’ve been building websites since the web was a very different place. Over more than 25 years, I’ve worked through changing technologies, platforms, standards, and expectations, but the part of the job I’ve always enjoyed most is solving problems.

I work primarily with nonprofits and small organizations, often as the person who handles the technical work they don’t have the staff or expertise to manage in-house. Sometimes that means building something new. Just as often, it means figuring out an existing website, fixing something that isn’t working, adding functionality, improving accessibility or performance, or finding a better way to accomplish something that’s become unnecessarily difficult.

Starting over isn’t always the answer.

A website represents an investment of time, money, and institutional knowledge. Before recommending a rebuild, I take the time to understand what’s already there and why. This means understanding what works, what doesn’t, and what can reasonably be improved. Your budget is part of that conversation from the beginning. Sometimes starting fresh is the right choice, but often a targeted solution can accomplish what’s needed without the cost and disruption of replacing everything.

I’m comfortable stepping into websites built by other developers, including older or poorly documented systems. I enjoy figuring out how things work, untangling problems, and finding practical solutions—especially when the answer isn’t immediately obvious.

I’m a people person.

Many of my client relationships have lasted for years. Over time, I get to know how an organization works, what its staff are comfortable managing themselves, where they need support, and what they’re trying to accomplish beyond the immediate technical request. I’m there when they need me, whether it’s for a planned project, a quick question, or something that suddenly stops working.

I work independently, but I enjoy collaborating with staff, designers, vendors, and other developers. I explain what I’m doing in plain language, document things that someone else may eventually need to understand, and try not to make technology more complicated than it needs to be.

If you need someone who can build something new, take care of what you already have, or figure out why something isn’t working, I’d be happy to hear what’s going on.