Rust7
Our approachStart a brief
DATA PARTNERSHIPS

Your business history.
New possibilities.

The decisions, documents and outcomes behind everyday work can help teams understand how AI should perform. Explore a data partnership with Rust7.

Explore your data’s potential See the data we look for

Starting with Nigeria · Scoped source by source

Data we’re interested in

The records behind
the real work.

These are sourcing interests, not a live inventory or demand ranking. Start with the records you have permission to discuss.

01Customer conversations

Support tickets, business email and service conversations.

A possible evaluation task

Follow an issue through its resolution.

Support → decision → resolution
02Orders & delivery

Order records, inventory movements and fulfilment events.

A possible evaluation task

Check whether an order reached the agreed outcome.

Order → stock → delivery
03Invoices & payments

Invoice histories, reconciliation records and payment status.

A possible evaluation task

Connect a transaction to its final recorded state.

Invoice → adjustment → settlement
04Sales & customer history

CRM stages, quotations and documented account activity.

A possible evaluation task

Understand how an opportunity moved from enquiry to decision.

Enquiry → quote → outcome
05Projects & engineering

Tasks, issue histories, review records and change logs.

A possible evaluation task

Trace a request through implementation and review.

Request → change → review
06Documents & knowledge

Operating guides, product information and versioned business documents.

A possible evaluation task

Evaluate an answer against the guidance in effect at the time.

Question → source → answer

Useful context includes dates, linked records, outcomes, languages and field definitions. Availability and permitted use are assessed for each project.

Potential partner profiles

Every industry has
work worth understanding.

We’re interested in businesses with documented processes and connected operating history, starting in Nigeria.

These are areas for sourcing conversations, not confirmed buyer orders. Each source needs its own permissions and suitability review.

Context across systems

One task. The whole story.

An isolated record tells you what happened. Connected records help explain how the work got done.

Illustrative workflow · order fulfilmentMade-up example
  1. 01 / REQUESTA customer places an order

    Items, quantities and the agreed delivery date.

  2. 02 / DECISIONThe team resolves a shortage

    An approved substitution and the reason behind it.

  3. 03 / ACTIONThe shipment is recorded

    Dispatch details linked to the original order.

  4. 04 / OUTCOMEDelivery is confirmed

    A checkable ending, including any exceptions.

What an evaluation could ask

Can an AI identify the approved substitute, reconcile the shipment and explain any remaining discrepancy?

From interest to an agreed scope

A clear path
for a careful partnership.

You should understand what is being proposed before sharing any records.

  1. 01

    Describe the source

    Outline your systems, time period, geography and the business process the records describe.

  2. 02

    Establish the boundaries

    Identify who can authorize use, what must be excluded and which intended uses need review.

  3. 03

    Define a pilot

    Agree on a limited scope, a suitable sample, preparation work and acceptance criteria before any transfer.

  4. 04

    Agree on delivery

    Document permitted use, privacy treatment, review, retention and commercial terms for the specific project.

A useful first step

Map your data’s potential.

A few questions to prepare for a sourcing conversation. Your answers create a checklist, not a valuation or approval.

Enable JavaScript to prepare and download a brief on this device.

Which records could you discuss? *

Select at least one category. Describe the source; do not upload company records.

This tool uses only your answers. Nothing is uploaded, sent to Rust7 or saved by this tool in browser storage. A downloaded brief stays on your device.

Partner questions

Clarity from
the first step.

Contributing as an individual? →
What makes a source useful?

A documented origin, relevant coverage and enough context to interpret the records. For workflow evaluation, linked steps and checkable outcomes can help define meaningful tasks. Fitness depends on the buyer’s intended use.

Will I be paid for my data?

Any compensation would be agreed in a specific partnership. This website does not quote a price, guarantee demand or commit Rust7 to acquire a dataset. The readiness tool prepares discussion points only.

Can I send company records here?

No. This page asks about categories only and has no upload feature. Any future sample exchange needs an agreed scope, authorized use and an appropriate transfer process.

Does removing names make the data ready to share?

No. Removing direct identifiers alone does not establish that a dataset is safe or authorized for reuse. The proposed use, remaining identifying details, source permissions and restrictions need review.

What if I have expertise rather than a dataset?

Language knowledge, research experience and domain judgment can support annotation and evaluation. Explore our contributor pathways and prepare a profile.

Start with a better question

What will your
next model need?

Tell us what you’re building. Let’s define the data that could move it forward.

Start a data brief