Investor FAQ

AI Canadian Solutions (AICS) is a proprietary, multi-tenant SaaS platform purpose-built for Canada's most regulated and relationship-driven professional service sectors — law, mortgage lending, real estate, healthcare, property management, and professional coaching.

We are not a chatbot company. We are not a CRM. We are not a scheduling tool. We are an intelligent AI intake, compliance, and automation layer — the operating system that sits between a professional's existing practice and their clients, doing the work that historically required a full-time receptionist, a compliance officer, a document coordinator, and a follow-up specialist. Combined. Simultaneously. At 3AM on a Sunday.

The market thesis is straightforward: there are over 80,000 licensed professionals in our six target niches in Canada alone. Every single one of them is losing revenue right now due to missed calls, slow intake, non-compliant data capture, and manual follow-up that never happens consistently. We fix all four — with a single subscription.

What we are seeking is not capital for survival. We are seeking strategic distribution partners — channel partners, association relationships, enterprise resellers, and co-development investors — who can accelerate market penetration across niches where we already have proven product-market fit.

Three market forces are converging in 2025–2026 that will not repeat:

1. Regulatory pressure is creating a compliance vacuum. PIPEDA amendments, PHIPA enforcement under Ontario's digital health strategy, and the Law Society of Ontario's increasing scrutiny of intake practices are forcing professionals to upgrade their systems — now, not eventually. Most have no viable path without a platform like ours.

2. Existing SaaS incumbents are not AI-native. Clio, Jane, Buildium, and Follow Up Boss were built for a pre-AI world. Their AI bolt-ons are superficial — conversation wrappers over generic models. Our AI logic is hardcoded to niche rules at the architecture level, not the prompt level. That is a defensible moat that takes years to replicate.

3. The cost of a bad intake is now visible. A missed call from a personal injury prospect has a lifetime client value of $8,000–$65,000. A missed mortgage lead in a rate-sensitive market closes with a competitor in 48 hours. Professionals now understand the math. Our platform converts the conversation about ROI from hypothetical to calculable.

Partners who enter now secure first-mover positioning within their respective channels before the market consolidates. We are not pitching a concept — we are pitching a deployed, revenue-generating platform actively managing real client intake today.

AICS operates as a multi-tenant SaaS subscription business deployed on Canadian AWS infrastructure, built on a proprietary Laravel-based architecture using the Stancl/Tenancy framework — meaning every client (tenant) operates in a fully isolated data environment with their own database partition.

Revenue is subscription-based with tiered plans by niche and usage volume — AI call minutes, active contacts, document vault storage, and number of team seats all scale with the plan. There is no per-transaction revenue share, no white-label licensing dependency, and no single-client concentration risk.

The platform is 100% proprietary. There are no third-party CRM dependencies, no white-labeled tools, and no critical path vendors beyond LLM API providers and infrastructure (AWS Canada). All intake logic, compliance workflows, disambiguation rules, conflict check scoring, vault architecture, and automation sequencing are built and owned by AICS.

Most AI intake products are prompts wrapped around a generic language model. When an end-user gives an ambiguous answer, those systems either log it incorrectly, ask a robotic clarifying question, or fail silently.

Our platform contains proprietary disambiguation logic hardcoded at the agent level — not in a prompt that any developer can copy. The AI cross-references every incoming answer against all previously collected fields in that session before accepting the value. This prevents the class of errors that expose AI systems as non-human, damages trust, and produces dirty intake data.

A real example from production: an end-user says their name is "Sandra Owens." Two questions later, when asked for their city, they respond "Owens." A standard AI logs City = Owens. Our system recognizes the collision — Owens already exists as a surname in this session — and asks: "Is Owens the city you live in, or were you reminding me of your last name?"

This is one of over thirty disambiguation patterns embedded across our niche agents. The result is intake data quality that rivals a trained human receptionist — which is the only bar that matters when that data flows into a legal conflict check, a mortgage application, or a patient intake file.

Our AI Phone Receptionist is built on top of an AI's telephony infrastructure, but the intelligence layer — the conversation flow, the compliance instructions, the disambiguation logic, and the post-call automation — is entirely proprietary.

When a call is received:

1. Niche agent activates. The system identifies which tenant's number was dialed, loads that firm's knowledge base, hardcoded compliance rules, and custom persona instructions — all within the first 200ms of the call.

2. Structured intake runs. The AI conducts a full intake conversation — collecting name, contact details, matter type, service type, Sentiment, urgency level, referral source, and niche-specific qualifying questions — while simultaneously running our disambiguation logic against every answer in real time.

3. Conflict check fires (Law niche). For law firm tenants, before the conversation concludes, our AI runs a live conflict check against the firm's, lender's, realtor's or clinic's existing contact database — cross-referencing last name, first name, city, and email — and communicates the result to the agent before wrapping the call. This is inline with Law Society of Ontario guidance and happens without any human involvement.

4. Post-call automation triggers. The call is transcribed, AI-summarized to key intake points only, saved to the tenant's intake dashboard, auto-tagged, and if the caller expressed scheduling intent, the AI checks the tenant's Google Calendar in real time and proposes available times — booking the appointment before the tenant ever picks up their phone to review the summary.

5. Tenant is notified. Dashboard alert, optional SMS or email notification — the firm wakes up to a completed intake, a clean summary, a tagged contact in their CRM, and a calendar appointment already confirmed.

The difference is architectural, not cosmetic.

Off-the-shelf chatbots are horizontal tools — trained on generic datasets, deployed with basic scripted flows or thin GPT wrappers, and designed to answer FAQs. They have no niche context, no compliance rules, no conflict check logic, and no CRM backbone. When the chat ends, the data goes nowhere useful.

Our widget is a front-end intake engine connected to a full multi-tenant CRM, compliance engine, and automation stack:

• The widget is embeddable on any website or funnel — not just AICS-hosted properties. A law firm running their own WordPress site, or a mortgage broker using a third-party landing page builder, can embed our widget and every conversation flows directly into their AICS dashboard.

• Every intake conversation is processed by our niche-specific AI agent — not a generic GPT. The law agent knows conflict check rules. The mortgage agent knows what qualifying questions precede a product recommendation. The health agent knows how to ask about conditions without triggering privacy violations.

• All collected data auto-populates the tenant's CRM contact record — creating or updating an existing contact, tagging it as "AI Intake," syncing the AI summary, and triggering any configured follow-up automation immediately.

