[UPDATE] Here is a sample project specification for a fictional website to illustrate the level of detail that goes into a project specification.
Such a simple question, yet it causes so much confusion.
Obviously, it’s one of the questions we hear the most, so we’ve had plenty of experience answering this complicated question.
“It’s a straight forward question. What is so complicated about it?”
We hear you.
First off, we’ll just be honest. If you’re looking for a bargain website, Gunner Technology is the wrong company for you.
We’re not a cookie-cutter company – in our design or development.
If you’re willing to sacrifice on quality, functionality and branding, you can save a lot of money by taking your project overseas or to a U.S.-based chop shops. We’ll even be happy to recommend some for you. These companies have a place but that place is not for individuals and companies who are serious about long-term commitments to a presence in the digital world.
OK, now to demystify pricing, so get ready for some analogies.
As you might have noticed, Gunner Technology has three divisions: Marketing, Technology and Web Design. For the purposes of this discussion, only the Technology and Web Design departments are relevant.
Our Technology department is responsible for building and extending software. One such software is our Content Management System, which our Web Design department uses to create websites for clients. Often, this software is more than enough to satisfy a clients’ requirements for a publishing or e-commerce site.
While there are different components to the Content Management System, the pricing is pretty straight forward, depending on what modules are required. For example, if you need a website that requires a storefront, it’s going to be more than a website without one. And if the storefront needs affiliate integration, that’s going to cost a little bit more.
But for the most part, it’s pretty ala carte. The only other price point is the design (logo, site layout, branding, color, typography, etc).
So, if your requirements fit within our existing software’s capabilities, we can give you a quote pretty easily and quickly.
However, often, the client requires custom components.
For example, maybe the client requires being able to filter a listing of physicians by geographic location. That’s too fine of a requirement to make into a generic software component.
It’s at this point that we need a written product specification in order to give you a quote.
A product specification is not a simple outline. It’s a detailed document that spells out how the application needs to operate from different perspectives.
If there will be a site admin, we need to know how the site will work from the admin’s perspective in addition to a guest’s perspective.
Maybe there will be a super admin, too. And a moderator. How does the site function for them?
Unfortunately, this is often where potential clients get frustrated.
They’ve told us they want a site that will be a directory for physicians and expect us to be able to give them a quote.
It’s not that we won’t. We can’t give a quote on a project without great detail.
Let’s just say that based on the skimpy information, we tell the client that it’ll cost 10 Ears of Corn. The client says “Great” and signs our MSA and SOW.
We put together a development team and they built out a “site that will be a directory for physicians.”
They build an application that allows physicians to visit the site, submit their information and be listed in the directory.
Visitors to the site can filter the directory by city, state and type of physician.
The team is stoked. They tested the product and it works great. Time to show the client.
The client sees it and says “That’s not what I wanted.”
The client didn’t want other physicians to automatically be listed in the directory. The client wanted an email from applicants first.
Also, the client expected users to be able to rate the physicians and then be able to sort the directory by rating.
Oh, and where is the zip code search? And why can’t visitors create accounts and save their favorite physicians?
Here comes the dilemma.
We now have two choices. Tell the client that those are major, out-of-scope changes that are going to require more money and watch the client turn beet red. Or we can make the changes and a hefty loss to the business.
That’s why we require a detailed, written product specification.
Yes, other firms will give you a project quote without one. And if the above situation never comes up, you won’t have a problem and your project will have never needed a product specification.
However, more often than not, clients who demand a project rate and refuse to write a project specification come back to us because they took it to a firm that built something that wasn’t even close to what they wanted.
We’re then in the uncomfortable situation of telling them that they wasted their money, because the strong likelihood is that we won’t be able to re-use anything that the other firm built.
So does that mean the we won’t work on a development project without a project specification?
It means we can’t give you a price quote on the project.
Clients still have the option of contracting with us at our hourly rate or lease a team from us on a monthly retainer.
We also have team members who specialize in writing project specifications, so clients can hire us to write their project specification – regardless of whether they end up contracting with us for the development.
And, yes, of course, we will freely offer written feedback on a project specification. If you email Gunner Technology your project specification, someone will let you know if there is information lacking or that needs clarification.
As a final note, project specifications are not technical documents. We’ll make the technical choices. Think of it this way. You tell us what you want to eat and we’ll decide how best to make it.