WHAT FOR
WE STAND FOR
Anyone working in the business side of insurance IT is usually familiar with two career paths: as a consultant who moves from project to project, or as a permanent employee working directly for an insurer. At tech11, we combine both— proximity to the customer and the depth of our own product.
We develop our own core insurance system—a platform that serves as the digital heart of an insurance company, covering everything from application review and claims settlement to policy management and the underwriting ledger. We don’t operate a third-party product; instead, we’re responsible for a system that we develop ourselves. In doing so, we actively support our clients, understand their processes, examine their requirements, and work together to develop the best solution for their business.
For our business professionals, this means they work more closely with technology than in almost any other business role in the industry—not because it’s required, but because you can only truly design your own product if you understand how it works.
Join our team
You don't just develop strategies—you help shape the future of the insurance industry together with us.
Three Roles, One Stance
Business Analysis (BA)
We understand insurers and speak the language of technology. This results in a solution—not just a document.
Project Management / Agile Coaching
We keep projects on track—not through control, but through trust, clarity, and the courage to speak the truth early on.
Business Development
We don't sell consulting services; instead, we sell a product that we develop ourselves and promote with conviction.
-
- When working with the insurer’s department, we don’t simply sanction requirements; instead, we keep asking questions until we understand the real need behind the request.
- We design solutions directly within the platform, ranging from product, claims, and auxiliary ledger configurations to calculation engines, document templates, and BPMN processes. As our experience grows, we’ve also started working directly with JSON configurations.
- We discuss with the development team which approach is the most stable and are part of the decision-making process—not just a supplier.
- We test the finished feature in the staging system, document any discrepancies, and complete the cycle from the initial customer discussion to the accepted solution.
- We draw up project plans so that they are realistic, even when the client wants everything—and preferably yesterday.
- Every day, we pull data from Jira, analyze it in Excel, and prepare it in PowerPoint in a clear and actionable format for steering committees.
- As an Agile Coach, we act as the glue that holds the team together. We monitor team morale, resolve roadblocks, and keep information flowing—both internally and with the client.
- We maintain contact with the client at all levels—from the operational team to the decision-makers—depending on the project’s needs.
- As the first point of contact for potential tech11 customers, we make a strong impression with our professional expertise, personal charm, and a genuine understanding of insurance processes.
- What we learn from customer conversations goes directly into the platform roadmap. We initiate feature ideas and change processes without political hurdles.
- We work closely with the business team, communicate requirements, prepare demos, and bridge the gap between the market and the product.
- Sales at our company doesn’t follow a prescribed process. We develop our own approach, staying close to the customer and close to the product.
Business development at our company isn't traditional sales. You're selling a real solution, and you can influence features, processes, and the company itself.
Lukas
Senior Business Development Manager
Every challenge is something new. After 5 years, I’m still solving a different problem almost every day—always within the same context, but rarely the same one twice.
Felix
Senior IT Business Analyst
We don't take a high-handed approach; instead, we work together to find solutions. And giving the client a realistic picture, even if it’s uncomfortable, builds a foundation of trust that’s worth more in the long run than any project plan.
Alexander
Senior Project Manager
Traditional Consulting vs. tech11
BAs write user stories and pass them on.
Business supports features from the initial meeting through to the go-live.
Requirements end with the ticket.
Solution Design concludes with the completed implementation.
The business actively helps shape technical solutions.
Project management provides status reports.
Business Development follows a sales guide.
We support features all the way through to production deployment.
Does our
way of working
suit you?
you question the requirements before you solve them.
you take responsibility and set priorities.
you communicate proactively.
you want to understand how software works.
you think like an entrepreneur.
you don't let mistakes hold you back.
you expect clear instructions rather than taking the initiative on your own.
your shifting priorities frustrate you.
you prefer to leave technical matters to others.
you prefer a rigid corporate environment.
you have little interest in direct contact with customers.
Tools & Tech Stack FAQs
Significantly more technical —and that’s no coincidence. A traditional BA at other companies analyzes and documents. Our BAs configure insurance products, claims, calculation engines, and document templates directly in the Business Workbench—a graphical user interface that you can think of as tech11’s own IDE for actuarial configurations. On top of that, there’s BPMN process modeling—and for those who want to dive deeper, work in code repositories as well. You don’t have to be a developer, but you’ll be working more closely with software development than in almost any other role with “Business Analysis” in the title.
The core of your daily work involves using BPMN 2.0 in CIB Seven (an open-source fork of Camunda) for process modeling and the Atlassian Suite (Jira, Confluence, Bitbucket) for everything related to requirements and documentation. In addition:
-
-
The IDE of your choice (IntelliJ, VS Code, or similar) for code repositories and Git workflows
-
Postman for validating implementations
-
JSON for product configuration
-
Office tools (e.g., MS Excel) for documentation and analysis
-
BPMN 2.0 (Business Process Model and Notation) is the standard for graphical modeling of business processes. Our guiding principle is that no state change occurs in the platform without an underlying business process. From claim review to claims settlement, everything runs through modeled, executable processes.
-
-
Jira for Effort Tracking and Sprint Management
- Excel for financial control and analysis
- PowerPoint for client presentations
- Miro for retrospectives
-
-
-
LinkedIn Sales Navigator for Lead Generation
-
HubSpot as our CRM, which we’re currently expanding
-
Anyone who wants to represent tech11 to prospective clients must truly understand our company. That’s why a deep understanding of the platform and knowledge of the insurance industry are just as important to us as any tool.
Michelle Lewis
Web DeveloperIndise takes into account even smooth and responsive...
Lucia Stuart
Web DeveloperIndise takes into account even smooth and responsive...
Michael Shadix
Web DeveloperIndise takes into account even smooth and responsive...
