Manufacturing technology & strategy

Compound capability.
Not complexity.

If every new system adds another contract, integration, login, training path, data model and support dependency, the stack may be growing faster than the value.

I help manufacturers start where the work happens, follow the thread vertically and horizontally across people, process, equipment, OT, systems and data, and decide what should be preserved, simplified, connected, consolidated or replaced.

Start with the problem, not the product. Preserve and amplify what already works. Make the right thing easier to do. Make the next investment simplify the environment.
Does this sound familiar?
More systems.The work is not getting simpler.
Great demos.Then come integrations, training, support and lifecycle cost.
Plenty of data.Still too much translation, normalization and manual work.
Heavy investment.Yet new tools keep getting added around old limitations.
Who I help

The scale changes. The underlying problems often do not.

I’ve worked with manufacturers from roughly $20 million to $20 billion in annual revenue. The scale changes. The need for a clear, practical answer does not.

$20M$20B
The approach scales to the situation, not the size of the logo.
Disconnected operations, systems or data.
Uncertainty about where to begin a transformation.
An expanding technology stack with overlapping capability.
Underused investments that should be creating more value.
MES, OT/IT, industrial-data or integration decisions.
Technology choices that are difficult to evaluate objectively.
How I help manufacturers

Specific help when you need a practical next move.

You need enough clarity to decide what to do, what not to do, and what deserves investment next.

01 / Get unstuck

Digital Transformation Starting Point

For manufacturers that know improvement is needed but are stuck between competing systems, priorities and possibilities.

You leave with:current-state findings, prioritized opportunities, immediate actions and a practical roadmap.
02 / Connect the layers

OT / IT / MES Strategy

Define how equipment, controls, industrial data, MES/MOM and enterprise systems should work together.

You leave with:architecture direction, data/integration approach, system boundaries, modernization priorities and sequencing.
03 / Simplify the stack

Technology Stack Rationalization

Identify overlapping tools, duplicated capability, integration burden, commercial cost and support overhead.

You leave with:preserve / consolidate / integrate / retire / replace recommendations, dependency visibility, recurring-cost and support-burden insight, and a clearer path to lower complexity and risk.
04 / Choose well

Technology Fit, Vendor & TCO Evaluation

Evaluate software, equipment and emerging technology in the context of the real operation, architecture, support model, scaling requirements and lifecycle cost — not just the demo.

You leave with:requirements, fit/gap analysis, architecture impact, TCO considerations, risk/tradeoff analysis and a defensible recommendation.
How I think

Compound capability, not complexity.

A system can solve its local problem and still make the overall environment harder to operate. I look at whether each investment strengthens the whole operating model or simply adds another layer to manage.

Capability compounds when…

  • Data and integrations can be reused.
  • Common workflows make the next line, plant or use case easier to add.
  • Existing investments become more useful.
  • Users have fewer handoffs and clearer ways to do the work.

Complexity compounds when…

  • Every problem creates another application, contract or dependency.
  • Systems overlap while each still needs training, support and administration.
  • Integration and normalization grow faster than useful information.
  • Scaling multiplies interfaces, licenses, skills and recurring cost.
Follow the thread

Start at the point of use. Follow the impact vertically and horizontally.

A problem at the line can ripple through operators, maintenance, quality, planning, OT, IT, enterprise systems, leadership and economics. I am not solution-centric. I follow the problem until the actual constraint becomes visible. Operator reality, OT architecture, IT requirements and executive economics are often different views of the same issue.

01
OperatorsPeople doing the work
02
ProcessesHow work gets done
03
EquipmentAssets and physical systems
04
OT / InfrastructureControls, networks, collection
05
SystemsMES, ERP, QMS, CMMS
06
DataInformation and insight
07
EconomicsCost, productivity, value
08
BusinessDecisions and outcomes
How many systems are doing overlapping work?
Did the last investment eliminate work — or create more?
Are you using what you own before buying around it?
Are you making the right thing to do the easiest thing to do?
On your side of the table

Technology should be evaluated in your operation, not in the demo.

I can help define requirements, support RFP/RFI/RFQ work, participate in vendor interviews and demos, and challenge assumptions around integration, support, training, commercial terms, scaling and TCO.

