The method
How we work
Four stages, from the first conversation to the delivery you accept: we listen, agree the perimeter in writing and build with controls.
Let's talk about your workFour stages
Let's talk
We start with a conversation about your company and your work, at no cost: up to three meetings. We do not open with the service list: we listen, and the next step may be to do nothing. Reviewing your material is already paid work, and we say so beforehand.
- What happens
- You tell us about your work, where it jams and what it costs you.
- What you decide
- Whether you want a next step, and which.
- What happens
- You tell us about your work, where it jams and what it costs you.
- What you decide
- Whether you want a next step, and which.
Where to find us
Who takes part
- You, or whoever runs the area
- A Qvasar partner
What we understood of your work and the next step, or a proposal.
Diagnosis and proposal
If there is work to do, the written proposal sets the perimeter: the work, the output, who reviews it, the connected systems, which data is touched and with which permissions, and the acceptance sample. Before any real data leaves your systems, the confidentiality agreement and the data processing agreement are signed.
- What happens
- We look at how your company works, area by area, and prepare the proposal.
- What you decide
- Whether you accept it or change it, and which data and tools go in.
- What happens
- We look at how your company works, area by area, and prepare the proposal.
- What you decide
- Whether you accept it or change it, and which data and tools go in.
Your systems
- Gmail
- Outlook
- Google Drive
- HubSpot
Who takes part
- You
- Whoever manages your tools
- Both partners: one drafts, the other reviews
Perimeter, data and permissions, acceptance sample and the cost of licences, hosting and consumption.
Build with controls
We record the starting point of the process and agree with your reviewer the sample, the rules and the expected results.
- What happens
- We build and test on your task, in a test environment.
- What you decide
- What is delegated, what is sensitive and where your approval is needed.
- What happens
- We build and test on your task, in a test environment.
- What you decide
- What is delegated, what is sensitive and where your approval is needed.
Agreed controls
- Minimum permissions
- Approval of sensitive actions
- Activity log
- Test cases
- Failure threshold
Who takes part
- Your reviewer
- The Qvasar team
Built with the agreed controls and tested on your sample, before delivery.
Delivery, acceptance and review
We deliver when the system passes the agreed sample. There is no universal accuracy percentage: the criterion is the one agreed for that sample. The warranty terms are on Pricing. Then, within the agreed measurement window, we compare the result with the recorded starting point.
- What happens
- You accept the delivery on the agreed sample.
- What you decide
- Whether you accept it, and how maintenance goes on.
- What happens
- You accept the delivery on the agreed sample.
- What you decide
- Whether you accept it, and how maintenance goes on.
Who takes part
- Your reviewer
- Your process owner
- A Qvasar partner
With usage instructions, the handover to your process owner and a warranty from acceptance.
Security and privacy, agreed in writing
Before touching any real data, we put in writing where the data lives, who can reach it and what gets logged. You review and accept it before we build anything.
Your data
Where it lives
In your systems. Until the confidentiality and data processing agreements are signed, we work with anonymised samples.
Who reaches it
The people and agents the perimeter provides for, with read-only access limited to what is needed.
What does not leave
No real data before the agreements are signed, and nothing outside the written perimeter.
Access and permissions
Per person
You grant each access, and you can withdraw it.
Per agent
Each agent has its own permissions and a written perimeter of actions, and does nothing else.
Only what is needed
For each person and each agent, we propose the minimum the work needs.
Traceability
Log
A record of what the system does, so it can be reviewed whenever needed.
Approvals
Before sending, deleting, buying or changing permissions, the system leaves it ready and a person approves it.
If it fails, a person takes over
When a case does not fit or goes past the agreed failure threshold, the system passes it to a person on your team.
Outside the system
Your professional decisions stay outside the system.
What we do not do
We do not review your material in the free meetings; if needed, we tell you beforehand.
WhyThe free meetings are for listening to you; reviewing your material is already paid work.
We do not promise that AI never errs or works alone: a person reviews the sensitive steps.
WhyAccuracy is measured on the agreed sample and against an agreed failure threshold, not with a promise.
We do not give dates without a confirmed owner, reviewer and availability.
WhyDelivery depends on the sample we agree with your reviewer: without a confirmed reviewer, a date would only be a promise.
We do not sell with urgency or fear, not in the follow-up either.
WhyAt every stage you decide whether there is a next step, and when.