SMStefan MihovSystems & AutomationDesign portfolio ↗

Client implementation · Anonymized

From fragmented ordering to a connected operating workflow.

A year-long implementation for a European B2B supplier. What began as a website and structured order flow evolved into the operational layer connecting customers, orders, documents, shipping, inventory and management visibility.

RoleSystem design & implementationProcessed≈250 ordersOrder value€500k+Reach20+ countries

01 · Context

The bottleneck was not one task. It was the chain of manual handoffs.

Orders arrived mainly through calls and email. Staff then had to interpret them, recreate the information elsewhere, prepare documents, coordinate shipping, update stock and reconstruct customer history whenever context was needed.

INPUT

Unstructured ordering

Different customers supplied different information in different formats, making every order partially manual.

HANDOFFS

Repeated administration

The same facts moved through multiple tools and documents, creating duplication and avoidable checking.

VISIBILITY

Operations were hard to see

Customer history, stock, fulfilment and sales patterns existed, but not as one usable operational picture.

02 · Evolution

The system grew with the business problem.

I did not begin by proposing a monolithic platform. Each stage removed a real operational friction point and created the foundation for the next.

PHASE 01Brand + Webflow

Rebuilt the public digital experience and created a structured way to select varieties and quantities.

PHASE 02Order automation

Connected web submissions through Zapier into structured Sheets records and automated confirmations.

PHASE 03Operations application

Built the AppSheet CRM/order-management layer around the real internal workflow.

PHASE 04Integrated operations

Added document logic, shipping APIs, inventory rules, signatures and analytics as the system matured.

03 · Architecture

Simple tools, deliberately connected.

The implementation used accessible technologies the client could realistically operate. The sophistication sits in the workflow between them.

Selected layer

04 · Operating system

One interface for the operational context that used to be scattered.

This is a reconstructed demonstration using synthetic data. The actual application and records are client-owned and confidential.

Reconstructed operations console · synthetic data
Order intakeStructured
StatusTracked
ConfirmationAutomatic
#DEMO-1042GermanyProcessing
#DEMO-1041FranceReady
#DEMO-1040NetherlandsReview

05 · Ownership

I owned the path from an ambiguous operational problem to a working system.

DISCOVER

Mapped the real workflow

Worked directly with the client to understand orders, customers, documents, shipping, inventory and exceptions.

DESIGN

Defined architecture and rules

Selected the stack, structured the data and translated business behavior into system logic.

BUILD

Implemented end to end

Built interfaces, automations, API integrations, document flows, stock logic and dashboards.

ENABLE

Tested, trained and iterated

Debugged edge cases, documented the system and refined it as operational needs changed.

06 · Evidence

A live workflow supporting real cross-border orders.

Developed iteratively over roughly one year, the ordering and operations workflow has processed approximately 250 orders representing more than €500,000 in value across 20+ countries.

Orders processed0
Order value0
Countries0
Build evolution~1 year