A practical software framework for the solo RCIC running intake, drafting, filing, billing, and follow-up on every file.
A solo RCIC practice runs on a single license-holder doing every role on every file. The same person who runs the discovery call drafts the retainer, sends the intake form, chases the missing passport scan, writes the submission letter, files through the IRCC online portal, issues the invoice, books the follow-up, and answers the 10:42 p.m. WhatsApp from a client who just got a procedural fairness letter. There is no triage layer. There is no junior to delegate the IMM 5669 review to. There is, on most days, no admin. So the software question for a solo RCIC is not which platform a 14-seat firm has standardized on. It is which platform one license-holder can configure, support, afford, and still recover the per-hour cost of in reclaimed evening time. That framing changes which features matter and which ones are a tax.
This piece is for practitioners running their own shingle. It walks through the operational diagnosis, the selection criteria that actually filter useful tools from impressive ones, the three feature priorities that have the highest return for a single-seat practice, and the over-buying pattern that drains solo budgets without moving any file forward.
The economics of solo practice, in one paragraph
A solo RCIC carries roughly six job functions concurrently: marketing and intake, scoping and retainers, document collection, drafting and review, filing and IRCC correspondence, and billing and follow-up. None of those can be skipped. Some can be compressed. The compressible ones are exactly the ones software is supposed to handle: structured intake, document checklists, autofill of repeating client data into forms and the IRCC online portal, deadline tracking, e-sign and invoicing. The non-compressible ones are the substantive work — the legal analysis, the submission letter, the judgment calls. Software earns its seat when it gives back hours from the compressible bucket, not when it adds steps to the non-compressible one.
The procurement pattern most solos fall into is one of two extremes. On one side, the spreadsheet practice: Google Sheets for matter status, Gmail for client correspondence, a desktop folder per client, a paid PDF reader for IMM forms, and goodwill holding the rest together. On the other side, the firm-tier purchase: a horizontal CRM or a legacy immigration platform priced and configured for teams of eight to twenty, bought because it looked comprehensive on the demo. Neither is calibrated to a single-seat workload. The first leaks data and time. The second buries you in configuration debt and seat fees you do not need.
Selection criteria that filter useful from impressive
When a single person owns the configuration as well as the casework, the bar for what counts as a useful tool is higher and stricter than it is for a firm. A platform that requires a half-day kickoff with a customer success rep, a custom field mapping exercise, and a written internal SOP before it returns any value is not viable. Solo practice tolerates ten minutes of setup per feature, not three days.
Five criteria, in priority order:
1. Time to first useful workflow
From signup to a working intake form, sent to a real client, the gap should be under an hour. Anything longer means the practitioner will abandon mid-setup, default to email, and treat the platform as a stalled experiment. Test this on a free trial before paying. Configure intake, send it to your own personal email, fill it as if you were a client, and see whether the data lands somewhere usable. If you cannot get to a sent form in 60 minutes, the tool is wrong for solo use, regardless of how it scored on a feature comparison.
2. Single-pane-of-glass for the file
A solo practitioner needs every artifact for a single matter — the retainer, the IMM forms in progress, the supporting documents, the submission letter draft, the IRCC correspondence, the timeline of communications, the invoices and payment status — visible on one screen. Tab-hopping between a CRM, a separate document store, a separate forms tool, a separate billing system, and a separate e-sign provider is the most common reason solo practices revert to email. Consolidation is not a luxury feature for a single-seat practice. It is the feature.
3. Canadian privacy and data residency
Practitioners are bound by PIPEDA and by the confidentiality obligations in the CICC Code of Professional Ethics. A platform that hosts client data outside Canada, or that cannot answer where data is stored when a client asks, is not a defensible choice for an immigration practice. This is also a CICC complaint surface: a client whose application turns adverse can and does ask, in a complaint, where their data was stored and who had access. A clean answer is a small thing until you need it.
4. Pricing that survives a quiet quarter
Solo revenue is lumpy. A platform priced per seat is fine. A platform priced per matter, with a high per-matter floor, will quietly punish you in any quarter where intake slows. Annual contracts with steep early-termination clauses lock you into a tool you may need to replace by month four. Read the renewal terms before the demo, not after the trial. Month-to-month with the option to annualize once the workflow is genuinely working is the right shape for a single-seat practice.
5. Genuine support, not "knowledge base"
A solo RCIC has no internal IT. When the IRCC online portal session expires mid-submission and the platform's autofill stops responding, "submit a ticket" with a 48-hour SLA is not support — it is an outage. The right tools have either responsive chat support during business hours or an active practitioner community where the same questions surface and resolve quickly. Ask, on the demo, what the response time looks like when something breaks at 6 p.m. on a filing day. The answer separates serious vendors from ones that brochure well.
Three feature priorities for a single-seat practice
Across the dozens of features that case management platforms advertise, three carry disproportionate return for a solo practice. The rest is either useful at scale or not worth what it costs in attention.
Priority 1: Intake automation that produces structured data
Most solo RCICs collect client information through some combination of an initial call, a Word-document questionnaire emailed back and forth, and a follow-up email asking for the items the client missed. This is the single largest reclaim opportunity in the practice. A mobile-friendly client-facing intake form that captures the same fields you would otherwise type into IMM 0008, IMM 5669, IMM 5645, or IMM 5257 — and that lands in your case file as structured data, not a PDF attachment — collapses the front of the file from days to hours.
The non-obvious requirement is that the intake form output has to map to the form fields downstream. An intake tool that captures rich data into a vendor-proprietary format, but cannot then push that data into IMM PDFs or into the IRCC online portal, leaves the practitioner re-typing everything anyway. The intake-to-form pipeline is the value. The intake form on its own is a half-built bridge.
Two specifics worth checking on any intake tool: (a) does the form support conditional logic, so a client filling a spousal sponsorship intake does not see a question about a dependent child if they have answered "no children" earlier — long forms with no branching get abandoned around question 30; and (b) can the client save and resume from a phone, because most clients do their intake on the bus or on a lunch break, not at a desktop.
Priority 2: IMM PDF and IRCC online portal autofill
Manual data entry into IMM forms is one of the largest single time sinks in a Canadian immigration practice. The IMM 0008 alone has dozens of fields, many of them repeated across IMM 5645 and IMM 5669. The IRCC online portal compounds the problem: any mid-typing session interruption forces a reauthentication, which loses unsaved work in some flows. For a solo who is also handling the phone, the door, and the email, that is not theoretical — it is a Tuesday.
Autofill that takes the intake data and writes it into both the IMM PDFs and the IRCC online portal forms is the highest-leverage piece of automation a solo practice can buy. Two notes on doing it right. First, the autofill has to actually preserve formatting in the IMM PDFs — date formats, address line wrapping, signature block placement. A tool that fills 80% of the form and leaves the other 20% requiring manual cleanup is producing a different problem, not solving the original one. Second, the autofill has to update when IRCC revises forms, which they do regularly. A platform that was accurate in 2024 but has not pushed an autofill update against the current IMM 0008 revision is silently producing rejection-bait submissions. Confirm release cadence before committing.
Priority 3: E-sign and invoicing inside the file
A retainer that has to be exported as a PDF, uploaded to a separate e-sign tool, sent from a different email address, and then re-attached to the case file once it comes back signed — that workflow loses two clients a year, minimum. Not because clients refuse to sign. Because the friction extends decision time, and clients who are already nervous use the gap to reconsider. The same applies in reverse for invoicing: a separate invoicing tool that does not know whether the matter is open, paused, or closed is going to send reminders to clients you have already refunded, and miss reminders to clients who are quietly two months late.
For a solo, e-sign and invoicing both belong inside the case file, not adjacent to it. The retainer should be drafted, sent for signature, signed, and stored against the matter without ever being exported. Invoices should reference the matter, reflect retainer drawdowns automatically, and reconcile against trust accounting rules without manual ledger entries on a separate spreadsheet. This is the integration that makes month-end take 90 minutes instead of an afternoon.
The over-buying pattern
The cleanest way to lose money as a solo on software is to buy a platform configured for a 12-person firm. The features look impressive on the demo. The price-per-seat looks tolerable for one. The configuration debt is what kills you.
Common symptoms of an over-bought tool in a solo practice:
Custom roles and permissions you do not use, because you are the only user. Workflow automation that requires you to define triggers, conditions, and notifications for stages of a process that, in a solo practice, you are mentally tracking yourself anyway. Document templates that ship as stubs and require a multi-day initial population. Reporting dashboards that surface metrics designed for partner meetings — utilization, realization, write-off rates — that have no decision relevance to a single-license practice. Integrations with systems you do not run.
None of these are bad features in the abstract. In a solo context, they are configuration tax. Each one represents a setup obligation, a learning curve, and a re-configuration cost when something in IRCC policy or practice changes. Software that is right-sized for a single seat does the opposite: it makes opinionated defaults, hides advanced settings until you need them, and ships with templates that are usable as-is.
A useful diagnostic before signing anything: count how many of the platform's top-level menu items you would touch in a typical week. If the answer is more than five, you are probably over-buying. Solo practices live in three or four screens — the matter list, the open file, the intake inbox, and the billing tab. Everything else is either set-and-forget or scenery.
A note on the spreadsheet practice
Solos who run on Google Sheets and Gmail are not wrong to have started there. The spreadsheet practice has the right operating discipline at small volume: every artifact is somewhere you control, costs are near zero, and there is no vendor between you and the work. The failure mode is not the spreadsheet. It is what happens when matter count crosses the threshold where one person can no longer hold the full state of every file in working memory.
That threshold is usually somewhere between 12 and 20 active files, depending on complexity. Below it, spreadsheets are fine. Above it, the practitioner is dropping deadlines, missing follow-ups, and re-asking clients for documents already provided. The signal that the spreadsheet practice has expired is not "I want fancier tools." It is "I am chasing the same thing twice." When that signal arrives, the move is not to a comprehensive platform on day one. It is to the smallest tool that solves the immediate leak — usually a structured intake form first, then autofill, then e-sign and invoicing, in that order of pain.
A note on AI features in current platforms
Almost every case management vendor now ships some flavor of AI. Document review, draft letter generation, summarization of client uploads, suggested next-step prompts. For a solo, these are worth evaluating, but only after the foundational workflows are in place. AI document review on a practice that still types IMM 0008 fields manually is solving the wrong problem first. The order is: intake, autofill, e-sign and invoicing, then layered AI on top. Skipping straight to AI features on a foundation that still leaks data into Word and email produces no real time saving — it just adds another tab.
When AI features do start to matter, the test is whether they shorten the work or just decorate it. Document review that flags a missing IMM 5669 question 2 disclosure in 30 seconds, with a defensible audit trail, saves time. Draft letter generation that produces submission language a practitioner has to rewrite from scratch does not. Demo the AI on real, anonymized files from your practice, not on the vendor's polished sample data, before it shapes any purchase decision.
What this looks like in practice
A solo RCIC who has the three priorities right typically runs a week that goes something like this. New inquiry comes in by email or referral. Discovery call is booked from a calendar link. After the call, an intake form goes out — mobile-friendly, conditional on the matter type, saves and resumes. The intake comes back as structured data, not a PDF. The retainer is generated from a template, sent for e-sign inside the same platform, and signed by the client without leaving the file. The invoice for the initial retainer draw is issued from the matter automatically and paid online. IMM forms autofill from the intake. The IRCC online portal autofills from the same data. The submission letter and analysis still get written by the practitioner — that is the substantive work, and it stays human. Filing happens. The matter status updates without manual movement on a kanban. Follow-up reminders fire on the dates the file expects.
Nothing in that flow is exotic. None of it requires a 14-seat configuration. All of it is achievable by one license-holder with the right tools. The reason most solo practices do not run this way is not capability. It is that they bought either too little — spreadsheets and email — or too much — a firm-tier platform that demanded more configuration than a single seat can sustain.
Closing — and where VisaFlo fits
The case management decision is not a feature comparison. It is a fit decision. A solo RCIC needs software that respects the operating reality of a single seat: short setup, single pane of glass for the file, Canadian data residency, pricing that does not punish a quiet quarter, and real support when the IRCC portal is timing out at 5:55 p.m. on a Friday. The three feature priorities — intake automation that produces structured data, IMM PDF and IRCC online portal autofill, and e-sign and invoicing inside the file — return more reclaimed time than any other configuration choice in the first year. The over-buying trap is real and worth avoiding by reflex.
VisaFlo is built for exactly this shape of practice. Modern Canadian immigration software, AI-assisted, with the four pillars — CRM, intake, AI document review, and IMM PDF plus IRCC online portal autofill — designed to consolidate the file into one workspace rather than scatter it across five. Canadian privacy compliant, integrations with Google Drive, OneDrive, Gmail, Stripe, and QuickBooks, and built with solo and small-team practices in mind. If the workflow above sounds like the one you have been trying to assemble out of separate tools, it is worth a 30-minute look. Book a demo here and bring a real intake question to the call — that is the fastest way to see whether the fit is right for your practice.
