Our approach
Find the right material, shape it around your research, and put it to work. We connect specialized sources to the application you have in mind.
Tell us what you are researching or building. We work through the task, domain, source requirements, and what a strong example looks like. A few positive and negative examples make the brief concrete.
A shared brief and a clear definition of useful.We source a focused review set in the proposed format. Your team can inspect the content and the accompanying source record, then tell us which examples meet the bar and why.
A review set and an agreed selection standard.We agree the pilot scope, acceptance criteria, preparation requirements, and delivery terms. For task environments, that includes the grader and the evidence needed to trust its results.
A scoped pilot with a review and replacement process.Expand the work in versioned tranches. Keep the accepted standard consistent, track feedback, and introduce new task families as the research need changes.
A repeatable delivery and feedback loop.The evaluation kit
The working material is only one part of a useful delivery. Its source, preparation, and version should be inspectable too.
Use these templates to brief a program or plan a technical review. The example manifest demonstrates structure; a customer review set contains the actual material and its evidence.
The material
The task, the reasoning, and the details that make the result useful.
Working together
Yes. We start with a focused review set so your team can assess fit and shape the pilot. Sample scope, access, and permitted use depend on the material and are agreed before delivery.
Yes. Domain, task type, format, context, and evaluation requirements shape the program. We can adapt an existing collection or develop a new sourcing and preparation workflow around the brief.
The package is agreed for the program. It can include source files, rendered views, structured text, task metadata, source and preparation records, review notes, and a release manifest. Graded environments also need their environment and verification evidence.
Yes. We document the source and preparation of a collection and work through the licensing requirements for your application. Training, evaluation, exclusivity, and distribution are scoped to the program.
Where the source and permissions support it, yes. The join policy is agreed explicitly. Some collections use document-local identities; others may need a coherent workflow across records. Those require different preparation choices.
We scope the collection, review requirements, and delivery schedule before quoting. A pilot establishes the standard for a larger program. Source access, preparation, annotation, exclusivity, and review effort determine the commercial terms.
Work with Gerra
Tell us what you are building and the data you need. We will connect you with the right collection or program.
Let’s talkteam@gerra.com