• Our context-awareness and disambiguation engine runs on every answer — ensuring the data quality that downstream compliance, scheduling, and document workflows depend on.

No other embeddable widget in the Canadian or American market does this at the niche compliance level. Not one.

The Secure Vault is one of the most significant features we have built — and one of the clearest examples of why AICS operates in a category of its own.

What it does: The Vault allows tenants to create a fully secured, auditable document repository for each client — segmented per contact in the CRM pipeline. Tenants can upload documents, request documents from clients, version-control files, and invite third-party collaborators (such as co-counsel, referral partners, lenders, or appraisers) through a secure magic-link token system.

The compliance architecture: Every file uploaded passes through a three-layer PHI (Protected Health Information) detection scan before storage. The Vault maintains a full audit log — timestamped, filterable, exportable as CSV — of every action taken: who uploaded, who accessed, who was invited, when, from what IP. This audit log is SOC 2 and PIPEDA-aligned and meets the evidentiary requirements for professional regulatory bodies.

The client-facing layer: Clients receive a magic-link invitation via email — no account creation required. They authenticate via OTP verification, access their dedicated portal, upload requested documents, and engage in a two-way secure messaging thread with the tenant. The session auto-expires on inactivity. The link has a configurable expiry date. The entire flow is encrypted in transit and at rest.

Why this matters to investors: No existing CRM in our six niches — not Clio, not Jane, not Buildium — offers a client-facing secure document portal with this level of compliance architecture natively. Professionals are currently solving the document exchange problem with Dropbox, DocuSign, personal email, or nothing at all. We replace that gap — not their practice management platform.

AICS is designed to function as the intelligent front door: we capture the client, qualify the intake, run the compliance check, collect the initial documents, and organize the relationship before it ever reaches their existing software. We are explicitly not a practice management platform, a clinical notes system, a billing tool, or a lease management system — the core daily workflows that Clio, Jane, Buildium, and their peers are built around.

This makes AICS a natural affiliate and API integration partner for every major vertical platform in our six niches. A completed, conflict-checked, document-collected AICS intake record pushed directly into Clio as a new matter — or into Jane as a new patient file — eliminates dual entry entirely and makes both platforms more valuable to their existing users. We are building toward those integrations intentionally, and we treat every incumbent platform as a distribution partner, not a competitor.

The honest boundary: this positioning holds as long as AICS does not build billing, matter management, clinical documentation, or lease management features. Those are lines we have no intention of crossing — because staying out of that territory is precisely what keeps every major platform in our six niches a potential partner rather than an adversary.

A 5, 10, 20-minute intake call produces a transcript. A transcript is not actionable. This is the gap our AI Summary system addresses.

After every AI phone call or web chat intake, our system automatically generates a structured summary — not a transcription — that extracts only the clinically, legally, or commercially relevant information depending on the niche. The summary is saved to the intake record, displayed in the dashboard, and tagged with intent signals (urgency, matter type, appointment preference, emotional tone) that help the tenant prioritize follow-up.

The practical outcome: a busy law firm, mortgage brokerage, doctor, realtor or property maangement office can wake up to six AI-handled overnight inquiries, each with a 4-sentence summary telling them exactly what the matter is, what outcome the client, lead or tenant wants, and whether an appointment was booked — without reading a single transcript. That is the productivity multiplier professionals pay for.

Appointment scheduling in AICS is not a "send a Calendly link" feature. It is a real-time, AI-driven negotiation between the caller's stated availability and the tenant's actual calendar — resolved and confirmed without human involvement.

During the call or chat: If the AI detects scheduling intent — the prospect says they want to come in, or asks when they can speak with the lawyer, realtor, lead broker or manager in charge, or confirms they are available tomorrow afternoon — the AI initiates a live calendar query against the tenant's connected Google Calendar. If they are persistent the tenant has the option of enabling call transfer, initating a 3-way-call between you, ai and the agent, prior to you connecting Your AI Receptionist will provide a summary of the call allowing them to merge call or reject it and allowing AI to handle the re-booking.

Real-time availability matching: The AI checks for open slots, prioritizes the nearest available time, communicates the options to the prospect conversationally, confirms a selection, and creates the calendar event — all before the conversation ends.

Edge case handling: If the next day has no availability, the system looks two days forward, communicates that to the prospect, and confirms the adjusted time. The tenant's calendar is never double-booked. The appointment appears on the AICS dashboard with a notification alert the moment the session closes.

Why this matters: The average professional service firm converts 23% of intake inquiries into booked consultations. Firms using our scheduling automation convert over 60% — because the commitment is locked in while the prospect is engaged, not asked to "check the link we'll email you." That conversion delta is the core ROI story for every tenant we onboard.

AICS integrates natively with Google Calendar, Calendly, and Cal.com. Our Google Calendar integration is the operational core — it is the only calendar platform that offers both reliable read and write access, meaning our AI can check availability and create confirmed appointments directly inside a tenant's calendar in real time during a live intake call or chat. Calendly and Cal.com are sync integrations: we import contacts, read scheduled events, and surface that data inside the AICS CRM. As both platforms have recently opened booking APIs — Calendly launched theirs in late 2025 — programmatic write access across all three is on our active roadmap.

What that means in practice: a tenant can connect all three calendar platforms to AICS and see every appointment from every source in a unified calendar view within their dashboard — without switching tools. More importantly, our AI can write to their calendar to create appointments in real time during an intake call or chat. Calendly and Cal.com integrations in competing platforms are typically read-only imports or manual syncs. Ours are live, bidirectional, and automated.

Beyond scheduling, the calendar integration extends to contact synchronization. Every contact associated with a calendar event — whether booked through AICS or imported from Calendly or Cal.com — becomes a first-class citizen in the AICS CRM. Tenants can attach notes, run AI phone campaigns, send drip sequences, or initiate vault document requests against any synced contact — regardless of where that contact originally came from.

The AICS CRM treats every contact — regardless of origin — as an actionable relationship record. Contacts can come from AI chat intake, AI phone intake, manual entry, inbox messages, or calendar sync from Google Calendar, Calendly, or Cal.com.

What makes the system powerful for existing contact bases: A tenant who has 500 existing clients in their Gmail contacts can sync those contacts into AICS and immediately treat them as first-class CRM records. If those contacts have notes attached — and they typically do — the AI reads those notes before initiating any outbound communication, and uses them to form a personalized conversation.

