In spite of what you may read, a smaller, non-interactive web site can be a very powerful tool, especially if it is made so that Google and other search engines index it properly.

Below a certain size, the memos and meetings involved in team development become too top-heavy. I can handle every aspect of your site development from planning to launch, with only occasional intra-cranial internal meetings.

Bottom line is, a small site will work better, look better, get done faster and cheaper when built by a single craftsperson — if he is good at what he does.

Maybe you need a web site, maybe not. I simply do not sell people things they don't need. Nor do I take on projects I can't handle.

Call me in for a little bit of paid consulting. I'll listen carefully, ask lots of pointed questions (in a non-threatening sort of way), and let you know what I think.

I may recommend another solution or another vendor. Or I may give you a detailed proposal to create your site.

Building a new site should be exciting and fun, not a grinding, nerve-wrenching battle. I use a lot of humor because it keeps people communicating more openly, and it's also more fun.

I make it a point to keep the relationship with my clients constructive and positive. Once a working relationship turns hostile almost all the energy goes into the hostility, which has serious consequences for the final product.

See what people say about working with me.

Maybe your current web firm is giving you something you are just not sure about. Maybe they are right, but you'd feel better with an outside opinion.

For example, you might ask me for my opinion on such questions as: Is Flash the right way to do your project? Is a certain design too radical? Is this navigation system really workable?

How do you know I won't trash your current vendor in an attempt to get your work? If I did stuff like that I would end up without any clients. People trust me precisely because I don't do things like that. Better check the what people say page again.

Having written many proposals I know where to poke and prod to look for dry-rot and termites. I will ask your potential vendors questions like, "Who will be on the project team, and exactly what has their experience been in the past?"

I will also call up past clients provided by a vendor and find out what their experience has been, again asking questions that are hard to get around, such as "Did your main contacts on the project stay with you from beginning to end?"

I will find out enough about your web needs to determine if a vendor is really giving you what you need.

An outside consultant has a big advantage when it comes to reaching consensus between internal factions. He or she is usually accepted as a neutral point of view.

In facilitating the development of such large sites as The Boston Public Library, The Boston Foundation, and Berklee College of Music, I was able to get all parties to participate in an open way. I believe that in these cases each constituency felt that they had been listened to and their concerns dealt with in a constructive way.

I avoid confusion two ways:

I refuse to use buzzwords and jargon just to sound cool. I find that after a meeting full of buzzwords nobody actually has any idea what was decided. I really like plain English. I believe if someone truly understands a topic they can explain it in plain language.

I repeat and restate decisions to make sure everyone really gets it, and then I document what was said that is worth remembering.