Success Stories
These are selected success stories from projects I led as CTO, focused on situations where the business needed more than coding effort alone. Each example shows a real problem, the practical constraint around it, and the measurable result. Names and some details may be anonymized for confidentiality, but the substance is real. The goal of this page is simple: to show how sound technology leadership helps businesses move forward with less risk, better control, and outcomes that can be defended in plain language.
Read the stories
Modernizing a legacy estate operation without disrupting harvest
Building a unified trading platform across fragmented systems
Use AI to modernize a document platform by removing a critical technology constraint
Modernizing a legacy estate operation without disrupting harvest
A large U.S. coffee producer had inherited an estate operation that still depended on manual processes, obsolete hardware and software, and undocumented systems. The technology no longer matched the way the business actually worked. Even basic seasonal preparation had become painful: getting the old system ready for harvest took several weeks, and finding people who could support it was either very hard or very expensive.
Under my leadership, the operation was replaced with a modern ERP platform built to support harvesting, production, manufacturing workflows, and regulatory reporting. The work was delivered in six sprints, in less than three months, with the first MVP available in sprint two. Just as important, the rollout was timed so the new system could go live after harvest without disrupting the estate's busiest season. No issues were reported during launch.
The results were operational, not cosmetic. The estate could start harvest with one click instead of spending weeks preparing the old system. The cost of making changes dropped by 5x, service restoration was under 10 minutes on standard replaceable hardware, and the system no longer required ongoing maintenance or administration, saving hundreds of thousands of dollars annually in support costs. The business also gained better reporting, cleaner process documentation, and better visibility into operations for remote management.
Quick Facts
Industry: Agriculture / manufacturing
Company profile: Large U.S. coffee producer, part of a global coffee group
Problem: Obsolete, undocumented systems slowing operations and creating support risk
Approach: ERP replacement under tight timing constraints, staged delivery, production-safe rollout
Timeline: Less than 3 months for first release, less than 1 year total
Outcome: Harvest startup reduced from weeks to one click, 5x lower cost of change, under-10-minute restore time, hundreds of thousands saved annually in support expense
Building a unified trading platform across fragmented systems
A multi-asset trading business wanted to offer clients one coherent product experience across forex, CFDs, stocks, crypto, and wallet functionality. The challenge was not simply adding more features. The real problem was that the underlying environment was fragmented: different asset classes, different platform components, different vendors, and different technical constraints all had to work together without creating friction for the user. At the same time, the platform had to meet the expectations of serious traders around speed, reliability, and control.
Under my leadership, this was approached as a platform unification problem rather than a feature delivery exercise. The goal was to create a seamless multi-asset experience with silent login, instant fund movement across asset classes, biometric authentication, and consistent performance at every critical point in the transaction flow. That required more than application development. It required resolving compatibility and reliability problems, reducing vendor sprawl, aligning multiple stakeholders, and treating each part of the transaction chain as mission-critical, because failure in one component would compromise the whole experience. The solution combined hybrid delivery speed with custom native engineering to meet mobile platform requirements and support enterprise-grade performance.
The result was a unified trading app that brought together previously disjointed capabilities into one product experience. The published case attributes a 4.8+ rating across app stores and more than 200,000 downloads to the platform. It also notes that 88% of the customer base accessed services through mobile, which made mobile-specific engineering central to the success of the product. The broader outcome was strategic as well as technical: complex backend architecture was turned into a user-facing platform that remained scalable, secure, and operationally reliable while supporting long-term product growth.
The decision window is shorter than many teams assume. According to the study, 81% of leaders believe firms relying on disconnected digital experiences will fall behind within two years.
GehtSoft Thought Leadership Survey November 2025 Among 300+ Business Leaders
Quick Facts
Industry: FinTech, multi-asset trading
Company profile: Established trading platform business serving active investors
Problem: Fragmented systems, vendor sprawl, and complex transaction flows across multiple asset classes
Approach: Platform unification, stakeholder alignment, resilience-focused architecture, mobile-specific engineering
Outcome: Unified multi-asset product experience, 4.8+ app-store rating, 200,000+ downloads
Additional context: 88% of customers accessed services through mobile
Use AI to modernize a document platform by removing a critical technology constraint
A document generation product had become harder to maintain not because the business logic was unclear, but because part of the product still depended on C++ inside an otherwise C# environment. That created a serious support and hiring constraint. To maintain and evolve the product well, the business effectively needed people who understood C++, C#, PDF internals, and text processing. People with that combination of skills were rare, expensive, and difficult to hire. Over time, this stopped being just a technical inconvenience. It began to affect maintainability, delivery speed, and the long-term viability of the product.
Under my leadership, the modernization effort focused first on removing that constraint rather than simply "using AI." AI-assisted coding was used to accelerate the migration of the C++ portion into C#, eliminating the most expensive and fragile part of the support model. But the real value did not come from speed alone. The migration was governed very tightly. The team first captured the existing behavior as a reliable baseline, then used test-driven discipline and behavior-equivalence controls to ensure that modernization did not change what the product actually did. AI was used inside a controlled engineering process, not as a substitute for engineering judgment.
The result was that a transition that would normally have required a rare specialist team and an estimated six to nine months of work was completed by technology leadership directly in about one month. More importantly, the product no longer depended on the hardest-to-hire skill combination in its support model. That improved maintainability immediately, reduced hiring risk going forward, and put the product back onto a normal .NET path for future development.
Quick Facts
Industry: Software / document generation
Company profile: Product company with a mature .NET-based platform
Problem: Critical C++ dependency inside a C# product created a rare-skill hiring and maintenance bottleneck
Approach: AI-assisted migration from C++ to C#, governed through strict engineering controls and behavior-equivalence testing
Timeline: About 1 month, versus an estimated 6 to 9 months through traditional staffing and delivery
Outcome: Removed the most expensive support constraint, restored maintainability, and returned the product to a cleaner .NET architecture