Don't think it has to be stock options that made the difference. They got more of that as freelancers too - they exchanged a rate cut for options early on and came out ahead of any employee there too.
These aren't rhetorical questions, by the way -- I'm genuinely curious and would eager to have a chat about this. My experience has very much been that it's only really possible to integrate freelancers into a development process and product that's either fairly conventional or fairly mature. But if you've got a different experience, then I'd be keen to hear about it and learn from it! Contact me at [email protected] if you feel like talking in more depth at some point.
Two of the freelancers worked out of their office (they were partners in their firm). The third lived in the same town. Both were 2000 miles from the corporate office.
The product was a collaboration tool. In a few months the first features were demo-able. After that the company 'ate its own dog food' i.e. used this tool to meet multiple times a day. Eventually we spend our entire day logged into this tool, available for instant communication, aware of what other communication is occurring in our 'area', sharing documents and status freely.
Plug: this tool is amazing, and enables freelancers and remote workers to behave as if in the same office. We often notice we get LESS done when we travel to other sites, because its harder to stay connected when travelling.
And that's quite a good plug for Sococo -- I'll definitely check it out. Thanks again for sharing your experience here!
As I said in another reply, imagine if Google had tried to design and implement Pagerank, the Google File System, and its custom server architecture using catch-as-catch-can freelancers. I'm in roughly the same boat. Freelancers can be stupendously great for working on more or less standard types of technology -- but when it comes to defining and maintaining truly unique pieces of technology, they are not the way to go.