Maica is healthcare software for Australian providers, built natively on the Salesforce platform. It began as a Care Management solution for NDIS and Aged Care providers and is now a set of connected products covering Care Management, forms, document generation, client portals and staff learning.
Five: the core Care Management product, Maica Forms for collecting information, Maica Docs for generating documents, Maica Portals for giving clients and families a view of their own record, and Maica Learning for staff training.
No, they are separate products that solve opposite halves of the same problem. Forms collects information and writes it into Salesforce. Docs takes information already in Salesforce and turns it into a branded, signature-ready document. Many providers use both, and they work well together, but neither requires the other.
Yes. Each product is separately licensable. There is no core-plus-extensions arrangement where you have to buy a base product before you can add the others, so you can start with the one that solves your most pressing problem and add more later.
It depends which product. The core Care Management product is built natively on Salesforce as a managed package, so it runs in Salesforce. Forms, Docs, Portals and Learning connect to Salesforce data and are at their best that way, but they also work without it.
Because a great deal of what care software has to get right is already solved there. Security, sharing rules, audit trails, reporting, extensibility and a large ecosystem of other applications come with the platform rather than being rebuilt from scratch, which means our effort goes into the care-specific parts.
No. Clients and families sign in to a Maica portal, not to Salesforce. The portal reads and writes their record on their behalf, so there is no per-client licence cost.
NDIS providers, Aged Care providers across Home Care Packages, CHSP and Support at Home, and Support Coordination. The language, funding models and claiming rules are built for the Australian context rather than adapted from overseas.
Shared, not duplicated. Forms write into Salesforce, Docs read from it, and Portals query it live at page load. There is no separate copy of your client data sitting inside each product waiting to fall out of step.
No. Forms, documents and portals are all built and configured in the browser by your own team, with drag and drop rather than code. Where you do want full control, custom CSS and HTML are available, but they are an option rather than a requirement.
Vertic, a Melbourne team that has worked with social and nonprofit organisations for over a decade, founded by Jan Tenenberg and Stephen Kent. Maica was built with providers rather than only for them.
Our commitment to the organisations doing the hardest work with the least funding. ACNC-registered nonprofits get their first ten users free.
Yes, and most providers do. Because each product is separately licensable and they all read the same Salesforce data, adding a second product later is a matter of switching it on and configuring it, not a migration.
Yes. Maica talks to the NDIS systems directly, with secure authentication and synced participant records, so plan and claiming information moves without anyone re-keying it. The availability of those digital integration APIs is what made Maica possible in the first place.
Xero for invoicing and reconciliation, Stripe for payments, and KeyPay for payroll and award interpretation. Because Maica sits on Salesforce, the wider Salesforce ecosystem is available to you as well.
Yes. Participant sync, Budget Management setup, claiming and monthly statements are built to match the Support at Home program rather than retrofitted onto an older Aged Care model.
Yes, and per item rather than once globally. Forms, generated documents and portals each carry their own logo, colours, typography and layout, so a form sent to a client and a statement they receive both look like they came from you.
A learning platform for training your own staff. You author the content, deliver it, assess it with quizzes and scenarios, and award badges and certificates. Completions can be written back into Salesforce, though that link is optional rather than required.
Yes. Maica Learning imports SCORM 1.2 and SCORM 2004 packages and runs them with full progress and score tracking, alongside content authored natively in the same module. You can also import course content by spreadsheet.
Your team signs in to Care Management through your own Salesforce environment, and to Forms, Docs, Portals and Learning through the Maica app. Clients and families sign in only to the portal you publish for them, using a magic link, a password, Google, Facebook or your own single sign-on.
Whatever your Salesforce configuration says. Because Care Management runs on the platform, it inherits Salesforce security, sharing rules and audit trails rather than maintaining a separate permission model that could quietly disagree with them.
Yes. You can embed a prefilled form in a portal page, and requests are logged to a dedicated Salesforce object, so they arrive as records your team can work rather than emails in somebody's inbox.
Yes, and in more than one way. Support workers have the Mobile Worker App for schedules, notes and the tools they need in the field. Forms, documents and portals are mobile-first, because the people receiving them are usually on a phone.
Pricing depends on which products you licence and how many people use them. The pricing page has current per-user pricing and a calculator, and the fastest way to get a number for your situation is to talk to us.
%201.svg){kind=icon}