We've built a decentralised clinical trial platform — the ePro Clinical Trial Platform — enabling sponsors, research sites and participants to collaborate securely on a single system: electronic patient-reported outcomes (ePRO), participant engagement, site coordination and real-time monitoring, hosted in Australia and built to support TGA and HREC-governed trial conduct.
Quick answer
Custom clinical trial and ePRO software in Australia starts from around $22,000 for a first release covering one study, with a discovery and specification phase from $3,500 credited against the build. Most established clinical trial management and ePRO platforms are large international SaaS products hosted offshore, licensed per participant or per site. A custom Australian-built system keeps participant health data in Australian jurisdiction and removes a licence that scales against your trial's size.
1 · Data sovereignty
Participant health information under the Privacy Act 1988 is materially simpler to govern when it never leaves Australian jurisdiction. Most major CTMS and ePRO platforms are US or EU-hosted SaaS, which means a cross-border data transfer assessment for every sponsor and every HREC submission. We build and host in Australia, or on-premise inside your institution if your governance requires it.
2 · Licensing that penalises scale
Per-participant and per-site pricing means a trial that enrols ahead of target, or extends across more sites than planned, costs more precisely when it's succeeding. A custom build is a project with a support agreement, not a subscription that grows against your enrolment numbers.
3 · Protocol fit
Every protocol has its own visit schedule, its own outcome measures and its own consent structure. Generic CTMS platforms configure within their own data model. When your protocol, your amendment history or your HREC conditions don't fit, you work around the software. A custom build starts from your protocol.
Decentralised trial management
Remote, hybrid or traditional site-based designs, all on one system — participants aren't limited to what a scheduled visit can capture.
Electronic patient-reported outcomes (ePRO)
Participants or clinicians enter outcome data directly through a secure app or portal, timestamped and audit-ready, instead of paper diaries transcribed weeks later.
Participant engagement tools
Reminders, scheduling and consent renewal that keep participants engaged through a multi-month or multi-year protocol.
Secure data collection
Structured capture against your protocol's actual outcome measures and visit schedule, not a generic form builder.
Sponsor & site collaboration
Role-based views so sponsors, coordinating sites and satellite sites see exactly what they need, in real time.
Real-time monitoring & reporting
Enrolment, data quality and protocol deviations visible as they happen, not at the next scheduled monitoring visit.
Role-based access control
Granular permissions across participants, site coordinators, principal investigators, sponsors and monitors.
Regulatory compliance support
Audit trails, protocol version control and consent records built to support TGA, HREC and ICH-GCP expectations.
To be precise about what we can and can't claim: ethics approval sits with your HREC and regulatory sponsorship with you, not with your software vendor. What we do is build systems designed to make that oversight demonstrable rather than difficult.
| What the system supports | |
|---|---|
| TGA clinical trial notification (CTN/CTX) | Trial and site record-keeping, protocol version history, notification-ready documentation |
| HREC requirements | Protocol and amendment records linked to approvals, consent version enforcement, reporting for ethics review |
| ICH-GCP | Audit trails, role-based access, data integrity controls aligned to Good Clinical Practice expectations |
| Privacy Act 1988 | Australian hosting, participant data minimisation, access logging, de-identification where required |
| 21 CFR Part 11-style records | Electronic records and signature-equivalent attribution for audit-ready data collection |
We've built the ePro Clinical Trial Platform — a decentralised clinical trial system covering participant enrolment, ePRO data collection, site coordination and sponsor-facing real-time monitoring. We're not publishing a specific trial name or sponsor here without their permission, and we don't invent case study numbers or imply a client roster we don't have. If you'd like more detail on the build to assess our capability, ask us directly on a discovery call.
| Off-the-shelf CTMS/ePRO SaaS | Custom build | |
|---|---|---|
| Time to first use | Weeks | 10–14 weeks for a first release |
| Upfront cost | Low | Higher |
| Cost as enrolment/sites scale | Per-participant or per-site, often scales upward | Capital project plus support |
| Fit to your protocol | Configurable within its data model | Built from your protocol |
| Data location | Typically offshore | Australia, or on-premise |
| Ownership | Licensed | You own the code |
| Suits | Standard protocols, immediate need, single small study | Multi-site or long-running trials, sovereignty requirements, unusual protocols |
If an established CTMS or ePRO SaaS genuinely fits your protocol and site count, use it — it'll be faster to start and we'll tell you so. Come to us when the licensing maths stops working, when the data can't leave Australia, or when your protocol doesn't fit a generic form builder.
| From | Timeline | |
|---|---|---|
| Discovery, requirements and specification | $3,500 — credited against build | 2–3 weeks |
| First release (single study) | $22,000 | 10–14 weeks |
| Multi-study, multi-site platform | Quoted after discovery | 4–9 months, phased |
| Support, hosting and enhancement | From $990/month | Ongoing |
| Validation support documentation | Quoted |
We work in phases against trial milestones and funding cycles where that helps — many research and sponsor budgets are structured that way, and a single-invoice, twelve-month project rarely fits them.
A first release covering participant enrolment, ePRO data collection and site coordination for a single study typically starts around $22,000, with a discovery and specification phase from $3,500 credited against the build. Multi-study, multi-site platforms with sponsor dashboards and advanced monitoring are quoted after discovery. Compared against per-participant or per-site SaaS licensing on international CTMS platforms over the life of a multi-year trial, custom is frequently the more predictable cost.
Australian data centres by default, or on-premise inside your institution or sponsor organisation if your governance requires it. Participant health information under the Privacy Act 1988 is materially simpler to govern when it stays in Australian jurisdiction — most established CTMS and ePRO platforms are hosted offshore, which adds a layer of cross-border data transfer assessment most sponsors would rather avoid.
We build to support them. TGA clinical trial notification (CTN) and clinical trial exemption (CTX) scheme record-keeping, HREC-approved protocol version control, and audit-ready electronic records are built into the data model from the start, rather than retrofitted. Ethics approval always sits with your HREC and trial conduct with your sponsor — the platform's job is to make that oversight demonstrable.
Electronic Patient (or Clinician) Reported Outcomes — participants or clinicians enter outcome data directly through a secure app or portal instead of paper diaries or phone calls. It reduces transcription error, gives sites real-time visibility into participant status, and produces a clean, timestamped, audit-ready dataset instead of a shoebox of paper forms transcribed weeks later.
Yes — that's the core design. Participants can complete outcome reporting, consent renewal and scheduling remotely, with site staff and sponsors monitoring status in real time rather than only at scheduled visits. Fully remote, hybrid and traditional site-based designs are all supported; you're not locked into one model.
Consent is recorded against the participant and the specific protocol version, with re-consent workflows when a protocol amendment changes what a participant agreed to. Withdrawal is tracked and propagates to reporting — a withdrawn participant's future data collection stops immediately and the audit trail records exactly when and why.
Yes. Role-based access separates what a participant, a site coordinator, a principal investigator and a sponsor monitor can each see and do, across as many sites as the trial runs at. Sponsors get real-time enrolment and data-quality visibility without needing to phone each site for a status update.
We can produce the documentation needed to support system validation — requirements traceability, test scripts and results, and change control records, aligned to the kind of evidence a monitor or auditor expects for electronic systems used in a clinical trial. The validation and audit itself is performed by your quality team; we supply the evidence they need.
A first release covering one study — enrolment, ePRO collection, site coordination — typically takes ten to fourteen weeks after a two-to-three week discovery phase. We deliver in phases so sites can start enrolling before every sponsor-facing feature is finished.
Yes — source code, documentation and infrastructure, in your organisation's name. There's no per-participant or per-site licence to us, and no dependency that could strand a multi-year trial partway through if you ever needed to move to another developer.
Yes — REDCap or other EDC exports, hospital or clinic patient management systems, and reporting tools your sponsor already uses. We scope integrations during discovery so the data flows you actually need are built in from day one, not bolted on afterward.
Yes, Australia-wide. Discovery and most build phases run remotely; for multi-site trials we typically recommend at least one on-site session with a coordinating site to see the real enrolment and visit workflow before finalising the design.
Running or planning a decentralised trial?
Tell us about your protocol, your site count and your sponsor's data governance requirements. We'll tell you honestly whether a custom build is the right call, or whether an existing CTMS already fits.
