Under the hood.

How the portfolio is built

Four products, one philosophy. Everything is TypeScript end-to-end. Everything sits on Supabase (Postgres) as the data layer — three of the four lean hard on PostGIS for geospatial work. Every repo ships through pull requests with a documented architecture (each has its own ARCHITECTURE.md and agent-ready conventions), and AI-assisted development is standard practice here, not an experiment. The codebases are written to be legible — to humans and to agents.

GrandRapids.RealEstate (Neighborhood Atlas)

A hyperlocal real-estate knowledge graph for West Michigan: 15,000+ boundary polygons (counties down to subdivisions and condos), each enriched with ~140 columns of computed stats — walkability scores, drive times, school ratings, parcel-derived home values — plus live MLS listings geo-matched to every boundary. The largest and most mature codebase in the portfolio.

• Current status: live in production and stable, ~1,700 commits in. Active work is growth-oriented — new counties through the documented 15-step enrichment pipeline, SEO/content systems, and mobile polish.
• Worth knowing: MLS/IDX compliance and fair-housing rules are codified in the repo and enforced in the pipeline.

The Church Map

A national geospatial collaboration platform: 241,000+ churches and 227,000+ Census/TIGER boundaries on an interactive map, with city-scoped community platforms layered on top — prayer journeys, community feeds, church profile claims, and digitally signed partnership agreements. Philanthropic by design.

• Current status: live in production. Most recently shipped: the SEO build-out (state and city hub pages, JSON-LD, sitemaps) and the digital contract-signing flow.
• Up next: state-by-state data backfill for the Michigan/Texas/California launch, city-platform onboarding tooling, and performance work on the national map.

The Formation App

A multi-tenant spiritual-formation platform — web app plus native iOS and Android via Capacitor. The interesting architecture is the content model: an immutable template layer (the master journey and achievement blueprints) compiles into module instances, which deploy into per-community live data. One-way flow, enforced with database triggers and audit logging.

• Current status: feature-complete and tested; the web app is live. The project is in the last mile between "built" and "in the stores."
• Up next: the launch checklist — transactional email, native OAuth clients, and iOS/Android app-store review.

Compass KPI

A KPI-tracking and production-forecasting platform for real estate agents, teams, and coaches. The core domain logic is a forecast engine with strict separation between projected production, leading-indicator activity, and confirmed actuals — modeled with decay and timing rules, never mixed. Unlike the other three, Compass KPI is not a shipped product — it is an active work in progress, pre-launch, with the build happening right now.

• Current status: in active development. The backend MVP and forecast engines are built; frontend feature sprints are underway.
• Still ahead: the messaging and live-video integration waves, subscription billing, and launch hardening — all on a written, sprint-gated roadmap.
• Worth knowing: the engine math (forecasting, confidence scoring, deal attribution) already has unit-test coverage.

Questions about any of these?

For repo access, architecture docs, or a deeper walkthrough of any project, the fastest path is a short call.