A real-world example: a real estate agent has 300 past buyer clients in their CRM with notes like "bought in 2021, interested in upsizing." Our platform can initiate an AI phone call campaign to all 300 — not a robocall, but an intelligent, personalized conversation that references their purchase history, asks where they are in their homeownership journey, and qualifies whether they are ready to transact again. No human dials a single number.

For healthcare tenants: The AI follows up with past patients — asking how they are recovering, whether they have questions from their last appointment, and whether they would like to schedule their next visit. This is automated client nurturing at scale, with zero human intervention, and full PIPEDA/PHIPA-compliant data handling throughout.

Campaigns can be configured as drip sequences — SMS, email, and AI phone calls combined — with branching logic based on response or non-response. The ROI for this single feature justifies the platform subscription cost for most tenants within the first 30 days.

Every intake conversation — whether from AI chat, AI phone, or inbound email — flows into a unified inbox within the AICS dashboard. The inbox is designed for firms with multiple staff members who handle intake and follow-up collaboratively.

Assignment system: Any lead or contact can be assigned to a specific team member with a timestamp, assignment attribution, and real-time row update — so the assigned employee's name appears on the intake table immediately, across all team members' views, without a page refresh. Both the all-leads intake table and the inbox operate on the same assignment architecture.

Reply and communication: Staff can reply directly to prospects from within the inbox — maintaining all communication in a single thread, with full history. Email replies are sent from the firm's branded email via our email provider, not from a generic AICS address. The firm's identity is preserved at every touchpoint.

Audit trail: Every assignment, every reply, every status change — logged with user, timestamp, and source. For law firms subject to file management requirements, and healthcare providers subject to PHIPA audit obligations, this logging is not a feature — it is a compliance requirement that AICS handles automatically.

Salesforce is validating our market by trying to move down into it — but they can't get below a $20,000/year contract without destroying their own margins. Our entire addressable market lives below that price point. By the time they build what we've already built at a price that works for a solo practitioner, we will have owned that relationship for years. And frankly, we'd rather be on the Salesforce AppExchange than compete with them — their distribution network in real estate and mortgage is something we want access to, not a fight we want to have.

Important framing first: AICS does not compete with Clio, Smokeball, or MyCase. We are designed to integrate alongside them and dramatically increase the value of whatever practice management platform a firm already uses. This matters for partnership conversations — and we will return to it.

What the incumbents do well: Clio, Smokeball, and MyCase are excellent matter management platforms. They handle billing, time tracking, document storage for active files, and court deadline calendaring. They are the operating system of an active file.

Where they fail completely: None of them have a meaningful answer for what happens before the file opens. The intake problem — who answers the phone at 9PM, who captures the matter details, who runs the conflict check, who books the consultation — is completely unaddressed by all three. Law firms are solving this today with a $22/hour receptionist who works 9–5, a Calendly link, and a prayer.

What AICS brings that none of them offer:

• 24/7 AI phone and chat intake — calls answered, information captured, conflict check run, consultation booked, without a human on staff
• Law Society of Ontario-compliant conflict check logic — hardcoded, not configurable, not bypassable — running automatically on every intake before a file is even considered
• Secure Document Vault with third-party collaborator access — a magic-link, OTP-authenticated portal for exchanging sensitive client documents with full PIPEDA-compliant audit logging
• AI-summarized intake records — not transcripts, but structured summaries surfacing matter type, urgency, conflict status, and appointment confirmation in a single glance
• Drip follow-up campaigns against unconverted intake leads — something no practice management platform even conceptualizes

The partnership angle: Our roadmap includes a Clio API integration that pushes a completed, conflict-checked, consultation-booked intake record directly into Clio as a new matter — eliminating dual entry entirely. For Clio's existing 150,000+ user base, AICS becomes the front door they never had. That is a channel partnership conversation, not a competition conversation.

Real estate CRMs are the most saturated vertical SaaS market in North America. Follow Up Boss, kvCORE, BoomTown, and Sierra Interactive have raised hundreds of millions of dollars collectively. Understanding why AICS wins in this vertical requires understanding what those platforms actually are: they are lead routing and follow-up reminder tools. They are not AI intake platforms.

The standard real estate CRM workflow: A lead comes in from a portal (Realtor.ca, Zillow, etc.), gets routed to an agent, the agent receives a notification, and if they call back within 5 minutes, they win the lead. If they don't — because they're showing a property — the lead goes cold. The CRM sends automated drip emails that every prospect in 2026 recognizes and ignores. The agent is still doing manual follow-up on a Monday morning for leads that came in Friday night.

What AICS replaces and adds:

• Instant AI phone response to every inbound inquiry — the lead is engaged in a live, intelligent conversation within seconds of submitting a contact form or calling the agency's number, regardless of time of day
• Qualifying intelligence — our AI asks whether they are buying, selling, or refinancing; their timeline; their pre-approval status; their target neighborhoods; their motivation — all structured data that flows into the CRM contact record
• Personalized re-engagement of cold contacts — the 500-contact database campaign described earlier is a direct response to the #1 problem real estate teams report: "We have thousands of past clients and no systematic way to stay in front of them"
• Calendar booking during intake — a showing request or buyer consultation is booked before the call ends
• Secure document handling for listings — offers, agency agreements, and strata documents exchanged through the Vault instead of personal email

Pricing comparison: kvCORE starts at $500–$1,500/month for a team. Follow Up Boss is $69–$500/month per agent. Neither includes AI phone intake, conflict-equivalent lead qualification, or secure document exchange. AICS delivers all three in a single subscription at a price point competitive with a basic CRM — with a demonstrated ROI attached to the lead conversion differential.

The mortgage industry operates with a fragmented technology stack that was designed around lender submission workflows — not client relationship management. Velocity and Filogix are fundamentally application processing and lender submission tools, not client-facing intake or relationship platforms. This is where AICS creates an entirely uncontested category.

Current broker workflow reality: A prospective client calls a mortgage broker. If the broker is busy, the call goes to voicemail. If they don't call back within hours, that prospect calls another broker. Rate-sensitive clients in an active market close with the first responsive broker who gets them to an appointment. There is no AI qualifying that call. There is no instant follow-up. There is no structured intake in most broker offices outside of a Google Form.

