A day in the entrance of our own real estate agency

We talk a lot about AI in the brokerage market. Seldom about a normal Thursday.

We talk a lot about AI in the brokerage market. How a normal Thursday looks like in the inbox of our own brokerage office is rarely mentioned.

At SureIn, we look after many customers in the SME property insurance business. The brokerage operation itself runs with three to four people. In total we are 13, the majority of whom are building Modus as an engineering team. Every morning the same inbox. Every morning the same question: What of this is work today, what is information, what is noise.

With us at SureIn, the day is decided by what we do with the inbox.

This article shows a Thursday in our brokerage business, as it really happens and counted by hand. For three weeks in our own office, we recorded which transaction types actually arise, how long they take and where the operational time disappears. What you read here is the operational view of a typical weekday at our company, counted by hand and not automatically pulled from a system. But every number appears regularly in our inbox, and we assume that it is representative for SME property insurance offices of our size.

We do this for one reason. When we talk about Modus, we talk about the answer to a question we ask ourselves every morning before we open the inbox. Modus is not a product that was created on the drawing board.

8:30 AM. What has come in since Wednesday evening.

Thursday morning, 8:30 AM. The employee sits down in front of the inbox. What has come in since Wednesday evening 7:00 PM adds up to around 80 items. In a week with more claims or more BiPRO deliveries, it is quickly more, in a quiet week slightly less. The order of magnitude remains.

What accumulates in these approximately 80 items is not homogeneous. They are BiPRO deliveries from insurers with new policy documents, confirmations and endorsements. They are customer inquiries via email and WhatsApp, sometimes short, sometimes with an attachment. They are claim notifications, some of which must be forwarded immediately and others of which still need information. They are broker contract confirmations from insurers that only need to be filed. They are reminders due to late payment that someone has to clarify. And it is newsletter noise that lands in the same inbox as everything else.

Before anything is answered at all, another question is in the air: What of this is even work?

This is exactly where the invisible effort begins, which nobody shows in the weekly reports. Sorting, evaluating, forwarding, creating, following up. That happens before the actual process starts. And that happens every day.

Three weeks hand-counted, six months measured. Always the same processes.

For three weeks, we counted every incoming item by hand. For an additional six months, we measured which process the time actually flows into. Both show the same picture. A few process types carry the bulk of the work, and the most expensive ones are not the ones that seem the loudest.

At the top is proposal preparation. An inquiry comes in, often incomplete, and is virtually built from scratch. Gathering risk data, checking existing portfolio, clarifying missing details, obtaining comparisons, preparing for the customer. Over the month, this workflow binds most of our time.

Immediately after comes the preparation of appointments and consulting. Not the conversation itself, but gathering the context before it begins.

Then the classic incoming processes that fill the morning. Claim notifications: customer reports, we check, we notify the insurer, we document. Policy documents from BiPRO deliveries that want to be checked, filed and confirmed with the customer. Contract and address changes, each of which entails insurer communication and a resubmission. Premium queries, the most common small single process, rarely completed under twenty minutes. And applications that go through several hands until policy issuance.

The rest is distributed across the long, quiet spread. Broker contract confirmations that are only filed. Instant WhatsApp needs between two other processes. Reminders from the insurer. Open resubmissions from the previous week. Real, but not setting the pace.

The anchor remains stable. When we know which processes carry the day and the month, we also know where the operational leverage lies.

What a single process looks like today.

Take a process type that actually comes up for us on Thursday: a broken glass claim in a retail shop. Customer sends an email in the morning with a photo, a brief description, asking for feedback. What your team does on such a process today before anything executable is even created is precisely the manual structuring work that occurs per employee and process.

What happens then?

The employee reads the email. They check which contract is affected, look up the contents insurance in the MVP, identify the insurer. They reply to the customer with confirmation that the report has been received and ask for missing details, such as the exact time of the damage or the amount of damage. They request the claim number from the insurer, either via the insurer portal or by email. They create the claim process in the MVP and link the correspondence. They set a resubmission for the following day, because the insurer usually returns a claim number within 24 hours. They inform the customer that the report is with the insurer and will get back to them as soon as the claim number is there.

Per process, that is between 10 and 25 minutes of manual work. Closer to ten for simple cases, closer to 25 for complex ones with queries and multiple documents.

