Get your own customer support community
 

How estimates will work

We've been discussing this internally and we think we've got a model that will work for most people, which we've outlined below. There's a lot of ground covered here and this may or may not all be released at the same time, but we welcome any feedback.

Broadly speaking estimates will be modelled on how Invoices work. The flow would work as follows:

Create a new “Estimate”


  • With the option to select “Type” from a selection of Estimate, Quote and Proposal. This is a purely semantic decision for some people but for others it ties into a workflow process.

  • Fill in other details: Contact and optionally Project. We thought about this for a while and it may be important to associated an estimate with a project once it’s been given the green light and converted into a live project

  • Other possible fields: Date, Ref, P/O, Additional Info



Estimate State Bar

Similar to the invoice status bar this would allow people to set the state of the estimate:


  • Draft

  • Sent

  • Mark as Approved

  • Convert to Invoice



Estimates differ slightly from invoices in that they can be resent multiple times.

Viewing Estimates and Workflow

Once the estimate has been saved/sent it gets added to the Estimate list.

This would display the Status and potentially a "Show History" link here. This would reveal a list of the history of the estimate.

The Status thing is important as it allows people to create their own workflow by changing the type from Estimate > Quote > Proposal and then resending to the client. The Show History link in the Status Column would show what was done, and when, so examples might be:


  • Draft Estimate

  • Quote sent 3 feb 09

  • Proposal sent 6 feb 09

  • Proposal approved 9 feb 09

  • Converted to Invoice 13 apr 09



The great thing about this workflow is that it can completely ignored it or used it as much as people want.
 
happy I’m excited about getting feedback
Inappropriate?
10 people like this idea

The company implemented this idea.


User_default_medium