Back to portfolioEDRA Ecommerce

EDRA Media LLC / Internal SaaS / Product Strategy & Operations

From a Full Day of Manual Operations to Under 40 Minutes

Designing and building a connected operations platform that brings publishing workflows, inventory, Amazon orders, fulfillment, accounting preparation, and marketing intelligence into one system.

At EDRA, I was responsible for work that extended across ecommerce, marketing, logistics, inventory coordination, and customer operations.

Each workflow involved separate platforms, spreadsheets, manual reconciliation, and constant switching between tools.

What began as an operational efficiency problem became a product opportunity.

I designed and developed an internal operations platform to bring these processes together, reduce repetitive work, improve data visibility, and create more time for the strategic decisions that drive the business forward.

Today, the daily operational routine that previously occupied much of my workday can be completed in under 40 minutes at a good pace, based on my operational estimate.

The platform provides a centralized view of the business, connecting inventory, orders, fulfillment, customer operations, and marketing performance.

Explore the Platform

The internal EDRA operations dashboard, captured November 2026. Order references are pixelated for privacy.

Organization
EDRA Media LLC / EDRA Publishing operations
Product
Internal business operations SaaS-style platform
Tools
Base44, Figma, Photoshop
Role
Product Creator, Product Strategy, UX/UI, Workflow Architecture, AI-Assisted Implementation & Operations
Users
Internal publishing, ecommerce, marketing, and operations functions
Status
Working internal platform with ongoing development
Focus
Automation, systems integration, business intelligence, and operational efficiency

01.The Challenge

The work wasn't difficult because of one task. It was difficult because everything was disconnected.

Managing a specialist publishing business means coordinating multiple systems every day.

Amazon Vendor Central provides purchase orders. Warehouse systems provide inventory and shipping information. Ecommerce platforms capture orders. Accounting workflows require structured data. Marketing platforms produce acquisition and campaign reports.

Each system performs an important function, but the information needed to make a business decision can be scattered across all of them.

Before the internal platform, much of my working day was consumed by operational execution. Processing orders, checking stock, coordinating shipments, updating customers, handling Amazon-related work, moving lead information, and gathering marketing performance data left limited time for higher-value analysis.

The central problem was not simply the number of applications. It was the amount of human effort required to make the applications work together.

01

Manual process overload

Routine tasks required repeated checking, data entry, reconciliation, and communication.

02

Fragmented visibility

Inventory, order status, logistics, ecommerce, and marketing information lived in different systems.

03

Delayed decisions

When information has to be assembled manually, identifying the next priority requires additional time.

04

Limited strategic capacity

Operational responsibilities competed with the time needed for product strategy, creative development, competitor research, and growth decisions.

The opportunity

Build one internal product that turns disconnected tools and recurring manual activities into clearer, more coordinated workflows.

The objective was not to replace every external business system. It was to create the operating layer that connects them.

02.The Strategy

Build a command center, not another dashboard.

I approached the problem as a product designer and business operator.

The important question wasn't how to display more information. It was how to make recurring work easier to complete, make exceptions easier to identify, and make the next decision clearer.

The product vision centered on three objectives.

1

Consolidate operational context

Create one place to access the workflows and information needed to run the business.

2

Reduce repetitive work

Automate or simplify tasks such as purchase-order processing, inventory checks, shipment communication, and reporting preparation.

3

Turn information into decisions

Bring operational and marketing KPIs closer together so I could spend more time identifying commercial opportunities and less time collecting data.

The best internal tool does not necessarily display the most data. It makes the most important work easier to complete.

03.My Role

Translating business problems into working software.

I defined the problems because I worked directly with the processes every day.

That gave me visibility into where time was being lost, where information was disconnected, and which activities were preventing the team from moving faster.

My work included defining the product vision, mapping processes, designing interfaces, prioritizing functionality, coordinating data requirements, and using AI-assisted development to implement and refine the platform.

I am not positioning myself as a traditional software engineer. My strength is understanding the business and the people using the system, then turning that knowledge into a coherent product.

