PROTECTING YOUR DIGITAL WALLET WITH MUYERN TRUST HACKER

Take the # of hours it takes you to do it and charge $50/hour. That's the price. Eventually you can charge $100/hour but that will require a bigger customer. If the customer is small < $1M in gross sales per year - charge $50/hour If the customer id medium < $1-5M / sales - charge $75 Over $5M - charge $100 The challenge you'll face is clearly defining the expectations and handoff so that you're not stuck doing stuff that you can charge for and always getting interrupted from past customers.

Usually Programmers are only slow when they don't know how to solve a particular problem. So they will spend a lot of time researching and a lot of trial & errors to solve a problem. It is important that before you engage a programmer on a project, you break down the entire project into simple, easy to understand modules. Let him give you an estimate of how many hours he will require to complete each of the modules. Example: a typical site will have a login module, registration, My account, profile etc. So let him estimate how much he will require to do the login. You can go even detail here. (e.g. how much extra time if you were to implement Facebook/Twitter Login?). Once he start developing, track his progress closely and make sure he is following his given timeline. If he goes over his budgeted time on a module, talk with him and see what went wrong. It is often seen that they may be wasting their time on something very insignificant that you may have asked him to implement, but you can totally go by without it too. So by understanding what is taking longer time, you will be able to prioritise things better. You definitely need some tools to get this done. Google Spreadsheet or Excel works just fine. But if you don't mind spending a few bucks there are many agile project management tools that you might look into. Here is a list, google them all and sign up for trials: * AgileZen * Agile Bench * Assembla * AssiTrack * Blossom * Basecamp * Breeze * DoneDone * Eidos * Fogbugz * GreenHopper * Jugggla * Kanbanpad * Pivotal Tracker Or the reason why he is slow can be purely non-technical. Sometime your developer may don't share the same level of enthusiasm as you about the idea that you are working on. They often don't often see the "bigger picture" (since you don't share everything with them explicitly). If you can somehow get them excited about what he is a part of, it will work like a drug :) He will work day and night without questioning you. But you need to work equally as hard as him. The moment he sees that you are the boss and he is just the guy doing work for you -- his mentality will shift from being part of something to being the low paid developer. Ultimately its all about motivation and making him a part of your venture. After all he deserves it, if he is really playing a crucial role in the entire development.

A generalized question can only get a generalized answer. The most significant accomplishment is validating that the product you have built is a fit with your target market. This is demonstrated primarily by engagement (the people who sign-up or who previously visited, continue to return) and secondarily by growth, ideally based on word-of-mouth or viral growth but effectively converting paid traffic is a great second prize. Other significant accomplishments include: Not running out of money Recruiting and retaining great talent who believe in the founders' vision. Your loved ones not thinking you're as crazy as they thought you were a year ago. I'm happy to talk to you in a call to give you more specifics about what you want to set as your goals more specific to your startup.

There is quite a bit of information available online about eCommerce conversions rates. According to a ton of sources, average visitor-to-sale conversion rates vary from 1-3%. This does not mean the Furniture conversions will be the same. The bigger problem is that visitor-to-sale conversions are not a good data point to use to measure or tune your eCommerce business. All business have some unique friction factors that will affect your final conversion rate. It's very important to understand each of these factors and how to overcome them. The best way to measure and optimize is to take a conversion funnel approach. Once you have defined your funnel you can optimize each conversion rate to better the total effect. For example: Top of the funnel: - All web site visitors, 100,000 / month First conversion: View a product page, 50% of all visitors Second Conversion: Add to Cart, 10% of people who view products Final Conversion: Complete Checkout, 80% of people who put items in a cart In this example we see that only 10% of people who actually view products put them in to a cart, but 80% of those people purchase. If you can figure out why visitors are not adding items to their cart and fix the issue to increase the conversion rate, revenue should increase significantly because of the high checkout rate. You can use free tools like Google Analytics to give you a wealth of information about your site visitor and their behavior or there are some great paid tools as well.

I'm answering your question assuming that you hope to be able to replicate it's own success in your own mobile app. There are a couple of factors responsible for it's growth that are instructive to anyone building a mobile app. "Leveraging the intimacy and privacy of the mobile phone." We now have an *intimate* relationship with our phone like no other device in the history of technology. Every internet company that started before around 2010 has built their core interactions around "the old web" one which was accessed primarily via a browser on a computer. Companies that start with a clean slate, should be building their interactions around how to do whatever the app is supposed to do while leveraging what is unique to people's relationship to their mobile devices. Photo-sharing has become a core part of the way we communicate now. Snapchat built something that provided an experience that leveraged the feeling of privacy and intimacy that is unique to mobile. "Provided an escape from the "maturity" of other online services." Too many parents, aunts, uncles and other "old people" have encroached into the social networks of teens and young people. As a result, they've had a desire to find places to express themselves in places inaccessible by older generations. An important distinction is that it's not just parents and relatives that young people are trying to avoid, but also employers & colleges who are increasingly using "mature" social networks to review applicants. "Leveraged PR even bad PR" The fact that the app got so much press about it being used to sext was perfect PR for the company, as it essentially reinforced the brand experience that it has today. Essentially, "if it's safe enough to send a sext, it's safe for any kind of communication I want to have." And although the safety and security of Snapchat is actually not as advertised, it still enjoys the reputation of having less impact than any primarily web-based service. Building a successful mobile application is one of the hardest challenges to face designers, programmers and entrepreneurs in the history of writing software. Happy to talk to you if you're considering building a mobile app, about what I've learned about the "table stakes" for success.