Skip to main content
SA

Forward-deployed / product engineering

I build software around the way operations actually work.

I work with the people running a process, find where records and decisions break down, and build the right control layer: a spreadsheet system, an integration, or internal software.

Talk about a workflowSee selected work

Selected forward-deployed work

Three operating problems. One at a time.

Use the controls to move between concise, source-grounded case studies.

01 / Inventory operations

Stock movement the team can record and management can trace

A real company needed one reliable way to record stock coming in and leaving without asking staff to rebuild the management view by hand.

Problem
Stock entry, current balances, and transaction history needed to stay connected.
Decision
Keep the familiar Google Sheets interface and add Apps Script controls around the workflow.
Outcome
Staff record a movement once. Management can review the balance, history, and items that need attention.
Related systems

Consumables movement trackingAsset and cylinder audit

View inventory workbook (opens in a new tab)
Evidence and limits

The archived system flags the original transaction as VOID and creates an offsetting row. A later review found that a second void could target a reversal row. The hardened reconstruction excludes reversal rows and checks the resulting balance.

Inventory Control fictional data
ItemMovementBalanceStatus
Safety Gloves−48LOW
Router−13VOID
Router+14ACTIVE
ITEM_LISTLEDGERDASHBOARD

1 / 3

The work hiding between tools

Small gaps make everyday operations hard to trust.

01

Records without history

A balance exists, but nobody can quickly explain what changed.

02

Work between systems

Reports arrive in Slack and email, while follow-up stays manual.

03

Exceptions in memory

Low stock or an invalid submission is visible only to the person checking.

How I work

Understand the operation. Then choose the technical layer.

  1. MapPeople, inputs, handoffs, decisions, and exceptions.
  2. ProveThe risky logic: balances, reconciliation, validation, or control.
  3. FitThe smallest system the team can use and maintain.
Excel / SheetsApps Script + integrationsInternal applicationFull product system

Choosing the delivery layer

A spreadsheet can be the interface. The workflow is the real product.

Excel or Google Sheets can be right for structured entry, reconciliation, summaries, and visible exceptions. Apps Script adds validation, alerts, and integrations.

When the process needs stronger permissions, concurrency, or scale, I carry the same workflow understanding into React, Next.js, Node.js, APIs, PostgreSQL, real-time services, and payments.

View the full software engineering portfolio

For operations teams and founders

Still handling part of your operation manually?

Show me how it works today. I can help decide what to automate, what to leave alone, and which technical layer fits.

Talk about a workflow