Specifying web developer client requirements

Portfolio Item:  Freckle Creative

In 2006, Freckle Creative engaged Clarity to help clients specify their requirements in detail.

Freckle’s objective was to define the scope of complex projects in detail to allow accurate quoting and optimal allocation of resources across all projects.

We held a series of briefing meetings with each client to help them think through their requirements and consider options.

Between meetings, we used a combination of traditional requirements analysis and web UX techniques to define the scope, interaction scenarios, functional and data requirements, and business rules for the website.

For Freckle, we recorded planning decisions in a functional specification.

However, we can communicate the plan in the best form for you ― for example, as a prototype, a presentation, a set of diagrams, or a brief.

 

Samples:

On behalf of Freckle, we developed functional specifications for clients who needed web applications, content-rich websites, or highly interactive websites.

We can’t provide samples of these documents because they're commercial-in-confidence. But we can show you the process we developed for writing functional specifications:

Clarity process – writing a  functional specification (PDF 149Kb)