How to make a good quotation?

[benjaminbogaert]

So I was wondering, when you guys make a quotation, what do you add?

 

I'm wondering what to write down, I was thinking something like this

 

-Hours modeling

-Hours Rendering

-Hours post-production

 

-purchased models

-purchased cut-out people

 

Does this seem about right? Or do you just say, well its about X€$ per render, and nothing more?

 

( pssh if someone could link me to a typical example or some sort )

 

As always, much obliged.

[John Dollus]

there are a few good examples here:

http://www.asai.org/Contracts

 

I never include purchased assets as you never know what those are going to be going into a project and, as a service provider, you are expected to have what you need to do the job already (rightfully so). Build a percentage into every job for assets if you have to but it shouldn't be in a quote.

 

Itemized per deliverable seems to work best. breaking it down by hours/task is great for your own planning/budgeting but ridiculous for a quote and can get you into trouble.

[Scott Schroeder]

Pretty much what John said. The only time I break things down is when it is a highly customized job and requires custom items like furniture that cannot be purchased, people that I have to custom green screen shoot, etc. But for your a-typical rendering job is is just $$ for total hours and delivered on this date. I may break up the hours like so, 24 hours project time + 6 hours for additional fixes within the scope of the project. Changes outside the scope may incur additional charges.

 

The more info you give them on the basic jobs, the more they can nickle and dime you.

[benjaminbogaert]

Aha thanks for the useful info, I shall take it with me, still need to get it down on paper hehe.

 

As always, much obliged.

[Fooch]

+1

 

 

 

Pretty much what John said. The only time I break things down is when it is a highly customized job and requires custom items like furniture that cannot be purchased, people that I have to custom green screen shoot, etc. But for your a-typical rendering job is is just $$ for total hours and delivered on this date. I may break up the hours like so, 24 hours project time + 6 hours for additional fixes within the scope of the project. Changes outside the scope may incur additional charges.

 

The more info you give them on the basic jobs, the more they can nickle and dime you.

[junglee]

I go very simple by providing fixed cost per project type and size.

I tried many different ways to charge, dividing individual items for them to customize and what not, but I feel that fixed cost charge for complete package always guarantees the best rendering.

If you break down too much, clients will start pick and choose to negoicate the final price and in the end, you will earn less for mediocre quality rendering.

In the end, your skill will always improve and after certain level, it's always easier to give them everything you got for your set amount without negociation. That extra $500 for extra gimick doesn't mean much. You want your clients to be happy and come back to you without thinking twice.

[Reitveld]

Yep, the more you break it down, the more the client will want to question each line item. They don't really care it takes 40 hours to complete the 3 renderings... just that you deliver on time and the rendering looks good.

I do break down the check rendering dates, and the number of client interactions that can occur (they get 2 minor revisions, etc.). This way I do have a way to drive a project forward when dealing with needy / hands-on clients.

[junglee]

Yep, the more you break it down, the more the client will want to question each line item. They don't really care it takes 40 hours to complete the 3 renderings... just that you deliver on time and the rendering looks good.

I do break down the check rendering dates, and the number of client interactions that can occur (they get 2 minor revisions, etc.). This way I do have a way to drive a project forward when dealing with needy / hands-on clients.

 

Correct.

This is the way to go. After specified revision dates, anything else is additional scope.