Use cases: what teams build with SpreadAPI.
Teams use SpreadAPI wherever a calculation already lives in an Excel workbook and has to run somewhere else: in an app, on a website, in a workflow or in an AI assistant. The workbook stays the one place where the logic is maintained. These are the typical cases.
By task: what the workbook calculates.
Quote and price calculation
Quantity tiers, edition, term and discount become a price. The calculator on the homepage runs on exactly such a workbook: change a value and see the answer.Try the calculator →Commissions
Rates by product and target attainment, accelerators and caps as formulas. A workflow sends the closed deals and gets the commission back; many deals go through one batch call.See the worked workflows →Lead scoring
Points per criterion, a tier and the team that takes the lead. Marketing tunes the weights in the spreadsheet, the workflow stays as it is.See the worked workflows →Business rules without a rules engine
Tiers, eligibility and exceptions as formulas a specialist can read and change, called as one API step. A lightweight alternative, not a rules engine: no approvals, no audit trail.Business rules in a spreadsheet →Decision tables
Conditions, rules and outcomes in rows anyone can check, evaluated by lookup formulas and called as an API. The guide has a worked example with every formula and a live service.Guide: decision tables as an API →Live data in the calculation
The price list, tariffs or exchange rates stay in your own system. The formulas read them from a JSON address, and every calculation uses current records.How live data works →Stop rewriting Excel logic in code
The formulas of the workbook do the calculating, so nobody translates them into code. When the logic changes, the Excel file is updated and published again.Why not to rewrite it →By industry: three typical workbooks.
Each with a live example from a demo workbook: change a value and see the answer.
Insurance