The pilot: 10 to 15 companies.
Before opening Shara to the public, we want to watch it work at companies other than our own, with you alongside and the freedom to tell us what is wrong.
No promised date: we call in order of request.
What you get and what we ask.
What you get
- The complete product. The director and all the department agents, the web app and the desktop app, the connectors and the panel. Nothing held back.
- Setup, with us in the room. We connect your tools together, write the agents’ identity with you and go through the first assignments.
- What you ask for jumps the queue. What you ask for goes to the front of the queue: we fix it first and, if it makes sense for the product, we build it. That is what the seat buys.
- Terms agreed case by case. We settle them with you before starting, and they go in writing. No lock-in.
What we ask of you
- Half an hour a week. Someone at your company who tells us what worked and what did not. It is the part we actually need.
- Real work. Tasks you do by hand today: proposals, recurring reports, client follow-up, document review.
- Your tools connected. Mail, calendar, chat, CRM, document storage. The more of your day is connected, the better the pilot goes.
- Tell us when it fails. It is new software: things will break, and things will change because you said so.
Ask for a seat: tell us what you would do with it.
Two lines are enough for us to tell whether it fits. A person reads it, and we answer even when the answer is no.
Or write to us directly at support@aiginer.com
How you get in
- 01
A half-hour call
You tell us what you do and what repeats. We leave with a yes or a no, and with the reason.
- 02
Setup
Your company is created in Shara, your tools are connected and the identity of the agents you will use gets written.
- 03
Real use, accompanied
You work with it. We watch what comes out, fix what breaks and ask you every week.
- 04
You decide
If it works, you move to a plan. If it does not, we switch it off and you take your data: you export a .zip with one NDJSON file per table from Settings (CSV, we prepare for you). No argument.
Data is processed inside the European Union. If that is not enough, Concerto Local runs on your own machine, and its cloud allowance is switched off from the admin console.
When it does not fit.
If the call shows it does not fit, we say so right there. Better that than a pilot nobody touches.
- If you want something settled and predictable. This is a pilot. Things will break, and things will change because you said so. If you need a product that sits still, wait for launch.
- If the use case is one narrow process. A single automatable process is cheaper as a bespoke automation. We will say so, and build you that instead if you want.
- If nobody on your side will look at it. A pilot without a counterpart turns into a dormant licence. We would rather give it to someone who uses it.
What we will not promise you.
None of this makes us look good, which is why it is here and not in a footnote of the contract.
- A date. There is no start or launch calendar. We call in order of request, and we tell you when your turn comes.
- A service level agreement. During the pilot there is no SLA and no written uptime commitment. Support is us, by email, in European working hours.
- Certifications. We are not ISO 27001 or SOC 2 certified. What does exist (encryption, per-company isolation, audit log) is written out and dated in Security.
- That it will go well. This is new software working on your operation. Things will break. What we do promise is that what you ask for goes to the front of the queue.
The ones we always get
What does it cost?
Terms are agreed case by case before starting and put in writing. There is no lock-in and no penalty for leaving.
Who sees what we do with Shara?
Each company's data is isolated from every other. Only two people on the AIGiner team have technical access, and only for support, incidents or a legal obligation.
Where is the data processed?
The product database and the models are in the EU. Transactional email, Cloudflare and payments are outside it, under standard contractual clauses; the subprocessor list is published and dated. If nothing may leave your network, Concerto Local runs on your own machine and its cloud allowance can be switched off: with the switch off, nothing leaves.
Do we have to install anything?
The web app runs in the browser. The desktop app, on Windows, macOS or Linux, is optional. Connectors are authorised from the browser, with each tool's minimum permissions.
Can it act without me knowing?
Anything with consequences (sending, publishing, paying, signing) is proposed and waits for your approval. There are also spend limits that stop the run, not warn about it.
And if we stop?
It gets switched off and you take everything: you export a .zip with one NDJSON file per table from Settings (CSV, we prepare for you). No retention call, no paperwork.