# TR Ingram

> GIS / GeoAI systems builder for teams that need spatial workflows, maps, data products, and AI-assisted operations to become working software.

Official site: https://ingramgeoai.com/
Contact: tr@ingramgeoai.com
Primary CTA: Send a rough GIS / AI workflow brief or request a consult call.

## What TR Builds

- GIS and GeoAI product proofs for maps, dashboards, parcel intelligence, and decision-support tools.
- ArcGIS workflow automation for repeated AGOL, Portal, map-update, reporting, QA, and handoff steps.
- Agent operations loops with durable tasks, memory, blockers, verification evidence, and human review gates.
- 3D cartographic product surfaces for terrain, parcels, constraints, report views, and inspectable site decisions.

## Best-Fit Starting Points

- A spatial workflow, dataset, map viewer, report, or handoff is repeated often enough that friction compounds.
- A reviewer can inspect a narrow prototype and say what would make it trustworthy.
- The useful output is a scoped build, pause, or hardening decision rather than an open-ended strategy deck.

## Proof Surfaces

- ParcelIQ: live Laramie County parcel intelligence with 46,000+ public records, map search, value symbology, draw/query workflows, aerial context, and Pro-gated exports.
- Git-Map: Git-like version control for ArcGIS web maps, including clone, pull, commit, branch, and merge workflows.
- ProjectIQ / OpenClaw: local-first operations layer for AI-assisted project work with durable issues, memory, dashboards, and native tools.
- Open World Model: geospatial reasoning benchmark focused on provenance, trust precedence, conflict handling, and visible uncertainty.

## Engagement Packages

- Parcel / Spatial Data Product Audit: source inventory, user task, trust gaps, first demo surface, and one metric that proves whether the idea deserves hardening.
- ArcGIS Workflow Proof: narrow local build around one real workflow, before/after steps, failure modes, and a human review gate before production use.
- Agent Ops Review Loop: lightweight operating loop that turns work into issues, artifacts, verification notes, and approval gates.

## What To Send First

- The workflow, decision, or handoff that is costing time now.
- Current maps, data sources, tools, screenshots, users, and constraints.
- What a credible first proof should answer in 2-4 weeks.

## Boundaries

- First proofs should be reviewable before public launch, paid plans, or production hardening.
- Sensitive data, production deployment, public launch, outreach, and account changes require explicit human approval.
- Static demos should be labeled as demos until connected to real approved data sources.