Operations & Systems Consulting

Manufacturing discipline for the support workflows AI didn't fix.

I'm Nicholas Dona. I spent my career running production programs for a Tier-1 automotive manufacturing supplier in Japan. Now I find and eliminate the operational waste in B2B SaaS customer-support workflows, and quantify exactly what it is costing you.

Book a Diagnostic Call A focused 5 to 7 day engagement, delivered as a written diagnostic.

The Problem

AI cleared the easy tickets. The expensive problems didn't go away.

The hard tickets still wait.

The bot handles volume. The complex tickets still land in a general queue and sit there, because nothing routes them to the person who can actually resolve them.

Senior people absorb the overflow.

Your most expensive staff quietly pick up work that should never have reached them. It does not show up as a cost. It shows up as their week disappearing.

The dashboard hides it.

Deflection looks healthy while resolution quality slips. The real cost surfaces later as slow resolution, burnout, and churn risk, not as a line item.

This is not a tooling problem. It is a workflow problem underneath the tool.

The Approach

Lean manufacturing principles, applied to digital workflows.

  1. 01

    Map the flow.

    Every ticket has a path. Most teams can describe where it enters and have no clear answer for where it stalls or who owns the stall.

  2. 02

    Find the waste.

    The same discipline that removes waste from a production line applies directly to a support queue: handoffs, waiting, rework, over-processing.

  3. 03

    Fix the system, not the symptom.

    The output is a prioritized plan to remove the friction, usually without buying another tool.

The method comes from manufacturing. The standard is the one used to keep an automotive production line running: map the flow, eliminate the waste, make the system accountable.

The Diagnostic

A focused, 5 to 7 day operational diagnostic.

  1. 01

    Structured intake.

    A focused working session to map your current support and CS workflow end to end.

    Day 1
  2. 02

    Workflow analysis.

    I identify the top three operational bottlenecks and trace each to root cause.

    Days 2 to 4
  3. 03

    Impact quantification.

    Each bottleneck is quantified: hours per week, where the time goes, what it costs. No vague recommendations.

    Days 4 to 5
  4. 04

    The fix plan.

    You receive a written diagnostic: the three friction points, their cost, and a prioritized, specific plan to eliminate them.

    Days 5 to 7

The diagnostic is where we start. It shows you exactly what to fix first, and how far to take it.

Book a diagnostic call

The Deliverable

What you walk away with.

Sample Nomar workflow friction diagnostic, showing cover and interior pages

A written diagnostic containing an executive summary, the three bottlenecks with root-cause analysis, the quantified time and cost impact, and a prioritized fix plan.

The Operator

Nicholas Dona, founder of Nomar

Nicholas Dona, Founder, Nomar

I spent years running production-bound programs for a Tier-1 automotive manufacturing supplier in Japan, coordinating quality, engineering, and operations across languages, time zones, and cultures, against some of the most demanding manufacturing standards in the world.

The same discipline that keeps a production line running, mapping flow, eliminating waste, making systems accountable, is exactly what a chaotic support operation needs.

I build Nomar as one operator doing precise work, with my name on every diagnostic. The business is registered in Woodstock, Ontario. I work from Japan, with clients globally.

  • Automotive Tier-1 background
  • Lean / APQP systems
  • Working globally from Japan

The Next Step

Book a diagnostic call.

A focused 30 minutes. We will look at where your support operation is losing time, and whether a diagnostic is worth running. No pitch deck.