For independent insurance brokerages in Alberta
We run the admin around your broker management system.
OutlookExcelWordCalendarTeamsWhat we do
We build and run the admin systems around your BMS, so the work that arrives as email and PDF stops landing on your staff.
The week you actually have
Today
A request hits the shared mailbox. Someone opens the file, checks the policy, types the holder and the additional insured, and sends it back. Then the next one.
With Ardell
The request is read, the holder and the description of operations are pulled and checked against the file, and a complete certificate waits in the approval queue. A Level 2 approves it and it goes. Issuance stays in your BMS.
Today
The expiry report gets exported. Someone works down it, loss runs get requested when there is time, and the file that needed remarketing three months out gets opened with three weeks left.
With Ardell
The clock runs itself. Loss run requests go out on schedule and get chased until they arrive. Replies come back sorted, summarised, and filed against the account. Anything that needs a broker's judgment lands in a short queue.
Today
The same details typed into an email, a PDF, a portal, and the BMS. Four times, by hand, four chances to transpose a policy number.
With Ardell
Captured once, handed back as a ready-to-key pack in the order your screens ask for it. We do not drive your carrier portals. We remove the typing that happens before them.
Who builds this
Jordan Ardeleanu Founder, Alberta I am Jordan Ardeleanu. I build these systems and I run them, in Alberta.
That is the whole company. The person who designs your system is the person your staff call when something looks wrong, and the person who answers your E&O carrier's questions. There is no account manager in between.
What we build
Each system is a piece of your admin week, built once and then run for you. Most brokerages start with certificates and add the next one when the first has gone quiet.
System 01
Certificate requests and renewal follow-up, handled from the shared mailbox your team already uses.
Issuance stays in your BMS with a Level 2. We prepare the work. We never issue.
From $900/month, plus a $4,500 build. Twelve-month initial term.
System 02
Commercial submissions, prepared before anyone touches a portal.
From $900/month, plus a $4,500 build. Twelve-month initial term.
Next
Routine client email drafted, sorted, and queued for approval, so the inbox stops being a queue of small decisions.
Available to existing clients
Next
One weekly view of what moved: certificates out, renewals closed, submissions outstanding, exceptions caught.
Available to existing clients
Works alongside your broker management system. Applied Epic, Power Broker, SIG, Acturis, Brokercore, and yes, TAM. There is no integration project, no migration, and no new login for your team: the systems run from a shared mailbox and hand work back in the format your BMS accepts. If you are moving from TAM to Epic, this keeps working before, during, and after.
Systems stack, and the second one costs less than the first. The governance layer, the approval queue, the audit logging, and the monitoring are built once and shared. You pay for the new work, not for the foundation again.
| One system | $900/month |
|---|---|
| Two systems | $1,600/month |
| Three systems | $2,200/month |
Build fee is $4,500 for the first system and $2,000 for each one added after it.
Every system includes a monthly report built from the system's own numbers, not from memory. Microsoft cloud costs are billed in your own tenancy at cost, with nothing added by us. Typically $150 to $400 per month depending on volume.
Why this is different
Most automation work in this industry runs on consumer tools wired together with an API key. For an unregulated business that is a reasonable trade. For a brokerage holding client policy data under Alberta's PIPA, with an E&O carrier and the Alberta Insurance Council to answer to, it is not.
The system prepares the work. A Level 2 decides what goes out.
Every system runs in your own Microsoft cloud subscription. You own the resources, the data, and the configuration. If we part ways it keeps running, and it stays yours.
Client data sits at rest in Microsoft's Canadian Azure regions. Where processing also has to stay in Canada, we deploy the models regionally in Canada East. Your agreement names the deployment your system runs on.
Each thing the system does is written to storage you own, with the input it saw and the output it produced. When someone asks what happened on a file, you can pull it.
The review queue is how the system is built, not a setting we switched on. Nothing client-facing leaves without a Level 2 approving it.
We build to the obligations you already carry: Alberta's Personal Information Protection Act and PIPEDA, and the privacy commissioners' published principles for generative AI. We will sign a written agreement covering privacy obligations and breach notification, and we keep to the boundary the Alberta Insurance Council draws around licensed activity: the system does administrative preparation, and a licensed person does everything else. Read the full trust page →
How it works
The same shape every engagement. Different content each time.
We built this for brokerages and the site talks like it. Law firms, mortgage brokers, accounting practices, and property managers run on the same shape: regulated paperwork, files that have to be right, deadlines that do not move. Email us and we will tell you whether it fits.
hello@ardellsystems.comQuestions
You probably should use it. BMS-native AI is good at the things inside the BMS. What we build is the work that happens around it: the shared mailbox, the requests that arrive as email and PDF, the follow-up nobody owns, and the re-keying between systems. We also do not sell you seats. We run a system for you and report on what it did.
Most of them are software you log into, priced per seat, and built for brokerages much larger than yours. This is a managed system that runs on infrastructure you own, built for the way a small independent office actually works. If you are large enough that the big platforms are courting you, buy those instead. We will tell you if that is the case.
No. There is no integration project and no migration. The systems run from a shared mailbox and hand work back in a form your BMS accepts, which is why it works with Epic, Power Broker, SIG, Acturis, Brokercore, and TAM without us touching any of them.
Client data is stored at rest in Microsoft's Canadian Azure regions, in your own subscription. Processing is a separate question and we answer it separately: where a client requires processing to stay in Canada, we deploy the models regionally in Canada; otherwise processing runs on Microsoft's global infrastructure with the data still stored in Canada. We put whichever applies in writing. Details are on our trust page.
Access is controlled by identity and role, and it is logged. We hold only the access needed to run and support the system, and you can revoke it, because the tenancy is yours.
Read, sort, extract, draft, and prepare. Nothing else. It does not solicit, advise, quote, bind, or issue, and nothing reaches your client without a Level 2 approving it. That boundary is written into the contract, not just the software.
Usually four things: what the system can do on its own, who approves client-facing work, where the data lives, and whether there is a record. We keep a due-diligence pack with the architecture, the controls, our insurance certificate, and answers to the standard security questions. Ask for it and we will send it under NDA. The short version is on our trust page.
The infrastructure is in your subscription and stays there. We hand over documentation and credentials, help you export, and the system keeps running. What stops is us maintaining it, and unmaintained systems break when the underlying AI models are retired, which happens on published schedules every year or two. Better to know that going in.
A build fee to design and ship the system, then a monthly fee to run it. The Certificate & Renewal Desk starts at $4,500 to build and $900 a month to run, on a twelve-month initial term. A second system is $700 a month on top rather than another $900, because the governance layer is already built. Microsoft cloud costs are billed in your own tenancy at cost with nothing added by us, typically $150 to $400 a month. The scoping call is free and you get the map whether or not you hire us.
Two to four weeks from signed scope to running in parallel with your current process.
A fair question, and the honest answer is in the contract: you own the infrastructure, you get the documentation, and the export procedure is written down before we start rather than after something goes wrong.
Talk to us
A scoping call is 30 minutes. We look at where the admin actually goes, and you get a one-page map of what we would build first and what it would cost. You keep the map either way.