How to Build an Asset Out of Giving Stuff Away for Free

Written by Jim Green

We all do it I guess: give something away for free to stimulate interest in our online promotions, an e-book here; a report there, whatever elsewhere.

But can you really build an asset out of giving stuff away?

I believe you can and I’ll tell you why.

I have dozens of small web businesses in diverse fields and one site in particular drives traffic in droves to most ofrepparttar others.

That’s its job. It’s a portal; a catalyst and it’s good at what it does.

You know what though?

I have been consistently and unwittingly underestimatingrepparttar 138959 power of its innate potential to build an asset, a priceless asset.

Until recently this valuable catalyst had no opt-in facility, no newsletter.

Crazy - and it took my ten year-old granddaughter to point outrepparttar 138960 error of my ways.

Here isrepparttar 138961 4-point action plan I implemented to persuade her I wasn’t a terminally doddering old duffer.

Beware the Software Siren

Written by Ross Lambert

Copyright 2005 Ross Lambert

I’ve heard several prominent web marketers mention in their classes and public forums how easy it is to create your own software. Why, all you have to do is run over to or and have some poor shmoe from Outer Slobvia whip out what you want. And all forrepparttar price of a few trips to Starbucks.

Uh, not quite.

Is that a spec in your eye? -----------------------------------

First of all, there isrepparttar 138938 matter of specifications. A spec is a description of what your software should do. The more specific your desires,repparttar 138939 more detailed your specification needs to be. Evenrepparttar 138940 most malnourished coder in Slobovia is going to balk if you say, “Try a gray background–oops, no, don’t like that. Let’s try light blue… Oh, that’s not right, either. Let’s try mauve.” If you just want to specify “the important stuff”, you have to be prepared to accept allrepparttar 138941 “unimportant stuff” however it is handed to you.

Byrepparttar 138942 way, both and have provisions in their process and terms of use that protect their developers from vague specifications. The good news is that there are also provisions to protect you,repparttar 138943 publisher. Regardless,repparttar 138944 more detailed your specification,repparttar 138945 greaterrepparttar 138946 chance of a happy outcome. Ah, but writing those darn specs takes a lot of time… far more time than it sounds like whenrepparttar 138947 gurus tell you how easy it is.

This was only a test… ----------------------------

There’s alsorepparttar 138948 small matter of testing. Once you accept a developer’s work, they get paid and get on with their lives. You, however, must live withrepparttar 138949 software. If you don’t find every bug that must be fixed before you payrepparttar 138950 coder, you either have to put out another project for bid to repair things or live withrepparttar 138951 problems until you do.

Therefore, you must test your software upside down and backwards, on a variety of machines and different versions of operating systems. You must also testrepparttar 138952 installer andrepparttar 138953 help system… oh, you forgot to specify those? Too bad, those tasks now require an additional project. Since they are radically different in nature (one is technical, one is not), you probably need two different people to dorepparttar 138954 work. Coders are rarely proficient enough writers to create an effective help system. I’m being kind, so let me emphasize this point without getting nasty: Don’t let your programmer touch your documentation. Period. Never. Ever.

Cont'd on page 2 ==> © 2005
Terms of Use