Our Design Process

So you want to know a little more about our design process? This generally awesome explanation outlines how we produce websites, from ideas to deployment.


The client and the designer both lack key aspects that a good design should consider. The designer may not know all the aspects of the client's work, and the client may not know the best approach for abstracting their information on the web. The main objective throughout the project is to bridge this knowledge gap between client and designer in order to produce a fitting design.

At the first meeting we'll get to the pulp of this website problem. We'll establish generalities such as the intent of the website, the fundamental purpose it serves, the demeanor that should be used in copy, etc. We'll discuss what capabilities the website should have and how much those capabilities will cost.

We’ll start by drafting the prototype and services contract. The contract will outline everything we're going to do, a cost, and a timeline, if needed. The prototype will be a visual representation of the site on paper or in digital images. The contract will keep everyone honest throughout the project, and the rendered prototype will allow the client to provide input about the general layout of the website before we actually build anything out of code. It's important to start with a basic structure for the rest of the design process to grow from, and this is what we’ll do in the beginning.


Through close cooperation between the client and the designer, the product incrementally becomes better. In this step we get down to the nuts and bolts of building the web application. We apply various technologies to the fundamental problem of the website. Once a feature or a set of features is complete, we'll meet with the client for approval and move to the next set of features. Building the website incrementally like this will decrease the amount of time wasted if we need to make alterations to features. Often during this phase, the design that we began with evolves into something a bit different than we thought it would be. We'll polish the features according to input from the client until the website accomplishes all the goals we set.


The final step is deployment, where we actually put the website on the internet. It needs to have an address to reach it through, like "sappworks.com," and it needs to have a home on a server, where the address will point to.

The other important part of putting a website online is to raise awareness about it within your intended audience. Sappworks will submit the site to Google and others in order to drive traffic from searches, but this is the only the beginning of getting a website into public awareness. When we get to this step, we'll provide guidance on improving the website's rank in search results and getting traffic to the site from other sources on the web. Once the product is complete and deployed, we'll stand by to provide updates and support the website if issues arise.