Axiom International
contact@axiominternational.ca

Kitchener–Waterloo, Ontario, Canada

Axiom Revenue Engine. Qualified first. Controlled always.

Proprietary software engineered by Axiom International to qualify leads on evidence and keep every send under control.

Case studyRead on Or experience it as a 3D story

About Axiom Revenue Engine

Axiom Revenue Engine

Qualified first. Controlled always. Axiom Revenue Engine is the private system we built to find the right businesses and keep every send under control. It is not for sale. It shows how we engineer software that acts on a business’s behalf.

At a glance

Kind
Proprietary internal software. Not a public product.
Built by
Axiom International, led by Riley Hinsperger with Aidan Magee
Built for
Axiom Web’s lead generation
Status
Live internally behind sign-in. Follow-ups are paused and sending is operator-controlled.
Built with
TypeScript, Next.js and Cloudflare Workers with D1
Tested by
35 test files covering scoring, qualification, contact validation, automation policy, de-duplication and the CRM

The challenge

Contacting more businesses was easy. Contacting the right ones safely was not.

Finding local businesses worth contacting means gathering listings, studying websites, finding the right person, writing, sending, tracking replies and moving the good ones forward. Done by hand it does not scale. Automated carelessly, it is dangerous.

Scattered

No single place showed which businesses had a real problem, whether there was a verified route to the right person, and what had already been sent.

Unqualified

Volume is not qualification. Leads without evidence waste effort, and messages that claim more than the evidence shows damage trust.

Uncontrolled

Software that sends email in your name needs limits, switches and a way to stop, or one mistake reaches many inboxes.

The solution

One private operations app, from lead to reply.

Axiom Revenue Engine handles intake, enrichment, qualification, first-touch outreach to qualified recipients, reply tracking and a pipeline view, behind sign-in and with controls on every stage.

Lead intake

Leads arrive through scraping and manual entry, de-duplicated, and kept in one vault that can be filtered and exported.

Enrichment

Cloud browser rendering reads a business’s site for facts and contact routes. Local development can fall back to a local browser.

Qualification

Scores fit and need, and applies hard gates for chains, very large businesses and unusable addresses before anything is queued.

Outreach and replies

First-touch email to qualified recipients through connected mailboxes, with replies tracked back to the original thread.

CRM pipeline

A board that moves replies and deals through stages, so a conversation does not disappear after the first message.

Safety controls

Separate switches for intake, queueing and sending, a global pause, an emergency stop, a daily cap, and follow-ups capped at zero until deliberately re-enabled.

Engineering

Where the engineering is.

A selection of what we built and chose carefully. Each rule below is enforced in the code, not left to convention.

01

Qualify on evidence, then on reach.

A business has to matter before it is contacted. The engine checks fit and website need first, and only then whether there is a trusted route to the right person. A missing email changes the channel; it does not hide a good business.

AlsoHard gates, such as chains, very large businesses and generic or malformed addresses, sit apart from the score.

02

Confidence thresholds before any send.

An owner’s email needs at least 50 per cent confidence and a staff member’s 65 per cent. Generic, role-based, scraper-artifact and malformed addresses are blocked outright.

AlsoThe dashboard shows projected send times from mailbox cooldown and capacity, not stale scheduled dates.

03

Controls before capability.

Intake, queueing and sending are separate switches, each off unless enabled. There is a global pause, an emergency stop and a daily cap, and follow-up sends are paused and capped at zero in configuration.

AlsoTests and local checks must never send mail or touch an inbox.

04

Releases are guarded as well.

Production deploys and remote migrations are blocked until the app has an isolated target and a verified backup and rollback path. The deploy command exits before touching the platform, and dry-run checks stand in.

AlsoAn outside watchdog checks the live app every 30 minutes and opens an issue if it goes down, then closes it when the app recovers.

05

Private by default.

Sign-in is limited to named accounts, and export, settings and automation controls are admin-only. Secrets live in platform secrets, never in the repository.

AlsoA command palette, keyboard search and a restrained interface keep dense, repeated work fast.

How it is built

Interface
Next.js 16 and React 19
Edge
Cloudflare Workers through OpenNext
Storage
Cloudflare D1, with SQL migrations
Sign-in
Better Auth with an allowlist of named accounts
Integrations
Gmail OAuth for sending, Cloudflare Browser Rendering for reading sites, and a language model for assessment and drafting

Where it stops

Follow-ups are off

Only first-touch email is enabled. Follow-ups stay paused until they are deliberately switched back on.

Production release is gated

Remote migrations and production deploys are blocked until an isolated target and a verified rollback path exist.

Targets are not results

The rebuild blueprint sets reply and bounce targets as goals. We make no claim about reply rates here.

For your business

The same engineering, pointed at your problem.

Axiom Revenue Engine is ours, so every decision in it was ours to make. These are the problems the same thinking applies to.

Your leads outrun the people checking them.

We build the qualification layer: evidence first, hard gates apart from the score, and a reason attached to every decision.

Automation that sends needs a hand on the brake.

Separate switches, daily caps, an emergency stop, and tests that can never send.

Releasing changes to a live system is risky.

Deploys and migrations gated behind isolation, backup and rollback, with an outside watchdog watching the result.

Off-the-shelf software almost fits.

Where a standard product does the job, we will say so. Where your own process is the advantage, we build software around it.

Custom software

Tell us how your business runs, and where the software you have stops.

Kitchener–Waterloo, Ontario, Canada

All work

All contact details