← Selected work
C-04 Mining & resources

Investor platform for mining data

A consumer-facing way to explore mining companies, project maps, people, and watchlists — built on top of a shared mining-data backbone.

Real project · client withheld · outcomes discussed under NDA

  1. 01 Reuse the data backbone
  2. 02 Map-first exploration
  3. 03 People and watchlists
  4. 04 A consumer surface over specialist data
1730 / C-04 / Relationship network Build path / 4 stages PostGIS

Once mineral-exploration data is modeled properly, the same backbone can serve more than one audience. Individual investors want to explore companies, see where projects sit on a map, follow the people involved, and keep a list of what they are watching — without the raw complexity of the underlying registries.

The problem

The data that answers an investor’s questions is spread across corporate filings, tenure registries, and market feeds, and it is organized for specialists, not for someone browsing. Presenting it as a clean, navigable product means building a consumer front end that stays honest to a messy source of truth.

What we did

  1. 01
    Reuse the data backbone

    A consumer platform built on the same PostGIS-backed model that holds companies, projects, and tenure, rather than a second copy of the data that drifts out of sync.

  2. 02
    Map-first exploration

    Company and project browsing anchored to a map, so where a project sits is part of how you navigate it, not an afterthought.

  3. 03
    People and watchlists

    Profiles for the people behind projects, and personal watchlists so someone can follow the companies and projects they care about across visits.

  4. 04
    A consumer surface over specialist data

    A front end shaped for browsing and following, that hides the registry-level complexity while staying faithful to the underlying records.

Relevance

Where this pattern applies.

  • You have specialist data that needs a clear public or member-facing product.
  • Maps, company and project relationships, people, and watchlists must stay tied to one data backbone.
How we would start

A comparable engagement starts by settling the shared data model, then builds the consumer surface on top of it — usually a scoped first version covering company and project browsing before people and watchlists are layered on.