Saturation.io is a browser-based budgeting and cost-tracking tool: you build a production budget, share it with the people who need it, and track spending against it. That answers a real problem — legacy budgeting software is installed on one machine, barely collaborative, and the spreadsheet that replaces it always drifts. Soldum picks up the same project earlier: AI reads the screenplay, and the breakdown, the budget, the shooting schedule and the call sheets all follow from it.
This page is not out to disqualify Saturation.io, which is solid at what it does. It sets out what changes when one tool produces the budget instead of receiving it already costed, and carries the same numbers through to the schedule — the criterion that decides the choice far more often than a feature count does.
- AI screenplay breakdown on upload: scenes, locations, cast, extras, costumes, props and technical needs.
- Budget derived from the breakdown, so quantities are read rather than re-typed.
- Shooting schedule tied to the budget: a moved day is priced before you commit to it.
- Estimates, commitments and actuals on the same account, with alerts firing on commitments.
- Billed per account rather than per seat, so the whole team can be invited at no extra cost.

What Saturation.io does well, and it should be said
Production budgeting was for a long time the business of software installed on a single machine, opened by one person at a time, and shared by emailing files around. Saturation.io took the problem from the right end: a budget in the browser, readable by the producer, the line producer and the financier without anyone exporting anything, and cost tracking attached to the same accounts. For a team spread across cities, that is an immediate and real gain. Nothing below claims a collaborative online budget is the wrong idea — Soldum does the same thing. It is simply not where the comparison is decided.
A budget is not the first document of a project
This is the distinction that settles the choice, and it is easy to miss because both families of tools share the same vocabulary. A budgeting tool assumes costing is possible: somebody read the script, counted the scenes per location, listed the characters and the days they work, noted the technical requirements — and it is that work, the screenplay breakdown, that costs a line producer days, not typing the numbers in. As long as it happens somewhere else, in a spreadsheet or on paper, the budget starts from a base that nothing connects to the text. Soldum targets exactly that: you upload a PDF or a Final Draft file, AI extracts the substance of the film, and the budget is built on a breakdown you have reviewed.
| On this point | Budgeting tool | Soldum |
|---|---|---|
| Starting point | A breakdown done elsewhere | The script, uploaded and broken down by AI |
| Screenplay breakdown | Out of scope | AI-generated, reviewed and approved by you |
| Where budget quantities come from | Typed in by hand | Derived from the breakdown |
| Shooting schedule | Built in a separate tool | Derived from the breakdown, tied to the budget |
| Call sheets | Out of scope | Generated from the schedule |
| Effect of a script revision | Every quantity reworked by hand | Propagated through to the budget |
| Collaborative budget in the browser | ||
| Cost of a schedule change shown before you commit |
From breakdown to budget, with no re-entry
In Soldum the breakdown is not an end in itself: it is the source the other documents flow from. A location extracted from the script becomes a number of shooting days, so a rental line and a transport account; a character becomes days worked, so a fee and the employer costs on top of it; a technical requirement noted in a scene becomes an equipment line. Those quantities are not copied from one file to another, they are read in one place. That continuity is what makes the difference in daily use — more than the accuracy of the initial extraction, because a correct but isolated breakdown still forces you to carry every change by hand into the budget, then the schedule, then the call sheets.
Why an AI breakdown still gets reviewed
Automation is only worth having if you can trust the output, and a screenplay is full of things a model can read the wrong way: a location named two different ways across forty pages, a character who appears only in a line of action, a prop implied rather than written. Soldum treats the AI pass as a first draft, not a verdict. Nothing is applied without your approval: you review the breakdown scene by scene, correct what was misread, add what the text leaves implicit, and the corrected version is what the budget and the schedule are built from. That review is where the real saving is decided — it takes hours where manual entry takes days, and it is what makes every number downstream dependable.
One tool from the script to the call sheets
The question worth asking of any tool is how many others you still need around it. A budgeting tool covers one document well, which means the breakdown lives in a spreadsheet, the schedule in a scheduling app, and the call sheets in a third place — three products, three exports, and three chances for the film they describe to stop being the same film. The cost of that split is never visible on a feature list; it shows up as the afternoon someone spends reconciling a schedule with a budget that no longer matches it. Soldum covers the whole preparation from a single source: what the AI extracted feeds the budget, the schedule and the call sheets at once, and a change made in one of them is a change in all of them.
Pricing a change before you commit to it
In preparation the question is almost never what the film costs, but what this change costs. Losing the week-three location, adding a night shoot, pushing the start date by a month: each of those is decided in a couple of hours, and the budget is only updated much later, when nothing is negotiable any more. A budgeting tool on its own cannot answer, because it knows nothing about the schedule: a human has to translate the move into crew hours, hotel nights and transport, then type the result in. In Soldum the schedule and the budget are two views of the same material — you move the day, and the cost of moving it appears before you approve anything.

