T2meen: A Central Issuance System for Third-Party Motor Insurance in Sudan

I worked with Phoenix International on T2meen, a central issuance platform for third-party motor insurance. The goal was simple to state and hard to execute: get every licensed insurer to issue the same class of policy through one governed system so premiums are collected in full, intermediaries are accountable, and regulators can trust the data.

The problem

The market had three knots. First, intermediaries sat between insurers and vehicle owners with uneven controls. Leakage and delayed remittances were common. Second, “full premium collection” was more a hope than a process. Companies ran separate books, reconciled late, and tolerated mismatches. Third, regulators needed timely, consistent data to supervise the market, but collection and sharing were slow and inconsistent across insurers.

Building thirteen separate fixes would only multiply the inconsistency. We needed one issuance backbone that all companies could use without losing their identity, pricing rules, or internal workflows.

How I approached it

I started with interviews to cut through assumptions. Over several weeks I met C-suite and SVP stakeholders from thirteen insurance companies and representatives of the supervisory bodies to frame the regulatory and business requirements. Then I sat with thirty-nine users across underwriting, claims, and IT to see the friction in daily work. These conversations anchored the scope: a shared issuance core with clear roles, strong audit trails, and data pipelines regulators could trust.

With that scope in hand, I led a ten-person cross-functional team in an Agile cadence. We split work into short iterations that always ended with something someone could test in the real workflow: policy creation, premium capture, receipt and sticker issuance, and daily settlement files. Every demo tied back to a control problem, not a wishlist. That helped decision-makers see why certain trade-offs mattered, like enforcing full premium capture before printing a policy, or requiring unique vehicle identifiers to prevent duplicates.

Varying IT infrastructure across companies was a reality we could not wish away, so the system supported online issuance and a controlled offline mode with queued sync and conflict checks. Role-based access defined who could issue, void, or amend a policy. Each action left a traceable record. Settlement reports ran on a fixed schedule so finance teams could reconcile without manual compilation. For regulators, we produced a standard data extract with validation rules baked in, keeping “garbage in, garbage out” from sneaking back in.

Change management needed as much attention as engineering. I trained more than two hundred users from thirteen companies across sixteen states. Sessions were short and task-based, anchored in the exact screens they would use. Resistance softened when people saw how a rule protected them from downstream disputes—for example, blocking issuance when required fields were missing or when an intermediary’s float was insufficient.

What changed on the ground

After go-live, policy issuance moved from scattered tools to one governed flow. Intermediaries still worked with insurers, but every policy number, receipt, and payment status lived in a shared source of truth. Finance had daily settlement files they could reconcile without hunting through spreadsheets. When a policy was voided or amended, the audit trail showed who did it, when, and why, which reduced arguments and shortened investigations. Regulators received consistent datasets in the same format from every company, which meant fewer resubmissions and faster checks.

Adoption depended on sequencing as much as on features. We started with a small set of companies and states, fixed issues quickly, then widened the circle. That gave skeptics proof the system handled peak days, network dips, and the messy realities of field issuance.

Results

Within the first year, the platform was adopted state-wide by all licensed insurers for third-party motor policies. The system issued over 1.6 million policies in under twelve months. Net profit attributable to the rollout exceeded one million US dollars in the same period, driven by fuller premium capture, lower leakage, and reduced rework. Reconciliation time dropped thanks to standardized daily outputs. Compliance shifted from ad-hoc compilation to scheduled, validated exports. More important than the numbers, the market gained a baseline of trust in shared data, which made operational conversations shorter and more factual.

What didn’t work, and what I’d change

I underestimated how deep change resistance runs when a system touches money, authority, and routine. Some managers felt the controls restricted their flexibility; some intermediaries pushed back when float requirements were enforced. Technical disparities also bit us: a few issuers operated on low bandwidth, and the offline mode needed extra iteration to handle long sync gaps without duplication.

If I were doing this again, I would set up a governance council from day one with representation from insurers and regulators, publish a living change log that explains the “why” behind each control, and set firmer expectations on data standards before the first pilot. I would also invest earlier in telemetry—simple dashboards showing issuance volume, error rates, and sync health by state—so support can be proactive rather than reactive.

Why this project still pays off

Beyond immediate outcomes, T2meen left reusable assets: a standard data schema for third-party policies, a requirements baseline that aligns business controls with system behavior, and training materials focused on tasks rather than theory. The most useful lesson is to design the control first, then the screen. If you flip that order, leakage finds a way back in.

Takeaway

If you need full premium collection and credible regulatory reporting in a fragmented market, a central issuance system is worth the political and technical effort. Start with shared definitions, enforce controls at the moment of issuance, and make reconciliation a daily habit backed by standard outputs. People accept stricter rules when they see fewer disputes and faster closeouts the same week.