Okay! @Connexium I experimented with the quote system more - it is a great system for actual quotes of tangible products, but it doesn’t work so well for my business (where I need task/hourly/service based estimates instead of quotes).
You can’t quote for tasks, and second of all, even if you could, they can’t be adjusted later after the invoice is created from a quote. You can add more products (or maybe even tasks), but you can’t adjust if the amount of time comes in under or over, or if the product price changes - which is what I need when sending out estimates for tasks/services.
This is basically a great quote system (quotes are fixed and will not change) but doesn’t work well at all as an estimate system (estimates will be different than final invoice).
Product based businesses tend to use “Quotes” while service based businesses tend to use “Estimates”
Since my invoices are detailed by Service Date + Service Description, I may can convert the quote system to an estimate system by quoting my services as “Items” and then creating a separate task based invoice later.
I think all of this could be solved if I could sell a product that triggers giving a client a specified amount of credit, that way they could buy so many hours from me in advance (at varying rates depending on the service) - I think this would make it more user friendly for service based businesses.
In this way a new invoice could be created later with more details, instead of trying to adjust an approved quote where things are “fixed”…However, that is the nature of quotes vs. estimates (fixed vs not fixed). But I think being able to sell credits would fix the quote system where we could use it like an estimate system.
The other thing (not a quick fix) would be to introduce a true estimate system where the client can approve estimates, and it triggers a draft invoice but it doesn’t publish the invoice to the client (because it’s not finalized yet) - and everything can be adjusted before finalization.
I think service based businesses could really use both of these features. @hillel Would it be okay to write them up as a feature request in GitHub for v5?