The rule of getting something working quickly should not increase the cost of doing it right in the future.
I personally prefer using CSS for layout, not because it is more intuitive than tables, but because I prefer to remove the table-cruft from my html. I think it makes php and rhtml files easier to read. However, in the limited freelance work that I've done, I've run into more than one client that preferred I use tables because they couldn't or didn't want to maintain their layout with CSS.
Anyway, that discussion is ancilliary to my point, which is that the benefits offered by the author aren't going to be convincing to someone who sees a 40-fold or so difference in time-to-production.
I briefly taught a web design class and I remember students struggling with their table-based layouts. Layouts would be inconsistent from one page to the next because of content stretching the cells, and they could never figure out why dimensions set on a table or cell would be ignored by the browser.
The first rule should be to get something working quickly, even if it's suboptimal. And the jury seems to still be out on the suboptimal part.