Getting started
What Gini is
An AI coworker with its own machine, its own context on your company, and the ability to finish work rather than describe it.
Most AI in a chat window hands you instructions and leaves the work exactly where it was. You still open the dashboard. You still write the report. Gini takes the job instead, and what lands in the channel is the finished thing.
You@Gini our ad spend looks off this month, can you look?
Gini
Paused Retargeting-broad: it took 38% of spend at 3× your blended CAC. Budget moved to the two campaigns clearing target. That's about $1,240 a month back.
I waited for your OK before changing anything. Here's the breakdown by campaign.
The difference is not the quality of the answer. It's that there is an artifact at the end.
Three things that make that possible
It has its own machine
Gini doesn't run inside a browser tab or on someone's laptop. Each job gets a sandboxed machine in the cloud with the tools your team connected, and that machine is torn down when the job finishes. That's why it can spend twenty minutes on something, work across six tools in one job, and keep going after you close Slack.
It has context on your company
Gini reads the channels you invite it to, and it builds a picture of how your company actually works: who owns what, which decisions got made, what your team calls things. A question like "why did we drop the enterprise tier?" gets a sourced answer with the thread and the person who decided, because it was in the room.
That context lives in the company wiki, which Gini keeps current as decisions change.
It works where your team already is
Slack is the interface. Nobody installs anything, learns a new tool, or changes where they work. You @mention Gini the way you'd @mention a colleague.
Microsoft Teams
These pages are written for Slack, which is where most teams run Gini. Gini for Teams works the same way. See Gini for Teams, or book a demo.
What it is not
It is not a search box over your Slack. It reads to work, not to index. Ask it a question and it will often go find the answer in a tool rather than in a message.
It is not autonomous. Before something irreversible reaches another person (an email sent, a form submitted, money spent), it stops and asks. The waiting is enforced by the runtime, not by the model choosing to be patient. See Approvals.
It is not always right. It cites its sources so you can check them, shows its plan so you can stop it, and tells you in the channel when a run fails and why. When Gini gets it wrong covers what to do about it.
What people actually use it for
Auditing spend. Weekly reports that used to eat someone's Monday. Triage. Following up after meetings: the tasks filed, the emails sent, the CRM updated, not just a summary that mentions all three. Keeping the wiki current. And then, once it has done the same job a few times, taking that job over on a schedule.
The pattern worth noticing: the work people hand to Gini first is usually the work they were already doing badly because nobody had time to do it well.