Search the Community
Showing results for tags 'clients'.
Found 4 results
Hey guys, As the question says, I'd really like to learn about your initial client communication workflows. In other words, what's your process like from the moment you get a request to provide a quote for a website to the moment you actually send the quote? My current workflow: A client fills out the contact form on my site to request a quote. I review the information provided and send them a Word document questionnaire with a list of questions. I ask for things like project scope, features needed, desired timeline, allocated budget, etc. They fill out the document and send it back to me. I review the information provided and make sure I've got everything I need. I write and send the quote to the client. Client accepts the quote. I send them a contract, get it signed and collect 50% of total payment. I gather some extra information from them, usually just by asking questions via email or by sending them another Word document questionnaire. I start building their site. Lately, I've been thinking about changing this workflow a bit. Currently, my online contact form has three fields: name, email and message. What I'm thinking is, what if I provide a select toggle above my form so that clients can choose between a simple, general enquiries form and a larger form (with all the questions I've got in my Word document) to request a quote? This would allow me to do away with the Word document, and would make this a one-step process. The reason why I haven't done this so far is because I'm not sure how good of an idea it is to have a long contact form with say, 10-15 questions. What's your take on this? Another thing I'm not entirely happy with is having to send them two questionnaires (steps 2 and 8). The reason why I do this is because I don't want to overwhelm them with lots of questions at the beginning, and also because, to be honest, the questions I ask in the 2nd questionnaire do not really influence pricing, as they have more to do with the nature of their business, their goals with the new site, possible corporate colours they may have, things like that. What do you guys think? Does my workflow seem sensible to you? Is it similar to what you do? What would you change? Thanks, and sorry for the brick! P.S. If some of you guys are willing to share your client questionnaires I would certainly appreciate it.
SomeDay Tool I'm working on a series of restricted collaborative websites that are geared towards me working with my clients. It's a mashup of CRM, Project/Task Management, Tracking, Documentation and Configuration Control features. Everything is controlled by PW Roles. It's a tool that allows me to have a great deal of transparency with those I work with. The objective is to easily know the who, what, when, where and how of whatever is being worked on. I call it a Collaborative Resource Management System (CRMS) which has the nickname of SomeDay. I currently have one of these websites for each of my important clients and an additional one to keep track of my internal work. They all use the inherent native power of PW to produce specialized status reports. The websites intentionally incorporates the front-end and back-end of the PW platform. There is a lot of information stored within this type of website, what I like to call an Information Portal. You are able to easily query a status and get a good view of what's going on. This is a long-term ongoing project and I will update this post as more features/capabilities are added. Meanwhile, here are a few pictures of the CRMS Tool: Figure 1-3 (The SomeDay Tool for one of my clients) Figure 1 (Login courtesy of Adrian's Protected Mode Module) Figure 2, Homepage is a summary of all information Figure 3, Each item can be clicked on to get to detailed information Figures 4-7 (My internal SomeDay Tool website) Figure 4, (Login) Figure 5, Homepage Summary for my internal work Figure 6 , Homepage Summary Figure 7, FlagPages showing Bookmarks Figures 8-11 (Looking at a Task) Figure 8, Front-end view Figure 9, Back-end view (editing) Figure 10, Place for adding Priority or Statuses Figure 11, Private Tab only available to selected PW Roles Figures 12 and 13 (Site Structure) Figure 12, CRMS structural flow Figure 13, Tasks and Sub-Tasks can be added to Projects Figures 14-16 (Customized Reports) Figure 14, Review all items based on what type of work it is Figure 15, Review items based on their status Figure 16, Listing of all items with a status category of Active That's it for now.
Am just in the process of going over my new profile and making it as user friendly as possible. I'vs started putting things into fieldset tabs as I think it makes things look a lot neater and less overwhelming. I was just interested if any of you have noticed whether or not clients can sometimes miss these? Do you only really store fields in there that are not critical? I'm thinking of mainly using it for media but on a portfolio item for example, I don't really want them forgetting to upload an image or two...
As our studio is getting close to finishing another project, we are facing the challenge to provide our client with easily understandable materials or kind of a manual on how to manage content in PW. As I guess that this happens from time to time to you guys around here, too, I wonder if it would make sense to collaborately work on a kind of manual document explaining key actions to be done for an editor. So there could be an open document or wiki providing texts in different languages and supportive images we all could use to e.g. turn it into a nice PDF or printed handbook (yes, some clients still like paging through paper) where we just have to replace images. I don't think this work has to be done over and over again by each one of us for his own purpose. And I'm sure, all our clients would benefit from something like this. Also it would be a nice plus for everyone thinking about using PW the first time for a client project.