Eight to ten such processes run through a normal morning per employee. Project that, and you see why with three to four people in the broker office, the largest part of the paid time goes into neatly building processes from an unsorted inbox and thus hardly into consulting or portfolio expansion.

Not every email is work, but every work starts with an email.

What we learned in the three weeks is hardly about volume. Eighty incoming items are manageable, and insurance brokers have been working with high volumes of correspondence for decades. The bottleneck lies in structuring: Someone has to decide whether an incoming item is a process, enter it, take it over, check the resubmission, document it for the portfolio and ensure that an email with a photo attachment becomes a structured process that is still traceable in a week when the customer asks back.

This structuring work is invisible. It does not appear in any statistics, is not billed and does not translate into commission. Nevertheless, it happens every day, multiple times per employee.

We recorded it between 8:30 and 11:00 AM in our brokerage office. It is around three hours per employee and day that flow into translating an incoming item into a process, and thus neither into sales nor into consulting.

In our brokerage business with three to four people, that's about 9 to 12 hours daily, more than a full full-time equivalent that disappears into translating before the first real process is executed. That is the figure that does not appear in any portfolio statistics and which you as managing director nevertheless pay for every month.

Not every email is work, but every work starts with an email. As long as translating happens manually, it is exactly this translating that slows down the operational leverage.

What happens when the same work flows as a process into an operational layer.

We started building Modus because we sat at exactly this spot. We asked ourselves what would happen if decisions, sorting and translating no longer had to be done at the inbox, and instead already structured processes arrived there which the employee only has to execute.

Modus consolidates incoming communication into a structured operational layer above the existing MVP. Around 80 incoming items become structured processes. Every process has a responsibility, a priority and traceability. The BiPRO document, which was previously a PDF in the inbox, becomes a policy process with customer, insurer and action. The claim notification, which was previously an email thread, becomes a claim process with all attachments, the next resubmission and the finished insurer cover letter as a draft.

The same glass breakage process looks different in this model. Instead of an inbox with 80 unsorted messages, the employee opens a process list in the morning with clearly assigned cases. The glass breakage is already identified as a claim process, insurer and affected contract are linked, the missing mandatory details are marked, and the draft of the insurer email is ready. The employee checks, completes and approves. Instead of 10 to 25 minutes, that's 1 to 2 minutes of structured execution.

Scaled to the morning, this means: the three hours per employee and day that currently flow into translating migrate from administration to consulting. The inbox does not disappear, it is just no longer the bottleneck.

The leverage therefore lies in the architecture of how work enters the business in the first place. It is about more than a faster email response.

What has changed for us since Modus has been running in our own business.

Modus is running in our own brokerage business today. We therefore describe the before and after not from a demo, but from daily use.

The most visible effect is where most of the time used to disappear. Proposal preparation and the preparation of appointments, i.e., the two largest items, no longer start from scratch. The context is available in a structured format, a draft is prepared, the employee checks and approves. 10 to 25 minutes of manual preparation per process turn into 1 to 2 minutes of structured execution. The time that is freed up as a result flows back to where it generates revenue.

An operational layer above the MVP.

A clarification is important at this point, because we hear it in every conversation.

Modus is not another MVP and does not replace the system in which contracts, customers and portfolios are maintained. It is not a CRM and does not replace the sales logic, not an AI assistant that answers questions in chat, and not an add-on built on top of an existing MVP module.

Modus is an operational layer above Outlook, BiPRO delivery and the existing MVP, an architecture that receives incoming communication, structures it and plays it out to the team as executable processes. If your setup changes, if you change the MVP, if you connect another pool, your operational layer does not change with it. That is the crucial point.

Modus is pool-independent. This is more than a technical feature, it is a commercial-structural decision. Anyone who builds an operational AI layer into a pool contract ties operational efficiency to the pool commitment. We deliberately separate that.

In concrete terms, this means: if you change your pool or your MVP today, your operational layer migrates with you. With a pool-bound solution, you start from scratch again at this point. That is precisely the essential difference to the pool-bound approaches that are most visible in the market.

Some pool-bound solutions sit deep in the MVP with several specialized language models, working reactively via speech and chat commands as of today, and remain bound to the respective pool. Other solutions work with several proactive AI agents, but remain bound to the respective pool structure. Both approaches have their justification, but both remain bound to the respective commercial platform.