My process and the capabilities behind each step

  1. 01

    Discover

    Observe how the work is actually performed, identify repetitive tasks, and locate missing information.

    Product Discovery · Cross-Functional Coordination

  2. 02

    Analyze

    Study relevant operational data, KPIs, bottlenecks, errors, and workflow dependencies.

    Operations Analytics · Data Quality

  3. 03

    Research

    Investigate available technologies, competitor solutions, and possible implementation approaches.

    Product Strategy

  4. 04

    Architect

    Map workflows, organize information, define data requirements, and establish the relationships between system modules.

    Workflow Mapping · Technical Requirements · Systems Integration

  5. 05

    Design

    Create user journeys, interfaces, dashboard structures, and task-specific experiences.

    UX/UI Design

  6. 06

    Implement

    Use Base44 and AI-assisted development to build and integrate the product, testing its workflows against the business process.

    AI-Assisted Development · Business Process Automation

  7. 07

    Iterate

    Review outputs, identify errors or friction, improve usability, and expand capabilities as requirements evolve.

    Product Iteration

04.Product Architecture

One platform. Multiple connected business functions.

A

Operations and fulfillment

  • Amazon Vendor PO workflow
  • Warehouse inventory visibility
  • Maple Logistics order and shipment operations
  • Operations Hub
  • International orders
  • Commercial invoice preparation

B

Finance and administration

  • Odoo Converter
  • Accounting data preparation
  • Operational reporting

C

Marketing and commercial intelligence

  • Meta Ads performance
  • AttributionROI
  • Campaign and lead reporting
  • Product catalog visibility
  • Commercial decision support

D

Management and assistance

  • Main operations dashboard
  • Live activity and status indicators
  • AI-assisted operations interface
  • Convention tools
  • Settings and role-based application functions

Maturity varies: Not every module has the same automation level or integration method. Some workflows use file uploads and structured transformations; others use connected data or synchronization.

How information moves

Data and external systems

  • Amazon Vendor
  • Warehouse inventory sources
  • Maple Logistics
  • Ecommerce order records
  • Meta Ads and leads
  • Accounting files and requirements

EDRA internal operations platform

  • Data ingestion
  • Validation
  • Product / ISBN mapping
  • Workflow processing
  • Status visibility
  • Reporting and analysis

Business outputs

  • Purchase-order availability decisions
  • Inventory visibility
  • Fulfillment and tracking workflows
  • Accounting-ready files
  • Campaign and revenue analysis
  • Operational priorities

Conceptual diagram of the information flow. It does not describe specific databases, authentication, or API connections.

05.The Solution

Turning complex operations into focused experiences.

Each workflow below pairs the problem being solved with the process I designed and the operational value it created. Screens are real captures of the internal application.

01.The operations command center

One place to understand what needs attention.

The dashboard acts as a central entry point for the business's operational activities.

Instead of navigating several disconnected applications before beginning work, the user can access core processes through a consistent structure.

The layout organizes modules by business function while also displaying relevant operational activity and status information.

UX details

  • Clear functional categories
  • Large, recognizable workflow entry points
  • Active operations panel
  • Consistent visual hierarchy
  • Status indicators
  • Role-aware workspace elements

Principle: A status shown in the interface reports activity. It does not mean that operation runs fully autonomously.

Design decision

Prioritize clarity, grouping, and direct access to business tasks over displaying every available metric on one screen.

Product value

Reduced navigation complexity and a more coherent overview of operational activity.

02.Amazon purchase order processing

From purchase-order files to inventory decisions.

Amazon PO Availability workflow, session captured November 2026. Purchase-order and vendor codes are pixelated for privacy.
41
Purchase-order rows loaded in the captured session

An example of processed input, not a claim about order volume or time saved.

Amazon Vendor orders require checking requested items against available stock and identifying the products that can be fulfilled.

The application organizes this into a step-by-step experience, with visible progress and a structured representation of the source data.