What AICS introduces to the mortgage vertical:

• AI phone receptionist that answers calls, runs a qualifying intake (purchase vs. refinance, property type, employment status, timeline, approximate credit range, down payment availability) — producing a structured lead record before the broker ever speaks to the client
• Secure Vault for mortgage document collection — T4s, NOAs, pay stubs, bank statements, rental agreements — all collected through a PIPEDA-compliant, magic-link-authenticated client portal with PHI detection and audit logging. This replaces email-based document exchange, which is a compliance liability every broker is currently carrying
• AI-driven document decision logic (in development) — the system analyzes collected documents and the intake profile to recommend the appropriate lender category, product type, and submission pathway. Not a final decision — but a trained first-pass recommendation that saves the broker 45 minutes of file review on every new application
• Automated client nurturing — past clients who closed two years ago receive an AI-initiated check-in during rate renewal periods, personalized to their file notes, asking if they want to discuss their renewal or refinancing options. No broker manually calls their entire book of business every six months. AICS does it automatically
• Third-party collaborator access — a referral lawyer, a co-borrower, or a financial planner can be invited into a specific client's Vault via magic link to review documents without receiving them by email

The Filogix/Velocity integration angle: Our roadmap includes an API integration that pushes a completed AICS intake record — with documents pre-collected — directly into Filogix as a new application, eliminating duplicate data entry at the most time-consuming stage of the broker workflow. For any aggregator or franchise network operating on Filogix, AICS becomes the intake infrastructure that makes their existing stack significantly more productive.

Property management software is designed to manage the landlord side of the ledger — rent collection, maintenance work orders, owner statements, lease renewals. What Buildium, AppFolio, and Yardi do not do is handle the high-volume, time-critical tenant communication layer that consumes 60–70% of a property manager's daily operational bandwidth.

Consider the daily communication volume of a property manager with 150 units: maintenance requests, status check-ins, lockout calls, noise complaints, renewal inquiries, prospective tenant questions. This is dozens of inbound contacts per day — each requiring a response, a log entry, and often a follow-up. Property management software expects a human to handle all of it. AICS automates the majority.

How AICS transforms property management operations:

• AI phone receptionist for tenant calls — the AI answers maintenance request calls, captures the issue, unit number, urgency level, and tenant contact details, and creates a structured work order ticket in the tenant's dashboard — no staff involvement required
• Personal status validation without human resource consumption — tenants can call or chat to check on the status of their maintenance request, their application, or their lease without speaking to a staff member. The AI retrieves the current status from the contact record and communicates it accurately. This alone eliminates 30–40% of inbound "just calling to check" volume
• Automated vendor dispatch workflow — when a maintenance issue is identified and logged, the property management company receives a dashboard alert and can trigger an AI-initiated outbound call to a vendor from their Contacts list with a single button press. The AI calls the vendor, communicates the issue summary, and negotiates a booking time — which is then confirmed to the tenant automatically
• Prospective tenant intake — every inquiry about a vacant unit is handled by the AI 24/7, qualifying the prospect (income, desired move-in date, number of occupants, pets), scheduling a showing on the property manager's calendar, and creating a contact record with full intake notes
• Lease renewal campaigns — 90 days before a lease expiry, the system initiates an AI phone campaign to every tenant in the renewal window, confirming their intention and guiding them toward a renewal or notice to vacate — structured data that feeds directly into the manager's operational planning

Why this is not competition to Buildium or AppFolio: It is an intake and communication layer that makes their platforms more valuable — because every AICS intake record, work order, and vendor booking can be pushed via API into their existing work order management system.

Critical framing — and this defines our entire healthcare go-to-market strategy: AICS does not compete with Jane App, Cliniko, or OSCAR. We do not manage schedules, clinical notes, billing codes, or insurance submissions. Those platforms are clinical operating systems. We are the intelligent intake layer that sits in front of them — and we are actively pursuing partnership integrations with all three to become their recommended AI front-end.

The gap that Jane, Cliniko, and OSCAR leave open: All three expect the patient to arrive at a booking page on their own. They provide no AI phone receptionist. They provide no after-hours call handling. They provide no intake qualification that distinguishes between an acute concern requiring same-day booking and a routine inquiry that can wait two weeks. They provide no automated follow-up for missed appointment slots. And for health practitioners in private practice — chiropractors, dentists, physiotherapists, psychologists, tanning and aesthetics clinics — none of them provide a secure document portal for intake forms, health history questionnaires, or consent documents that meets PHIPA audit requirements.

What AICS adds without replacing anything:

• 24/7 AI phone and chat intake — patients call after hours, AI handles the conversation, collects reason for visit, health concerns, insurance information, and preferred appointment time, and books the appointment directly into the connected Google Calendar
• PHIPA-compliant intake document vault — new patient health history forms, consent documents, and referral letters collected through the secure portal — with three-layer PHI detection on every uploaded file and a full PHIPA-aligned audit log
• Post-appointment follow-up campaigns — the AI calls patients 48 hours post-treatment to ask how they are doing, confirm their next appointment, and collect any concerns — creating a documented patient engagement record that supports continuity of care standards
• Reactivation campaigns for lapsed patients — every patient in the contact database who has not visited in 6+ months receives an AI-initiated wellness check call, personalized to their last visit notes. For a practice with 800 inactive patients, this is a revenue reactivation lever that no scheduling software provides
• Personal status validation — patients can call or text to confirm their appointment, check on a referral, or ask a non-clinical administrative question — all handled by AI without consuming front-desk staff time

The partnership path: A Jane App or Cliniko integration that pushes completed AICS intake records directly into their patient management system — eliminating front-desk manual entry — is a feature that their user communities have been requesting for years. We build the integration; they recommend us to their 60,000+ combined clinic customers. That is the distribution conversation.

Dental practices share the same fundamental operational bottleneck as medical clinics — the front desk is the single point of failure for intake, scheduling, document collection, and patient communication — but with sector-specific compliance and workflow wrinkles.

What AICS does for dental practices:

