Prepare the week’s royalties without rebuilding the calculations.
The performance count changes. Your team works through the same calculations again, checking which fees stay fixed and which depend on the week. We build software around the rules and source figures you already use.
Your finance team confirms the relevant terms: for example a fixed weekly fee, a performance-based amount, a minimum or a share. Missing or conflicting terms remain questions for your team, not assumptions made by the software.
Make a changed week easier to check
Enter or import the agreed source figures, keep their reporting period visible and prepare the calculations together. The source, rule and result stay connected so the reviewer can understand what changed.
Test against completed periods
Before using a new calculation process, compare it with examples your finance team has already checked. Include unusual weeks and resolve differences. Preparing an amount does not authorise a payment.
Where we would begin.
Bring one completed spreadsheet, its source figures and the rules your finance team has approved. We agree the first calculation and the examples it must match.
Not necessarily. We start with the process you want to improve, then agree whether it needs a connection, an export or a separate tool. Compatibility and any migration are checked during scoping.
Who decides the financial rules and contract terms?
Your team and advisers approve those rules and templates. We implement the agreed process and test it against examples you have checked.
How much does a project cost, and how long does it take?
That depends on the process, the source data, connections and review requirements. We agree the first deliverable, price and schedule before development; there is no universal package or promised turnaround.
Who owns the software, and who supports it?
Ownership, source-code access, licences, hosting, maintenance and support responsibilities are set out in the project agreement. We can discuss managed hosting or deployment to your own environment.
What should we bring to a discovery call?
No preparation is required. If useful, have one spreadsheet, form or repeated task in mind. In 30 minutes we can talk through the process and identify what it would take to automate it.
Free 30-minute discovery call · Google Meet
Talk through one process.
Identify what it would take to automate it. No preparation required; if useful, have one example in mind.
