insurancetech.dev: an open board for developer ideas in insurance

Most insurance product ideas from developers never reach anyone who can act on them. They sit in a notes file, a side-project repo, or a conversation that ended with "someone should build that." We wanted a place where those ideas are written down, visible, and answered.

That place is now open. insurancetech.dev is an open idea board where developers pitch insurance products and choose the rails to build them on.

What insurancetech.dev is

It is a board, not a contest and not a marketplace. A developer describes an insurance product they want to build, says which rails they want to build it on, and submits it. The pitch goes on the board, where other builders can see what is being proposed.

Three things define how it works:

• Open. The board lists the ideas. You can see what has been pitched before you write your own.
• Your choice of rails. The person pitching picks what the product is built on. We do not assign it.
• A person reads every pitch. Each submission is read by a person, who replies by email.

That last point matters more than it sounds. A form that disappears into an inbox nobody checks is worse than no form at all. Every pitch on insurancetech.dev gets read, and the reply comes from a person.

Where the board stands today

The board already lists 8 ideas. 2 of them are live.

We are stating those numbers plainly because they are the point. An idea board is only useful if it is honest about what is an idea and what is running. Eight pitches on a board is a start. Two of them live tells you the path from pitch to product exists and has been walked.

We are not going to dress that up. It is a small, working board, and we want it to grow with more pitches from people who build.

Why an open board

InsurEco's work is about trust and transparency in insurance data: every record has an owner, every access is visible and logged, and data is shared only with consent. The opposite of that is opaque data resale, where information moves between parties without the people it describes ever seeing where it went.

An open idea board follows the same instinct, applied to product ideas instead of records. The ideas are listed where people can see them. The person who pitched an idea is the person it belongs to. The reply goes back to them directly.

We think insurance gets better software when the people building it can see what others are proposing and know their own pitch will be read. That is a small mechanism, but it is a concrete one.

How a pitch moves

The flow is short:

1. Go to the board. Start at the insurancetech.dev home page and look at what is already listed.
2. Write your pitch. Describe the insurance product you want to build.
3. Choose your rails. Say what you want to build it on.
4. Submit. You land on the thanks page.
5. Get a reply. A person reads your pitch and replies by email.

There is no step where your idea is scored by a script and filed away.

What makes a pitch easy to answer

The board does not require a business plan. But some pitches are easier to respond to than others. From an operator's point of view, a useful pitch tends to answer a few questions:

• Who is it for? An agency owner, an MGA, a carrier operations team, a reinsurance desk, a regulator, a policyholder. Name the user.
• What does it replace? A spreadsheet, a manual reconciliation, a phone call, an email chain. Say what the work looks like today.
• What data does it touch, and whose is it? If your product reads or writes insurance data, say who owns that data and how consent is given. That question is central to how we think about insurance software.
• Which rails, and why? You choose. A sentence on why that choice fits the product helps the person reading it.
• What would "live" look like? Two of the eight ideas on the board are live. Describe what the first working version of yours would do.

None of these are gates. They are the questions the reply is likely to ask, so answering them up front shortens the conversation.

Who should pitch

If you write software and you have seen an insurance workflow that should work better, this is for you. That includes developers inside agencies and MGAs who know a specific operational problem well, independent builders who have worked near insurance and noticed a gap, and engineers at carriers or reinsurers with an idea that does not fit their current roadmap.

You do not need to have started building. You do need an idea specific enough that someone can reply to it.

Submit a pitch

The board is open. It lists 8 ideas today, 2 of them live, and every new pitch is read by a person who replies by email.

Start here: insurancetech.dev. Read what is on the board, write down the product you want to build, choose the rails, and send it.