On this page
The project existed because DME providers needed storefronts, inventory, order processing, catalogs, customer accounts, and search, but the only option was an expensive custom build per business. The platform had to onboard providers quickly while letting each keep operational independence — own branding, pricing, business rules, and their own banking relationship for payments — all on shared infrastructure, in an era with none of the tooling that makes this routine now. The source summary is: Built, solo, a multi-tenant hosted commerce platform for DME Providers in Miami, FL, that let Durable Medical Equipment providers launch and run online storefronts without commissioning a custom website. The problem it solved was market timing: in 2001 every business website was a bespoke build costing thousands and taking weeks, and there was no hosted alternative — so the work was making one platform serve many independent merchants. The role was: Sole technical employee and full-stack architect — system and database architecture, multi-tenant design, DNS routing, storefront publishing, auth, payment routing, catalog, CRM, search, reporting, deployment, and support. Worked from leadership's business goals and designed the platform independently; also trained the onboarding, sales, and operations staff. The work sat squarely inside the existing business, so the goal was never to add complexity for its own sake.
Operating flow
- Map the current system and the constraint first.
- Choose the smallest change that can hold the load.
- Build against the real workflow instead of a toy case.
- Roll it out with enough monitoring to catch the edge cases.
This series follows the build in the order it happened: discovery, the solution direction, the implementation steps, and the operational result. Each post stays on one decision or one build step so the reader can see how the system moved from the initial constraint to a working result.
The details come from the project files and the company context, not from a generic template. That keeps the story grounded in the mechanics of the work: what was built, what it replaced, and what changed when it shipped.
The implementation stayed close to ColdFusion, MS SQL Server, IIS, HTML/CSS/JavaScript because the new system still had to live inside the same operating environment as the old one. That kept the work from drifting into a clean-room exercise that would look better on paper than it would in production. The practical question was always whether the implementation could hold up under the real workflow and the real users. If it could not do that, it was not finished.
The constraint behind the step was that DME providers needed storefronts, inventory, order processing, catalogs, customer accounts, and search, but the only option was an expensive custom build per business. That is why the work had to trade one kind of cost for another instead of trying to eliminate cost altogether. In almost every case, the useful move was to spend a little more effort on clarity, validation, or control so the business would spend less effort on repeated manual work later. That is the pattern the project files keep pointing to.
The role in the work was Sole technical employee and full-stack architect — system and database architecture, multi-tenant design, DNS routing, storefront publishing, auth, payment routing, catalog, CRM, search, reporting, deployment, and support. That meant the implementation could not stop at the code boundary because the operating model, handoff, and support path were part of the outcome. The relevant outcome was ~300 storefronts within 24 months, including multi-location operators running several storefronts each. The build only earns its place if the new result is visible in the way the business works after launch.
The specific step in this article was Built, solo, a multi-tenant hosted commerce platform for DME Providers in Miami, FL, that let Durable Medical Equipment providers launch and run online storefronts without commissioning a custom website. That is the piece that moves the story from analysis into execution. It is also the part that shows the difference between a conceptual fix and a system people can actually use. That distinction matters more than style or novelty.
The point is to show how the system works, not to turn the project into a slogan or a summary stub.
When the architecture changes, the real question is what the new system allows the business to do that the old one could not. That shows up here in throughput, reliability, operating cost, turnaround time, and how much manual work disappears once the workflow is redesigned.