Discovery
2yr → 1mo
A planned two-year discovery effort compressed to roughly a month once HC3 produced a trusted, system-wide map of the live estate.
HC3 insurance case
From black box to blueprint.
A Stingray-based policy administration platform looked like no-code on the surface. Underneath sat 5M lines across five languages — understood by a thin global specialist pool — until HC3 compressed discovery and unlocked a high-fidelity path to .NET and Azure.
Based on an anonymized customer engagement. The customer is not named. Metrics reflect that project’s outcomes; results vary by estate.
2yr → 1mo
discovery timeline
5M
lines of code
<1K
fluent specialists worldwide
.NET + Azure
high-fidelity plan + AI assist
01 · Situation
No-code surface. Multi-language core.
At an insurance conference, a CTO and chief architect described a familiar bind: modernizing a Stingray-based core insurance workflow platform. Stingray gave them a no-code foundation, but beneath it sat logic implemented across five different languages — Delphi, XML, JavaScript, SQL, and HTML baked into a single Stingray codebase. By 2025, that hidden complexity had become a growth constraint.
02 · Problem
Discovery kept getting harder.
They struggled to find engineers who could confidently support the platform, and even experienced teams found end-to-end workflows hard to trace. Fragmented business logic across languages, plus the effort to discover, document, and validate existing use cases, kept increasing — while a multi-year discovery plan stood between them and credible policy administration modernization to .NET and Azure.
The stack
Five languages. One codebase. One modernization target.
Single codebase
Stingray policy administration
- DelphiCore business logic & UI
- XMLConfiguration & data contracts
- JavaScriptClient workflows & scripts
- SQLPersistence & reporting
- HTMLPresentation & forms
03 · Challenge
Where modernization programs stall.
The work started where most Stingray-to-.NET and Azure programs stall: establishing a trusted, system-wide understanding of the live estate — not a slide of intended architecture.
| Pressure point | What was hard | What was needed |
|---|---|---|
| Language mesh | Business rules and workflows were split across five languages inside one platform, not five clean services. | Cross-language tracing so a policy change could be followed from form to rule to database. |
| Talent & ownership | A thin global pool of engineers who understand Stingray-class estates; onboarding meant archaeology, not orientation. | Living documentation so the system is no longer locked inside a scarce specialist community. |
| Modernization planning | A multi-year discovery plan before any credible Stingray → .NET and Azure cutover sequencing. | Compressed, evidence-backed discovery and a high-fidelity plan the team could execute with AI assistance. |
04 · Approach
Map the mesh before you plan the move.
Production software does not live in a single language. It is a mesh of code, configuration, DevOps, containers, services, libraries, infrastructure, and data models. If documentation misses those layers, it is not documentation — it is an excerpt. Adapts traced and connected functionality end to end into a navigable source of truth.
| Dimension | Before HC3 | With HC3 |
|---|---|---|
| Starting point | No-code surface with opaque multi-language logic underneath. | End-to-end map of workflows, rules, integrations, and dependencies. |
| Documentation depth | Excerpts that miss DevOps, data models, and cross-language edges. | Facet-complete documentation across languages, services, and ops dependencies. |
| Planning confidence | Modernization stalled on “what exists today?” | A trusted blueprint that unlocked a Stingray → .NET + Azure plan and AI-assisted delivery. |
05 · Results
Faster discovery. Shared knowledge. Executable plan.
Knowledge risk
<1K → documented
The legacy system was understood by fewer than ~1,000 fluent practitioners worldwide. HC3 turned tribal knowledge into shared, queryable documentation the broader team could use.
Execution
.NET + Azure
A grounded Stingray → .NET application modernization plan and Azure migration plan, with an AI assistant accelerating delivery against verified workflows — not guesses.
There is no public open-source Stingray developer community or published global headcount. The platform is a commercial Sapiens P&C suite with vendor- and partner-mediated support; independent implementers note that knowledgeable Stingray developers are hard to find (Cameo Code wiki revision oldid=83, accessed 2026-07-12). “Fewer than 1,000 fluent specialists worldwide” reflects the scarcity observed on this engagement, grounded by that public signal — not a published industry census.
See it on your codebase
See Adapts HC3 on a multi-language insurance estate.
30-minute technical walkthrough with an enterprise architect. No slides · a live demo on real code.