Which process runson one person’smemory?
We turn it into a logged, approved workflow — in an environment dedicated to your company, with a person approving every message that leaves it. Start with a short brief. Sašo Hauzer reads it and replies personally.
Two minutes. Sašo Hauzer, former sales director in satellite telecommunications, replies personally. No sales sequence follows.
Which of these sounds like you?
Pick the closest one. It opens the solution built for it, and the same sentence is a good start for your brief.
Something else, or more than one? Send a brief →
One page, four seats at the table.
An enterprise decision is made by several people asking different questions. Each of them should find their answer here in a few clicks.
What changes in the business?
Which processes we automate, how a pilot is scoped and how you decide whether to continue.
Solutions CTO · CIO · Head of DataHow does it fit our stack?
A dedicated database and execution environment, API-first integration, your sending domain.
Architecture Security · DPO · LegalWhere is the data, and who sees it?
Data isolation, a DPA signed before go-live, human approval of outbound messages.
AI Governance Procurement · FinanceHow is it bought?
A fixed-fee pilot quoted in writing, then an annual agreement. No surprise line items.
Procurement FAQThree rules we don’t bend.
They are why we can be trusted with customer-facing processes — and why our proposals are shorter than most.
Evidence, not estimates.
We do not quote projected ROI percentages. Every workflow writes a log of what it did — records found, messages drafted, approvals given — and that log is what we report against.
A person signs off.
Nothing reaches your customers or prospects without approval by a named person on your side or ours, as defined in the contract. The automation prepares; people decide.
Your data stays yours.
Enterprise clients run in their own environment — their own database and credentials — never in a shared pool with other companies.
We would rather show you a log of what the system did than a slide of what it might do.— How AI Vision reports
Organised by business problem, not by technology.
Each solution answers three questions: which problem it solves, how it runs safely, and what we measure. Open one for the detail. All of them are built from workflows already running in production, adapted to your systems and rules.
- Problem
- Sales teams spend their time on lists where nobody reachable makes the decision.
- Who it’s for
- B2B sales, partner and channel teams entering a new segment or region.
- How it works
- Companies are sourced from agreed sources, the owner or decision-maker is identified, emails are enriched and verified, and each record is scored for fit. Your team reviews the list before any outreach.
- What we measure
- Verified contacts per segment
- Share that reach a decision-maker
- Records accepted by your team
- Problem
- Generic campaigns burn the sender domain and the contact list.
- Who it’s for
- Teams launching an offer to a defined B2B segment.
- How it works
- Sequences are written per segment and language and reviewed by a native speaker. Every message waits in an approval queue, is sent from your domain, and replies are routed to the account owner.
- What we measure
- Reply rate
- Meetings booked
- Bounces and unsubscribes
- Problem
- Agents call without context, and missed inbound calls are lost.
- Who it’s for
- Inbound and outbound contact centres and sales desks.
- How it works
- Scripts and objection guides are prepared per segment. An AI receptionist handles first contact, a missed call triggers an SMS with a booking link, and call outcomes are logged against the record.
- What we measure
- Connect rate
- Missed calls recovered
- Meetings booked per agent hour
- Problem
- Signs that a customer is leaving sit in different systems until it is too late.
- Who it’s for
- Subscription businesses and account management teams.
- How it works
- New customers get a structured onboarding sequence. A health score is built from signals you agree on, and accounts at risk are flagged to their owner with context. Feedback and reviews are collected after key moments.
- What we measure
- Onboarding completion
- At-risk accounts flagged and contacted
- Churn in the flagged group
- Problem
- Quotes and invoices wait for someone to remember to follow up.
- Who it’s for
- Sales operations and finance teams.
- How it works
- An offer is drafted from each inquiry for review. Open quotes get timed reminders, overdue invoices get staged payment reminders, and every step is written back to the ERP.
- What we measure
- Time from inquiry to quote
- Quotes followed up
- Days sales outstanding
- Problem
- Leadership gets reports late, assembled by hand from several systems.
- Who it’s for
- Executives and process owners.
- How it works
- A daily and weekly brief is built from the workflow logs and connected systems and delivered by email or messaging. Items that need a decision are listed first.
- What we measure
- Briefs delivered on schedule
- Decisions closed per week
What changes between an inquiry and a paid invoice.
The same process before and after. The sequence below is illustrative and built from the Revenue operations workflows; it is not a client case.
| Step | Today | With AI Vision |
|---|---|---|
| Inquiry arrives | Sits in a shared inbox until someone picks it up. | Recorded in your CRM or ERP, with an offer drafted for review. |
| Quote goes out | When someone has time. | Released by a named person on your side, from your domain. |
| Quote stays open | Follow-up depends on memory. | Timed reminders are drafted for approval. |
| Invoice is overdue | Noticed at month-end. | Staged payment reminders; every step is written back to the ERP. |
| Leadership asks “where are we?” | A report assembled by hand from several systems. | A weekly brief from the workflow logs, decisions first. |
Real results are reported from the pilot logs against criteria agreed in writing before the pilot starts. We do not quote percentages in advance.
Three sectors, described in their terms.
We keep the list short on purpose. These are the sectors where our team has worked and where our workflows fit the way the business already runs. Sector experience is discussed in detail under NDA.
Subscriber growth and retention
For operators selling to households and to business accounts such as hospitality venues.
- Business-account prospecting by region
- Contact-centre scripts for B2B packages
- Campaigns around live events and seasons
- Early warning on accounts at risk of leaving
From inquiry to paid invoice
For distributors and wholesalers with large catalogues, resellers and repeat orders.
- Quote drafted from the inquiry
- Follow-up on open quotes
- Reseller and partner outreach
- Payment reminders and reorder suggestions
A pipeline that doesn’t depend on memory
For firms that sell expertise and live from meetings, proposals and renewals.
- Lead qualification and meeting booking
- Follow-up after presentations
- Structured client onboarding
- Weekly brief for the partners
A controlled path from question to production.
No instant promises. Each phase ends with a written decision point, and you only commit to the next one when the previous one has done what it said it would.
Brief
Two minutes of your time. Tell us the process, the size of the organisation and what you have tried. Sašo Hauzer replies personally — with questions, with a workshop proposal, or with a candid “not yet”.
- No call required to start
- Nothing is sent to anyone but us
Discover
A working session with your process owners and IT. We map processes, data, opportunities and risks, and agree how success will be measured.
- Process and data map
- Integration and security requirements
- Written pilot proposal
Build
Fixed scope, fixed fee, success criteria agreed in writing before we start. The pilot and its integrations run in your dedicated environment from day one.
- DPA signed before any data moves
- Integrations with your systems
- Approval flow with your named owners
- Pilot report from the workflow logs
Scale
An annual agreement covering operation, governance, maintenance and change requests, extended to further processes once the first one proves itself.
- Team training, by agreement
- Agreed maintenance windows and response times
- Quarterly review with leadership
Every commitment comes after the evidence.
One fixed fee, in writing
You know the full cost of the pilot before you commit to it.
Success criteria, in writing
Agreed before the pilot starts, with a baseline where one exists.
DPA before data
A data processing agreement is signed before any personal data is processed.
Named approvers
Nothing is sent externally until a named person on your side or ours releases it.
A report from the logs
The pilot report is built from the workflow logs, measured against those criteria.
Your decision
An annual agreement follows only if you choose it on that evidence.
We don’t publish a price list for enterprise work. The pilot is quoted as one fixed fee after the workshop, so you know the full cost before you commit. Production is an annual agreement sized to the processes in scope. Smaller companies looking for ready-made packages with public pricing can find them at aivizija.com.
Shared know-how. Separate everything else.
Workflows are versioned once and deployed to each client’s environment. Your data, credentials and sending reputation are never shared with another company.
Our workflow library
Your environment
Governance built into the workflow, not added after.
Your legal, security and data teams will ask how the system is controlled. Send us your security questionnaire before the workshop. We answer it in writing, and the answers become part of the agreement.
Data isolation
A dedicated database and execution environment for each enterprise client.
Access management
Separate credentials per client and environment. Who can access what is agreed in the contract.
Human in the loop
Outbound messages are released by named people. Nothing reaches a customer automatically.
Traceability
Every workflow run is logged with its inputs, outputs and approvals, and the log is open to your team.
DPA before go-live
A data processing agreement is signed before any personal data is processed.
GDPR
We operate from the EU under GDPR. Every sub-processor is listed in your DPA.
Hosted in Germany
Enterprise environments run at Hetzner’s Falkenstein data centre in Germany.
Local rules first
Before launch we check the rules for B2B contact in your market and have a native speaker review all copy.
Questionnaires, DPA requests and sub-processor lists: privacy@ai-vision.ai
Discretion is part of the service.
We publish a client’s name only with their written consent. Case studies — including the workflow logs behind them — are shared under NDA during the discovery workshop. Each one follows the same structure:
The people who run your project.
Enterprise buyers check who will actually do the work. Here is who you meet in the workshop.
AI Vision is the enterprise division of AI Vizija, a research and development institute in Domžale, Slovenia, that builds and operates AI automation for companies in Slovenia and the wider region.
Sašo Hauzer
Former sales director in satellite telecommunications. Leads every enterprise engagement from the first workshop.
LinkedIn profile ↗Your project team
The people who build and operate your workflows are named, with their roles, in the written pilot proposal.
Five doubts, answered plainly.
These are the objections we hear most. The answers are the same ones we put in writing in the pilot proposal.
“We already have a CRM and an ERP.”
Good, that is where the work starts. We connect over APIs and webhooks to your CRM, ERP, billing and contact-centre systems. The exact integrations are defined in the workshop and written into the pilot proposal.
“We won’t let AI write to our customers.”
It doesn’t, on its own. Every outbound message is released by a named person on your side or ours, goes out from your domain, and each approval is logged.
“We have no time and no spare IT capacity.”
The brief takes two minutes. The workshop needs one or two process owners and someone from IT or security. We build and operate the workflows in an environment dedicated to you.
“We can’t commit to a price we don’t know.”
You commit to nothing until the pilot is quoted as one fixed fee in writing, with success criteria agreed in advance. An annual agreement follows only if you choose it, on the evidence from the logs.
“How do we know it will work for us?”
We don’t promise percentages in advance. The pilot report is built from the workflow logs and measured against the criteria agreed in writing before the pilot starts.
Questions before the purchase order.
What happens when I send a brief?
What is AI Vision?
Who is AI Vision for?
How does an engagement with AI Vision start?
What should we bring to the workshop?
How is an engagement priced?
Where is our data stored, and who else is in the database?
Will anything be sent to our customers automatically?
Can you work with our existing systems?
Which languages and markets do you cover?
How do you measure results?
Can we see references?
Send one brief.
Name one process.
You get a personal reply from Sašo Hauzer — a proposal for a working session, or a clear reason not to automate it yet.
Sašo Hauzer reads your brief
Personally. It is not routed to a sales team.
You get a reply
Questions, a workshop proposal, or a candid “not yet”.
If it makes sense, a workshop
With your process owners and IT. It ends with a written pilot proposal.