Archive for the ‘process’ Category

From Contact to Contract

For me, one of the tough­est stretches in the web design game has always been the phase between the ini­tial con­tact with a client and ham­mer­ing out those final agreed-​upon specs. Not that I have trou­ble ‘closing the deal’. I think most design­ers can sell them­selves quite well. The real issue is actu­ally that most design­ers and devel­op­ers are so great at com­mu­ni­cat­ing their own vision, some­times they have issues with lis­ten­ing to poten­tial clients express­ing their own. That com­mu­ni­ca­tion gap must be bridged, and early, if both par­ties want to come out of this dance happy.

All too often, we forget that folks coming to us for a project don’t have a lot of expe­ri­ence with this type of stuff. We don’t make it all that easy either, usu­ally hit­ting them over the head with dozens of tech­ni­cal ques­tions and jargon-​filled sur­veys. No wonder we either get back noth­ing, or noth­ing useful. It’s impor­tant to clear out the clut­ter and cut to the really impor­tant ques­tions before that first meet­ing with the client. If you can single out their goals, their budget, and their dead­lines, the rest gen­er­ally falls into place.

One com­pany who does a fan­tas­tic job of find­ing that ’sweet spot’ is Airbag Indus­tries (not that I should be sur­prised). They recently launched a really solid RFP that quickly gets the impor­tant infor­ma­tion from the client, doesn’t hit them over the head with pre­ten­sion, and gets them out the door asap. The more acces­si­ble you make your­self, and the fewer bar­ri­ers that you have between the infor­ma­tion in the client’s head and your inbox, the more likely that you’re going to get folks com­mu­ni­cat­ing with you and want­ing to work with you.

There are zil­lions of tal­ented devel­op­ers and design­ers out there. There are also zil­lions of design­ers and devs who can sell them­selves to anyone. But the real pros are the folks who work just as hard to really listen to the client as they do pol­ish­ing their ele­va­tor pitch.

Long story short, look for a new Square­One RFP form in the coming days.

Small Studios and How They Can Help You

When approached by a prospec­tive client, a lot of the time the ques­tion is floated to me in one way or another, “why should I use a small studio?”, and I think the answer is quite clear. Smaller stu­dios not only save you money, but they give you the atten­tion and flex­i­bil­ity that folks need and deserve. In the end, the client is hap­pier because of this unique sit­u­a­tion, and we ben­e­fit from per­son­ally making sure each of our clients leave com­pletely satisfied.

Examining Costs

On aver­age, a (small to medium-​sized) web site designed, built, tested and deliv­ered should take some­where between 20 and 40 hours. This of course can vary wildly, but this is a pretty good esti­mate for most small to medium sized busi­nesses. I’m sure a rush job could be accom­plished in roughly half this time, but it’d be akin to taking your car to the mechanic and asking them to do the bare min­i­mum amount of work, and hurry up with it! You may be able to drive out of the shop, but God knows how long you’d last before the engine needs more work on it. In the end, you would pay much more to have the same amount of repairs done.

We charge a rate roughly 1/3 what a large design studio does, mainly because we lack the over­head that those places do. Because of that, not only are your costs lim­ited, but the atten­tion of the firm is squarely on you and your needs. If a project becomes larger in scope than orig­i­nally antic­i­pated, we can always hire extra folks to come in and help out (as we have exten­sive con­nec­tions to design­ers in the Atlanta and South­east­ern region in gen­eral), but you don’t have to assume that over­head regard­less of your needs.

Personal Touch

All to often, when you do busi­ness with a design firm, you first speak to some­one in sales. Once you show your­self to be a poten­tial client, a project man­ager or designer will come to the meet­ing to talk about the par­tic­u­lars of what your project entails. You will then usu­ally talk to a few design­ers, cre­ative direc­tors, or other project man­agers by the time it’s all said and done. How do you know if what you spoke to one person about was prop­erly relayed to another? Work­ing with a smaller com­pany ensures that, from start to finish, you are deal­ing with at most one or two folks. When you limit the number of times you have to repeat your­self, the less time we all spend on get­ting your needs taken care of.

It all just makes sense

If you’re look­ing to get a small-to-medium sized project taken of, don’t want to pay an extreme over­head just to do busi­ness with a design firm, and want the per­sonal atten­tion a small busi­ness can offer, then we hope that you keep Square­One Web Design in mind when you con­sider your next web design or redesign.

The Process

