BROADCASTS.com

Getting details from your customers can be a challenging experience, but it is vital so that you can deliver a complete produce on time.\nSegment 1 - The Contact\nThere are a lot of way that customers can contact you\nSome clients want to be hands-on, some want to hand over everything to you - the professional, and others get right to the point\nDespite how many details these customers give you, every project has a unique spin on it, even if it seems run of the mill, this makes it vital that your communication is on point\nSometimes you need to resist customers requests/demands in order to deliver a complete and quality product (ie refusing to move forward on a project that hasn't had enough details communicated to begin accurately)\nSegment 2 - Gather Project Requirements\nBefore sending the first quote we need to know what the client needs us to do\nEnsure that you ask the right questions to get all the information you need, clients generally don't know how many details you need\nWhen we work on a small business site some of the sample questions we might ask include:\nHow do your current clients find you?\nIf you have a site currently, what are some things you like about it, what are the things you really don't like\nWhat is the intention with the new site, generate leads? Just a digital business card/a way to for people to find your phone number? \nWho are your biggest competitors? And which of their sites do you like the most?\nDo you have a database of products you want displayed on the site?\nDo you want to be able to edit the main components of the site yourself?\nHow important is the google rank to you?\nDo you see your website expanding in some way? Becoming a web app? Or growing a lot? Having a team of editors?\nGenerally you should gather details over a personal meeting or screen share\nAfter gathering the details you can start creating the basis of the project including details on time to completion and what will be required\nThis is a major component in your quote for a client\nSegment 3 - Changing Project Requirements\nChanges can suddenly happen, even in the middle of a project\nThey can be brought on by customer preferences, market conditions, or company-wide strategy changes of some sort\nWhen a project requirement changes, especially when it drastically changes from the original vision, it often falls to you as the creator to make the appropriate changes\nIt\u2019s important to have a layout of what you\u2019re willing to do with a client before you begin any work and to have a similar layout for what you're willing to do about changes that arise\nWeb News - What do yo want from a phone/Android launcher?\n\xa0\nWe all have different needs and wants from our mobile devices, they\u2019re an extension of us and the main way the people communicate with one another these days\nWith that being said, they\u2019re still mobile computers and can be used for a wide variety of tasks from working on the go, taking photos, chatting with friends, and much more.\nWith different use cases comes a variety of user preferences in terms of hardware and software\nAre you a fan of Android fragmentation, or is there too much variation?\n\xa0\nApply to become our SubReddit Manager/Mod -\xa0matt_lawrence@digitaldynasty.ca\nYou can find us on...\nFacebook\xa0|\xa0Twitter\xa0|\xa0Instagram\nRSS | Patreon | Spotify\nMedium\xa0|\xa0YouTube\xa0|\xa0GitHub\xa0\nReddit