03 / Business software / calculations / handover
Turning a portfolio spreadsheet into working software
A workbook-based allocation workflow expressed as editable web tables and derived portfolio views.
The recurring problem
Start with
the actual work.
A useful spreadsheet can become the centre of a repeated business process. Moving that process into an application requires understanding its calculations, its editable inputs and the outputs people rely on.
The implementation contribution
Implementation translated the allocation workbook into a web application with editable tables, derived views and calculation checks against workbook baselines. This is conventional business software; AI-assisted development does not require an AI model in every runtime calculation.
Implemented behaviour
What the work contains.
- 01Editable application tables for the allocation workflow.
- 02Derived portfolio views and target calculations.
- 03Calculation tests using workbook baseline values.
- 04Checks for new constituents and recalculation of scaffolded positions.
Explore the workflow
Change an input. Check the result.
A reconstructed example using invented inputs. The original client system is not exposed.
Reconstructed example / synthetic allocation
Explicit calculations| Asset | Target % | Derived amount |
|---|---|---|
| Equity | R 432 900,00 | |
| Bonds | R 288 600,00 | |
| Property | R 144 300,00 | |
| Cash | R 96 200,00 | |
| Total | 100.0% | R 962 000,00 |
Targets add to 100%. The derived amounts reconcile to the illustrative total, including rounding.
Simplified, synthetic data. This is not the client application or an investment recommendation.
Watch the edited walkthrough
Evidence
What supports this account.
Application code and calculation tests substantiate the implemented behaviour. The interactive example uses a simplified, invented allocation to explain the approach; it is not the client's application or investment advice.
Limits
What remains unmeasured.
The public account does not establish actual build hours, measured time savings, current deployment status or user adoption. Those require separate measurement and confirmation.
The practical lesson
A faster first version is useful when the original business rules remain visible and testable.
Discuss a similar workflow ↗Your next workflow
Let’s put the
week to work.
Tell us what your team does repeatedly. We’ll discuss the opportunity, your tools and whether an implementation week is a useful first step.
Pricing follows discovery. We aim to reply within one business day.