ASCEND AUTOMATION
For regulated B.C. businesses — finance & property · Plan A-2026

Every lead answered in 60 seconds. Every file chased to the finish. Every action on the record.

We build and run AI systems for B.C.'s mortgage brokerages, property managers, and financial firms — systems that do the chasing your office does by hand, with compliance checks and a tamper-evident audit log behind every action. Licensed humans stay in the seat.

No advice given by AI · Audit trail on every action · Built in B.C.

Sheet 01The gap

Fast and compliant are treated as a trade-off. That trade-off is the whole problem.

Speed

A web lead that waits hours has already called two competitors. The first useful, personal response usually wins the client — and the file.

Paperwork

Every file means chasing the same documents and re-keying the same data. It's the most expensive use of your most senior people.

Risk

Generic AI tools answer fast and log nothing. When a regulator or E&O insurer asks what the system said and why, "we're not sure" is not an answer.

We build the third option: machine speed with a paper trail a compliance examiner could follow line by line.

See how the audit trail works ↓
Sheet 02Record of work

In build for Monument Mortgages: the 60-Second Handshake.

One real engagement tells you more than a wall of logos. This is what's being built for a Vernon brokerage right now — and the standard every build is held to before it goes live.

Client
Monument Mortgages — Vernon, B.C.
Build
60-Second Handshake (lead response system)
Status
In build — pre-launch
Context

Monument Mortgages is a mortgage brokerage in Vernon, B.C. Like every brokerage, its web leads arrive around the clock — including the evenings and weekends when nobody is in the office to answer them.

What is being built

The 60-Second Handshake: a lead-response system designed to answer every web lead inside 60 seconds with a personalized, compliant reply and a booking link — not an autoresponder template.

How it works
  • Duplicate-proof intake. Every form event is checked for idempotency — no lead is dropped, none is answered twice.
  • Advice never leaves the machine. Replies contain no rates, no lending advice, no regulated judgments. Anything resembling advice routes to a licensed human.
  • Every action is logged. Each step is written to an append-only audit ledger that can't be silently edited after the fact.
  • No silent failures. If something can't be processed, a human hears about it. Nothing disappears.
Compliance posture

No personal information is written to system logs. The ledger records what the system did and when, in order, and the record belongs to Monument — available line by line if a regulator, insurer, or client ever asks. Nothing goes live until Monument's compliance sign-off and the required third-party security review are complete.

Next on the file

The Funded File Engine — document chasing and FINTRAC checks from application through funding — is on the board for Monument after the Handshake launches.

Sheet 03What we build

Three systems. Each one replaces a job your office does by hand.

Build 01

The 60-Second Handshake

Web leads get a validated, personalized, compliant response and a booking link inside 60 seconds — around the clock, including the 9 p.m. Sunday inquiry that currently waits until Monday.

Replaces Manual lead triage, morning inbox catch-up, and the leads that quietly go cold overnight.
Build 02

The File Engine

From application to close: documents requested, received, checked, and filed — against the rules that apply to you, FINTRAC for brokerages, tenancy requirements for property managers — with your team approving at defined checkpoints.

Replaces Document chasing by email, manual completeness checks, and status updates typed out one client at a time.
Ongoing

The Managed Service

We run what we build — monitoring, upkeep, and improvements, with a readable audit trail handed to you so the system's record is always yours.

Replaces The "who maintains this?" problem that kills most automation projects within a year.
Sheet 04Method of engagement

From first call to filed system: four steps, each with a gate you control.

Step 01

Fit call

Thirty minutes, direct with the founder. We map how leads and files actually move through your office and find the highest-leverage build. If we're not the fit, we say so on the call.

You approve: whether this goes anywhere · 30 minutes
Step 02

Scoped build

One tightly scoped system. Scope, success criteria, and human approval points are defined together before a line of code is written. Your compliance sign-off is a gate to launch, not an afterthought.

You approve: scope, success criteria, compliance sign-off · weeks, not quarters
Step 03

Live in production

Deployed and proven on real leads before it expands. Human approval points sit wherever the stakes require a name attached — agreed in scoping, enforced by the system.

You approve: defined checkpoints inside the running system
Step 04

Managed service

We run what we build: monitoring, upkeep, improvements. The audit trail is handed to you on request — the system's record is always yours.

Ongoing · the record stays yours
Sheet 05Why compliance-native

Compliance isn't a feature we added. It's the foundation everything is built on.

Every system starts from four commitments:

K-1The advice firewall

The AI never gives financial, lending, or legal advice, quotes rates, or makes regulated judgments. Anything resembling advice routes to a licensed human. The system handles logistics; your people handle judgment.

