Skip to content

Q-Dev / Data

Data your process can build on.

We source, organise and prepare data for an agreed use. We collect information regularly, bring it together in a shared database or deliver a dataset prepared on request.

Describe one process Explore the possibilities

Q-Dev Data

Choose what it needs to do.

Each option starts from a different need. We agree on the scope, acceptance criteria and timeline for your project.

01Data

Harvest

Repeatable data collection from agreed, permitted sources.

What we define together

  • Sources, schedules and collection rules
  • Validation and change detection
  • Export or integration in an agreed format
Talk to us about Harvest
02Data

SSOT

One up-to-date database used by your teams and systems.

What we define together

  • A shared schema and quality rules
  • Importing, reconciling and updating information
  • Clear ownership and access rules
Talk to us about SSOT
03Data

Dataset

A dataset prepared on request and delivered for further use.

What we define together

  • Agreed scope and data usage rights
  • Sourcing, cleaning and structuring the material
  • Delivery in an agreed format, including for AI knowledge bases
Talk to us about Dataset

These elements help shape the scope. The contract sets out the final list of work.

Connected to your work

Delivery shaped by the next use.

Dataset covers preparing and delivering a collection on request. We agree on its intended use, provenance, usage rights and delivery format. If your goal is a Hermes environment inside your company, we plan that deployment through Q-Journey.

From agreement to deployment

Four stages. Shared decisions.

Every Q-Dev project has four stages with an approval meeting after each one. We document the agreed decisions and revisions together.

  1. Design

    We define the process, scope, solution design and acceptance criteria.

  2. MVP

    We build the first working version and check the core scenarios.

  3. Deployment

    We launch the agreed solution in its target environment.

  4. Training and maintenance

    We prepare your team to use the solution and start maintenance.

Agreed revisions

The document following each gate sets out the approved number of revisions. Once approved, you have two additional rounds of changes to the completed work for that gate.

Clear scope and timing

Timelines are agreed for each project. Changes may affect the schedule; the price changes only when work goes beyond the contract scope.

Rights to the code

Rights to the code transfer to you after the entire project has been paid for.

QA10 knowledge base

Understand the topic before deciding.

Explore the knowledge base

Q-Journey

Starting with an organisational audit?

When an application follows an audit and is designed to improve your organisation, we deliver it in stage two of Q-Journey — including applications that do not need AI.

Explore Q-Journey

Let’s start with you

One process is enough to start.

Tell us who does the work today, how it happens and what needs to change. We will agree on the next step together and prepare an individual proposal.

Describe one process We prepare a quote after discussing and defining the scope.