Workflow

  1. 1.Upload the Amazon Vendor purchase-order file.
  2. 2.Upload or retrieve the relevant inventory data.
  3. 3.Review product identifiers and mapping.
  4. 4.Run the availability check.
  5. 5.Review and export the results.

Principle: Automation must preserve the ability to inspect exceptions, review mismatches, and validate the result before a business action is finalized.

Design decision

Transform a spreadsheet-heavy task into a guided and reviewable sequence.

Product value

Less manual comparison, clearer verification, and a structured output for the next operational step.

03.Multiwarehouse inventory

Inventory visibility across different markets.

Live Inventory dashboard, captured November 2026. The United States source is synchronized automatically; Canada and Italy are updated by manual upload; France is marked as coming soon.
612
ISBNs tracked
327
ISBNs in stock
122
ISBNs at low stock
22,461
Total units

U.S. warehouse snapshot, November 2026. Snapshot values, not permanent inventory quantities.

Inventory is one of the most important inputs into publishing operations. It affects sales decisions, availability, promotions, fulfillment, and the information shown to customers.

The platform brings warehouse-level information into a centralized interface, with sections for the United States (Maple Logistics), Canada, Italy, and France.

Experience details

  • Stock search and filtering
  • Warehouse selection
  • Availability counts
  • Low-stock indicators
  • Inventory synchronization status
  • Monthly stock movement view
  • Warehouse comparison view
  • Export and audit options

Design decision

Make stock conditions immediately visible while allowing users to inspect detailed records and warehouse-specific information.

Product value

Better operational visibility for order processing, availability checks, and merchandising decisions.

04.Order management and fulfillment

Connect the order to the customer experience.

The platform brings order-related processes closer to warehouse and shipping information.

Workflows cover order processing, shipment status, tracking information, and customer communication.

This reduces the need to repeatedly gather information from different sources before responding to a customer or checking an order.

Modules on the dashboard

  • Maple Orders: shipments and tracking
  • Operations Hub: ecommerce and direct orders

Design decision

Organize the workflow around the order's operational state rather than around separate software tools.

Product value

More coordinated order follow-up, better visibility, and reduced repetitive communication.

05.International and accounting workflows

Make operational data usable across systems.

Publishing operations may involve different markets, shipping requirements, and accounting formats.

The internal platform includes modules for international order handling, commercial invoice generation, and converting operational data into a structure suitable for accounting workflows.

Modules on the dashboard

  • International Orders: order conversion
  • Commercial Invoice: PDF invoice generator
  • Odoo Converter: converts data into an Odoo template

Principle: The Odoo Converter produces a converted, template-compatible file. It is file conversion, not automated accounting synchronization.

Design decision

Simplify repetitive document preparation and reduce unnecessary reformatting between systems.

Product value

More consistent administrative workflows and less manual preparation.

06.Growth Marketing & Attribution

Connecting acquisition activity to actual commercial evidence.

Cheap leads are useful. But are they actually becoming customers?

As a growth marketer, I could measure campaign spend, leads, and cost per lead. Those metrics were valuable, but they did not answer whether the acquired leads generated downstream purchases.

I developed AttributionROI to connect acquisition data, lead records, and ecommerce order information in one analysis environment.

edra/AttributionROI
Anonymized view

Total Spend

$3,932.89

all-period

Total Leads

1,961

all-period

Total Avg CPL

$2.01

under $3 target

Total Campaigns

6

distinct canonical campaigns

Total: Monthly Trend

Leads and spend per month with CPL trend

By Month
JanFebMarAprMayJunJulAug015030045060000.40.81.21.6
  • Leads
  • Spend ($)
  • CPL ($)

Campaign Totals Across Active Months

Duplicate uploads for the same month replace old rows instead of double counting.

Canonical campaignMonths activeLeadsSpendWeighted CPLVariants
Campaign AJan · $0.00Apr · $194.47May · $276.89319$788.38$2.473
Campaign BApr · $85.08May · $187.32Jun · $153.49419$785.33$1.871
Campaign CJan · $100.82Feb · $92.69Mar · $103.42280$766.67$2.742
Campaign DJan · $102.19Feb · $82.81Mar · $101.65576$760.41$1.321
Campaign EJan · $102.19Jun · $85.42Jul · $97.09168$466.60$2.781

