Web developer in Hanover for insurance brokers and financial advisers

What a broker’s website has to do

A client picks a broker or an adviser for trust in a person and for knowledge of a field, such as occupational disability, retirement or commercial property. The website has to show both in text, with a name and a face.

In Hanover, where several large insurers have their head offices, a broker’s pages compete with the insurers’ own pages for the same searches. If your product texts come from a service that supplies many brokers, the same paragraph stands on many sites, and Google and AI assistants have no reason to quote yours. Comparison calculators load as scripts or frames from the provider’s server. Vercel reported in December 2024 that the crawlers of OpenAI, Anthropic and Perplexity do not execute JavaScript (Vercel), so for them the calculator’s place on the page is empty. Clients then send policies and statements as email attachments, because the site offers no other way.

A page for each field of advice

The new site has one page per field of advice, written in your words, with the questions clients ask you in a first meeting. Each page names you, your region and how a consultation runs, and it ends with an appointment booking. The calculator sits on the page and loads after a click. Structured data states who you are, where you advise and which services you offer.

A client area for documents needs logins and a database, so it runs on Symfony or Laravel next to the static pages. I have built such areas before. At Policen Direkt in Frankfurt, from 2016 to December 2021, I programmed the front end of a portal in which thousands of customers uploaded and managed their insurance policies (customer count from those years). I used WordPress for the group’s websites through several launches and relaunches, and in 2018 TU Dresden named the group’s online guide the insurance blog of the year. For a financial services group I built a portal that gives companies its documents on the Money Laundering Act behind a login. Details: A digital insurance manager on AWS.

Client questions and the page that answers them

The table maps questions that clients ask an adviser, or an AI assistant, to the page that answers them and what that page states. Use it as a plan for your own site.

Client question	Page on your site	What the page states
Which independent broker in Hanover advises on occupational disability insurance?	Occupational disability insurance	Your name, your region, the cases you take on and how a first meeting runs
How is a broker paid?	How I work	Commission or fee, in the words of your status information
Which documents do I need for a review of my policies?	Policy review	A list of documents and the upload in the client area
Can a broker help after a claim was rejected?	Claims support	What you do in a claim and what the client sends you
Is this adviser registered?	Imprint	Your register number with a link to the public register
Does the broker also advise companies?	Commercial insurance	The trades and company sizes you work for
How do I book a first meeting?	Every page	An appointment button in the first screen and at the end

Who I am

I am Michael Wutzke, an IT architect for data platforms in Frankfurt with more than twenty years in IT and media. After my years at Policen Direkt I was Head of Decentralized Finance and Node Operations, then CIO, at the Frankfurt-based company Blocksize Capital. I have published articles in specialist media on finance and insurance, among them Der Bank Blog, hold the AWS Solutions Architect Associate certification and teach at Claude Hacker House. I build software with Claude and Codex and am interested in open-source AI models that a brokerage can run on its own servers. Details: Background.