Over the years, we have devel­oped a work­flow that encour­ages com­mu­ni­ca­tion & the free flow of ideas all through­out the design and devel­op­ment process. We have found that this is the best way to ensure that we deliver a prod­uct that is in line with your goals, and is some­thing we can both be proud of. While every stage is cer­tainly open to detours along the way, this is a gen­eral idea of the path we will take on your project.

The more engaged and invested the client is in the process, from start to finish, the hap­pier we’ll all be.

Preproduction (25% due upon completion)

  • Client survey – This is the first step, where the client fills out an online or print ver­sion of the client survey we have cre­ated. Not every ques­tion has to be answered, but it does help us get an idea of where you’re coming from, and where we are headed together.
  • Dis­cuss audience/industry – Once we have the survey, we gen­er­ally will sit down with you and go over your com­pe­ti­tion and see how we can dif­fer­en­ti­ate you from them on the web. This helps us with orga­niz­ing your con­tent and cre­at­ing your design.
  • Estab­lish require­ments for site – As a con­tin­u­a­tion of the above step, here we deter­mine where we can improve on your cur­rent site’s offer­ing, and what we will con­sider a ’success’.
  • Dis­cuss exam­ple sites and why – Now the fun part. We will find a few exam­ple sites that you like, and find out why. This will help us come up with a design that works for you.
  • Dis­cuss budget and dead­lines – Finally, we will deter­mine a time­line that works best for both of us, and how to stay within your budget.

Content Audit

Once we have agreed on the frame­work for your project, the actual work begins. In this step we will deter­mine what con­tent you have, what can stay, what should go, and the struc­ture of your new site.

  • Audit exist­ing con­tent – Here we will review your cur­rent site (if you have one) and see which con­tent works, which con­tent should pos­si­bly be con­sol­i­dated, and what con­tent should be dropped or rewritten.
  • Estab­lish pro­posed site map – Based on what we deter­mined in the last step, we will now come up with a rough skele­ton of what con­tent is going to go where, and how the user will nav­i­gate to that information.
  • Create wire frame & pro­to­site – A simple site with your con­tent will be cre­ated so that we can test the ‘flow’ of the site. This way, if impor­tant con­tent is orphaned some­where that is hard to find by a user, we can make those changes now instead of after your site launches.

  • Begin work on CMS if requested – If you have requested a con­tent man­age­ment system, we will dis­cuss the require­ments for that at this stage, and begin work on it immediately.

Design Visual Interface (25% due upon completion)

Here’s where the actual design phase begins. Based on the infor­ma­tion we dis­cussed in the first meet­ing, we’ll go ahead and pro­vide you with designs based on sites you like, improve­ments you have requested from your cur­rent site, and things we have learned from your competition.

  • Develop comp – Here we will deliver a mock-​up of your site based on the infor­ma­tion we dis­cussed in our first meeting.
  • Receive revi­sions – If the client has any changes to the design, we will make them and return a revised comp for client review.
  • Deliver revised comp
  • Make fur­ther changes if needed

Assess deadlines & make changes as needed

If needed, we will adjust any dead­lines based on the progress of the project thus far.

Build out site (25% due upon completion)

  • Imple­ment design – Once the design is approved by the client, we’ll write the markup to make your new site look like the mockup we agreed upon.
  • Create and pop­u­late pages with con­tent – Once the page has been struc­tured, we’ll put the con­tent into the site based on the sitemap we agreed upon in an ear­lier meeting.
  • Inte­grate con­tent man­age­ment system if requested – Finally, if there was a con­tent man­age­ment system requested by the client, we will inte­grate that into the design at this stage.

Conduct QA Testing

Before we hand the site to the client for final changes, we will con­duct a round of tests to make sure that every­thing appears the same in all browsers, there are no typos or gram­mat­i­cal errors, and that the site is as easy to nav­i­gate as we orig­i­nally intended it to be.

Client Preview

Finally, we hand off the site to you at this point. Bar­ring any other changes or revi­sions, the site is as the public will see it.

  • Receive client changes – If there are any out­stand­ing revi­sions to be made, it is at this point that we will com­plete these changes and seek approval from the client.

Deliver Site (25% due upon completion)

Once all changes are com­pleted from the final pre­view stage, we will pub­lish your site. And with that, you’re on the web!

While most of these steps seem to be common sense, and some will actu­ally be invis­i­ble to the client, I feel it’s impor­tant to have trans­parency in the entire work­flow, so that that every­one is on the same page on day one, on the day the site is pub­lished, and every day in between.

Tech­no­rati Tags:
, , , , , ,