Getting started
Your first job
Give Gini a real piece of work in its first ten minutes, and read the result it posts back.
The instinct with a new AI tool is to test it. Ask something you already know the answer to, see if it gets it right. That tells you very little about Gini, because answering is the part it has in common with every chatbot.
Give it something you were actually going to do this week.
A good first job
The shape to look for: something you'd have done yourself, that takes 20–40 minutes, and that touches a tool Gini can reach.
Examples that work well on day one:
- "Pull our open PRs older than a week and tell me which ones are actually blocked and on whom."
- "Go through last month's Zendesk tickets and find the three things people complain about most. Quote real tickets."
- "Everyone who emailed us about pricing in the last two weeks: who are they, what did they ask, and did we reply?"
- "Read the last month of this channel and write down the decisions we made. I want to know what we'd forget."
Notice what these have in common. They're specific, they have an obvious finish line, and none of them can be answered without going and looking at something.
A bad first job
- "What can you do?" You'll get a list, and lists are what every other tool gives you.
- "Summarise this channel." Gini will do it well, and you'll learn nothing about whether it can work.
- Anything with a real consequence. Not because Gini will fire it off; it won't, approvals stop that. But your first job should be one where you can judge the output on the merits without also being nervous.
What comes back
Gini works in a thread off your message. You'll see it move (reading, calling a tool, waiting on you) and then a result. On anything non-trivial it'll show you the plan first.
You@Gini go through last month's Zendesk tickets and find the three things people complain about most. Quote real tickets.
Gini
Read 214 tickets from July. Three clusters, biggest first:
SSO login loops (41 tickets). Almost all Okta. "I log in, it bounces me back to the login page, forever.": #4821
Export times out on large accounts (23). Every one over 50k rows. "Third try today, still spinning.": #4903
Billing date confusion (17). People expect the 1st, we charge on signup anniversary.: #4877
Full breakdown attached. Want me to open Linear issues for the first two?
Two things to look at in that reply. Every claim has a ticket number behind it, so you can check any of it in ten seconds. And it ends by offering the next step rather than doing it: opening issues is a change in another system, so it asks.
It costs credits, and not many
A job like the one above runs 25–75 credits. Your free 10,000 covers a lot of first jobs. How credits work has the full picture.
Then do it again next week
The second time you ask for the same thing, Gini will often offer to take it over on a schedule. That's a routine, and it's the point at which Gini stops being a tool you use and starts being work you no longer do.