Selected builds

The work behind the promise.

Egan Forge has built across field safety, people operations, public-safety scheduling, interactive surveys, web-native presentations, customer experiences, and agentic company operations. These summaries show the engineering range without publishing the private machinery.

The build pattern

01Understand the operating constraint
02Design the human decision path
03Build the interface and automation
04Test failure and exception paths
05Deploy, document, and verify

Precise status. Public, private, early-access, and active internal work are labeled separately.

No borrowed credibility. A project name never implies endorsement, deployment, or measured results.

Private by design. Operational data, security details, source code, and proprietary workflows stay private.

Operational applications

Software shaped around the actual job

Focused applications for work where roles, constraints, context, and human judgment matter more than a generic AI feature.

Environment, health, and safety

Commercial baseline · Productization

Forge Safety Manager

A tenant-configurable EHS platform baseline for field, fleet, and facility operations, with web and iOS field workflows.

Business problem: Incidents, observations, JSAs, inspections, training, equipment, corrective action, and safety knowledge become difficult to operate when they live in separate tools and handoffs.
System response: A tenant-neutral product baseline spanning incident management, observations, JSAs, inspections, SDS access, equipment workflows, training, coaching and CAPA, analytics, offline capture, and optional integrations.

What it demonstrates

Tenant-configurable platform design
Web and iOS field workflows
Integration-ready EHS architecture

Disclosure: Private proprietary baseline with blank-by-default tenant data. No customer or personnel records, production identifiers, or integration secrets are published. Productization, security, disaster-recovery, and customer-acceptance gates remain; no deployment, compliance determination, or operational outcome is claimed.

View the public surface

People operations

Private application build

MEDAC Manager

A role-aware HR and talent-management application for turning people-operations workflows into a coherent operator experience.

Business problem: Talent and management work becomes difficult to govern when responsibilities, records, and follow-up are spread across documents, inboxes, and disconnected tools.
System response: A purpose-built management interface that structures the work, separates responsibilities, and gives decision-makers a clearer operating view.

What it demonstrates

Role-aware product design
Structured management workflows
Private-data access boundaries

Disclosure: Private build. No employee data, screenshots, deployment claim, adoption figure, or business outcome is published here.

Public-safety operations

Private scheduling build

Ritchie County Sheriff scheduling assistant

A schedule-planning assistant created for a public-safety scheduling context with coverage, rotation, constraint, and operator-review needs.

Business problem: Operational schedules are not simple calendars: coverage requirements, rotations, exceptions, and human judgment have to remain visible together.
System response: A focused planning interface that helps organize constraints and candidate schedules while keeping the responsible operator in control of the final decision.

What it demonstrates

Constraint-aware assistance
Human-controlled planning
Operational interface design

Disclosure: The name identifies project context only. No endorsement, agency deployment, schedule data, security detail, or measured outcome is implied.

Interactive deliverables

Business documents rebuilt for the browser

Surveys, assessments, reports, and presentations become responsive software experiences instead of static files passed between inboxes.

Guided data collection

Interactive deliverable

Interactive surveys and assessments

Browser-based surveys that turn static questionnaires into guided experiences and structured, reviewable outputs.

Business problem: A document or generic form can collect answers, but it rarely explains context, adapts the experience, validates inputs, or produces a useful decision artifact.
System response: Responsive web experiences that guide participants through the right information, validate what is entered, and present completed input in a more useful format.

What it demonstrates

Guided participant experience
Input validation and structure
Responsive reporting surfaces

Disclosure: Capability summary only. Survey questions, responses, identities, analytics, and organization-specific workflows remain private.

Modern business communication

Interactive deliverable

Interactive HTML presentations

Self-contained web presentations that replace linear slide decks with responsive, navigable, and interactive decision experiences.

Business problem: A static deck forces every audience through the same sequence and separates the presentation from the data, interaction, and next decision.
System response: Shareable HTML presentations with progressive disclosure, navigable sections, visual data, embedded interaction, and layouts that work from a conference screen to a phone.

What it demonstrates

Web-native storytelling
Interactive data presentation
Portable responsive delivery

Disclosure: The delivery pattern is public; private presentation content, source material, and organization-specific decisions are not.

Company systems

The operating platform behind the studio

Egan Forge is itself a working systems problem: customer communication, executive oversight, product delivery, governance, and agent operations have to fit together.

Customer and executive experience

Active company system

Two web systems for one company

A customer-facing marketing and product site paired with a private CEO decision system built for remote oversight and accountable agent execution.

Business problem: Customers need a clear, credible buying experience while the operator needs a very different surface for metrics, decisions, system health, and execution evidence.
System response: The public site explains offers, products, and field notes. The private dashboard unifies source-labeled company metrics, proposal review, exact-effect approvals, and postcondition evidence.

What it demonstrates

Audience-specific product architecture
Source-labeled executive reporting
Evidence-bound approval workflows

Disclosure: Only the customer surface is public. Dashboard access, raw company data, credentials, control paths, and internal operating details remain private.

View the public surface

Agentic company engineering

Active internal platform

The Egan Forge operating platform

A multi-language monorepo that treats products, services, evaluations, governance, observability, publishing, deployments, and agent operations as one engineered company system.

Business problem: A solo operator cannot responsibly scale disconnected scripts and model conversations. Work needs shared contracts, durable state, testable boundaries, and visible human authority.
System response: A common engineering substrate for web applications, Python services, evaluation suites, source-of-truth catalogs, deployment gates, monitoring, decision records, and specialized agents.

What it demonstrates

System-of-systems architecture
Evaluation and deployment discipline
Human authority over agent execution

Disclosure: Architecture is described at capability level. Proprietary orchestration logic, prompts, credentials, infrastructure details, and operating data remain private.

View the public surface

Your workflow is the next specification

Bring the operational problem, not an AI shopping list.

We'll map the constraint, the people who own the decision, the systems already in place, and the acceptance test before choosing what to automate.

Discuss a build Review engagement options