We reproduce one of your real quotes
Send a quote you have already priced. We configure it in the CPQ engine live and you compare the two line by line. This is the fastest honest test of whether the parametric model fits your catalogue.
Talk to engineering
Book a working session, not a demo
3 short steps. Everything you tell us is used to configure the environment before we speak, so the 45-minute session is spent on your catalogue and your dispatch board rather than on a product tour.
- SOC 2 Type II aligned
- PIPEDA compliant
- AWS ca-central-1 tenant isolation
- SAML 2.0 single sign-on
Response within 2 business hours · 07:00 – 19:00 ET · a solutions engineer, not a sequence
Where we work
The platform is delivered as enterprise cloud software from Canadian infrastructure. Implementation, configuration, and support run remotely, with on-site API onboarding scheduled per engagement for trade operators across North America. Postal mail goes to the registered address on your order form.
- Coverage
- Greater Toronto Area · Golden Horseshoe Region · Southwestern Ontario Industrial Corridor · Eastern Ontario & Ottawa Valley Corridor · Central & Northern Ontario Distribution Nodes.
- These are territories served, not locations we occupy. Delivery is remote-first — implementation, configuration, and support run over video and the API — with on-site attendance arranged per engagement. Deployment, implementation, and support run remotely across Canada, so coverage is not the limit of who we can onboard.
- Support hours
- Monday–Friday, 07:00–19:00 ET. P0 incidents are covered 24/7.
- Reception
- (416) 555-0142
Skip the form
If you already know who you need, write to them directly. These go to people, not to a shared triage queue.
- sales@novelsystems.caNew business, pricing, and procurement paperwork.
- security@novelsystems.caSecurity questionnaires, penetration-test summaries, disclosure.
- support@novelsystems.caExisting customers. Do not send incidents here — use the in-app P0 path.
- (416) 555-0142Reception, Monday to Friday during Eastern business hours.
The session
Three things happen, and none of them is a slide
A demo where the data is ours proves nothing. Bring yours and the answer is either obvious or the fit is wrong, which is equally worth knowing in 45 minutes.
01 02 We dispatch one of your real days
A morning's worth of jobs, your actual technicians, your actual service windows. The optimiser runs against them and you see the route it produces beside the one you ran.
03 We map the integration seam
Whatever is already in place — QuickBooks, Sage, NetSuite, a spreadsheet — we walk the record boundary and say plainly which side owns what after go-live.
Enterprise support
What you get when something breaks
First-response targets are contractual and measured from the moment a ticket is raised, not from the moment somebody reads it. P0 means the platform is unusable for a production crew, or is actively producing wrong numbers.
Growth Trade
- P0 first response
- Next business day
- P1 first response
- 2 business days
- Coverage
- Mon–Fri, 07:00–19:00 ET
- Channels
- Email · in-app
Enterprise Commercial
- P0 first response
- 4 hours, business hours
- P1 first response
- 8 business hours
- Coverage
- Business hours, with phone escalation
- Channels
- Email · in-app · phone
Custom / Multi-Branch
Named contact- P0 first response
- 15 minutes, 24/7
- P1 first response
- 1 hour, 24/7
- Coverage
- 24/7/365 with a named on-call rotation
- Channels
- Email · in-app · phone · shared Slack channel
Availability targets, service credits, and the escalation path behind these tiers are published on the security page.