Rodd Dierker · making computers work for more than 45 years

I build the systems businesses run on.

For twenty years, I ran an independent software practice serving small and midsized businesses. Most projects were mine end to end: content management, shopping carts, inventory tools, customer and administrative portals, and the systems connecting them — often before those categories had settled names.

Then I moved inside a national industrial supplier — decades of data, half a million SKUs — and spent more than a decade operating commerce systems at scale, including an Amazon Marketplace channel I built and led past $30 million in annual marketplace sales.

Today I bring both perspectives to the same intersection I’ve worked my whole career: where software, commerce, and operations meet.

The short version

Four areas. One practice.

The systems a business sells through, the systems it runs on, the software shaped around its operations, and the AI increasingly working inside them.

Amazon, Walmart, and storefront channels connect through an integration layer to Odoo ERP handling catalog, inventory, pricing, and accounting. An AI layer for enrichment and digitization works alongside the integration layer. Amazon Walmart Storefront integration layer AI layer enrichment · analysis · digitization Odoo ERP catalog · inventory · pricing · accounting
fig. 1 — one connected system, not a hodgepodge of disconnected tools

01 · commerceCommerce & Marketplace Systems

Amazon and Walmart operations, storefront e-commerce, catalog automation, pricing, inventory, and the connections between sales channels and back-office systems.

02 · erpERP & Connected Operations

Odoo implementation and customization, data migration, and integrations connecting commerce, inventory, purchasing, and accounting.

03 · systemsCustom Business Systems & Portals

Websites, customer portals, admin tools, order entry, inventory and workflow applications — software shaped around how the business actually works.

04 · applied aiApplied AI

AI in the development process and inside working systems, aimed at defined operational outcomes.

For the record

  • 1981 First computer; self-taught from the start
  • 1996 Two decades of solo practice: architecture, code, hosting, servers, and support
  • pre-cloud Browser-based inventory and sales systems, built before “the cloud” was vocabulary
  • 10+ years Operating commerce systems at scale from inside the business
  • $30M+ One marketplace channel, from first listing to peak annual sales
  • 500K SKUs in the catalog behind the systems I run today
  • now Leading a full ERP migration to Odoo — and building applied AI into the systems themselves
How I build now

AI provides leverage. Experience decides where to apply it.

I use AI throughout research, prototyping, implementation, and testing. It helps me explore more approaches, automate repetitive work, and cover more edge cases in less time. It can surface possibilities quickly; I decide which ones matter in the actual workflow.

I remain responsible for the architecture, security, correctness, and final result. I decide what to trust, what to verify, and what deserves closer examination.

Increasingly, AI is not only part of how I build; it is part of what I build — modules aimed at specific operational goals, not AI for its own sake.