Harry J. Epstein Company

Context

Harry J. Epstein Company is an 80+ year-old industrial tool business with deep customer trust, a distinctive public voice, and institutional knowledge spread across people, inventory practices, product history, vendors, and customer conversations.

The work was a long-running implementation problem, not a website refresh: participate in modern e-commerce without flattening the specificity, humor, and product judgment that made the business valuable. Product knowledge needed a useful public form, while analytics, marketing, content, customer communication, and operations needed to work as one maintainable system.

What I did

Jamie maintained and improved the web and e-commerce presence, supported analytics and marketing, structured reusable content patterns, translated between technical and nontechnical needs, and turned recurring operational questions into clearer workflows.

In practice, that meant clarifying requirements, shaping product information for customers, coordinating incremental releases, interpreting what analytics could and could not establish, and keeping the public experience aligned with the company's voice. The product-operations work joined customer experience, internal habits, content, marketing, and technical stewardship without exposing sensitive operating detail.

1. 01

   Listen

   A customer or team question reveals friction in product information, publishing, commerce, or follow-up.

2. 02

   Frame

   Jamie translates the question into a bounded requirement and names what available analytics can and cannot establish.

3. 03

   Implement

   The team ships an incremental change to content patterns, product information, marketing, or the e-commerce surface.

4. 04

   Verify

   Jamie inspects the public customer path and reviews operational or analytical signals with stakeholders.

5. 05

   Continue

   Reusable patterns, ownership, and next actions preserve the work for staff and later maintainers.

Boundary: Derived from the governed public claim set. It is not an original company document and exposes no customer data, private analytics, revenue detail, vendor terms, credentials, or sensitive operating practices.

What became usable

Customers gained a more coherent surface for finding products, understanding the company's point of view, and ordering. Internal stakeholders gained more repeatable patterns for product communication, marketing, e-commerce operations, and customer follow-up.

Outcome and proof

Jamie's work contributed to 2x revenue growth while helping translate legacy operating knowledge into durable digital workflows. The public storefront is inspectable below; private dashboards, revenue breakdowns, customer data, and internal operations remain private.

For hiring teams, this is private-sector proof of technical project management, product operations, business analysis, stakeholder translation, incremental implementation, and long-term systems stewardship.