Finance, insurance and fintech

Financial software developmentfor insurance and fintech businesses

Our financial work is an insurance broker platform we built and ran for about five years, and a crypto buy/sell platform with a Telegram bot. Here is what each one had to get right.

Talk about your platformRead the detail

What we have built in financial services

Two platforms: one for insurance brokers and one for buying and selling crypto. We have not built core banking, card processing or lending systems, and despite this page's address, our direct record is in insurance and fintech rather than in banks. If you run a bank, the useful question is whether the problems below look like yours.

Insurance broker platform, about 2014 to 2019

We built this platform for Indian insurance brokers and ran it for about five years. It started as a general insurance platform, became a broker CRM, and was later extended to reinsurance.

  • A broker and sub-broker hierarchy, with brokers managing their sub-brokers, policies and renewals.
  • A claims module tracking each claim from intake to settlement.
  • Reports for supervisors, and IRDAI-format reports generated for the regulator.
  • A policyholder login to see policies and raise claims.
  • A reinsurance leads module handling the broker-to-reinsurer side.

Crypto buy/sell platform with a Telegram bot, 2024 to 2025

A Laravel and Next.js platform where customers see current rates, buy and sell, and follow their portfolio and transactions. Rates are live with a configurable margin and currency conversion. Login uses one-time passwords, and transactions are verified on-chain.

Around that sit multi-level referral commissions and payouts, configurable taxes and service charges, staff roles, an admin side for customers, content and sales analytics, and notifications by SMS, WhatsApp and email. A Telegram bot answers rate, portfolio and transaction queries and sends notifications, so it works as an interface in its own right.

What financial logic asks of a system

  • Commission rules have to be readable and testable. Multi-level referrals and broker hierarchies both produce numbers people will dispute, so each amount needs to be traceable to the rule that produced it.
  • Reports for a regulator have their own format and deadlines. They are a feature to design from the start, because reconstructing them from operational tables later is painful.
  • Margin, tax and charge settings change over time. They need to be configuration with history, so last year's transaction still shows how it was calculated.
  • An outside service will fail at some point. Rates, chain lookups and message gateways all need a defined behaviour when they do, especially where money depends on the answer.

Finance case studies

Questions from finance teams

Do you work with banks?

Our published financial work is the insurance broker platform and the crypto platform. We have no core banking project to show you. If your need is a portal, a reporting system or an integration, those two projects are the relevant comparison.

Do you handle regulatory reporting?

We built IRDAI-format reports into the insurance platform, working from the format the regulator requires. Your own compliance team stays responsible for what is filed. Tell us your regulator and we will say whether we have worked with its formats.

Where does the money logic live in your system?

Tell us what you need to calculate, report or pay out, and who checks it. We will tell you how we would structure it.

Talk about your platform

We reply within one business day (IST).