One Engineer. Entire Business Platform.
How I owned a 4M+ line production CRM/ERP platform supporting sales, leasing, listings, deals, compliance, HR, finance, call center operations, dashboards, automations, integrations, and day-to-day business workflows.
PRODUCTION · LIVE SYSTEM · V4M · PROD
0103
In plain English
This case study is about helping keep a large production CRM/ERP platform running while the business continued operating every day. The platform supported sales, leasing, listings, deals, compliance, HR, finance, call center workflows, dashboards, reports, automations, and integrations. My role was to understand the system deeply, fix production issues, improve old workflows, build new internal tools, and support different teams without slowing down daily operations.
Business value
- Kept daily operations running across departments.
- Made daily workflows faster across sales, finance, and reporting teams.
- Gave managers a clearer view of every lead, deal, and team activity.
- Protected revenue by keeping sales and leasing running during fixes.
- Turned scattered requests into tools the business actually uses every day.
- Role
- Sole Full Stack Engineer
- Design · Build · Ship
- Timeframe
- Ongoing production support and development
- Domain
- Business Operations, CRM, ERP, Internal Tools, Automation
- Category
- CRM
- Maintained a large production CRM/ERP platform with 4M+ lines of code across multiple business departments.
- Built and improved internal tools, dashboards, reports, automations, APIs, and third party integrations.
- Debugged production issues and improved legacy workflows without disrupting active business operations.
- Worked across backend, frontend, database, infrastructure, and integrations as the engineer closest to the platform.
- Supported daily operations across 9+ departments on a single platform, work that would typically require a team of specialists.
- Maintained a large production CRM/ERP platform with 4M+ lines of code across multiple business departments.
- Built and improved internal tools, dashboards, reports, automations, APIs, and third party integrations.
- Debugged production issues and improved legacy workflows without disrupting active business operations.
- Worked across backend, frontend, database, infrastructure, and integrations as the engineer closest to the platform.
- Supported daily operations across 9+ departments on a single platform, work that would typically require a team of specialists.
The Business Context
The company ran every daily operation through a single CRM/ERP platform. If it went down, sales stopped, listings stopped, compliance stopped, and the call center went dark. Every code change touched real revenue. It was not a small admin panel or a simple sales tracker. It was the central system behind leads, listings, deals, compliance, HR, finance, call center activity, reports, dashboards, automations, and third party integrations.
By the time I took ownership of the platform, the codebase had grown past 4 million lines. Different teams depended on it every day, which meant every change had to be handled carefully. A small issue in one module could affect sales workflows, listing operations, compliance checks, reporting accuracy, or the daily work of agents and managers.
The challenge was not just writing new code. The real work was understanding how the business operated through the system, how old workflows were connected, where data moved, which teams relied on which screens, and how to improve the platform without breaking the parts people already used.
The Operational Challenge
The platform had become business critical, but it also carried the normal weight of a mature internal system. Years of features, urgent fixes, legacy workflows, department specific rules, third party integrations, and operational shortcuts had made the system complex.
Different teams needed different things from the same platform. Sales and leasing needed faster lead handling. Listing teams needed smoother publishing and portal workflows. Compliance needed reliable AML and KYC checks. Management needed dashboards and reports they could trust. HR, finance, and call center teams needed internal tools that matched the way they actually worked.
That created a constant engineering problem. New requests could not be treated as isolated tickets. Every change had to be checked against existing workflows, database structure, user permissions, integrations, reports, and production behavior.
The biggest risk was disruption. The business could not pause operations while the platform was being improved. Fixes, features, refactors, and integrations had to be delivered while people were actively using the system.
When an internal platform carries sales, listings, leads, compliance, finance, HR, reports, and daily operations, every code change becomes a business decision.
Ownership
Everything I designed, built, and was accountable for.
Product & UX
- Lead management workflows
- Listing operations workflows
- AML and KYC workflow support
- Call center tools and workflows
- Data feeds and sync workflows
Engineering
- Backend API development
- Angular frontend updates
- Third party API integrations
- Property portal integration support
- User permissions and access logic
Operations
- Management dashboards and reports
Additional scope
- Core CRM/ERP maintenance
- Production issue debugging
- Legacy module improvements
- MySQL query fixes and optimisation
- Deals module support
- Internal automation logic
- System stability checks
- AWS infrastructure support
- Cross department technical support
Key decisions
The calls I made, what I rejected, and why: these are the tradeoffs that shaped the system.
Improve the existing CRM/ERP instead of proposing a full rebuild.
A full rewrite that would take longer, introduce migration risk, and delay urgent business needs.
The platform was already deeply connected to daily operations, reports, users, permissions, data, and integrations. Rebuilding everything from zero would create too much risk for a live business. The better decision was to improve the system layer by layer while keeping the business running.
How the Platform Worked
The platform worked as a full business operations layer, with a Laravel based backend , an Angular frontend, a MySQL database, AWS infrastructure, REST APIs, scheduled jobs, internal automation, and multiple third party integrations.
The backend handled the core business logic, permissions, workflows, data validation, reporting endpoints, integrations, and automation processes. The frontend gave different teams access to the tools they needed, including lead views, listing screens, dashboards, compliance flows, call center tools, reports, and internal forms.
The database acted as the operational source of truth for leads, listings, deals, users, activities, compliance records, notes, statuses, assignments, reports, and integration logs. Many parts of the system were connected, so changes had to be made with a clear understanding of data flow and business impact.
My work often sat across the full stack. I investigated production issues from the UI down to the API, database query, server behavior, scheduled process, or third party response. I also worked on improving workflows by adjusting backend logic, frontend behavior, data structure, reporting queries, and integration handling where needed.
The goal was not to rebuild everything from scratch. The goal was to keep the platform stable, improve the parts that slowed teams down, and extend the system in a way that respected the existing business operation.
0104
feedback · monitor · fix · improve
Frontend
Backend
Database
Infrastructure
Integrations
Also used
The goal was not to rebuild the platform. The goal was to improve it while the business kept moving.
What Changed
- 4M+ codebase maintained
- Production CRM/ERP
- Multi department platform
- Legacy workflows improved
- Daily operations supported
The platform continued to support daily operations while new features, fixes, workflow improvements, reports, automations, and integrations were added.
I maintained and improved a large production CRM/ERP system used across multiple departments, including sales, leasing, listings, deals, compliance, HR, finance, call center operations, management reporting, and internal automation.
The work made the platform more reliable, removed friction from daily operations, and gave each team tools that matched how they actually worked. It also helped management see more of the business through dashboards, reports, and cleaner operational data.
Every improvement shipped without stopping the business. The system stayed in use while legacy workflows were supported, production issues were debugged, and new internal tools were added across the platform.
One engineer covered ground that would typically need a team of 4 to 8 specialists across backend, frontend, database, infrastructure, and integrations.
4M+ lines of production CRM/ERP kept moving across daily operations
0106
Production scale handled
Multi department ownership
Safer production support
Less operational friction
Better management visibility
Full stack continuity
The work helped keep a large business critical CRM/ERP platform stable while the company continued operating every day. Teams across sales, leasing, listings, compliance, HR, finance, call center operations, and management could continue using the system while production issues were fixed, workflows were improved, and new tools were added. For the business, the value was continuity. The platform kept supporting daily work while becoming more useful, more visible, and easier to operate across departments.
“Rusty understands the difference between adding features and making software actually usable. He looks at how people work, finds the friction, and improves the system in a way that makes daily operations feel smoother.”
Operations Stakeholder
Internal Platform Team — name under NDA
What This Taught Me
This platform taught me that real business software is never clean, small, or simple. It grows around people, departments, habits, urgent requests, old decisions, and daily pressure.
A CRM/ERP system is not just a set of screens. It is where the business remembers things, routes work, measures activity, enforces rules, and turns messy operations into something teams can act on.
The hardest part was not learning one framework or one module. The hardest part was building enough context to make safe decisions inside a large system. Before changing a feature, I had to understand who used it, what data it touched, which reports depended on it, which integrations might be affected, and what could go wrong in production.
This changed the way I think as an engineer. I stopped looking at tasks as isolated code changes and started looking at them as operational decisions. A button, query, status field, report, automation, or API payload can affect real people doing real work.
That is why stability mattered as much as speed. In a platform used every day, a fix is only successful if the business can keep moving after it ships.
In a business critical platform, good engineering is not just about shipping features. It is about keeping the operation moving while the system keeps evolving.
The cost of one engineer. The output of a team.
8+
3
5+
10+
Need a business system that actually keeps up with operations?
I help businesses improve the internal systems they already rely on, from CRM and ERP workflows to dashboards, automations, integrations, and production support. If your operations are growing faster than your tools, I can help turn the mess into a system that is easier to manage.
Talk About Your System