Rebecca Horwitz
FORM
FUNCTION

I design the operating model, from customer interface to backend systems, so businesses scale without breaking.

Commerce architecture, pricing governance, ERP alignment, and workflow systems.

About 01

I work at the point where growth creates strain.

As businesses scale, product complexity increases, pricing models evolve, vendor networks expand, and systems multiply. What once worked through memory and manual coordination begins to fracture.

My role is to rebuild the operating model so the public-facing experience and the internal systems stay aligned.

I do not separate form and function. The customer-facing experience and the operational backbone are part of the same structure. When one evolves without the other, execution degrades.

My background spans design, manufacturing, and commerce. I have built and operated a product-based business end to end, with responsibility for production, inventory, wholesale, ecommerce, and fulfillment. That experience shapes how I think about margin, constraints, and delivery.

Today, my work includes:

Product and catalog architecture · Pricing and margin governance · ERP and ecommerce alignment · Vendor and supply chain controls · Automation frameworks · AI-assisted internal systems and knowledge management

I define ownership, protect high-risk identifiers, establish source-of-truth datasets, and design escalation pathways. The objective is operational continuity under growth.

Rebecca Horwitz Geneva, Switzerland
Working internationally
Selected Work 02
Operating Logic 03

Operational Leadership Mandate

01 Business Context
The company is growing
Complexity has increased
More teams, tools, and stakeholders are involved
Early-stage processes no longer scale
02 Observed Friction
Manual work expanding across teams
Inconsistent workflows and undocumented logic
Information stored across disconnected systems
Execution dependent on individual memory
Misalignment between customer experience and operational reality
03 Scope of Responsibility
Clarify how the business model translates into execution
Establish a maintained source of operational truth
Design repeatable, cross-functional workflows
Define tool roles and system boundaries
Create governance for planning, prioritization, and delivery
Reduce operational risk as the organization scales
04 Outcome
Clear ownership and accountability
Fewer points of failure
Reliable cross-team coordination
Systems that hold under growth pressure
Infrastructure that supports long-term scale
Contact 04

Working through something complex?

Share a bit about your product, team, and the friction you're experiencing. I'll respond personally.