PropertyWeb
Arts commerce house
Catalogue, provenance, direct sale and affiliate. Insured operating entity behind it.
Arts & culture
AI development for arts and culture organizations
Arts and culture organizations hold deep collections and thin metadata. Catalog records are incomplete, archives are scanned but not searchable, and visitors want context the label does not give. AI helps when it is grounded in the collection record and careful about attribution, rights and uncertainty.
We build cataloging pipelines that suggest metadata for curator review, retrieval over collections, archives and provenance files, visitor guides on web and mobile, and the data layer that keeps your collection management system as the source of truth.
Talk to an engineer →Scope in one week. You own the repo from commit one.
Start a project
Step 1 of 5
Got it. An engineer is reading your brief.
You will hear from us within one business day, usually sooner. If it is urgent, email t@moher.ai.
Problems we solve in arts & culture
- Large parts of the collection have minimal catalog metadata.
- Scanned archives and provenance files are not searchable.
- Collection search only works if you already know the accession number.
- Visitor guides are expensive to produce and update.
- Rights and image licensing status are tracked in spreadsheets.
- Donor, ticketing and collection data live in systems that never connect.
What we build
Systems we build for arts & culture
01
Cataloging assistant
Suggested descriptions, subjects and keywords from images and existing records, queued for curator approval before anything is published.
02
Collection and archive retrieval
Natural-language search over collection records, scanned archives and provenance files, with cited answers and uncertainty stated.
03
Visitor guide
Web and mobile guides grounded in the collection record, available in multiple languages, updated when the record changes.
04
Rights and licensing tracker
Image rights and reproduction terms extracted into a structured store and checked before any image is used.
05
Collection data pipeline
Sync from your collection management system to search, web and app surfaces, with the CMS kept as the system of record.
06
Audience data integration
Ticketing, membership and donor data joined in one warehouse for reporting, with access restricted by role.
Shipped in this industry
Running in production
Client names stay under NDA. The shapes do not.
Arts & culture questions
Something else? Email t@moher.ai and an engineer will answer it.
Will AI change our catalog records?
No. It suggests; curators approve. Nothing is written to the collection management system without a named reviewer.
How do you handle attribution and uncertainty?
Answers cite the record they came from and repeat its stated uncertainty. The system does not assert attributions, dates or provenance the record does not support, and that rule is tested.
How are rights, images and donor data handled?
Image use is checked against recorded rights before display. Donor and member data stays in restricted stores under your privacy policy, and we work inside your data protection program.
Which collection management systems do you work with?
We integrate through the APIs and export formats your system supports, and build a sync layer where an API is limited.
What does a first engagement look like?
Usually collection search or the cataloging assistant on one department. Six to ten weeks to production.
Tell us what you need built
Four quick questions and an email. An engineer reads every brief and replies within one business day with next steps, and a written scope follows within a week.
- Written scope and price within a week
- Production deploy by week three
- Your repo and cloud from the first commit
- Senior engineers only, no account managers
Start a project
Step 1 of 5
Got it. An engineer is reading your brief.
You will hear from us within one business day, usually sooner. If it is urgent, email t@moher.ai.