Production Web & Integration Work
RiteWipe + CrowDevelopment client systems.
01Problem
Operating businesses accumulate brittle web stacks: a WordPress site with stale plugins, a Shopify storefront fighting CRM/ERP sync, scraping tasks running on someone's laptop. The work is unglamorous but it's what keeps revenue moving.
02What I built
A curated case study of production systems: WordPress stabilization, Shopify Hydrogen rebuilds, CRM/ERP integrations between HubSpot and NetSuite, Python scraping and data pipelines, AWS-hosted automation, and IT administration.
03Highlights
- 01
Shopify Hydrogen storefront migration replacing legacy theme
- 02
NetSuite SuiteScript + HubSpot CRM integration (bidirectional contact + order sync)
- 03
Python (Scrapy + Selenium) data pipeline running on AWS EC2 with Pandas-based transforms
- 04
WordPress stabilization: plugin audit, security hardening, performance pass
- 05
Microsoft Intune + Entra ID administration with SSO / SAML rollout
04Outcomes
- The RiteWipe storefront now runs on a Shopify Hydrogen build serving live production traffic at ritewipe.com, retiring the legacy theme.
- HubSpot and NetSuite stay in sync through SuiteScript-driven bidirectional contact and order flow, removing manual re-entry between CRM and ERP.
- Scraping and data-transform jobs moved off a local machine onto scheduled AWS EC2 pipelines, and the team runs on Intune + Entra ID with SSO / SAML.
05Stack
06Status
Live client production work.
07What this demonstrates
Real-world judgment: stabilizing legacy stacks, integrating SaaS systems with custom code, building automation that runs in production, and operating IT infrastructure end-to-end.
08Author's note
Operational systems work is judgment-heavy: stabilize first, instrument second, refactor only where it pays. Most of the value is unromantic plumbing that keeps revenue moving.
4 min read