Agentic engineer. Product judgment. Practical delivery.
Software shaped by the work, not the other way around.
Practical software starts with the shape of the work: the awkward handoffs, edge cases, and operational gaps that off-the-shelf tools rarely fit. I bring domain judgment and an agentic build loop that compresses the path from real workflow pain to a working software surface. MindServe and ShelfFinder are the current proof.
MindServe
Cafeteria operations software, with StockSense as the central data layer.
Work surfaceShelfFinder
Voice-first grocery navigation shaped around natural shopping intent.
Work surfaceAtlier
The underlying idea: attention calls the right work forward.
Indirect thesisBuilder arc
The work came first. The build loop came later.
For two decades I worked close to real operational software: implementations, support, training, and the recurring gap between how work happens and how systems expect it to happen. Agentic engineering changed my role in that gap. I can now turn the workflow judgment I earned in operations into working software surfaces.
Current work
The apps on the desk
These are not sales claims or polished case studies. They are software surfaces I use to show how I think, design, organize systems, and build.
MindServe
Software surfaceCafeteria operations software. StockSense is the central data layer; RetailMind, QuickServe, and MealMind are application surfaces around it.
- FIFO costing
- vendor invoice import
- multi-tenant facility scope
- kiosk and mobile ordering
- menu data from StockSense
- guest-facing flow
- cashier-first workflow
- shift operations
- customizable item builds
- guest-facing flow
- facility and location scoped
- guided meal start
ShelfFinder
Software surfaceGrocery navigation for people who want to say the list, refine the trip, and get store-aware direction without wrestling a search box.
Read the proof story ->Technical proof repositories
Curated proof, not production source.
These public, sanitized repositories are prepared for technical conversations. They show architecture, ADRs, operating judgment, security posture, and selected safe excerpts without exposing the production code.
Grocery
Clean Architecture, ADRs, operations, and selected safe code excerpts.
- Clean Architecture
- ADR digest
- safe code excerpts
MealMind
Employee and guest meal ordering, protected data boundaries, voice, and security posture.
- guided ordering flow
- security posture
- voice and AI notes
MindServe
Suite architecture, tenancy, operating model, and intelligence-layer direction.
- suite architecture
- tenant boundaries
- operating model
More on the desk
The broader workbench.
The lead surfaces stay focused. The wider bench shows the range of system pieces, product ideas, ports, voice layers, and proof surfaces I can bring forward in conversation.
Cafeteria operations, inventory, point of sale, ordering, analytics, and onboarding.
The supporting pieces behind voice-first and agent-assisted product surfaces.
Separate product ideas, consumer tools, and public proof surfaces.
How I work
Agentic engineering, product judgment, practical delivery.
- Find the real workflow.Start with operator pain, constraints, and the moments software usually misses.
- Spec with AI as a thinking partner.Use Claude for architecture, edge cases, narrative, and ruthless scope discipline.
- Compress the delivery loop.Track the work in Linear, keep production source private, expose curated proof when useful, execute with Codex against the repo, deploy on Azure, then use the running surface until the unclear parts become obvious.
Doorways
Different reasons to start a conversation.
Bring me into the work.
For teams that need an agentic engineer with product judgment, workflow sense, and a practical path from idea to working software.
Talk about a roleConsulting, project-scoped.
For workflow design, integration thinking, internal tools, prototypes, or AI-assisted build execution that needs practical judgment.
Request a scoping callAdvisor, fractional, or build partner.
For founders or small teams who need agentic engineering, product judgment, implementation sense, and a clear-eyed build partner when the fit is right.
Check availabilityAgent-readable layer
The structured truth ships with the page.
Humans get the work surface. Agents get the same context as structured data in the page head - who Justin is, how he builds with agents, what he is working on, and how to reach him.
- MindServeSoftware surface
- Cafeteria operations software: StockSense as the data layer, with RetailMind, QuickServe, and MealMind as application surfaces.
- ShelfFinderSoftware surface
- Voice-first grocery navigation that turns a spoken list into a store-aware shopping route.
- MethodIn daily use
- Product judgment first, AI as architecture partner, agentic engineering loops, verified by using the software surface.
- Proof reposPublic
- Curated public proof repositories exist for Grocery, MealMind, and MindServe. They show architecture, ADRs, operations, and selected safe excerpts without exposing the production source.