I’ll tell you how we have been helping an insurance agent in Glyph media for several years to develop a corporate blog and develop IT services.
Photo Crew (Unsplash)This is one of our favorite cases. We quickly restarted the client's site, started preparing materials for the blog, reached podcasts and even mobile development.
Next - how we approached the insurance topic and found a couple of approaches that help our client to become more and more recognizable in their niche.
')
IT edition
We at Glyph Media (our
Telegram channel ) cooperate with IT companies. We help where the regular editor-humanist “slips” - we can prepare many regular publications about the structure of IT systems. For example, it is difficult to imagine an employee who for years makes 10-15 large materials per month on one highly specialized topic. And we do it.
We distribute tasks among several specialists who are already “in the subject line” and can quickly understand how and what works. We also check each other and look at the presentation of the material so that it is connected with the client's business, liked the audience and did not look like regular market news, press releases, SEO texts or something like that.
Frankly, when the work is delayed, there is no power left for its speakers and telegram channels. We
started talking about ourselves
recently , so as not to be a shoemaker without shoes.
Usually we are simply recommended by clients and acquaintances. That is how we met with Michael, an insurance expert. We will tell you how we started our cooperation.
Insurer
As we found out, Michael was able to communicate with the audience in specialized forums, where they discussed the settlement after the accident and the delay in payments from insurance companies. Mikhail tried to make recommendations based on the experience of interacting with insurance and explained how to achieve something and not spend all his time on it.
Marketing was built on live communication with potential customers. Even people came to insure cars of his wife, relatives, recommended Michael to friends. Surprisingly, the site was already a service history. His role was to give these people the opportunity to choose insurance on the desired topic. Then he looked like this:

Our task was not so much to offer some unusual site design, but rather to develop customer interaction in the spirit of what Fintech companies do: they give the audience understandable IT services and share relevant information.
Site
So, our client's specialization is auto insurance. The second area is property insurance. The third is medical risk insurance. And then a number of different
types of insurance for individuals and businesses. He has been doing this for almost 9 years.
Michael helps clients to monitor the implementation of all obligations under the insurance contract. Such support is provided from the first day of work and is now available at no additional cost and almost around the clock.
People do not always have the opportunity to get a competent assessment of the situation and a recommendation on how best to act to settle insurance claims, but here the clients receive expert support and, which is valuable, do not remain in debt.
As we found out in the course of analyzing the old site, in addition to basic information about the company, Mikhail collected hundreds of customer reviews. Some of them were duplicated, so we decided to immediately deal with this and distribute
reviews by year .
For the sake of interest, we even identified some trends for one of the richest year reviews and wrote about it
one of the first materials for a corporate blog. On the chart - keywords (by the number of entries) for the four quarters of the year.

From the point of view of working on the site, our priorities have been and remain - the speed of making simple changes and administration, plus the low cost of support.