Separate impressive capability from practical fit and measurable value.
Understand what a new investment replaces, duplicates or makes harder.
Pressure-test architecture, commercial and operational implications before committing.
Experience & results

Breadth matters when the problem crosses boundaries.

30+ years

Manufacturing technology

PLCs, SCADA and industrial networks through MES, SaaS and enterprise strategy.

~100

Customers

Built a manufacturing technology business serving almost 200 locations across 18 states and 13 countries.

12+ sites

Enterprise strategy

A narrow warehouse request expanded through discovery into roughly 30 operational and integration initiatives.

1.5+ sq. mi.

OT at physical scale

Controls and monitoring across major industrial utility infrastructure plus 2M+ sq. ft. of government facilities.

A narrow software request can be evidence of a much larger problem.

Started withA relatively small warehouse-management discussion.
Discovery revealedBroader operational, data and integration needs.
Strategy becameA multi-year direction spanning 12+ sites and roughly 30 initiatives.
The pointStart with the business problem. The product category may be only one piece of the answer.
How engagements work

Focused enough to move quickly. Deep enough to understand what actually matters.

Sometimes a few candid conversations make the path obvious. Sometimes the problem deserves a deeper investigation. The evidence should determine the effort, not a prepackaged consulting process.

Tony Kaczmarek
Tony Kaczmarek

OT depth. Software fluency. Business judgment.

I’ve spent 30+ years across manufacturing operations, industrial automation, OT/IT and enterprise software, including building and selling a manufacturing technology company.

My strongest contribution is translation: connecting what is happening in the operation to architecture, business value and a practical strategy leaders can act on.

Vendor agnostic and manufacturer advocate
Compound capability, not complexity
Follow the thread from point of use through leadership
Based in Southeast Michigan. Remote-first discovery and strategy, with purposeful on-site engagement when it materially improves the outcome.
Also useful when the problem sits on the other side of the table
For technology companies

Strong technology still needs a manufacturing story customers understand and buy.

I help technology companies translate capability into credible manufacturing use cases, customer value, demos, positioning, GTM and complex enterprise pursuits.

I help connect the technology to the operational problem, the buyer and the business case.

For consulting & integration partners

Bring me in where the problem crosses boundaries.

I can augment consulting and integration teams with manufacturing, OT and enterprise-software depth for discovery, architecture, technology evaluation, executive workshops and client pursuits.

Useful when the engagement needs someone who can move from the plant floor to the enterprise conversation.

Frequently asked questions

A few things worth knowing before we talk.

Do you sell or represent software?

No. P3ak is vendor agnostic. The best answer may be to use more of what you already own.

Do we need to know exactly what project we want?

No. In many cases, figuring out what the project should actually be is the engagement.

Can you work with our existing vendors and internal teams?

Yes. I can work alongside operations, engineering, IT/OT, integrators, software vendors, consultants and leadership.

Do you work on-site?

Yes, when seeing the operation materially improves the answer. Other discovery and strategy work can often begin remotely.

What if P3ak is not the right fit?

I’ll say so early, disengage rather than consume unnecessary time and, when I can, make a warm introduction to someone better suited.

Ways to work together

There is more than one way to bring me into the problem.

Engage P3ak

Direct consulting

For manufacturers that need an experienced, vendor-agnostic perspective on where to start, what to connect, what to preserve and what to do next.

  • Transformation starting point
  • OT/IT/MES strategy
  • Technology stack rationalization
  • Technology fit, vendor & TCO evaluation
Work with Tony

Senior strategic roles

I’m equally open to the right senior customer-facing role where manufacturing operations, OT/IT, enterprise software, discovery, solution strategy and business value come together.

  • Principal / strategic solutions consulting
  • Manufacturing technology strategy
  • Enterprise presales / solution strategy
  • Connected operations / digital transformation
Bring me something interesting

What problem are you trying to solve?

If your stack keeps getting bigger but the operation is not getting simpler — or the problem sits awkwardly between operations, OT, data, software, people and business value — I’d enjoy hearing about it.

Start with an email. Tell me what is getting in the way. You will talk directly with me, and we’ll figure out quickly whether I can help.

Email Tony →