SpreadsheetWeb customers run their own models in production
SpreadsheetWeb customers include manufacturers, insurers, reinsurers, hotel groups, actuarial consultancies and city governments. Twelve of them have written up what they built, how long it took, and what it replaced.
Thousands of organisations run models on SpreadsheetWeb
These are thirty-two of them, across insurance and reinsurance, industrial manufacturing, energy, hospitality, mortgage lending, professional services and public administration.
What it was worth to them
Four customers on the number that mattered, taken from their own case studies.
His average job is about $12,000, and he’s given $4 million of quotes. So, he’s using the tool well. It took me about four hours to build, and that’s with a complicated spreadsheet running underneath it.
I know we saved at least $13,000 on just the creation of the app compared to the lowest bids we got. Compared to some of the other medium-sized software companies, the savings are well over $20,000. If it wasn’t for SpreadsheetWeb, I don’t think this project would have been approved.
The process took about two weeks and was fast and effective. I was not even involved throughout much of the process. We now expect to save 10 hours and $1,000 in ROI on an approximate weekly basis.
The digital transformation has been going on for 18 months, saving us a lot of paperwork and manpower for creating and tracking documents. When we consider the cost of storage outside the property I think we saved not less than $30,000 per property. We are now implementing this for 87 other properties in the Middle East division.
Twelve worth reading first
Grouped by the kind of model rather than the size of the company, because the question is usually whether someone has already done something like yours.
Cooney was quoted $80,000 for a custom build and pays $99 a month instead
Read the case studyCoffee Break Financials avoided an $80,000 to $100,000 Ruby build
Read the case studyascendRE built a cloud-based sales acceleration platform on the engine
Read the case studyReinsurance Management Associates built quoting software with no programming
Read the case studyNew Jersey City University built interactive enrollment dashboards
Read the case studyEvean built a personnel scheduling tool after pricing a custom build in euros
Read the case studyTwelve more, on top of the four above. Dozens more are published across every sector here and several we have not listed, with new ones added regularly.
What most of them had in common
Different industries, the same starting point.
One spreadsheet, too many copies
A rating sheet, a quoting model or a reporting workbook that had been emailed around until nobody was certain which version was current, or what the last person changed.
The logic was not the problem
The model already worked and the people who owned it were not developers. Rebuilding it in code meant paying someone to reproduce years of accumulated business rules, then maintaining two copies of the same logic.
The quote made the decision
Several of them priced a custom build first. The comparison, rather than the technology, is what settled it, which is why the numbers above are the part worth reading.
If that sounds familiar, the fastest way to find out where your model lands is to send us the workbook. We check it against the supported function list and tell you what, if anything, needs attention.
Put your own model in front of people
Start on the free tier and upload a workbook, or send us the file and we will tell you what it would take. If another tool fits better, we will say so.