How can I track all of my customers conversions, clicks, etc on a limited budget?

Avoid buzzwords: - every founder thinks their idea is disruptive/revolutionary - every founder says their financial projections are conservative Instead: - explain your validation & customer traction - explain the assumptions underlying your projections Avoid: - focusing extensively on the product/technology rather than on the business - misunderstanding the purpose of financial projections; they exist in a pitch deck to: a) validate the founders understanding of running a business b) provide a sense of magnitude of the opportunity versus the amount of capital requested c) confirm the go-to-market strategy (nothing undermines a pitch faster than financial projections disconnected from the declared go-to-market approach) d) generally discredit you as someone who understands how to build a company; for instance we'll capture 10% of our market, 1% of China, etc. Top down financial projections get big laughs from investors after you leave the room. bonus) don't show 90% profit margins. Ever. Even if you'll actually have them. Ever. Instead: - avoid false precision by rounding all projections to nearest thousands ($000) - include # units / # subscribers / # customers above revenue line; this goes hand-in-hand with building a bottom up revenue model and implicitly reveals assumptions. Investors will determine if you are realistic, conservative, or out of your mind based largely on the customer acquisition numbers and your explanation of how they will be achieved. - highlight your assumptions & milestones on first customers, cash flow break even, and other customer acquisition and expense metrics that are relevant Avoid: - thinking about investor money as your money - approaching the pitch from your mindset (I need money); investors have to be skeptics, so understand their perspective. - bad investors; it's tempting to think that any money is good money. You can't get an investor to leave once they are in without Herculean efforts and costs (and if you're asking for money, you can't afford it). If you're not on the same page with an investor on how to run/grow the business, you'll regret every waking hour. Instead: - it's their money; tell them how you are going to utilize their money to make them more money - you're a founder, a true believer. Your mantra should be "de-risk, de-risk, de-risk". Perception of risk is the #1 reason an investor says no. Many are legitimate, but often enough it's simply a perception that could have been addressed. - beyond the pitch, make the conversation 2-way. Ask questions of the investor (you might learn awesome things or uncover problems) and talk to at least two other founders they invested in more than 6 months ago.

I've done a lot of complex analytics installations, usually cross-domain and including AdWords and manual tagging with conversion tracking of ecommerce transactions. The gclid by default will override the manual UTM values in Analytics so that is what you are looking for. If you are just grabbing the manual tags from the URL for your own purpose, this should be OK. However, if you at some point want to import conversions (say) connected to your manual tag, then you would want to enable UTM overriding the gclid: https://support.google.com/analytics/answer/1033981?hl=en. Do you have AdWords and Analytics accounts linked? Where and how are you tracking commerce conversions, if you are? Do you feel you are getting the insights you need from your current custom reporting? Let me know if I can help with a call about those or further optimization of your analytics capture. Best - Michael

The idea is a very small fraction of what it takes to earn the first million. Certainly billion. What actually matters is your ability to *execute*. Entrepreneurship means "having the talent of translating opportunities into money". Or, as Alexis Ohanian of Reddit said, "entrepreneur is just French for 'has ideas, does them'." As much as it may seem that transitioning off your 9-to-5 is the biggest hurdle, it's not. If you can't "get out of the gate" then you're also not ready to deal with the real challenges of business, like "competition that has 1,000x your funding" or "suppliers that jerk you around" or "customers who steal your intellectual property". It's easy to have a "billion dollar idea". I'd like to mine gold off of asteroids; I'm sure that would be worth billions. I'd also like to invest in Arctic real estate that will become coastal vacation property after fifty more years of warming. And, of course, to make a new social network that everyone loves. But saying these things is very very different from accomplishing them. Prove your concept by first taking a small step, such as making the first dollar. (Maybe try Noah Kagan's course at http://www.appsumo.com/how-make-your-first-dollar-open/). If you can't figure out a way to "make it go" without a giant investment, then you're kidding yourself about your ability to execute the business. If you *can* figure out a way to get a toehold, then by all means do it now! Happy to advise further, feel free to contact me for a call.

Cash money should be treated separately than sweat equity. There are practical reasons for this namely that sweat equity should always be granted in conjunction with a vesting agreement (standard in tech is 4 year but in other sectors, 3 is often the standard) but that cash money should not be subjected to vesting. Typically, if you're at the idea stage, the valuation of the actual cash going in (again for software) is anywhere between $300,000 and $1m (pre-money). If you're operating in any other type of industry, valuations would be much lower at the earliest stage. The best way to calculate sweat equity (in my experience) is to use this calculator as a guide: http://foundrs.com/. If you message me privately (via Clarity) with some more info on what the business is, I can tell you whether I would be helpful to you in a call.

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.