Home
← Gradient

Gradient

Leading the Website Buildout

Our old website, built on Odoo ERP, was beginning to fail under millions of SKUs. So I led the design and implementation of RM, the repack marketplace, standing it up as our main point of sale on architecture patterns built to hold billions of cards.

  • $102Krevenue, Jul 12 – Aug 31
  • 4,055paid orders
  • 7 weeksfrom launch
Sales summary
Paid orders only.
Daily revenue and orders
New against repeat buyers.

Decisions

  • AWS ECS for hosting, RDS Postgres for the database. Managed Postgres was easier to scale and back up.
  • Terraform for deployment, which works better for LLM coding.
  • CloudFront over S3, with transcoded and obfuscated images for safety and speed.
  • Integrated the user base and inventory locations from Odoo, since Odoo is the source of truth for that data. I did not want to rewrite inventory or fully migrate the user base.
    • I wrote the API layer that connected the two services.
  • Synced card data from MongoDB, our source of truth for identity.
    • I wrote the sync service that updates cards live, at 1000/s capacity.
Service architecture diagram for the marketplace
What talks to what: the RM repo, the Odoo repo, Stripe, and RDS.
Entity relationship diagram for orders, wallets and users
ERD for orders, wallets, and users.

The team did most of the actual website implementation. I did most of the integration with external services like MongoDB, Odoo, and Stripe, and kept tasks flowing down from above to keep everyone on track. I was working on plenty of other data and robotics problems while this was being built.

Marketplace homepage
Homepage.
Grid of card listings with prices
Every listing is a robot scan, priced live.
← Back to Gradient