I've taught a Rails 12-week bootcamp, delivered on-site Ruby on Rails trainings for various Fortune 100 companies, and in a past life spent a considerable amount of time teaching in another field.

Patrick covered the "charge more" side of things much better than I could, so I'll say "what Patrick said times ten" and talk about things from the teaching side. Here are some of the things I wish I'd known when I started:

* Both the trainees and the suits upstairs are very happy with “And here is the finished product we shipped to Heroku during our class”, even if this approach means you can't cover quite as many theoretical concepts. Think back to when you first start with a new framework: you're not sure how all the pieces fit together, yet, and until you ship a project or two you're not sure what you don't know. If they're sharp, they can fill the gaps in theory on their own—your job is to help them gain the confidence that they can ship.

* In my experience, trainees' eyes glass over after 6 hours straight or so, and covering new concepts is moot. If you have the freedom to mix up the training with 4-6 hours live, then drop down to QA, that should help keep their attention longer.

* I love mixing smaller exercises into the curriculum pretty regularly. Letting them actually try out the concepts helps them feel like they own it in their own minds.

* This may seem obvious, but schedule more breaks than you initially think you'll need. Your trainees will want a chance to get coffee and let things settle down in their minds. I'll usually give the trainees a full hour for lunch. I'll give myself at least 20 minutes away from the trainees to breathe, then I'm around to answer their questions during lunch before we start up again.

* You need two computers. One for WebEx, and one to run Google/Stack Overflow/debug quirky things off screen. It's much less confusing for your trainees, and far less stressful for you, to solve something on your own and then walk the trainees through how you solved it, than for them to try to follow everything you're trying in real-time.

* I'm not quite sure how WebEx works, but you need some form of group chat room if WebEx doesn't offer that already. A lot of your trainees are developers, and a lot of developers are introverted, and a lot of introverts will feel more comfortable asking questions via chat rather than piping up on a large conference call. Also, providing code samples and URLs orally is awful. Group chat solves that.

* If there are any tools or apps you recommend or require, make clear all trainees are expected to have them installed/compiled before class starts.

* This shouldn't be a problem since it's remote, but make sure all trainees have access to a computer. (You wouldn't believe how many of my trainees have shown up without computers...)

* I've taught anywhere from 3 to 20 developers at a time. 8 or so is my favorite. Any more than than and I highly, highly recommend you hire a TA for the live portions. The TA will be able to help you answer more questions, buy you a few minutes to get coffee and recover your own sanity, and if a trainee ends up with an issue that is halting the class's overall progress, the TA can focus on that trainee exclusively while you push forward.

(This is another reason to charge high rates: it allows you to do things like hire TAs and deliver a much better experience.)

I'm nj@third.io. If you'd like to talk more, I'd love to hear from you.