AI Insights: Campaign ROI Analysis

Benchmarks pulled from industry reports

Analyze with AI

Total Spend

$3,932.89

Saved Lead Rows

1,810

Attributed Orders

1

Verified Revenue

$68.27

Assisted Revenue

$2,697.15

ROI

-98.3%

CampaignSpendLeadsVerifiedAssistedROI
Campaign A$365.50200$34.13$836.80-90.7%
Campaign E$466.60174$34.13$0.00-92.7%
Campaign C$766.67204$0.00$1,231.61-100.0%
Campaign D$760.41458$0.00$628.74-100.0%

Anonymized AttributionROI campaign view.

What the module supports

  • Campaign spend and lead reporting
  • Canonical campaign organization
  • Monthly reporting and trends
  • Cost-per-lead analysis
  • Lead record ingestion
  • Ecommerce order-data comparison
  • Verified attribution
  • Separately identified assisted or contextual matches
  • Campaign-level revenue and ROI analysis
  • AI-assisted interpretation of reporting data

A critical product decision: attribution confidence

Verified attribution

Purchases connected to campaign or lead information using the defined verification methodology, including verified email-based matches where available.

Assisted or contextual matches

Potential relationships identified through other signals, such as product-title relevance, that should not be represented as confirmed attributable purchases.

Why it matters: Misleading attribution produces misleading marketing decisions. A low verified figure may also reflect incomplete identity matching or tracking coverage, not necessarily an absence of commercial value.

1,961
Reported leads
$2.01
Average cost per lead
6
Canonical campaigns

Historical January to August 2026 campaign reporting shown by the tool. These are campaign performance statistics, not improvements caused by the platform.

07.Results & Business Impact

Less repetitive work. More time for better decisions.

Before

Much of the workday

Manual recurring operational tasks

After

Under 40 minutes

Estimated time for the streamlined daily routine

Greater operational capacity and more time available for analysis, product strategy, and growth execution.

Methodology: The under-40-minute figure is my operational estimate for the recurring daily routine, not the result of a formal time-and-motion study. The earlier baseline was much of the working day, so no percentage reduction is stated.

Before

Day-to-day operational responsibilities consumed much of my working day.

Tasks included order processing, inventory coordination, shipment communication, customer responses, Amazon operations, lead management, and assembling marketing information.

The issue was not a lack of data. It was the amount of work required to collect, reconcile, and act on it.

After

With the connected platform and its streamlined workflows, I can now complete the recurring operational routine in under 40 minutes at a good pace.

This change gives me more capacity to work on activities that depend on judgment and creativity.

  • Studying business performance and KPIs
  • Identifying product and customer opportunities
  • Researching competitors
  • Evaluating possible solutions
  • Planning new product improvements
  • Developing growth and creative strategies
  • Acting on the most relevant commercial opportunities
The most meaningful result of automation isn't simply completing a repetitive task faster. It's being able to redirect attention from gathering information toward making decisions.

08.Product Management

Data is valuable when it changes what you do next.

I don't approach KPIs as numbers to collect for reporting alone.

I use them to identify a problem, picture possible solutions, and determine where the business should focus next.

With better access to operational and marketing information, I can move more directly from understanding what is happening to evaluating what should happen.

  1. 01

    Observe

    Review current business activity, sales, inventory, fulfillment, and campaign data.

  2. 02

    Identify

    Recognize bottlenecks, missed opportunities, performance changes, or recurring operational problems.

  3. 03

    Investigate

    Research customer behavior, competitor approaches, alternative technologies, and relevant market signals.

  4. 04

    Prioritize

    Evaluate opportunities based on business relevance, expected user value, feasibility, and operational urgency.

  5. 05

    Implement

    Design and build a practical solution within the product ecosystem.

  6. 06

    Validate and iterate

    Test the workflow, inspect the results, correct problems, and refine the experience.

