SYMBRIQResearch Lab

Field

Field work while the platform is built.

Federal grants are slow. Places still have plans, pipelines, infrastructure, and a season. Field work is how the lab sits next to the people who run a city — before, and besides, a research award.

Principal: Ahmet Seydanlioglu, Co-Founder & CEO.

Why this exists

A platform that talks about cities without sitting next to the people who run them is a paper. Field work is the honest start: paid, scoped, useful. Those relationships are how the lab learns a place.

What a first engagement looks like

Typical length: two to six weeks. Delivered as a briefing, a map-backed memo, and a working session — not a 200-page plan that sits on a shelf.

  1. 01

    Plan versus the living city

    Read general plans, specific plans, and infrastructure language against entitled or likely growth. Name the contradictions a council will eventually have to own.

  2. 02

    Entitled-but-unbuilt review

    Inventory pipeline housing and unbuilt designations. Show what “already approved” implies for future demand, access, and exposure.

  3. 03

    One room, more than one shop

    Planning, OEM, budget, or infrastructure in the same briefing. A shared picture of now versus the city already committed — not an operational forecast.

  4. 04

    University and studio partnership

    Guest method sessions, shared evaluation design, or a bounded data collaboration. We prefer labs that will argue with us.

What we will not sell

  • A replacement for a duty officer or a planning director
  • A black-box score for lenders
  • A full general-plan rewrite
  • Staff augmentation with junior GIS only

Who should write

Planning directors, city and county managers, infrastructure and OEM coordinators, council aides, university PIs in planning / geomatics / public policy, and state program staff.

Principal

Ahmet Seydanlioglu

Co-Founder & CEO

Dr. Seydanlioglu is a metropolitan systems architect and researcher working at the intersection of spatial intelligence, urban systems, and data architecture. He is CEO, Co-Founder, and Principal Investigator.

Ike Kavas backs engagements when the question is product, data pipeline, or how an institution would eventually sit on the platform.