Data On Demand, one-stop data solution
Markets Local sources. Your time zone.

Teams in five regions rely on us for local-language, multi-currency data.

Global coverage
Company A decade of data expertise.

An in-house team of 20+ engineers and analysts serving clients in 12+ countries.

About us
Core service

Bespoke extraction for the data nobody packages.

When the data you need sits across awkward sources, nested pages or several languages, off-the-shelf datasets fall short. We scope a custom schema with you and build extraction logic to match it, whether for a single research project or an ongoing programme.

The challenge

Research and strategy teams often need a dataset that does not exist anywhere in ready-made form. The information is public but spread across directories, regulator sites, marketplaces and brand pages, each structured differently and some in Arabic, Portuguese or Bahasa.

With Data On Demand

You get one coherent dataset built around your question, with fields defined in a data dictionary and every record traceable to its source URL. One-off projects can later be converted into a scheduled feed without rework.

What’s included

Everything needed to run it in production.

01

Scoping workshop

We translate your business question into a field list, entity definitions and acceptance criteria before building anything.

02

Complex navigation

Multi-step flows such as search forms, filters, location selectors and nested detail pages are handled in the crawler logic.

03

Multilingual parsing

Arabic, accented Latin and CJK text is captured with correct encoding, and key fields can be transliterated or mapped to English labels.

04

Entity matching

Records from different sources are linked to a common entity, such as the same product, company or venue, using rules and manual review.

05

Data dictionary

Each delivery includes field definitions, source lists, coverage notes and known limitations.

06

Path to automation

If the dataset proves valuable, the same extraction logic moves onto a recurring schedule with monitoring.

Sample output

What lands in your systems.

Typical fields
record_idsource_urlentity_nameentity_typeattribute_nameattribute_valuelanguageextracted_at
Custom extraction: private clinic directory compiled from public listings
record_idsourcecityclinic_namespecialtyconsult_feecurrencylanguage
CL-00412Directory AAbu DhabiFamily Clinic APaediatrics300AEDar/en
CL-00413Directory ARiyadhDermatology Centre BDermatology350SARar
CL-00587Portal CKuala LumpurKlinik CGeneral practice60MYRms/en
CL-00644Portal DBogotáCentro Médico DCardiology180,000COPes
CL-00702Directory EManchesterPhysiotherapy Clinic EPhysiotherapy55GBPen

Illustrative rows. Your schema, field names and formats are agreed during scoping.

Use cases by team

Who uses it, and for what.

Deal teams build a market map of a fragmented sector from public directories and company sites. The dataset supports sizing and target screening early in diligence.

How it runs
  1. Scope. Tell us the sources, fields and frequency. We confirm feasibility within a day.
  2. Free sample. A real sample from your own target source, in your format.
  3. Build. Engineers build extractors tuned to each source. No generic templates.
  4. Validate. Automated and manual QA on every run before anything ships.
  5. Deliver and monitor. Scheduled delivery, monitored pipelines, fast fixes when sites change.
How we work
FAQ

Questions about custom data extraction

Can’t find your answer? Ask an engineer

How do you scope a custom project?

We start with the decision the data should support, then agree entities, fields, sources and acceptance criteria. A free sample of 24–48 hours' work lets you check the shape of the data before committing.

Can you handle Arabic or other non-Latin scripts?

Yes. We capture text in its original script with correct encoding and can add transliterated or translated labels for key fields. Encoding checks are part of standard QA.

What if some sources do not have the field we need?

Coverage varies by source, so we report fill rates per field and per source. Where a field is missing we flag it rather than infer a value, and suggest alternative sources where they exist.

Is a one-off extraction cheaper than an ongoing feed?

The initial build effort is similar, but a one-off project has no ongoing monitoring or maintenance costs. Many clients begin with a one-off and move to a schedule once the value is proven.

Start with proof

See your own data before you commit.

Name the sources and fields you need. Within 24–48 hours you receive a real sample from your target sites, in your format, free of charge.

Request a free sample Talk to a data engineer Sample in 24–48 hours · NDA on request · Any format, any schedule