How a 12-broker Cairo firm could cut RFP turnaround by 70%

The starting point

Picture a typical mid-size commercial firm: twelve brokers, four hundred active policies, and a shared drive of spreadsheets only one office manager truly understands. RFPs take two to three days each — most of it retyping client data into Word templates. Renewals live in a color-coded Excel file that is updated when someone remembers.

This profile is a composite of the brokerage firms we sat with while designing Mizan — the numbers below show the workflow difference on that composite, not a named client's audited results.

The workflow, rebuilt

Data upload replaces retyping: the census spreadsheet is dropped into the deal, columns are inferred automatically, and low-confidence fields queue for human review instead of silently corrupting the record. The RFP is then generated from the deal itself — per line of business, in Arabic, English, or both — and versioned like code.

When offers return, they are normalized into one comparison grid: premium, limits, deductibles, exclusions, validity. The client sees one clean document; the broker sees the negotiation history behind every number.

What changes for the firm

The measurable difference is time: an RFP cycle that took days compresses to hours, and the 90/60/30 renewal rhythm runs itself because every policy generates its own countdown. The unmeasurable difference is posture — brokers walk into renewal meetings with the comparison already built, instead of apologizing for the delay.