Estimates, commitments and actuals during the shoot
Cost tracking is the ground a budgeting tool is judged on, and Soldum does not skip it. Every account carries three figures: the estimate from the approved budget, the commitment — a vendor quote accepted, a rental confirmed, a deal signed — and the actual. The alert fires on the commitment rather than the actual: an overage flagged as you approve the rental house quote still leaves a choice between renegotiating, trading off elsewhere and accepting it. The same overage found while reconciling invoices three weeks after wrap leaves nothing to decide. What differs from a standalone cost report is the chart of accounts: here the accounts being tracked are the ones the breakdown produced, so there is no mapping table to maintain.
What Soldum does not do
Better said before you open an account. Soldum does not write scripts and offers neither a text editor nor a storyboard: the screenplay is uploaded, not drafted here. We do not cover dailies, editing or sound post-production. We are not corporate accounting software either: ledgers, journals and statutory accounts stay with your accountant, who receives an export rather than a replacement. And we do not run payroll: the budget calculates gross pay and employer costs, but producing the payslips happens elsewhere. Soldum's scope is preparation, from the script arriving to the crew leaving for the shoot, plus budget tracking during it.
Switching, or running both
There is no data migration to orchestrate: Soldum starts from the script. You export your text as PDF or Final Draft, you upload it, and the breakdown runs. In practice the most common migration is not really one — teams try Soldum on the preparation of a real project, ideally one already finished whose final cost they know, and compare the budget it produces with the one they built by hand. It is the least risky test, since you compare two outputs on the same script without dismantling anything. The table below sets out where to start depending on your situation.
| Your situation | What matters first | Where to start |
|---|---|---|
| Production company with a regular slate | Producing the budget rather than typing it | Screenplay breakdown, then budget and schedule |
| Funding application to submit | A budget in the shape the financier expects | Budget derived from the breakdown, then the funding plan |
| Budget already built in another tool | Checking the gap between two costings | Break down the same script and compare account by account |
| Shoot under way, budget to hold | Seeing overages coming | Commitment tracking on the approved budget's accounts |
| Co-producing with a French partner | Deliverables both sides can read | French budget categories and call sheets alongside the English exports |
Who this alternative is for
Production companies, producers of features, documentaries, commercials and series, and line producers who spend their days keeping a breakdown, a budget and a schedule consistent with one another. Soldum also builds budgets on French industry rates and the standardised cost categories French financiers expect — a concrete advantage if you shoot in France or co-produce with a French partner, and simply neutral otherwise. If your first need is a standalone cost report on projects whose budget arrives already built and approved, with no breakdown to produce and no schedule to hold, the argument falls away: a dedicated budgeting tool remains the coherent choice, and nothing stops you preparing the film in Soldum upstream and exporting the budget it produces.
What's your pre-production challenge?
Frequently asked questions
What is the main difference between Soldum and Saturation.io?
+
Saturation.io is a budgeting and cost-tracking tool: it assumes costing is possible, so it assumes the breakdown is already done. Soldum starts from the script — AI breaks it down, and the budget, the shooting schedule and the call sheets follow. One costs what you hand it, the other produces the material to be costed first.
Does Soldum track costs during the shoot as well?
+
Yes. Every budget account carries the estimate, the commitment and the actual, and the alert fires on the commitment so there is still time to act. The accounts being tracked are those of the budget built from the breakdown, so there is no mapping table to maintain between two structures.
Is the screenplay breakdown really automatic?
+
AI reads the script and extracts scenes, locations, characters, extras, costumes, props and technical needs. The result is still reviewed and approved by you: nothing is applied without your consent, and the corrected version is what the budget and the schedule are built from.
Can I import a script written in another tool?
+
Yes. Soldum starts from a script in PDF or Final Draft format, whatever produced it. That is the most common setup: write on one side, prepare in Soldum.
Is a per-user subscription required?
+
No, the subscription is billed per account: €49/month excl. VAT on Solo for one active project at a time, €179/month excl. VAT on Studio for unlimited projects with the whole team invited, and 25% off with an annual commitment. Both plans start with a 7-day free trial, time enough to break down a first script.
Can Soldum run alongside an existing budgeting tool?
+
That is the most common setup at the start. You prepare the film in Soldum — breakdown, budget, schedule — and export the budget to Excel and PDF to feed whatever circuit your production already uses.
Related reading
Informational comparison page, compiled from publicly available vendor information (September 2026); features and commercial plans change over time. Soldum publishes one of the solutions compared. Saturation.io® and the other trademarks mentioned belong to their respective owners and are referenced only for the purpose of objective comparison.