K-2The audit ledger

Every action is written to an append-only, tamper-evident log. If a regulator, insurer, or client ever asks what happened on a file, you can show them — line by line, in order.

K-3Canadian infrastructure

Client data is a Canadian problem, so infrastructure is pinned to Canadian regions. Data residency is a hard constraint of the design — not a checkbox at the end.

K-4Human gates

Deterministic checks decide what's routine; defined approval points put a human in the loop wherever stakes require one. Nothing important happens without a name attached to it.

The audit ledger — what it actually looks like Representative entries · illustration only
SeqTime (PT)EventDetailPrev hash
041121:03:47LEAD.RECEIVEDweb form · source: website8c41f2…
041221:03:47INTAKE.DEDUPEpass — first occurrence of this inquirya90d17…
041321:03:49CHECK.ADVICE-RISKnone — reply contains no rates, no advice3fe8c4…
041421:04:31REPLY.SENT44 s — personalized + booking link · SLA 60 s: metd27b90…
041521:04:31NOTIFY.BROKERqueued for morning review6b03ae…
041621:11:02ESCALATE.HUMANfollow-up asked about rates — AI reply withheld, routed to licensed brokerf4519d…
041708:12:05HUMAN.REVIEWbroker approved — name attached to the file21c7e8…
Append-only · each entry carries the hash of the one before it, so any edit breaks the chain visibly · no personal client information is ever written to the log
Sheet 06Questions

Straight answers to what regulated buyers actually ask.

The objections we hear from brokers, property managers, and their compliance officers — answered plainly. Anything not covered here is a thirty-minute call away.

Is this compliant with my regulator?

We design to the strictest reading of the rules that apply to you — FINTRAC obligations, provincial licensing requirements, your E&O carrier's expectations — and your compliance officer's sign-off is a gate in our build process, not an afterthought. We don't ask anyone to take our word for it: every build ships with the audit trail to show its work.

What's the liability and E&O posture?

The system is built so the exposure your E&O carrier actually worries about can't occur: the AI never gives advice, quotes rates, or makes regulated judgments — those route to a licensed human, every time. And because every action is written to a tamper-evident ledger you own, there is never a question of what the system said or did. Your carrier's expectations are part of the design brief from day one.

Where does client data live?

In Canadian regions. Data residency is a hard constraint of the design, not a checkbox at the end — infrastructure is pinned to Canada, and personal information is never written to system logs or debug output.

What happens when the AI hits something it can't handle?

It stops. Deterministic checks decide what counts as routine; anything unusual, ambiguous, or advice-adjacent is withheld and routed to a named human. Nothing fails silently — if something can't be processed, a person hears about it.

Exactly where do humans approve?

At checkpoints we define together during scoping — before launch, not after. The principle is simple: nothing important happens without a name attached to it. The checkpoints are enforced by the system itself, and every approval is a line in the ledger.

What does the audit trail contain, and who owns it?

Every action the system takes — timestamped, in order, append-only, with each entry chained to the one before it so tampering is visible. It contains no personal client information. It's yours: handed to you on request during the engagement, and it stays with you if the engagement ends.

What happens if we part ways?

You keep the audit trail and the records, and the system is documented well enough that you aren't stranded. There's no long lock-in — we'd rather earn the next build than trap you in a contract that isn't working.

We already have a CRM. Does this replace it?

No — it plugs into it. Your CRM stays the system of record; our systems do the work around it: responding, chasing, checking, and logging.

How fast is a build live?

The first build is typically live within weeks, not quarters — scoped tightly, deployed to production, and proven on real leads before we expand it.

What does it cost?

It depends entirely on what we build, so we don't publish a rate card. Book the fit call: you'll leave with a clear scope, and you'll have exact figures in writing before anything is signed.

Sheet 07Prepared by

One person builds, signs, and runs every system.

Rob Blackwood Founder · Ascend Automation
Vernon, B.C.
Plan A-2026

Ascend is one person on purpose. I design, build, and operate every system myself — the person on your fit call is the same one running your system in production. I work in regulated verticals because I think compliance is load-bearing, not paperwork: if a system can't show its work, it shouldn't be doing the work.

Signed — R. Blackwood
Sheet 08Next step

Thirty minutes. We map your highest-leverage build — and tell you honestly if we're not the fit.

Bring how leads and files move through your office today. You'll leave with a clear picture of what's worth automating first, what it would take, and what the audit trail looks like — whether or not you hire us.

One conversation · No obligation · Direct with the founder