In financial services, downtime and mistakes cost you money and trust. We build for that from the start:
Managers need control over funds and clients need to see what is going on. We build software that gives both sides what they need:
Each of these is a page in its own right. In a compliance-driven operation the risk sits in the gaps: a client record updated in one system and not the other, and a figure in a report you cannot evidence.
One client record across advice, service and reporting, so a change of details is not made in one system only.
Fees, revenue and reconciliation connected, so a number in a board pack can be traced back to a transaction.
Onboarding, identity checks and periodic reviews run as a tracked process with a record of who did what.
Every one of them starts with a Rapid Insight Workshop: a paid session that maps your operation and hands back a prioritised roadmap. What you do next depends on what it finds.
We stay embedded and work through the roadmap with you month after month, as regulation, volume and client expectations change. One monthly fee, measured against results we agree at the start. From $15K a month, six-month minimum term.
One build, scoped in writing before anything starts, then quoted at a fixed price against that scope. A one-year warranty, and the code and the IP are yours. Typically $100K and up.
Test a client-facing tool with real users before a full build. Fixed price, $25K to $50K, and working software in four to eight weeks — enough to test it with real users before you spend more.
An advice or funds business runs on specialist systems that each own a slice: Xplan for the client file, HUB24 or Netwealth as the platform, Class for super administration, Xero for the ledger, and AUSTRAC and ASIC obligations over all of it. None of them agrees without a person in the middle, working in a spreadsheet.
CodeFish builds across those gaps: connecting client, platform and accounting systems so a record is entered once, and automating the recurring reporting and reconciliation. We build around the systems you already licence.
With a Rapid Insight Workshop. It maps your operational picture end to end: the systems you run, where work is being done manually, what that costs you, and which fix returns the most. You get a prioritised roadmap back before committing to a build, so the first move is an informed one. From there you either test one idea first (Ignite), build one thing at a fixed price and own it outright (Amplify), or keep us on to work through the roadmap with you month after month (Apex). We will tell you honestly which one fits.
Compliance informs design decisions from day one rather than being audited in at the end. The obligations you carry shape the UX, the data model, and the permission structure, and reporting and audit trails are built into the workflow so evidence is captured as work happens rather than reconstructed later.
Secure system architecture is the starting point, not a hardening pass before launch. That means least-privilege access, clear separation between customer-facing and internal systems, encrypted data at rest and in transit, and an auditable record of who touched what. We design for the assumption that the data is sensitive, because it is.
Yes, and uptime is the constraint we design around. We work in stages rather than big-bang replacements: rebuild the process underneath, run changes through testing, and cut over incrementally with rollout plans built to minimise customer friction. The legacy system stays in place until the replacement is proven.
Yes, and clear delineation between the two is core to how we design. Managers get internal systems to run clients and funds with the control they need; clients get a platform for fund reporting, agreement management and invoicing that shows them what they should see and nothing else.
This is usually where the fastest return sits. Recurring reporting, reconciliation, fee calculation and client communications are rules-based work that people are doing by hand at scale. We automate the workflow so the team handles exceptions and judgement calls instead of assembling the same spreadsheet every month.
Yes, and it is usually most of the value. These platforms are each strong at their own job and deliberately incurious about the others, which is why your team re-keys the same client detail across three of them. We connect them so the client record, the holdings and the fee data stay consistent, with permissions respected at every point.
They shape the data model and the permission structure from day one rather than being audited in at the end. Identity and AML checks, consent, retention and an auditable record of who touched what are part of the workflow, so the evidence is captured as work happens instead of being reconstructed for a review.
In Australia, in data centres you can name to your board and your clients. We host on the Australian regions of the major cloud providers, such as AWS Sydney or Melbourne and Azure Australia East, and keep backups and logs onshore too. Where a third-party service would move client data offshore, we flag it before it goes in and offer an onshore option or keep that data out of it. You get a written record of where each kind of data sits, which is the first thing an ASIC, AUSTRAC or client due-diligence question will ask for.
We give you the facts about the system we built so your team can answer accurately, without guessing. Wholesale clients, super trustees and platform partners often send a long questionnaire, or ask how a supplier lines up against APRA's CPS 234 or a SOC 2 report. We document how access is controlled, how data is encrypted, where it is hosted, how changes are tested and how incidents are handled, and keep that document current as the system changes. Your compliance or risk manager can then answer from evidence rather than chasing developers every time a form arrives.
Yes. Advisers stay in Xplan, or whichever advice platform you already run, and we replace the manual work that sits around it. That is usually the spreadsheets, re-keying and email chains between Xplan, the platform, the fee ledger and your reporting. Ripping out an advice platform risks losing client history and retraining every adviser, and the platform is rarely the problem. We read from it and write back through its supported integration points, so the client file stays the record your advisers and auditors already trust.
It runs overnight and leaves your team a short list of exceptions in the morning, not a spreadsheet to build. The run pulls holdings and transactions from the platform, such as HUB24 or Netwealth, matches them against the client file and the fee ledger, and flags anything that does not agree: a missing transaction, a fee charged at the wrong rate, a holding that moved without an instruction. Your operations team works through those exceptions, each one with the source records attached. Every match and every manual fix is logged, so the run doubles as audit evidence.