SaaSOptics

Like most start-ups, we moved from the subscription spreadsheet to the SaaSOptics platform so our initial need of having an automated system in place was solved immediately. Since then it's only gotten better. It was kind of like not realizing we had a headache until it went away. The more we use the SaaSOptics platform the more we find out it can give us, from ARR to Churn to Invoicing, to collections and more. We've also discovered that SaaSOptics as a company has a very strong commitment to customer success and that means we have access to people who really know the product and can advise us on how to achieve our goals for using the platform.

SaaSOptics made a huge difference throughout our company, from sales order management (implementing process controls on the GTM team) through to collections and dunning (dropping our AR from 65 to 32 in 3 months). It's been great for our size of company. I'm sure there are more robust softwares out there that can do more, but all of those were out of our price range. I also enjoy the fact that SaaSOptics is continually pushing out new features that directly impact and improve every day processes, not just higher level reporting or UI. Both high level reporting and UI changes are important, but being able to deliver on all 3 fronts, rather than just 2 means that SaaSOptics has been a pretty good company to grow alongside.

I do enjoy how easy it is to raise credits/invoices & sync these transactions to Quick Books from SaaSOptics. It is also very easy to reverse revenue by raising the transaction from the contract. The main issues I have, however, with this software can be narrowed down to - Future invoices, Tax options & Client Billing (info) Profiles:
1. I keep a self-maintained spreadsheet with future invoice details due to the following: Future invoices are not always pulling when the date is current; they are not appearing in the order processing (ready to bill) list within SaaSOptics because the 'e-invoice queue' check mark is dropping off. To avoid errors, to ensure that the client receives their invoice when the date is current, I track this info on a spreadsheet outside of SaaS.
2. I keep a maintained spreadsheet with billing profile information for our clients due to the following: Inconsistencies on the billing profiles between SaaSOptics, Sales Force & Quickbooks. Billing information can not be trusted, ease of use could be improved to avoid syncing headaches. To avoid errors, to ensure that the client receives their invoice with correct billing info, I track this info on a spreadhsset, outside of Saas.
3. I keep a maintained spreadsheet with tax tables and user tax details due to the following: The inability to add multiple sales tax rates in SaaSOptics / Quickbooks. Ease of use could be improved by allowing multiple rates to be added into the system & allowing tax addresses to be saved in the system. I calculate tax outside of SaaS/QB, maintain this info for reporting purposes & manually enter tax details on the tax line in QB/SaaS. My other option would be to create line items for tax ( I have discussed this option with QB) but then it would pull into SaaSOptics as a product line (not tax) which would in turn throw the financial summary out of balance. Total invoice line items scheduled would increase by the tax amount which would not balance to the revenue.
4. I pull data & cross-compare SaaSOptics with Quickbooks to fix the tax errors due to the incorrect sales tax rate is generating on the invoice. If the sales tax is blank in Quick Books but is set to taxable in SaaSOptics, an "inactive" rate pulls onto the invoice which is not at the correct rate. At the same time, when I pull this info, I also cross-compare against my self maintained spreadsheet to correct errors on the billing profiles.
Thank you for your time!

Again, the people have been incredible to work with. Management of imported historical data is not user friendly, but the management analytics functionality is pretty powerful.

I am hoping they implement some of the invoicing customization/flexibility we need.