Taking into account these requirements, we used the designer and
reworked the textual and visual presentation of information in comparison with what was on the old site.
Blog
We acted as the external editorial board
of the insurance team “Insurance Team” . For this project, we gradually developed a number of thematic headings:
- “ Analytical podcast Expertise ” - in this program Michael explains what is happening in the insurance market, talks about real situations and his experience in supporting clients in the process of settling insurance claims (we provided all the necessary infrastructure for recording the program - we take care of the audio and release this podcast in the web version and in iTunes )
It is worth noting that we did not use any advertising services for the project. The content was distributed by those readers who already knew Michael, and was used in discussions on thematic forums to refer people to guides and parse real situations.
Since the release of a number of materials attracted a significant amount of new audience and showed good results. Some of the most notable:
Further we will tell about what other content we did on external platforms.
UGC sites
In the early stages of work, we experimented a lot with external sites - we mainly concentrated our efforts on those that allow us to post materials without having to pay for placement and coordinate the content with the editors.
We tried to spread the experience of communicating with Michael clients on auto forums and on other platforms, for example
The Question . It is worth admitting that on this site we did not see a surge of interest in the topic and a significant increase in site visits, although we gave links to detailed materials in the
journal . But some of the answers of Michael were noticeable and
attracted the attention of thematic media . For such requests, we helped prepare
expert columns on behalf of Mikhail and wrote to those media outlets that were more suitable for the development of his business. For example, they wrote about
API for insurance companies and
insurance of gadgets for Rusbase.
If you go back to the UGC-sites, then you can not ignore the side Geektimes. Here we received
very good results and tens of thousands of views of materials, although we did not seek to advertise something directly - we just shared the expertise of Michael.
Here is his review of our work:
From the first day the project was founded, my main task was to become an insurance agent No. 1 in the Russian Federation. I advised clients on simple specialized topics - there was enough knowledge, and I actively shared information. But I also observed a situation that I didn’t like very much: among those who could develop this area, there are a lot of specialists writing articles about you - how good you are, etc. But this is all very boring and uninteresting.
It all started like this: on the recommendation of a client, I found out that there is a guy (his son) who is very keen on music. I listened to a couple of his tracks. Well, so-so ... For an amateur. Further, A.A. announced that his son is very talented and writes “podcasts”.
For me it was a novelty, and I decided to take contact. Find out, maybe something and we stir up this. In general, I fired up this idea. An additional incentive was that no one in the industry did anything of the kind. Several years have passed - nothing has changed.
We met with Dmitry and Alina (later his wife). It turned out that there is possible not just a “podcast” at the exit, but a comprehensive development of a part of the business (structuring the site, maintaining the style and its development, shooting, podcasts, it-solutions, applications, etc.).
In short, we sang. I like that guys do not slow down. In the truest sense of the word - always try to go further. Develop. They know how to listen to customer requests, make the right conclusions. I sincerely wish creative victories, development to the international level and great family well-being!
application
As we said at the beginning of the story, our task was to give the audience simple and relevant information on the topic. But besides that, we started developing the service component - we started developing a mobile application for clients.
For a number of the first public versions, we focused on
information services and provided Mikhail's clients with the opportunity to communicate with him in a chat, made a questionnaire for applying for OSAGO, KASKO and other types of insurance, plus - we carried out a number of basic reminders in the format of an action algorithm in an emergency.
If we talk about the stack, here we can highlight the following:
- Backend . The development language is Ruby. The Hanami Framework. Data Storage - Postgresql. The database for task queues is Redis (via the Sidekiq library).
- Frontend . Language - JS. Framework - React Native. Data storage - Redux + Redux Persist.
- Miscellaneous . Chat Backend is an open source solution for RocketChat. Sending push - library Rpush .
- Continuous Integration - Gitlab CI. It spills new versions of backend's into the Kubernetes cluster through the built-in Gitlab Auto DevOps. Kubernetes is deployed on servers in the Russian Federation through Rancher.
At the moment, the application does not provide for a closed authorized part. All sections are available without registration. Chat is no exception. Therefore, at this stage it was important for the client that any user could write (the so-called LiveChat).
The availability of a ready-made web interface for operators is a good opportunity for a quick start with a small base of active users. We picked up an open source solution with the prospect of expansion. Today, most open chat rooms either do not support LiveChat, or do not fit other requirements. RocketChat is fine for us at this stage.
As plans for the near future, we are considering launching a personal account with the possibility of receiving documents in electronic form and accompanying insurance claims from receiving the application until complete settlement.
Our content marketing microformat:
What do you have for such an office?
What is there on Habré: now "✚" and "-" go a whole month
Podcast. How does IT outsourcing work
Video: content is not about SEO, clicks and transitions
Glyph vs full time employee
Archetypes: why stories work
Writer's block: outsourcing content is not fair!
When eight o'clock ... enough (for work)PS We also record a podcast with chief technology media and content makers - in the @ glphmedia profile there are links to releases and text versions on Habré.