I'm just saying that the equation becomes a lot more complex at this point.
People worry about moonlighting when you have a full-time job but if you are running a startup they usually understand you can make time for them when you need it.
I was dealing with a pretty high maintenance client though, and dealt with scope creep and other consulting mainstays. If managed correctly this can be a good way to go, just be careful.
Consulting is not without its downsides. It doesn't scale up (well, it scales up with added in-house or out-sourced staff, and the associated project management and administration), and it tends to be price-competitive if you're working in a "mainstream" area of expertise.
Consulting can be a very effective distraction to your concentration, too.
Two or three days on customer work, and some focus on billing and proposals and related administration, and then several hours or more of spooling back up to speed on whatever part of the product or debug that you had been working on when the call came in. Then you realize your week is shot.
Put another way, TANSTAAFL.
Make sure you aggregate the financial and focus costs in your estimates. And make sure you can also efficiently encapsulate and snapshot whatever you were doing when the customer work arrives; hone your process skills around in-swapping and out-swapping projects.
Consider providing an end-project summary - not just for the customer's benefit and for the marketing, but also so that you can in-swap the project more quickly if there's additional associated work. The same approach can work for a summary and status for whatever you were doing on your project when the customer call arrives, though that can be a couple of cryptic paragraphs in a text file.