I architect the systems
that run the business.
I build the backend systems that companies depend on but don't want to think about. Pricing engines, data pipelines, infrastructure that runs without someone watching it. I take responsibility for the system's outcome, not just its delivery.
How I Work
Infrastructure Design
I once built a pricing pipeline on a single Postgres instance. It worked until the catalog hit 4,000 products and the daily sync started timing out. Now I design for the data volume I'll have in a year, not the data I have today.
Autonomous Systems
The first version of my pricing engine ran silently for two weeks with a 30% miss rate. Nobody noticed because it never threw an error. Now every pipeline I build checks its own output and alerts when coverage drops.
Technical Strategy
Picking SQLite over Postgres when the data fits. Choosing batch over real-time when latency doesn't matter. Saying no to microservices when a monolith ships faster.
Crisis Management
A wallbox pricing bug slipped through to production because I skipped the data and went straight to the code. Three hours of debugging later, I found a single ordering issue in the pipeline. Now I always start with the data, not the logic.
Client Feedback
“He was experienced enough to explain that we had to take the project in a different direction than what I thought and he delivered.”
“First class work...very quick and accurate.”
“Prompt, easy communication, great output. Will hire again.”
Selected Engagements
Centralized Property Intelligence Hub
A UK property technology company had built four separate microservices to handle different aspects of their data pipeline: one scraped Rightmove listings, one processed floorplans, one ran AI-powered image condition analysis, and one generated a universal identifier linking all three together. Each service had its own Supabase PostgreSQL database.
Idealo Price Optimization Platform
A German e-commerce seller was listing products on Idealo.de, Germany's largest comparison shopping platform. This is the same retailer whose supplier-to-store pricing pipeline I automated separately.
Inselvolt Pricing Engine
A German solar equipment retailer was running a Shopify store with over 4,000 products sourced from 13 different wholesale suppliers. Every morning, someone on the operations team would open supplier price lists, compare them against the current store catalog, update prices by hand, check competitor listings on Idealo, and adjust margins accordingly.
NBA Scenario Engine
In the NBA player prop market, the money is in the minutes between news and line adjustment. A star player gets ruled OUT on Twitter.
Frequently Asked
What kinds of problems do you solve?
Pricing engines that replace manual spreadsheet work. Data pipelines that pull from unreliable supplier APIs and normalize messy formats. Infrastructure that monitors itself and recovers without someone watching it.
How do you work with teams?
I work as an embedded technical partner or independent architect. For early-stage companies, I design the entire system. For established teams, I audit existing architecture and design the next iteration. I stay involved through deployment and production.
What industries do you specialize in?
E-commerce infrastructure, pricing systems, and data-heavy automation. Companies that process large volumes of product, pricing, or supplier data and need that processing to be reliable and fast.
Get Notified
New system breakdown? You'll know first.
Have a system that needs architecture?
Let's talk about what you're building.
Get in Touch