← All work
Internal system

Internal Systems

Internal Operations Platform

Internal Axionvex system · Operations workflow platform

Overview

This internal system replaced fragmented spreadsheet, email, and chat-based operations work with a single platform for task flow, ownership, reporting support, and audit history.

System Architecture

architecture — ops-platform

Ops Dashboard

Next.js · Role-based access

Task Pipeline

Status workflows

Automation Engine

Trigger-based

API Layer

Node.js · REST

PostgreSQL

Primary store

Audit Log

Every action traced

File Storage

S3 · Attachments

The Problem

Operational data lived across spreadsheets, email, and informal chat queues, which made ownership and status hard to trust.

Handoffs depended on messages that were easy to miss.

Leadership reporting required manual assembly and was often stale by presentation time.

Certain actions needed an audit trail that spreadsheets could not provide reliably.

Technical Approach

01

Mapped the real operating workflow before design

The build started from observed work patterns rather than an idealized process document.

02

Built task pipelines with status automation

Tasks move through defined stages with notifications tied to ownership changes.

03

Role-based access with clear ownership

Views and permissions were scoped by role so people see the work they own.

04

Built-in audit logging

Material actions are logged with actor, time, and change context.

05

Parallel run before cutover

Old and new processes ran together long enough to catch edge cases before full cutover.

Tech Stack

frontend

Next.jsReactTailwind CSS

backend

Node.jsExpressREST API

data

PostgreSQLPrisma ORM

infrastructure

AWS (EC2, RDS, S3)Vercel (frontend)

Engagement Details

Timeline

Approximately 8 weeks (subject to verification)

Team

Senior Axionvex Tech engineer with internal operators as design partners

Outcomes

Design and control changes are listed below. Numeric claims stay unpublished until measurement is verified.

Workflow centralization

Design change
Before

Fragmented spreadsheets and chat handoffs

After

Single system of record for task state and ownership

Compliance support

Design change
Before

No dependable action history

After

Audit log for material client-facing actions

Measured production results

Pending verification
Before

Baseline metrics not yet published

After

Numeric outcomes withheld pending verification

Published as an internal system. Quantitative time-saved claims remain pending verification before public use.

Have a similar workflow?