c-84, sector 65, Noida
c-84, sector 65, Noida
The Insight Clinic runs a multi service mental health and ABA practice with appointments in Jane and operations in Zoho CRM. Clixlogix designed the PHI boundary first, then built the intake foundation, the appointment sync layer, and a reconciled reporting layer that closed on formal client acceptance.

The Insight Clinic runs a multi service mental health and applied behavior analysis practice, serving counselling and ABA clients across a growing case load. Appointments live in Jane. Sales and intake operations live in Zoho CRM. Lead demand comes through a mix of paid Meta campaigns, organic search, referrals, and the clinic’s own community presence.
Before the Clixlogix engagement, intake was fragmented across a website form, phone lines, missed calls, and paid ad channels. Appointment activity in Jane did not surface into CRM in any structured way. Historical Jane records sat outside the CRM entirely. There was no shared definition across operations, finance, and clinical intake for what counted as an Open Lead, a Closed Lead, a converted client, or a first completed session. Executive reporting was assembled by hand each month, with numbers reconciled across three systems before any figure could be defended.
Clixlogix delivered the buildout in phased releases across Discovery and three implementation milestones. Discovery designed the Jane to Zoho security boundary before any code was written, so clinical records stayed inside Jane and out of every other tool in the stack. The build then stood up the CRM intake foundation, expanded the sync layer to bring appointment activity, Meta ad channels, and QuickBooks into a coordinated flow, and closed with a reporting layer of reconciled dashboards across Zoho CRM Reports and Zoho Analytics.
The engagement completed following a structured client owned UAT that walked every KPI definition against the clinic’s own ground truth, and closed on formal client acceptance. The practice now operates on a single spine, with Jane preserved as the clinical system of record and Zoho as the operational source of truth for pipeline, marketing, and finance.
Vielka Almanzar Bautista founded The Insight Clinic in Whitby, Ontario in 2019, and remains its CEO and Clinical Director. Bilingual in English and Spanish, she trained in Clinical and Health Psychology at ISEP in Spain and practices CBT, EMDR, and neurofeedback alongside running the business. The clinic has since grown to two locations and roughly thirty staff across counselling, ABA therapy, neurofeedback, and assessments, with three regional awards for best mental health service in the Durham area along the way.
Vielka approached Clixlogix in January 2026. The original ask was an AI layer over Zoho that could update CRM records automatically, enrich sales data, and summarize meetings. The diagnostic pass in Discovery identified that the value from an AI layer would compound only if the underlying operating spine was clean first. A structured lead lifecycle through Deal conversion, appointment activity flowing cleanly from Jane, and marketing attribution holding across the funnel had to exist before any LLM could add value inside CRM. The foundation had to come first. The engagement across Discovery and three implementation milestones built that foundation, which is what an AI layer would need underneath it.
The client side project ownership sat with Marcell Almanzar, Head of Sales, Business Intelligence at the clinic, who Vielka named to lead the engagement from day one. He engaged through every implementation phase, moved fast on feedback, surfaced edge cases early, and pushed for the precision the reporting layer needed to be defensible in leadership conversations. He walked dashboard totals against the underlying CRM records before acceptance, and worked with Clixlogix on KPI definitions until each metric read the same number across every surface. That level of client side involvement is what lets a delivery team hold automation and reporting to a standard that survives an audit.

