For businesses
Your everyday work could have another use.
AI teams need examples of how businesses work. A licence gives a buyer permission to use the records you agree to share.
What’s my data worth?Start with what you already have.
Start with an inbox, support tickets, or project records. Tell Korra what they contain and how much history you hold, and get a starting range.
A complete example of specialist work can be more useful than thousands of messages with no result.
Good starting points
- What was asked, what your team did, and what happened
- Enough detail to explain a decision
- Where the records came from and how old they are
- Permission to share them for the agreed use
What data do you have?
These are eight places to look. You do not need to connect your accounts to start.
Team conversations
The discussion behind a decision.
See an exampleBusiness email
Requests, replies, and the work between.
See an exampleSales records
From first inquiry to a recorded outcome.
See an exampleCustomer support
A problem, a response, a resolution.
See an exampleDocuments and guides
The knowledge that makes a task possible.
See an exampleApproved call transcripts
Spoken work, with the right permissions.
See an exampleOperational workflows
The steps, rules, and exceptions of a task.
See an exampleAI review and feedback
An output, a correction, and the reason.
See an exampleExamples from different teams.
These made-up examples show the kind of work a record can capture.
Software and engineering
A fault report, the investigation, the accepted fix, and the checks that passed.
Can the source separate a resolved incident from an untested suggestion?
Finance and accounting
A discrepancy, the supporting entries, the reconciliation steps, and the approved correction.
Which financial, account, or personal details must be excluded?
Customer operations
A service request, the decisions about handling it, and confirmation that the issue was resolved.
What does a successful result mean for this type of request?
Sales
A scope request, the needs discussion, a revised proposal, and the recorded decision.
Are the reasons for qualification or rejection available and permitted for use?
Legal and contract administration
A contract change request, the routing and approval record, and the version approved for signing.
Which privileged, confidential, or third-party materials are outside the scope?
Logistics
A shipment exception, the options considered, the revised route, and the delivery outcome.
Can the record distinguish a proposed route from the one actually used?
What needs to be agreed?
Make the records, the work needed, and the payment clear before you proceed.
- What you describe
- What your business does, the records you keep, where they live and how far back they go. In the chat, then in the full form. You do not upload anything.
- What buyers see
- A short description of your records: the record type, a rough size, the years covered and the uses you allow. Your name and your company's name stay out of it.
- What buyers say
- Once your form is in, we match it with the buyers who fit and tell you what they say. Nothing is binding, and you can say no.
- Your agreement, between you
- If you say yes, you and the buyer agree the licence, the delivery and the payment in writing. Korra is not a party to your agreement.
- How you get paid
- The buyer pays you the price you agree. Payment can come as fast as 7 days; usual terms are net 30.
License your data. Get paid.
Answer ten quick questions and hear back from us in 10 minutes. Nothing to upload.