• New patient intake by AI phone — the AI answers new patient inquiry calls, collects demographics, insurance provider, chief dental concern, and preferred appointment time, and books the consultation. No front-desk staff required after hours or during peak treatment periods
• PHIPA-compliant new patient health forms via Secure Vault — the traditional clipboard in the waiting room replaced by a magic-link-authenticated digital portal. Patients complete their health history, medication list, and consent forms before their first visit, from their phone. The practice receives a complete, PHIPA-logged intake record before the appointment
• Treatment follow-up automation — post-extraction, post-implant, or post-orthodontic adjustment calls to check on patient recovery, answer administrative questions, and confirm the next appointment
• Recall campaign automation — six-month recall reminders are not just SMS messages from a scheduling software. The AI calls patients who are due for their hygiene appointment, qualifies their availability, and books the appointment — dramatically outperforming static reminder messages in confirmed booking rates
• Reduced no-show rates through conversational confirmation — instead of a text reminder that gets ignored, patients receive an AI call 24–48 hours before their appointment that confirms attendance and allows real-time rescheduling if necessary

The coaching sector — life coaching, business coaching, executive coaching, fitness coaching, and wellness coaching — is one of the fastest-growing professional service categories in North America, and one of the most underserved by technology. Most coaches run on Calendly, a Google Form, and a Gmail inbox. The operational ceiling this creates is the reason most coaching practices never scale beyond a solo operator.

What AICS brings to coaching practices:

• AI discovery call intake — prospective clients inquire about coaching programs; the AI conducts a structured discovery conversation that qualifies their goals, current challenges, budget range, and availability — saving the coach 20–30 minutes per inquiry on calls that will not convert
• Program-specific intake funnels — the AI agent is configured with the coach's program offerings, qualification criteria, and enrollment pathway. It routes qualified prospects to a booked discovery call and non-qualified prospects to a nurture sequence automatically
• Secure onboarding document collection — coaching agreements, intake questionnaires, goal-setting worksheets, and progress assessments collected through the Vault portal — replacing Dropbox and email with a professional, branded, secure document exchange
• Client re-engagement campaigns — past clients who completed a program but haven't re-enrolled receive AI-initiated check-in calls, personalized to their program notes, exploring where they are in their journey and whether a next-level program is relevant
• Personal status validation for active clients — clients can check session schedules, homework assignments, and program milestones via AI chat without requiring the coach's direct attention

The coaching sector has the demographics, the average client value, and the operational pain profile that make AICS ROI extremely fast to demonstrate. A coach who converts two additional clients per month from AI-handled inquiry volume has recouped their subscription cost before the second billing cycle.

Most AI SaaS platforms entering the Canadian professional services market are American products with a Canadian flag sticker. Their data transits through U.S. servers, their compliance frameworks reference HIPAA instead of PHIPA, their conflict check logic (if it exists at all) references ABA rules instead of Law Society of Ontario guidelines, and their customer support teams have never heard of PIPEDA.

AICS is built from the ground up for Canadian regulatory reality:

• Canadian data residency — all tenant data for Canadian clients is hosted on AWS Canada (Montreal/Toronto regions). No data crosses the border. This is not a configuration option — it is the default architecture
• PIPEDA-aligned data practices — data collection, consent workflows, retention policies, and access controls are built to support PIPEDA compliance obligations out of the box
• PHIPA-compliant architecture for healthcare tenants — PHI detection, encrypted storage, access logging, and breach notification infrastructure aligned with Ontario's Personal Health Information Protection Act
• Law Society of Ontario conflict check compliance — our hardcoded conflict check logic mirrors the LSO's two-step conflict of interest identification process. This is not a generic name-matching feature — it is a rules-based compliance system that no U.S.-origin product has built for the Canadian legal market
• SOC 2-oriented audit architecture — the logging, access control, and data isolation framework is designed to support SOC 2 audit requirements for enterprise and health sector tenants

Every tenant on the AICS platform operates in a fully isolated database partition — not a shared table with row-level filtering, but a completely separate database schema per tenant. A security breach affecting one tenant's environment cannot access any other tenant's data by architectural design.

Additional security layers in production:

• TLS encryption in transit — all client-server communication, all AI API calls, all document transfers
• Encryption at rest — all stored documents, intake records, and contact data on AWS S3 and RDS
• PHI detection on document upload — three-layer scan on every file entering the Secure Vault, flagging protected health information before storage
• Magic-link token authentication for client portal access — no username/password to be phished. Every link is single-use, time-limited, and tied to a specific client record
• OTP email verification on every portal session — even if a magic link is intercepted, access requires a verified email OTP that expires in minutes
• Session inactivity timeout — client portal sessions auto-expire on inactivity, with forced re-authentication on return
• Full audit log — every document access, upload, collaborator invitation, and message — timestamped, attributed, and exportable for regulatory review

This is not startup security. This is enterprise-grade data architecture implemented at a SaaS price point — which is a significant part of why regulated professionals choose AICS over cobbling together third-party tools.

The conflict of interest check is one of the most consequential — and most commonly mishandled — obligations in legal practice. A law firm that accepts a client without running a proper conflict check, and later discovers a conflict, faces potential disqualification from the matter, professional discipline, and reputational damage that can end a practice.

How our conflict check works: When an AI intake (phone or chat) completes for a law firm tenant, the system automatically cross-references the intake data — specifically last name, first name, city, and email — against every existing contact in that tenant's CRM database. The matching algorithm requires a minimum of two corroborating fields to flag a potential conflict, reducing false positives that would create operational noise.

What makes this compliance-grade rather than cosmetic:

• The conflict check logic is hardcoded at the system level — it cannot be disabled by the tenant, turned off to speed up intake, or bypassed by a staff member in a hurry
• The result is surfaced in the intake record as a clear status badge — "Conflict Cleared" or "Potential Conflict Detected" — with the matching contact record linked for review
• The AI agent is aware of the conflict check result during a phone call and can communicate appropriately to the caller if necessary — "I'll need our team to review your file before we can confirm a consultation" — without revealing confidential information about the conflicting client
• Every conflict check result is logged with timestamp in the audit record, creating a documentable evidence trail that the firm exercised due diligence during intake

No general-purpose CRM, no U.S.-origin intake tool, and no existing practice management platform for the Canadian market provides this. It is the single feature most frequently cited by law firm clients as the reason they chose AICS over alternatives.

We are not conducting a traditional funding round. We have a deployed product, active paying tenants, and a platform that is operationally profitable at current scale. What we are seeking is strategic distribution acceleration — partners who can help us move from early traction to market leadership in one or more of our six target niches significantly faster than organic growth allows.

