If the client has provided a scope of work, you need to provide an “Approach.”
An approach is not:
What tasks you will do
A description of your experience or why you are so great.
An approach describes the “how” and “why” for the tasks the client has provided.
It’s best to start out your approach by describing your general philosophy when it comes to providing these services.
For example, if you design websites, your general philosophy might be that websites should be:
Easy for the average person to update
Built on an established open source CMS so they can be redesigned easier later.
Optimized to show up on the first page of Google for at least one key term
Optimized to load the first byte within a second
Next, you will go through the scope of work provided by the client. For each task, describe how you will do the task and why you will do it that way.
For example, let’s say the first task of a client’s scope is:
“Provide recommendations for a new Client Relationship Management System.”
Well, how are you going to do that?
There is a lot you might not know. Are they already using a CRM? What do they want to accomplish using this CRM? What is their budget? Do they prefer to host this system internally?
To accomplish this task, you’ll first have to gather some information from them. Describe how you’ll do that. Will it be a survey? Will it be a face to face meeting or phone call?
Then describe the advantages of gathering information this way. Maybe sending them an online survey is best because the client is very busy and won’t have time to meet. Maybe a face-to-face meeting is better because their answers might lead to more questions and you don’t want to make them meet twice for this task.
If the client has not provided deliverables, you will have to define the deliverable for each task. In the CRM example, the deliverable might be a list of three suitable CRM options compared by price and features. This might also include your recommende