>Hi All:
>
>Thanks for all your inputs.
>
>I'm getting a sense that this guy may not be so crazy after all. Some say that it's a requirement in their field (like Akiko in DC), some say it's not that unusual, some say do it but charge for it, and then some say (like I first though) the guy's crazy. But the overall jest is to try to do it and get paid (right?).
>
>I have a problem with this because I've never done a program this way. I usually try to get the big picture; break it down to busobj's and forms; then start coding. Yes, it does make sense to write a manual first because it takes you through the entire project in detail prior to any coding. But writing an entire manual first? I'm not sure about that.
>
>Anyway, I'm not secure about this person and I've not been offered to be paid to write a manual. He wanted to see the manual (or what I can do or understand, I guess) first.
>
>Thank you (ALL).
>
>Mal

That is what the customer wanted. I have called this request a Detailed Specification.

If you wanted a house built, would you let a builder go without a set of blueprints? If so you have more trust than I. Your Spec will be a set of blue prints that the customer can agree upon and then check off that you have done what HE wanted.

It's always billable, or I don't work for the customer. In large scale goverment work you may be required to create a spec as part of your bid, that's another thing.

Call him back and tell him gewt another apointment. Tell him that you spoke to some others and now you understand what he wants.

Your spec has to contain the bizObjects, form screen prints, and general functionality, maybe flow charts to document how a return will affect his inventory as well as his chart of accounts.

Spec costs per hour? 75 to 150 depending on your area. Hawaii, you may bump that up to 150 to 250 per. Make it higer than your coding rate.

Are you town or country? I use to be town back in 85. I worked as a waiter in Nicks Fish Market.

__Stephen