My team and I also tried this same approach for my mobile education startup - but differently.<p>The issue with working one week on, and three weeks off is that the client is willing to accommodate you flying off the radar for three weeks, and that makes it hard for them to plan their product according to your timing.<p>What we tried at App Ninja was to work a normal six day week, 12 hours a day. We would work on our product for the first 8 hours of the day, and the remaining 4 hours, we will work on our client projects.<p>I am an iOS developer and am fluent with web backends. So I was doing everything from iOS development to Ruby on Rails web apps. We charged by the project instead of hourly, and at one point in time, I actually earned USD $2,000 in 4 hours by completing a project in that time span.<p>If you work fast, charging by the project, instead of hourly can actually be beneficial.<p>We did this for almost 5 months to get our product off the ground, and other than being absolutely physically exhausting, it worked pretty well. Our clients were none the wiser, as we still delivered projects on time and on schedule.