Frequently asked questions

Tallify is AI financial planning software for South African financial services providers, built around client onboarding. The practice sends a client one personal link: the client completes the fact find online, e-signs the disclosure letter and sends their ID and proof of address. Tallify drafts the FAIS Record of Advice and financial needs analysis from the fact find for the adviser to review and file, checks the client book for fund movements every day and for cover gaps every week, and holds every drafted client message in an approval queue until an adviser approves it. It runs on a server the practice controls, or is hosted by Tallify in South Africa.

Independent FSPs and small to mid-sized practices: CFP professionals, risk and investment advisers, paraplanners and compliance officers. It is priced per adviser, from R799 a month; clients, paraplanners, administrators and compliance users cost nothing extra.

The adviser clicks Send fact-find pack in the console, which emails the client a personal onboarding link, or copies the link to pass on another way. The link opens a welcome page with three steps the client can do in any order: sign the disclosure letter online (their name and ID number are the checks, and a signature record is added to the signed letter), complete the guided fact find, and send a photo or PDF of their ID and proof of address. The client receives a signed copy of the letter by email, and the adviser sees each step arrive on the client's record. The link lasts 30 days. The annual client review uses the same guided steps, with what the practice already holds filled in.

Yes, in four stages, so the adviser decides the advice. Code builds the client's financial position and needs from the fact find. The adviser completes a worksheet, one row per need, with the premium from the insurer's quote. Code builds the financial needs analysis from that decision, and Claude writes the Record of Advice around it, structured to section 9 of the FAIS General Code of Conduct. The model has no say in the products. On Plus and Practice the client's picture, cover gap and cash flow diagrams, is drawn from the same figures. Nothing is filed as a final advice record until the adviser approves it.

The completed fact find from the onboarding link. The client answers it online, one plain question at a time, on a phone or a computer; a fact-find workbook a client still emails back is read the same way. A photo of a form, a PDF, a Word document or typed notes also works, through the assisted channel: a model on the practice's server reads it, with no accuracy promise, and the adviser checks every figure on the review form before the client is committed. Anything missing or contradictory is flagged for the adviser to confirm before drafting.

No. It never sends advice to a client. It drafts documents for the adviser, and it prepares client messages such as replies, review reminders, birthday messages, fund movement notices and market updates, which are only sent after a named adviser approves them. The adviser remains the FAIS representative giving advice.

No identifiable data leaves the practice. Names, ID numbers, dates of birth, contact details and addresses are removed on the practice's server by code before anything leaves it, and a fail-closed check stops any request that still carries them. The de-identified facts are read and the documents drafted by Claude, from Anthropic, under commercial terms that exclude training on the data. Names are put back on the practice's server. Nothing goes to ChatGPT or any consumer AI tool. Local models on the practice's server build the search index, run an extra check for names before anything is sent to Claude (without one running, the code's own removal and the check still apply), read an uploaded Astute CCP report, and read the assisted channel (photos, PDFs and typed notes uploaded in the console). Nothing they read leaves the server, and the onboarding fact find does not depend on them.

Tallify is built so that POPIA controls are structural: identity removed by code before any external processing, recorded consent required for every update the practice starts, role-based access, an audit log of every change, and data residency in South Africa, on a server the practice controls or one Tallify hosts for it. The practice remains the responsible party under POPIA; Tallify makes the controls hold without relying on a policy document.

In South Africa, either way. A practice can run Tallify on a server it controls, its own hardware or a private server it rents, with the console on a private network; the server needs a graphics card only if the practice uses the assisted channel for photos and notes, and without one the names check and the Astute CCP reader fall back to code. Or Tallify hosts it for the practice on a server in South Africa that Tallify operates, under an operator agreement, and the practice signs in at its own web address, through Cloudflare, with a password and a code sent by email. Either way each practice is its own installation, with its own database, documents, backups, services, settings and sign-in, and the same de-identification, approval gate and audit log; a hosted server can run several practices' installations, and none shares its database, documents, backups or sign-in with another. The pages a client sees are their onboarding link and the practice's sign-up form.

Every day it compares fund prices and drafts factual notices for clients affected by a material movement, and every week it compares each client's current cover with what they used to hold, by type, and briefs the adviser on gaps. It can also prepare birthday messages and review reminders. Client messages wait for approval; the briefing goes to the adviser.

No. It sits beside existing planning and administration tools rather than requiring a practice to switch platforms. It keeps its own client, holdings, policy and advice registers so that it can check the book for fund movements every day and for cover gaps every week. Clients come in through onboarding or are captured in the console, and fund prices load from the practice's price files. For Astute, the CCP report can be uploaded on an intake today: Tallify reads it, adds the client's existing contracts to the fact find and files them on the register when the intake is committed.

Through the Astute CCP report, today. With the client's signed Astute consent, the adviser runs a Consolidated Client Portfolio report on Astute Online and uploads it on the client's intake in the console. Tallify reads it and adds the existing contracts to the fact find, so the needs analysis sizes the shortfalls against what the insurers hold. It flags cover the client disclosed that the report does not show, and files the contracts on the register when the intake is committed. Tallify does not call Astute's service itself.

Yes. During setup the adviser imports their client book from a CSV export of their current system, and on the Practice plan Tallify imports it for them. After that, clients come in through onboarding, an uploaded CCP report files a client's existing contracts on the register, and fund prices load from the practice's price files. Every record is validated when it is saved (dates, amounts, product and policy types) so the book starts clean.

Tallify is built to load a daily unit price feed from a South African data provider. Until a feed is licensed, prices can be loaded from the practice's own files.

Roles are administrator, adviser, office staff and read-only. An adviser sees their own book; office staff see the books ticked for them; every screen, including approvals, intake and document downloads, follows that scope. Office staff and read-only users cost nothing extra. Every change is logged against a named user.

Yes, and the Security page sets it out in full. HTTPS throughout. On a practice's own server the console sits on a private network; a hosted practice signs in with a password and a code sent by email. Passwords are hashed and must meet strength rules, sign-in is rate limited, sessions lock after two hours idle, and every person chooses their own password. Pages carry strict browser security headers, uploaded files are checked by their content, and drafting has hourly, daily and spending limits. Identity is removed by code before anything leaves the server, with a fail-closed check. Every change goes to an audit log, backups run twice a day with permanent retention, and the server is monitored continuously. A written information security policy set is available to practices and their compliance officers on request.

Sign up on the trial page and we hop on a call to map out your process. Your Tallify is live in 1 to 2 business days, its own installation hosted in South Africa, set up like your practice. The first seven days are free. After that you pay per adviser a month, cancel any time, and there is no setup fee.

Per adviser, a month: Start R799 (100 client onboardings and reviews a month), Plus R1 199 (200 a month, with the client's picture) and Practice R2 799 (unlimited, with your own Record of Advice layout and the setup done for you). Clients, paraplanners, administrators and compliance users cost nothing extra. No setup fee, a seven-day free trial, cancel any time. The full table is on the pricing page. Data feeds (Astute requests, fund prices) are licensed by the practice from the providers at their published rates.

BlueBird Digital, a South African AI consultancy. Tallify was designed with an advisory practice and is deployed practice by practice.