Challenge
Replace fragmented workflows, reduce manual coordination, and create a system the business could keep evolving rather than fear touching.
Case studies from product, platform, AI, and execution systems.
These are operating stories, not portfolio thumbnails. I care about what changed in the business, what was difficult in practice, which decisions mattered, and what kind of system had to be built around the work.
Sahal ERP
Sahal ERP started as a response to a familiar enterprise problem: too many critical workflows spread across disconnected tools, too much manual coordination, and too little operational visibility. The hard part was not only building software. It was shaping a platform that people would actually use across HRMS, time tracking, project delivery, billing, and analytics without turning it into an over-engineered internal monster.
Decisions
I pushed for a cloud-first architecture, clearer module boundaries, and a product shape tied to real operating use instead of feature accumulation. The Sahal AI service layer was conceived, architected, and built as a focused capability layer rather than bolted on as a gimmick.
Outcome
The result was a working enterprise platform that reduced manual operational processes by 60% and gave the business a stronger base for scale, reporting, and cross-functional coordination.
ProposalPro
ProposalPro came out of a clear business bottleneck: proposal and RFP work was high-pressure, repetitive, knowledge-heavy, and hard to scale without quality drift. The real opportunity was not full autonomy. It was building an AI-assisted workflow that helped people move faster without losing judgment, context, or accountability.
Challenge
Improve response speed and proposal quality without turning a critical business workflow into unreliable prompt theater.
Decisions
I designed the system around workflow support, reusable knowledge, and operator review. That meant treating AI as leverage inside the process, not as a replacement for process.
Outcome
The outcome was 60% faster turnaround, 3× proposal throughput, and a more reusable body of organizational knowledge instead of repeated last-minute reinvention.
Engineering and Delivery Transformation
Some of the most important work is invisible from the outside. Delivery transformation is one of those cases. The task here was to improve team performance, execution trust, retention, and infrastructure economics at the same time, which meant changing the system beneath delivery rather than asking people to simply work harder.
Challenge
Execution quality was being constrained by process friction, infrastructure shape, and the absence of a clearer operating system for delivery.
Decisions
I focused on cloud-first transition, stronger SDLC norms, better DevOps practice, and tighter links between architecture, planning, and delivery responsibility.
Outcome
That system-level work improved delivery efficiency by 25%, increased retention by 45%, reduced IT cost by 35%, and improved system performance by 25%.
Labs and Long-Horizon Builds
The public case studies focus on business and operating outcomes. For frontier and long-horizon builds, see Projects, especially KUN and Astra.