Four categories of strategic partner are most valuable to us:

1. Professional association and regulatory body relationships. A partnership with a provincial law society continuing education program, a mortgage broker association like CAAMP/MBABC, or a dental association professional development network gives us direct access to the entire licensed professional base in a niche — not one firm at a time, but the whole addressable market simultaneously.

2. Existing vertical SaaS platform integrations. Clio has 150,000+ law firm users. Jane App has 60,000+ clinic users. A technology partnership that makes AICS the recommended intake layer for their user base — with a native API integration that eliminates dual entry — creates a distribution channel worth more than any advertising budget.

3. Enterprise resellers and channel partners with existing books of business. A commercial insurance broker, a B2B accountant serving professional services clients, or a legal IT consultant who manages technology for 50 law firms can embed AICS into every engagement as a value-added component — and earn meaningful recurring revenue doing so. Salesforce AppExchange is a named distribution channel for mortgage and real estate at scale.

4. Capital partners who bring network access alongside capital. If funding comes with a direct relationship to a franchise network, a professional services association board, or a channel with meaningful enterprise contacts — that is a conversation worth having. Capital alone is not the constraint. Distribution relationships are.

AICS operates on a monthly SaaS subscription model with tiered pricing structured by niche, feature access, and usage volume. Base plans begin at a price point accessible to solo practitioners and scale to enterprise plans for multi-location practices and franchise networks.

Revenue levers that compound over time:

• Seat expansion — firms that onboard with one or two staff accounts expand as they see the operational leverage. Multi-attorney firms, brokerage teams, and clinic groups naturally grow into higher-tier plans
• Usage-based components — AI phone minutes, document vault storage, and outbound campaign volume create a revenue layer that grows proportionally with tenant business growth — we win when they win
• Niche expansion — each new niche we fully onboard is a discrete, addressable market with its own playbook. We are not starting from zero in each niche; the platform infrastructure is niche-agnostic. The competitive differentiation is the hardcoded niche logic, which we develop once and deploy to every tenant in that vertical
• API integration licensing — enterprise-level integrations with Clio, Filogix, Jane, AppFolio, and similar platforms can carry a separate integration licensing component for the enterprise channel

The growth arithmetic is compelling: There are approximately 50,000 licensed lawyers in Ontario alone, 30,000 mortgage agents across Canada, 15,000 dental practices in Ontario, and 80,000+ real estate agents registered with CREA. Capturing 1% of any single one of these markets is a significant business. Capturing 1% across all six is a category-defining one.

We do not ask investors to fund a vision without interrogating the risks. Here is an honest breakdown:

Risk 1: Large players copy the features. Clio, Jane, and Salesforce Health Cloud have the engineering resources to build what we have built. Mitigation: our moat is not the features — it is the niche-specific compliance logic, the Canadian data architecture, and the speed of iteration in a market that large platforms move slowly in. We will have completed our next 18 months of development before a large player ships version one of an equivalent. First-mover tenant stickiness in a compliance-dependent workflow is extremely high.

Risk 2: AI model dependency. We use existing LLM AI as underlying model providers. If pricing changes or service deteriorates, it affects us. Mitigation: our architecture abstracts the LLM layer — we can swap model providers without rebuilding the intake logic or compliance rules. We are not locked into any single model.

Risk 3: Regulatory changes affect compliance claims. PIPEDA is currently under review. PHIPA enforcement is evolving. If the regulatory landscape shifts, our compliance positioning must shift with it. Mitigation: this is a risk our competitors carry identically — and most of them are less prepared to respond because compliance architecture is not part of their core product DNA. It is ours.

Risk 4: Sales cycle length in regulated professions. Lawyers, doctors, and mortgage brokers are not early adopters. They buy on trust, referral, and evidence of peer adoption. Mitigation: this is exactly why we are seeking association-level partners and channel relationships — because the trust is pre-established within those networks. One law society endorsement reaches 50,000 lawyers more credibly than two years of digital advertising.

Yes. AI Canadian Solutions is incorporated and operated as a Canadian entity. Our platform infrastructure for Canadian tenants is deployed within AWS Canada (Montreal and Toronto regions) — meaning all tenant data, all client intake records, all document vault contents, and all AI conversation logs remain on Canadian soil under Canadian jurisdiction.

This is not a marketing claim. It is an architectural commitment embedded in our deployment infrastructure — and it is one of the most frequently cited reasons regulated Canadian professionals choose AICS over U.S.-origin alternatives. A law firm, a healthcare provider, or a mortgage broker that stores client data on American servers is carrying a PIPEDA compliance liability that their regulator can and does scrutinize. We remove that liability entirely.

For firms requiring documented evidence of Canadian data residency — for their own compliance audits, their insurance requirements, or their professional regulatory filings — we provide infrastructure documentation confirming AWS Canada region deployment.

The platform is designed to support compliance with the following Canadian privacy frameworks:

• PIPEDA (Personal Information Protection and Electronic Documents Act) — governing collection, use, and disclosure of personal information in commercial activities across Canada
• PHIPA (Personal Health Information Protection Act, Ontario) — governing collection and protection of personal health information in Ontario healthcare settings
• Law Society of Ontario Practice Management Guidelines — including conflict of interest identification and client intake documentation requirements
• SOC 2 Type II-aligned controls — security, availability, and confidentiality controls aligned with the SOC 2 audit framework for our enterprise and health sector tenants

Individual firms remain responsible for their internal compliance policies and their interpretation of regulatory requirements specific to their practice area. AICS provides the technical safeguards, audit architecture, and data sovereignty infrastructure required to support those obligations — not legal advice about them.

For detailed compliance documentation, data processing agreements, or infrastructure attestation letters, contact our enterprise team directly.

Yes. We execute non-disclosure agreements prior to any substantive technology discussion, integration scoping, or proprietary architecture review. For enterprise partnership and distribution conversations, we also provide formal data processing agreements and infrastructure attestation documentation upon request.

We take intellectual property seriously — including ours. All partnership and integration discussions are conducted under NDA as a standard condition of engagement, not an exceptional one.

Canada is — and will remain — the foundation of this business. Our platform was architected specifically for the Canadian regulatory environment: PIPEDA data residency requirements, PHIPA health privacy obligations, Law Society of Ontario conflict check standards, and the reality that Canadian professionals deserve a platform built for their regulatory reality rather than adapted from an American one. That conviction has not changed.

