Common questions before you write
What does it cost?+
The first conversation is free. After that, each step comes with a written proposal and its price: the audit, then the pilot, then deployment and follow-up. You decide at every step.
How long before we see a result?+
A pilot covers a single use case, so you can judge in weeks rather than quarters. The exact duration depends on your tools and data; it’s written in the proposal, with the indicators we’ll measure.
Is this for our kind of business?+
Professional services, healthcare, construction, retail, manufacturing, distribution, solo operators: as soon as a process crosses several tools or several people, there’s something to work with. The first conversation exists precisely to check that before committing to anything.
Do we need to replace our software?+
Almost never. We start from your current tools, CRM, accounting, email, industry software, and we check what each one allows us to connect. If a tool is a blocker, we say so before the proposal.
Do you work outside New Brunswick?+
Yes, across Atlantic Canada, remotely, by video or phone. Moncton is where we’re based.
AI, with the right guardrails
Where does our data go, and who can access it?+
It depends on the tools chosen, decided with you before anything is connected. For every provider, we document where data is processed and what it states about its own access, page attached. What Over U sees during the project is set by contract. Being based in Canada doesn’t localize your data: each tool’s hosting is checked case by case.
Is our data used to train models?+
It depends on the provider and its contract, and terms change. We never put your data into a free or consumer plan. We check the clause at project time, also note how long the provider keeps its logs, and write it into the documentation we deliver.
Can we limit permissions and revoke access?+
Yes, it’s the starting rule: the narrowest access each tool allows, and we tell you when read-only doesn’t exist. Every access is dedicated, revocable by you, with a documented removal procedure.
What happens when the AI gets it wrong, or a tool goes down?+
It will sometimes, like a new employee. Sending and changing records go through human approval; no payment is ever delegated. Cases outside the rules stop and are escalated, a sample of the rest is reviewed regularly, everything is logged and a workflow can be suspended in one click. If a tool goes down, work continues by hand with the fallback procedure we deliver, and the workflow is adapted within the timeframe of your support agreement.
What happens to employees’ roles?+
The tasks change, not the people. Data entry, sorting and information lookup move to the automations; customer relationships, exceptions and decisions stay with the team, which is trained to supervise the tools. We don’t design projects whose goal is to replace a person with an agent.
How do we measure the value created, and can we leave?+
Indicators are set before the pilot: volume handled, turnaround, error rate, team time. They’re reviewed together afterwards. Your tools stay the reference, the automation accounts are in your name and the workflows are exportable: you can stop, or hand over to someone else.
