Hi Hodgman!

2) I think the first suggestion makes sense, perhaps for some balance in between. I just can't see much getting done with less than 20 hours a week - even if I were the one doing it myself!

4) Really good idea. Perhaps they would be more willing to negotiate based on royalties, too.

Main thing for the latter is that I want to avoid lulls in the projects due to god-knows-what will happen at my FT job.

I think that transition from employee to owner requires a crunch.

Personally, I was doing 60h/w at a day job while pushing for 20h/w contracts on the side when establishing the financial basis of my own business.

I was also working about 8-10h/w on my own project, which gave me little overhead as to what was happening, and I was averaging 90h/w of actual work across all projects (which drove my gf and kids insane).

Word of advice, keep the big picture here and hire someone for the lower level management (someone you trust).

If you can, try to cut a deal with your current employer to get more money. It will be a tough ride, but it will secure your financial angle so that you can focus on having the right people for your project to go smoothly.

One of the best local indie startup I've seen was a guy that had managed to muster 9 months in overtime salary. He cut out a deal with his employer so that they would pay him over 9 months (as opposed to all-at-once upon departure) and was able to have his business sustained full-time from this when things really started to kick in. This works well if your project isn't time sensitive.

Best of luck!

Don't do it this way.

Seriously, if people steal your project and run, you'll be left with no savings OR game.

Work on it a little bit at a time until you have a prototype, then try and find fundraising to get some cash in advance to hire a team.

Seriously, if people steal your project and run, you'll be left with no savings OR game.

You might know "a guy" where his crew ran and stole the project.

It's a risk, but if you know what you're doing and sign contracts, the risk is drastically smaller.

It still exists, but every business owner lives with risk and manages it.

Work on it a little bit at a time until you have a prototype, then try and find fundraising to get some cash in advance to hire a team.

Fundraising? As in, crowd-funding? Otherwise, even with a prototype, all you'll get is Friends, Family and Fools (I think that this is copyrighted by Tom Sloper though, so don't sue me!).

even with a prototype, all you'll get is Friends, Family and Fools (I think that this is copyrighted by Tom Sloper though, so don't sue me!).

Nope, it is old. I recall reading it in the 1980s, but I suspect it goes back a century or more.

There are either three or four F's depending on which list you read: Founders, Friends, Family, and Fools.

I guess I should also chime in with advice for the OP.

It is a business. Run it as a business.

Having a paid employee, even just one employee, means you must follow a bunch of additional laws.

You are a small business hiring your first employee. Make sure you have all your business workings in order, make sure that you have talked with a business lawyer about what all is required, make sure you have all your legal requirements met, including things like business insurance, unemployment insurance, government filings, government mandated safety reporting, employee tax reporting, and everything else that is mandated by law. Make sure you pay your taxes, and report your employee's taxes correctly. There are federal regulations, state regulations, county regulations, and frequently municipality regulations.

As an employer there are all kinds of quirky requirements, such as (in the United States) displaying several government-mandated notices about employee rights, requirements about prominently posting your annual business license which includes an estimate of the number of employees, and more. Even if you run your business from your basement, you still most prominently display the posters and the licenses.

Employees are expensive. They generally cost about 50% more than you pay them. Contractors are slightly less expensive, but they are only good for a short-term solution.

Since you insist on using a decently obscure language you available pool talent is going to be considerably smaller then a company looking for C++ or Unity people. You will end up paying more for an F# programmer since they don't have to compete with the droves of new graduates to find a job.