What has changed is our line of sight into the United States.

The decisions we made to win in Canada's most regulated sectors — the compliance-hardcoded agent logic, the multi-tenant isolated database architecture, the SOC 2-aligned audit infrastructure, the encrypted document vault, the PHI detection system, the magic-link authenticated client portal — are precisely the decisions that make U.S. expansion not a rebuild, but an extension. Our engineering team's current assessment is that the existing AICS platform represents approximately 70–80% of the technical work required to operate in the U.S. health sector at a HIPAA-compliant standard.

The remaining 20–30% is not a product challenge. It is a legal, contractual, and configuration challenge — one that is well-understood, costed, and executable within a defined timeline. For investors evaluating the U.S. expansion opportunity, that distinction matters enormously. We are not pitching a vision of building something new. We are pitching the execution of a near-complete technical foundation into the largest healthcare AI market in the world.

The numbers speak without needing interpretation.

The U.S. AI in healthcare market is estimated at USD 14.25 billion in 2025 and is expected to reach USD 446.38 billion by 2035, growing at a CAGR of 41.12%. North America currently holds the highest regional revenue share — over 45% of the global AI in healthcare market — driven by advanced digital health infrastructure and strong government support for health technology innovation.

For context on the SaaS layer specifically: the U.S. Healthcare SaaS market is projected to grow from USD 10.58 billion in 2025 to USD 53.38 billion by 2035 at a CAGR of 17.58%, driven by cloud-based EHR adoption, telemedicine expansion, and increasing demand for scalable operational management solutions.

The global healthcare software market is undergoing a fundamental structural shift — rapidly transitioning from legacy monolithic architectures toward unified modular platforms that automate non-clinical administrative burdens, with experts identifying this convergence as the primary growth catalyst.

This is precisely the category AICS occupies. We are not a clinical tool. We are the administrative and intake automation layer — the front door that clinical software platforms have never built — and in the U.S., that category is a multi-hundred-billion-dollar open field.

The healthcare vertical is our U.S. beachhead for three specific reasons:

1. HIPAA is a single federal standard. Unlike legal (50 state bars) or mortgage lending (multi-federal regulatory stack), HIPAA applies uniformly across all 50 states. Compliance achieved in New York is compliance achieved in Texas. We build once, deploy nationally.

2. The compliance gap is enormous and visible. Mishandling Protected Health Information can lead to fines of up to $1.5 million per violation category annually, and healthcare data breaches averaged $10.22 million in 2025. Private practice healthcare providers — dentists, physiotherapists, chiropractors, psychologists — are currently handling patient intake data over personal email, unencrypted SMS, and paper clipboards. The liability exposure is not theoretical. It is daily. AICS removes it.

3. There is no dominant AI intake platform serving private practice healthcare in the U.S. The large players — Epic, Cerner, Athenahealth — serve hospital systems. The 200,000+ private practice clinics in the U.S. are operating with scheduling software that was not built for AI intake, and intake workflows that were not built for compliance. That is our market.

This is the question every serious investor should ask — because "HIPAA-compliant" is one of the most misused phrases in health tech. Many platforms claim it by virtue of running on AWS. That is not what it means.

HIPAA compliance for a SaaS platform operating as a Business Associate — which is AICS's classification when handling patient intake data on behalf of healthcare providers — requires three distinct compliance domains:

Domain 1 — Legal & Contractual
The foundational document is a Business Associate Agreement (BAA) — a legally binding contract between AICS and every healthcare tenant, and between AICS and every vendor that touches Protected Health Information (PHI). AWS provides a self-service BAA through AWS Artifact — signing it takes minutes in the AWS Management Console and is the non-negotiable legal foundation for processing PHI on AWS infrastructure. This is not a complex engineering task. It is a contract. For AICS, this means: (1) sign the AWS BAA, (2) develop a HIPAA-specific tenant agreement template reviewed by a U.S. healthcare attorney, (3) audit vendor agreements for any sub-processor touching ePHI. None of our core vendor dependencies preclude HIPAA compliance — all three offer BAA execution for healthcare customers.

Domain 2 — Technical Safeguards
Core HIPAA technical requirements include AES-256 encryption, TLS 1.2+ for data in transit, role-based access control, multi-factor authentication, and immutable audit logs. Here is where our Canadian architecture's head start becomes material:

Already built and production-deployed in AICS:
✅ AES-256 encryption at rest (AWS S3 + RDS)
✅ TLS encryption for all data in transit
✅ PHI detection on document uploads (3-layer scan)
✅ Magic-link + OTP authentication on client portal
✅ Session inactivity timeout and forced re-authentication
✅ Full audit log with timestamp, user attribution, and CSV export
✅ Isolated per-tenant database architecture
✅ Role-based access controls at tenant level

Required additions for HIPAA gap closure:
⚙️ Expand PHI detection to all 18 HIPAA Safe Harbor identifiers (currently covers a subset)
⚙️ Configure AWS CloudTrail for PHI-access audit logging at the infrastructure layer
⚙️ Migrate U.S. health tenants to a dedicated AWS US-region account (US-East or US-West)
⚙️ Ensure only HIPAA-eligible AWS services are used in the U.S. health tenant namespace
⚙️ Implement MFA enforcement at the tenant admin account level

Domain 3 — Administrative Safeguards
HIPAA administrative safeguards represent over half of the Security Rule requirements — including a formal risk assessment process, a designated security official, workforce training, and an incident response program. These are operational policies, not software features. They require a U.S. healthcare attorney, approximately 60–90 days of policy documentation work, and a designated internal security lead. This is not a technical sprint — it is a compliance program build that is a one-time investment maintained through annual reviews.

The honest timeline: With focused execution and appropriate legal counsel engaged, AICS can achieve a credible HIPAA-compliant operational posture for the U.S. health sector in 90–120 days from decision to deploy. That timeline assumes no platform rebuild — because no platform rebuild is required.

We don't ask investors to accept a simplified story. Here is the complete picture of what U.S. expansion actually involves — and how each barrier maps to a defined solution path:

Barrier 1 — U.S. Entity and Legal Structure
Operating as a Canadian company selling to U.S. healthcare providers requires a U.S. entity for contracting purposes, tax treatment, and HIPAA Business Associate Agreement enforceability under U.S. law. A Delaware C-Corp subsidiary is the standard structure for Canadian companies entering the U.S. market. This is a legal formation task, not a technology task — typically 2–4 weeks and under $5,000 in legal fees. This does not require new infrastructure or a new codebase.