The practice is inquiry driven at the front end and appointment driven at the back end. Nothing lands on the schedule without an intake conversation. Every prospective client moves through a pipeline that starts with an inquiry and ends with a first completed session, and the operational question at every stage is whether the systems agree with each other about where that person actually is.
Mental health and ABA practices sit at the intersection of two operational forces that off the shelf tooling rarely models cleanly. On one side, clinical operations run inside a purpose built practice management platform. Jane is the leader in Canada for a reason. It owns the appointment book, the client chart, the billing to insurer flow, and every piece of PHI that a regulator will ever ask about. On the other side, marketing and pipeline operations run inside a general purpose CRM like Zoho, where lead capture, campaign attribution, sales follow up, and executive reporting are all supposed to happen. The two systems have very different data models and very different security requirements, and the seam between them is where most growing practices lose visibility.
The practice hits a scale ceiling when leadership can no longer answer four questions from a single dashboard:
Answering those questions manually across Jane and Zoho consumes ops and finance hours that a growing practice cannot afford to spend on data reconciliation.
Sector Perspective
Healthcare practice management vendors and general purpose CRMs are architected for different jobs. The clinical system is optimised for the patient encounter and the regulatory record. The CRM is optimised for the sales and marketing lifecycle. Neither is engineered to be the other's authoritative counterpart, and neither vendor is incentivised to build a clean two way sync into the other. The Canadian mental health services sector has grown fast enough over the last five years that this seam has become the single most common ceiling on operational scale. The practices that get past it are the ones that build the integration layer as an intentional piece of architecture, not as a set of manual copy paste routines run by an ops coordinator.
Small healthcare practices that grow into Jane for clinical operations while adopting Zoho for CRM almost always end up with a brittle set of handshakes across the stack, and a second brittle handshake between operational finance and the statutory accounting system. Discovery walked every application in the clinic’s Zoho environment and mapped exactly where the seams were opening.
Growing practices treat the website as a lead capture card while the real intake conversation happens on the phone. Discovery watched a full inbound cycle and saw the specific fields that were falling out of it.
The intake conversation and the first appointment approval are where growing practices lose time and audit trail together. Discovery mapped every hand off point across ops, clinical intake, and finance.
For a practice that runs on session throughput, the alignment between what was invoiced and what was actually delivered clinically is where working capital either flows cleanly or accumulates as friction.
Growing practices tend to run first and count later. Decisions get made ahead of the numbers because assembling them takes time that a growing practice does not have, and by the time the numbers are assembled the picture has moved.
Clixlogix delivered the buildout in five workstreams across the four phases. Track 1 designed the Jane to Zoho security boundary and cleaned the operating stack. Track 2 stood up the lead intake and CRM foundation. Track 3 built the appointment sync layer and the duplicate prevention model that keeps the pipeline clean. Track 4 delivered the marketing attribution and executive reporting layer. Track 5 ran a structured client owned UAT that reconciled every KPI against the clinic’s own ground truth and closed on formal acceptance. Every track shipped in phased releases so the operations team kept running on the live stack while each layer went into production.

