THOUGHT LEADERSHIP
Comparing Diesta with spreadsheets and an internal build
·
6 min read
When spreadsheets fit
Choosing how to automate insurance finance requires comparing the full operating cost of the process. Spreadsheets can support a contained workflow. An internal build can give a business control over specialised requirements. Diesta provides a dedicated financial infrastructure connecting premium reconciliation, sub-ledger accounting and payment operations for intermediated insurance.
The right choice depends on the complexity you need to manage and the capability you are prepared to maintain.
Start with the journey of a premium. If people must repeatedly join policy data, bank receipts, partner statements and settlement schedules, estimate the work required to keep that entire journey reliable.
Establish whether spreadsheets still fit the workflow
Spreadsheets are useful when a process has a limited scope, stable inputs and clear ownership. A finance team can inspect calculations and adapt a workbook as its needs change.
The cost rises when several versions circulate or a workbook becomes the main connection between systems. An amendment may require updates in several places. A settlement query may depend on the colleague who understands a particular formula or naming convention.
Count that work explicitly. Include preparation, review, exception resolution, handovers and the time needed to reproduce evidence. Retaining spreadsheets can be a reasonable decision, provided the controls and ongoing workload fit the business.
The commitment of an internal build
Scope an internal build as a financial system
An internal build can suit a business with unusual requirements, sustained engineering capacity and a clear reason to own the system.
The initial matching logic is only part of the commitment. The team may also need to maintain data ingestion, premium relationships, financial records, exception handling, permissions, payment status and accounting outputs. Changes to a bank format or policy system become part of that responsibility.
Before approving a build, identify who owns the product after launch. Agree how finance requirements become tested software changes, how releases are controlled and how operational incidents are resolved. Include the work that competes with other engineering priorities.
Assess Diesta and retained work
Assess Diesta against the work it would replace
Diesta's platform brings policy information, banking and payment provider data together around insurance reconciliation and financial operations. Its value in a particular business depends on which manual steps or internally maintained capabilities the proposed deployment can replace.
Evaluate that scope directly. A platform may be a strong fit where multiple counterparties and systems make it difficult to maintain a consistent premium position. A narrow reporting problem may call for a smaller change.
Diesta's OneAdvent case study describes a shared payment layer across selected MGAs using different policy administration and underwriting platforms. It is a relevant example for businesses seeking a consistent finance workflow across a varied technology estate.
Compare the responsibilities you will retain
The options distribute work differently. The comparison below describes responsibilities to assess, rather than guaranteed strengths or limitations of every implementation.
Decision area | Spreadsheets | Internal build | Diesta deployment |
|---|---|---|---|
Initial work | Design workbooks and establish controls | Design and deliver the system | Scope, configure and integrate the platform |
Insurance rules | Maintain formulas and procedures | Specify and maintain financial logic | Agree supported workflows and required configuration |
Data changes | Update files and mappings | Maintain ingestion and integrations | Agree ownership of source changes and connections |
Review and evidence | Maintain review records and version discipline | Build the required history and access controls | Validate the proposed controls and available evidence |
Ongoing ownership | Finance and workbook owners | Finance, product and engineering | Your operating team and the specialised Diesta team |
Future changes | Extend the workbook and reassess its controls | Prioritise engineering changes | Assess configuration, integration or product work |
A subscription changes which capabilities you maintain internally. Your team still needs to own its data, financial decisions and operating procedures.
Costs and a representative evaluation
Build the cost comparison around observed workflows
Use the same period and transaction scope for all options. Separate recurring costs from one-off implementation costs.
For spreadsheets, include the time spent preparing inputs, matching transactions, handling exceptions and checking outputs. Add the time needed for absences, handovers and audit requests.
For an internal build, include design, engineering, testing, infrastructure and support. Add ongoing integration maintenance and the opportunity cost of the roadmap work the team would defer.
For a Diesta deployment, obtain a proposal covering the agreed platform scope, implementation, integrations and any separately priced services. Include the operational work your team will retain. Do not assume that every connection or payment-related service is covered by one fee.
Calculate labour capacity using measured hours and a consistent loaded hourly cost. Keep hours released separate from cash savings. Time saved becomes a reduction in expenditure only if it changes hiring, outsourcing or another actual cost.
Also separate working capital from profit. Faster allocation can improve information and support settlement decisions, but client or partner money is not automatically available for the business to use.
Use a limited evaluation to settle the decision
Choose one representative workflow and define success before testing it. Include the straightforward transactions and the exceptions that drive most of the effort.
Compare the correctness of the resulting position, manual interventions, time to resolve exceptions and the evidence retained. Test a changed premium or a failed data transfer as well as the normal case.
Avoid comparing a working spreadsheet with an idealised future platform or an unbuilt internal system. Record assumptions and unresolved work for each option. A useful decision makes those commitments visible.
Investment questions and next steps
Questions buyers ask about build versus buy
When is an internal build justified
When the business has a strong reason to own the capability, requirements that warrant the investment and the capacity to maintain the system over time. Include operational support and financial control in that assessment.
Can we keep parts of our existing process
That depends on the agreed scope. Define the boundaries between existing systems, retained manual work and the new workflow. A partial deployment needs clear responsibility for the handovers.
How should we assess the return on a Diesta investment
Compare the proposed cost with a measured baseline for the work it will replace and the ability it gives you. Separate labour capacity, cash expenditure, control improvements and settlement outcomes. Validate the assumptions through a representative evaluation.
———-
Compare Diesta with your current operating model
Bring your transaction sample, current workflow and cost assumptions to a Diesta demo discussion. Ask which steps the proposed deployment covers and which remain with your team. That gives finance and technology leaders a concrete basis for the investment decision.