Barrier 2 — U.S. Telephony Compliance
Our AI phone receptionist currently operates on Canadian phone numbers through AI. For U.S. health tenants, outbound AI calls must comply with the Telephone Consumer Protection Act (TCPA) — which governs AI-initiated calls and requires prior express consent from the recipient. The practical implication: our campaign and follow-up AI call features require a consent capture workflow before initiating outbound calls to U.S. contacts. Our telephony AI already supports U.S. NANP numbers. The TCPA consent workflow is a form field and a database flag — not a architectural change. It is an estimated 2–3 days of development.

Barrier 3 — State Privacy Law Patchwork
The U.S. has no federal equivalent to PIPEDA — instead, a growing stack of state privacy laws led by California's CPRA, followed by Virginia, Colorado, Texas, Connecticut, and others. Compliance with California CPRA — the strictest state standard — provides substantial coverage across all other state frameworks. The required additions to our existing privacy program are: a U.S.-resident-specific privacy policy, a data subject rights request workflow (access, deletion, correction), and updated data processing agreements with tenants. Our PIPEDA-compliant data practices are structurally analogous — the legal templates change; the technical architecture does not.

Barrier 4 — Market Trust and Sales Cycle
U.S. healthcare providers — like Canadian lawyers — are risk-averse buyers who purchase on peer validation, not advertising. The fastest path to U.S. market trust is a professional association endorsement or channel partnership with an entity that already has the trust of our target buyers. A relationship with the American Dental Association, the American Chiropractic Association, or a healthcare-focused group purchasing organization creates the same effect in the U.S. that a provincial law society relationship creates in Canada: immediate credibility with a verified professional audience that is pre-qualified for our offer. This is the precise value a strategic U.S. partner brings — not capital for infrastructure, but access to distribution channels we would otherwise spend years building organically.

It is the right question, and the answer is strategic rather than aspirational.

Healthcare offers the cleanest compliance story. HIPAA is one federal standard, enforced by one federal agency (HHS/OCR), applicable across all 50 states identically. Contrast this with legal — where 50 individual state bar associations govern attorney conduct with meaningful variation in ethics rules, conflict check requirements, and technology guidance — or mortgage lending, which layers GLBA, RESPA, FCRA, ECOA, CFPB guidance, and NMLS licensing requirements in a regulatory stack that requires sector-specific legal counsel in multiple jurisdictions simultaneously. Healthcare's complexity is real, but it is a single-axis complexity problem. Legal and mortgage are multi-axis. We take the single-axis market first, build the U.S. compliance infrastructure and operational muscle, then expand horizontally into adjacent verticals from a position of demonstrated compliance credibility.

The private practice healthcare market in the U.S. is dramatically underserved. Enterprise health systems — hospitals, large clinic networks — have technology vendors. The 200,000+ independent dental practices, chiropractic offices, physiotherapy clinics, psychology practices, and aesthetics/wellness studios do not. They are running their front desk on Jane App or a generic booking tool, handling intake on paper or unencrypted forms, and losing new patients every evening because no one answers the phone after 5PM. This is the same profile as the Canadian private practitioners who became our earliest tenants. We know exactly how to sell to them, onboard them, and demonstrate ROI within their first billing cycle.

The upside arithmetic justifies the focus. There are approximately 200,000 dental practices alone in the United States. At a conservative average subscription of $299/month, capturing 0.5% of that single sub-segment represents $36M in annual recurring revenue. Physiotherapy, chiropractic, and mental health private practices add hundreds of thousands of additional addressable units. The U.S. private practice health market, even at fractional penetration, is a business that transforms the scale of AICS entirely — and it is accessible through the compliance infrastructure we are already 70–80% of the way to completing.

The partnership argument closes here. A U.S. strategic partner who brings a direct channel into private practice healthcare networks — a professional association relationship, a group purchasing organization, a healthcare staffing or billing company with an existing book of clients — compresses what would otherwise be a 24-month organic market entry into a 6-month distribution event. That is the conversation we are inviting.

U.S. expansion for the health sector is not a capital-intensive infrastructure project. It is a compliance, legal, and go-to-market execution project — with a disproportionately large market unlock relative to the investment required.

The four investment categories:

1. Legal & Compliance Foundation — one-time cost
U.S. entity formation, HIPAA legal counsel for BAA templates and risk assessment documentation, TCPA consent workflow development, California CPRA privacy policy adaptation, and U.S. healthcare attorney review of tenant agreements. Estimated: $30,000–$60,000 USD in legal fees plus approximately 90 days of internal compliance program build. This is not recurring cost — it is a one-time foundation that serves every U.S. health tenant we ever onboard.

2. Infrastructure Configuration — minimal engineering
AWS US-region account deployment for U.S. health tenant namespace, AWS BAA execution, CloudTrail audit logging configuration, PHI detection gap closure against all 18 Safe Harbor identifiers, and HIPAA-eligible services audit. Estimated: 3–6 weeks of engineering time. No new services, no new platform architecture — configuration and audit of what is already built.

3. Go-To-Market — channel and distribution
This is where strategic partner capital has the highest leverage. The technology is ready. The compliance framework is near-complete. The constraint is distribution access to the private practice healthcare market. A partner who contributes channel relationships, association introductions, or an existing client base in U.S. healthcare eliminates the 18–24 month organic trust-building cycle that every cold-entry SaaS company faces in healthcare — and replaces it with a credentialed introduction to a pre-qualified market.

4. U.S. Market Operations — scaling cost
U.S.-based customer success support, U.S. sales infrastructure, and localized marketing. These are growth costs that scale proportionally with revenue — not prerequisite capital requirements. They are funded by the U.S. subscription revenue they generate.

What it unlocks: Access to a U.S. private practice healthcare market addressable at hundreds of thousands of independent clinic and practice locations, in a sector growing at over 41% CAGR, where no dominant AI intake platform exists for the independent practitioner segment, and where our existing platform capabilities — HIPAA-aligned security, PHI-detecting document vault, AI phone and chat intake, automated scheduling, and post-visit patient engagement — map directly to the documented operational pain points of every private practice in the country.

The Canadian platform proved the model. The U.S. market scales it.