Fig 1 – System Architecture After the Build
Fixes the fragmentation across Jane, Zoho, WorkDrive, and QuickBooks and locks the design decisions that every downstream automation has to respect.
Structural Diagnosis
The security boundary between a clinical system of record and an operational CRM is the single most important architectural decision in a healthcare integration project. Designed in Discovery, it constrains every downstream automation and produces a clean audit trail. Retrofitted after the build, it either forces expensive rework or gets quietly abandoned. Healthcare regulators do not care which of the two happened. They only care about the resulting posture. This is why every successful practice integration begins with the boundary, then builds the workflow on top.
Fixes the fragmented multi channel intake, the duplicate lead risk carried by call automations, and the inconsistent service category capture.
The intake foundation covers four functional areas:
Every automation went through sandbox first. Production go live followed only after formal client sign off, and only after the operations team had validated the intake flows against their own live workflows. For a practice that takes real appointments every day, a sync bug in production translates directly into a lost client.
Fixes the sync loop that created false duplicates, the stale record problem in the CRM pipeline, and the alignment between the clinical system and the CRM Deal.
Compounding Design Decision
Sync hygiene between a clinical system and a general purpose CRM is a small category of design decision with a large downstream effect. Small rules that keep historical records from drifting back into current reporting look mundane in isolation. Three months later, when the executive team is reading month over month conversion trends and expecting those trends to be defensible under audit, the value of the discipline becomes obvious. This is a category of design decision that separates integrations that scale from integrations that decay.
Fixes the missing attribution funnel from ad spend to booked appointment and the absence of reconciled executive reporting.
Marketing attribution reporting covers:
Executive reporting covers:
Weekly and monthly KPI reporting cadence was set up across Zoho CRM Reports and Zoho Analytics, with reconciled KPI definitions so the same metric reads the same number across every surface and the scheduled reports.
Fixes the risk that dashboards built by an outside team may not survive contact with the client’s own definitions and ground truth.
Three setbacks are common in builds of this shape, and all three appeared in this engagement. Each has a well established recovery pattern, described below at the category level. Any operator considering a similar buildout should expect at least one of them to surface, and should have a plan for handling it.
| Setback | Why it happens in builds of this shape | Recovery |
|---|---|---|
| Sync layer creating false duplicates on every cycle | Sync layers between a clinical system and a general purpose CRM often re upsert every historical record on each cycle, which means stale or lost records keep resurfacing and drift the pipeline reports out of alignment with operational truth. | A reclassification rule is designed and agreed with the client's technical team. Stale or lost records close on the CRM side rather than re upserting. The sync layer stops re creating them. The pipeline reports then reflect reality without a manual reconciliation pass. |
| Duplicate leads from call automation | Incoming call automations often create a new Lead every time they fire, so a single caller who dials twice shows up in the CRM as two separate prospects. This inflates the pipeline and breaks the caller identity across dashboards. | Duplicate prevention is added to the call automation on the caller identity. Repeat calls match against the existing Lead record rather than creating a new one. |
| KPI definitions not agreed across teams | Dashboards built against reasonable defaults do not always match the client's own operational definitions. Lead volume can include records the client considers invalid. Event dating can rely on proxy fields, and historical events can be derived from current record state instead of preserved as facts. | Every KPI is walked in a structured UAT with the client's finance and technology leads. Definitions are formalised, filter logic is adjusted, event dating is anchored to the actual events, and historical facts are preserved so cohort analysis holds through subsequent activity. The reporting layer then reconciles against the client's own definitions. |
Underlying Mechanism
A healthcare practice integration that closes on formal client acceptance does so because the delivery team treats KPI reconciliation as a first class part of the engagement. The dashboards and the definitions are built together. The client's own team pressure tests both against their own ground truth. Every gap is documented at the level of the underlying reporting logic and adjusted until the two reconcile. This is what separates dashboards that get used from dashboards that quietly get replaced by a spreadsheet six months after launch.
The engagement moved The Insight Clinic from a manual, fragmented operation to a single automated spine running lead intake, appointment sync, marketing attribution, billing visibility, and reporting inside Zoho CRM, with the reporting layer running across CRM Reports and Zoho Analytics, with Jane preserved as the clinical system of record and QuickBooks preserved as the source of truth for accounting. Each outcome below is stated against the pre engagement operational baseline established during Discovery.




We've had a very good experience working with your team. One thing I've particularly appreciated is how responsive everyone has been throughout the project. Even with the significant time difference between our teams, whenever we had a question or something that needed attention, we normally heard back very quickly, often by the following day. And whenever we felt a call would be easier than going back and forth over email, the team was always willing to find the time to meet with us.
Six operational changes are now visible in the day to day at The Insight Clinic.
Five criteria identify the operator profile this buildout fits.
If three or more of the above hold, a discovery conversation is worth having. If fewer hold, the fit is weaker and a different approach may serve the operator better.
| Layer | Technology |
|---|---|
| CRM and Workflow | Zoho CRM with a stage Blueprint, workflow rules, and custom fields for billing status |
| Clinical System of Record | Jane, holding the appointment book, the client chart, and all PHI inside the security boundary |
| Cross App Sync | Zoho Catalyst serverless functions carrying non PHI appointment activity from the clinical system into CRM Deal records |
| Communication and Intake | Zoho Mail with SalesInbox for email inquiry to Lead automation, Zoho Forms for website intake with UTM capture, Zoho SalesIQ for web chat, RingCentral for incoming call automation with duplicate prevention |
| Marketing and Demand | Meta Lead Ads with LeadChain, with attribution retained across the lead lifecycle |
| Analytics and Reporting | Zoho CRM Reports and Zoho Analytics, together forming the reporting layer, with a weekly and monthly scheduled KPI cadence against reconciled definitions |
| Document Layer | Zoho WorkDrive with a formalised folder structure, naming convention, and role permission model |
| Accounting (Client Owned) | QuickBooks, outside the automation scope as the client's source of truth for accounting, invoicing, and payments; billing status surfaced into the CRM through custom fields and a QuickBooks to Zoho CRM sync |
The stack behind the build, with the PHI boundary holding clinical records inside Jane
Our team can share client references, scope your project, and answer any question about your delivery.
More engagements where our delivery teams shipped similar outcomes for clients across industries. Read on for context on the patterns we reused, the trade offs we navigated, and the metrics that landed in production.