00
GORDON TODD WATTS · LOADING SYSTEM
Gordon Todd Watts
Flagship work

Systems, not just
screens.

This page is where the portfolio stops acting like a gallery and starts acting like evidence. Each build below is framed in terms of the problem, the approach, and the proof it creates about product judgment, engineering depth, and systems thinking.

2024 · live
JPope Tax Portal
A portal that behaves like operational software, not a veneer over back-office chaos.
2025 · live
TaxScout.app
Turns specialized tax engineering into software people can actually use.
2025 · live
MAINFRAME
Infrastructure thinking, expressed in the most unforgiving runtime: pure shell.
2024 · live
PropertyJunk.com
Operational complexity turned into a single coherent software surface.
JPope Tax Portal
2024 · flagship case study

JPope Tax Portal

Enterprise client portal for tax consultancy. A portal that behaves like operational software, not a veneer over back-office chaos.

Surface
Portal + docs + comms
Mode
Realtime-ready
Focus
Security + clarity
Problem

The business needed one secure client surface instead of fragmented communication, ad hoc document exchange, and manual operational follow-up.

Build approach
■Built a role-aware client portal with unified communication and document workflows.
■Used a realtime-capable frontend architecture so the product felt operational, not brochure-like.
■Focused on making enterprise complexity legible to both staff and clients.
Why it proves something
▲Enterprise-flavored interface discipline, not just marketing-site polish.
▲Shows ability to design around access control and business workflow complexity.
▲Demonstrates product thinking in a regulated, trust-heavy environment.
Role-based accessRealtime data syncDocument workflows
TaxScout.app
2025 · flagship case study

TaxScout.app

AI-powered commercial real estate tax optimization. Turns specialized tax engineering into software people can actually use.

Domain
CRE tax workflows
AI layer
MCP-connected
Product move
Decision support
Problem

A domain-heavy tax workflow had to become understandable, actionable, and productized for users who care about financial outcomes more than internal complexity.

Build approach
■Translated niche tax strategy into guided product workflows.
■Connected domain logic to AI/MCP access so the platform could participate in agent-driven workflows.
■Designed the frontend as a decision-support surface rather than a generic dashboard.
Why it proves something
▲Shows you can productize high-complexity domain knowledge.
▲Signals AI integration as part of system design, not as a decorative feature.
▲Combines frontend execution with business-model awareness.
AI agent publishing surfaceTax calculation workflowsMultifamily domain modeling
MAINFRAME
2025 · flagship case study

MAINFRAME

Open-source bash stdlib for AI agents. Infrastructure thinking, expressed in the most unforgiving runtime: pure shell.

Functions
4,000+
Runtime
Pure bash
Use case
AI agent systems
Problem

Agentic shell workflows are usually a mess of brittle scripts and duplicated glue logic. They need durable primitives, not one-off hacks.

Build approach
■Built a broad bash-native standard library instead of relying on heavyweight runtime assumptions.
■Added memory, orchestration, and data-handling primitives so shell workflows could scale into systems.
■Framed the project as infrastructure for AI-native tooling, not just a utilities repo.
Why it proves something
▲Strongest evidence of systems-level engineering range in the portfolio.
▲Gives technical peers a concrete artifact to inspect, evaluate, and trust.
▲Signals authorship and initiative beyond client delivery work.
Pure bash runtimeAgent working memory primitivesCLI-first orchestration surface
PropertyJunk.com
2024 · flagship case study

PropertyJunk.com

Junk removal SaaS with integrated CRM. Operational complexity turned into a single coherent software surface.

Mode
Ops SaaS
Surface
CRM + fleet + billing
Focus
Workflow continuity
Problem

A field-operations business needed software that could coordinate jobs, people, vehicles, customers, and billing without forcing staff to bounce between disconnected tools.

Build approach
■Treated operations as a product surface, not just a CRUD admin panel.
■Designed around scheduling, fleet visibility, CRM, and financial workflow continuity.
■Used frontend structure to reduce operational friction for a real-world service business.
Why it proves something
▲Shows range across dashboards, workflows, and operational software design.
▲Demonstrates practical SaaS thinking tied to actual business movement.
▲Signals competence with systems that touch revenue-critical operations.
Operations dashboardFleet and scheduling workflowsUnified CRM + billing