Modus remains an operational layer above the MVP and does not work inside it. That is exactly why it works even when everything else around it changes.

Why we build this ourselves.

We build Modus because we sit in front of this inbox ourselves every morning.

We are not a large business: Approx. 2,000 customers, three to four people in the brokerage business. That is exactly why we see the same bottlenecks that you see.

At SureIn, we have never had a demand problem. SMEs need property insurance, the business is there. What slowed us down, and what still catches up with us in every growth spurt, is the question of how much administration we have to build up with every new portfolio, how many additional person-hours flow into translating incoming items into processes, and how many resubmissions per person can still be neatly maintained before quality suffers.

Insurance intermediaries do not have a demand problem, their bottleneck is an operational problem. We know this because we run a brokerage business ourselves.

This changes the way we build Modus. What we are building is the operational layer that we ourselves need daily in our brokerage business, not a generic B2B product for many industries. The process types that appear in this article are the process types we test Modus against daily. The time frames we mention are the frames in which we measure.

Building operational leverage instead of building up staff is more than a positioning for us. It is the question we have to answer for ourselves, every Thursday, 8:30 AM.

FAQ

How many incoming items typically accumulate overnight?

In our brokerage business, the incoming items between Wednesday 6:00 PM and Thursday 8:30 AM add up to around 80. This is a typical order of magnitude for an SME property insurance office with around 2,000 customers and three to four people in the operational team. In weeks with higher claims frequency or many BiPRO deliveries, the value is higher.

Which processes cost the most time?

Measured over the month, it is proposal preparation and the preparation of appointments and consulting. This is followed by claim notifications, service and policy documents, premium queries, research, applications and inquiries. The most expensive workflows are not the ones that seem the loudest in the inbox.

Which processes cost the most time?

Measured over the month, it is proposal preparation and the preparation of appointments and consulting. This is followed by claim notifications, service and policy documents, premium queries, research, applications and inquiries. The most expensive workflows are not the ones that seem the loudest in the inbox.

How long does a standard process take manually today?

Between 10 and 25 minutes, depending on complexity. A simple glass breakage claim with clear details is closer to 10 to 15 minutes. A premium query with research in the MVP or a change application with comparison is closer to 20 to 30 minutes. Eight to ten such processes per employee and morning are typical.

How much of this does Modus save per employee and day?

We measure the effect in our own business in the range between today and structured execution. The same process executed in a structured way takes 1 to 2 minutes instead of 10 to 25. Projected onto a working day, that is up to three hours per employee and day that migrate from administration to consulting. In our brokerage business with three to four people, this corresponds to more than a full full-time equivalent that currently disappears in translating.

Does Modus replace our MVP?

No. Modus is a layer on top of the existing MVP that neither replaces it nor merges into it. The MVP remains the system in which contracts, customers and portfolios are maintained. Modus takes over the operational level, i.e., how incoming communication is translated into structured processes and played out.

Is Modus bound to a pool?

No. Modus is pool-independent. This is a conscious architectural and commercial decision. If your pool, your MVP or your insurer connection changes, your operational layer does not change with it. That is exactly why Modus also works in multi-pool setups or when changing setups.

How does Modus distinguish itself from pool-bound AI solutions?

Some pool-bound solutions sit deep in the MVP with several specialized language models, working reactively via speech and chat commands today, and remain bound to the respective pool. Other solutions work with several proactive AI agents, but remain bound to the respective pool structure. Modus lies as a pool-independent layer above the MVP and does not work inside it. This is a question of architecture and secondary to the individual function.

Is Modus already available for our office?

Yes. Modus is live and in daily use, including in our own brokerage business and with first customers. Anyone who wants to see what the operational layer looks like in their own setup can book a demo.

Conclusion

Yesterday: Work arises unstructured in the inbox and is built up manually. Three hours per employee and day go into translating before the first real process is executed.

With Modus: Work arises structured and is prepared by the system. Around 80 incoming items become processes with responsibility, priority and traceability. 10 to 25 minutes per process turn into 1 to 2.

This turns the inbox into executable work instead of a growing backlog.

Scale revenue. Not headcount.