Product principle

A useful system should help people move from information to action.

For EDRA, connecting the systems made it possible to dedicate more working time to analysis, ideation, creative problem-solving, and strategic decisions.

09.Key Decisions & Trade-offs

The decisions that shaped the platform.

Decision 01

Integrate rather than replace

Problem
Existing external systems already performed specialized business functions.
Decision
Build a centralized operating layer that works with those systems instead of trying to recreate every service.
Reason
Preserve established business tools while reducing the effort required to use them together.

Decision 02

Guide complex processes step by step

Problem
Purchase-order and inventory workflows require validation and careful handling.
Decision
Use structured, reviewable stages with visible progress and outputs.
Reason
Simplify complex work without sacrificing operational control.

Decision 03

Prioritize accuracy over attractive reporting

Problem
Marketing attribution can confuse verified purchases with possible relationships.
Decision
Separate verified attribution from assisted or contextual matches.
Reason
Support more defensible decisions, even when the available data produces an incomplete or disappointing result.

Decision 04

Build around the operator's workflow

Problem
Switching between systems creates unnecessary cognitive and operational friction.
Decision
Group functions by how the business uses them, with clear navigation, status indicators, and purpose-built task screens.
Reason
Help the user complete work, not merely admire dashboards.

10.Evidence & Measurement

A working product with visible operational evidence.

01

Operational outcome

  • Recurring daily operational routine completed in under 40 minutes.

Source: My operating experience and estimate.

02

Product scope

  • Central operations dashboard
  • Amazon PO processing
  • Inventory availability checks
  • Multiwarehouse inventory visibility
  • Shipping and fulfillment modules
  • International order and commercial invoice tools
  • Odoo data conversion
  • Marketing performance and attribution reporting

Source: Captured screens of the internal application.

03

Historical reporting examples

  • 612 ISBNs and 22,461 inventory units in the captured U.S. warehouse snapshot.
  • 1,961 reported leads across six campaigns in a historical marketing reporting period.

Source: Stock snapshots and campaign metrics displayed by the platform.

Measurement integrity: The reporting examples show the platform's reporting scope. They do not establish that the software created those leads, increased stock, or generated incremental revenue. Where controlled measurement is unavailable, this page describes the actual product capability or the operator-observed result, and states no percentage, revenue, or error-rate improvements.

11.Next Steps

From workflow automation to a more intelligent operating system.

The platform is an evolving product.

Its next opportunities should be prioritized according to business value, the reliability of available data, and the actual workflow needs.

Potential direction

Operational exception management

Make failed imports, inventory mismatches, or shipment exceptions easier to detect and resolve.

Potential direction

Data reliability

Strengthen reconciliation and visibility across connected sources.

Potential direction

Attribution confidence

Improve the completeness and quality of lead-to-purchase matching, with transparent confidence rules.

Potential direction

Decision support

Develop more useful contextual recommendations for operational and commercial decisions.

Potential direction

Workflow measurement

Measure manual interventions, process duration, and operational error rates more consistently.

Potential direction

Safe AI assistance

Expand AI-assisted analysis where outputs can be reviewed and verified before affecting business operations.

Planned, not shipped: These are optimization opportunities, not claims that every capability is already implemented or autonomous.

12.What I Learned

Product leadership starts with understanding the problem.

The EDRA internal operations platform grew from a real business challenge. I worked with disconnected systems, repetitive daily processes, and fragmented information.

Rather than continuing to accept those limitations, I translated the problems into a product strategy and built an integrated working environment around the business's actual needs.

The result is a platform that brings operational workflows together, provides better access to decision-making information, and substantially reduces the time I spend on recurring manual work.

It demonstrates how I combine product thinking, UX design, business knowledge, AI-assisted implementation, and growth analytics to deliver functional digital products.

I don't believe technology creates value simply by adding more features. It creates value when it removes friction, improves decisions, and gives people more capacity to focus on what matters.
Explore EDRA EcommerceView Growth Marketing WorkBack to Selected Projects