Simple,
outcome-based pricing.

You'll have your first workflow live in 2–4 weeks. In week one we agree exactly what it will do. Then we build it, test it with realistic examples, apart from your day-to-day work, and show your team how it runs, with written documentation to keep.

No. Vertex handles the build and the integrations. We'll need a point of contact who knows the process and can grant access to the relevant systems.

Close, but not quite. A workflow covers a whole job from start to finish, such as taking on a new client: the form, the client record, the welcome email, the first invoice. An automation is software doing those steps for you. When we build you a workflow, we automate the whole job, not one step, and a person still signs off where it matters.

A workflow is one end-to-end automation, a trigger, the logic in between, and the actions it takes. We'll help you decide where one workflow ends and another begins during scoping.

Ongoing support keeps your automations current as your business changes, maintenance, adjustments, monitoring, and a dedicated point of contact. It's optional but recommended. Whether or not you take it, every workflow alerts you by email or text message if something goes wrong.

Yes. All pricing is in Canadian dollars plus applicable taxes.

Ignite is designed for exactly that: it automates two core processes to begin with. Start there, and if you want more later, step up to Elevate or Titan.

Every engagement follows the same path. Scope: we study how the job runs now and agree what to automate first. Connect: we link up the tools it needs. Automate: we build it and check it with realistic examples before launch. Monitor: every workflow is built to alert you by email or text message if something goes wrong; keeping watch, fixing problems and fine-tuning it for you is part of ongoing support. Scale: once that first workflow is doing its job, we build the next, if you want more. You see something working early, not after one long build.

Step one is our contact form. Our AI assistant will phone you about ten minutes after you send it, or when its calling hours begin again, to learn about your business and confirm we're a good fit. If you'd like to continue, we then settle with you on a time for your free 30-minute diagnostic consultation. You tell us how the work runs today and where the time goes; we tell you honestly where automation would help, what we'd tackle first, and roughly what it would take. Nothing is built until we've agreed what the first workflow will do and what you'll receive.

One point of contact who knows the process and can grant access to the relevant systems. We handle the build and the integrations. During scoping we'll need a little of their time to map how things actually work; after that, your involvement drops to reviewing and approving.

We map your real process end to end, the triggers, the rules, the handoffs, and the points where a person must stay in control. We find where time and value are leaking and agree on what to automate first based on impact. You leave with a clear picture of what's worth automating, whether or not you build with us.

Yes. They're yours whichever way we run them, and you get full written documentation for every one. Without ongoing support, the workflows are set up in your own accounts, on subscriptions you hold and pay for directly. With ongoing support, they live in our account instead, so we can keep watch, deal with failures and improve them over time. There's no long-term lock-in: if you cancel, we export your workflows and reconnect them in your own account with you, holding nothing back.

We connect through each tool's official, supported integrations, request only the access a given workflow actually needs (least privilege), and keep a human in the loop for sensitive steps. We work within your security boundaries and are glad to talk through your specific requirements before anything goes live.

Yes, that is where we start. We build around how your team works today, inside your current software. If a step only exists because two systems never talked to each other, we may suggest dropping it once the automation covers it. Where a step still changes from week to week, we agree a settled version with you first. Nothing changes without your agreement.

Workflows change, and the automation changes with them. Adjusting timing, rules, or steps as your business evolves is a normal part of ongoing support, not a new project. It's also why we recommend automating processes once they've settled into a stable shape.

No. We automate the repetitive busywork that follows set rules: data entry, sending each request to the person responsible, follow-ups, reports. The judgment, relationships and skilled work your team is there for remain theirs. The goal is to let the same team handle more without hiring, and to give the people you have their time back.

We build around the tools you already use, CRMs, email and marketing platforms, Google Workspace and Microsoft 365, finance and support tools, and more. The rule is simple: if it has an API, we can automate around it. We only recommend a new tool when it's genuinely worth it.

Every workflow is built to flag problems: you get an alert by email or text message, with or without ongoing support, so a fault doesn't slip by unnoticed. With ongoing support, we watch your automations as they run, catch the unusual cases and fix them. An automation nobody keeps an eye on is a risk, which is why we recommend ongoing support.

Yes. We start from your current software. Where work stalls because your tools don't talk to each other, connecting them is a big part of what we do. We only suggest a change when a tool is genuinely limiting you.