Reliable internal tools for ecommerce and support ops.

I help teams automate the messy work between Shopify, Front, Slack, Aircall, Zapier, spreadsheets, dashboards, and guarded AI tools so the system fails loudly enough to fix.

Layered ecommerce operations cockpit with dashboard, workflow, alert, and deployment verification panels
Product-style composite showing the kind of dashboard, workflow, alert, and deployment surfaces I build.
Stack fit
Shopify, Front, Slack, Aircall, Zapier, Railway, spreadsheets
Delivery style
Dry runs, alerts, validation, docs, deployment notes

How the work is different

Reliable automation is less about connecting apps and more about making failure visible.

Source-aware reporting instead of blended metrics
Dry-run paths, write locks, validation, and diagnostics
Production-minded deploys, migrations, and handoff notes
Operator-facing tools across support, ecommerce, and reporting

Packaged offers

Buy the smallest packaged service that fits the problem.

View all services

Pay first, scope clearly

$350

Workflow Diagnostic

Send the messy workflow and get a written repair plan before anyone starts building.

  • Async intake review plus one focused follow-up if needed
  • Failure points and source-of-truth map
  • Prioritized fix plan with next-step recommendation
  • Delivery target: 3 to 5 business days after intake and access

Fixed-price planning service. Non-refundable after the diagnostic is delivered.

Buy diagnostic

For one contained fix

$950

Automation Quick Fix

A fixed-scope implementation for one small workflow that needs to stop wasting time.

  • One contained automation or repair
  • Basic validation, alerts, or failure visibility
  • Handoff notes and short bug-fix window
  • Delivery target: usually 5 to 10 business days after scope is confirmed

Covers one contained workflow issue. Larger fixes are quoted before extra work starts.

Buy quick fix

For serious builds

$1,500

Automation Build Deposit

A paid deposit to start scoping and building a deeper ecommerce or support-ops system.

  • Build kickoff and technical discovery
  • Implementation plan for dashboards, workflows, or internal tools
  • Deposit credited toward the final fixed project scope
  • Next step: kickoff intake, access review, then final scope approval

Deposit starts discovery and implementation planning. Final build scope and any balance are confirmed before deeper work continues.

Pay build deposit

Case studies

Real systems, shown through sanitized implementation artifacts.

Sanitized Returns Dashboard interface showing cohort-aware return trends, source filters, diagnostics, and proof artifacts.

Ecommerce analytics

Returns Dashboard

Cohort maturity + source-aware reporting

A production ecommerce reporting system that made return, marketplace, and economics data easier to audit, explain, export, and operate.

  • Internal dashboard development
  • Data audits and reporting semantics
  • Production migrations and deployment verification
Sanitized workflow artifact showing order events, validation, merge-safe writes, and support contact enrichment.

Support operations

Shopify-to-Front Order Enrichment

Merge-safe Front writes

A TypeScript webhook service that added order context to support contacts while preserving existing conversation routing.

  • Webhook automation
  • CRM/contact enrichment
  • Deployment migration planning
Sanitized guarded AI draft assistant interface showing private preview, validation issues, write lock, and audit trail.

Guarded AI operations

Guarded AI Front Draft Assistant

Write locks + evals

A support drafting tool designed around private previews, write locks, deterministic validation, diagnostics, and human review.

  • AI support tooling
  • Safety and validation design
  • Operator diagnostics and evals
Sanitized support load report showing workload cards, channel bars, diagnostics, and Slack-ready summary status.

Operations reporting

KPI and Support Load Reporting

Ledger-first monthly reporting

Reporting automation that turned support-platform, telephony, spreadsheet, and Slack-shaped data into repeatable management visibility.

  • KPI reporting automation
  • Support workload modeling
  • Documentation and templates

Builder proof

The developer signal is in the guardrails.

TypeScript and Node

Webhook services, support tools, review commands, diagnostics, and automation scripts built to be read and maintained.

Reporting Semantics

Postgres-backed data modeling, source-aware reports, cohort maturity, exports, and dashboards that say what they can prove.

Production Guardrails

Dry runs, write locks, validation, scoped access, health checks, alerts, and recovery notes where workflows can fail.

Operator Handoff

Deployment notes, runbooks, migration checks, Slack-shaped summaries, and docs that keep the system usable after launch.

Builder lab

Side projects stay secondary, but they show range.

Personal finance tools, mobile experiments, and product prototypes belong behind the commercial automation work. They are useful proof of product taste, learning velocity, and curiosity, without diluting the ecommerce and support-ops front door.

Bring me the workflow that keeps breaking.

Pay for a diagnostic when the pain is clear, or start small with a free scan.