Skip to main content

JET BI employees are not only experienced Salesforce developers, but also good football players.

About Us
Published by JET BI
12 September 2023
87

Introduction

Let’s introduce Roman Litvin, who works as a Salesforce Developer at JET BI. In addition to his role here, he also holds the position of captain and founder of the AFC JET BI Poznan football team.

This article will be about the JET BI footbal team's journey, why we decided to create it, and how football brings people together and adds bright colors to life. Let’s start!

Salesforce developer

Football team goals of a Salesforce consulting company

Before creating a team, Roman Litvin asked himself, what are the goals of our team? He decided that the result should not come first, because they are not professionals. He defined that the goals of our team are to maintain a healthy lifestyle, build team spirit, and receive unique emotions from mind-blowing victories and disappointing defeats.

The first steps of the IT-company football team

The idea of creating our own football team had always been in Roman’s mind, but he made the decision to bring it to life only this year. It all started with the fact that his friends and he used to gather every weekend to play football. It was fun, but sometimes we felt the need for more competition. That's when the idea struck him that the time was right to build our own team. He discussed this idea with his friends, and they all supported it. Then he proposed to our company to be a part of this venture, and the management gladly agreed. 

The most challenging phase of building the team began - the initial recruitment of players and bringing the strongest into the squad. The core of our team consists of his colleagues, employees of JET BI, but that alone wasn't enough to complete a season; we needed a minimum of 14 players to play the season. Currently, our team has 15 players. The national composition is also very diverse - Belarusians, Ukrainians, Poles, and Germans. Nevertheless, an atmosphere of mutual understanding and respect prevails within the team.


Impact on JET BI company's corporate culture

Participation in the team has a significant impact on our company employees. It builds team spirit and close friendships that extend beyond the football field. Employees celebrate victories together and support each other during challenges. This spirit of solidarity carries over to the workplace, helping to solve even the most difficult tasks. For example, in our team, there is a Junior Developer whom Roman mentors, and thanks to playing football together, they communicate more and understand each other much faster than before.


Sport, work, and life balance

Balancing work, sports, and personal life isn't always easy, especially in team sports. However, Roman believes we've found the perfect solution.

  • Firstly, it's the timing of league matches. They always start on weekdays after 8 PM, so it's not an issue.
  • Secondly, it's a large number of players. If someone can't make it to a game or training session, no problem, we have substitutes for everyone.
  • Thirdly, it's respecting the players' opinions. The timing for each training session is chosen through voting in the chat, so we select options that suit everyone as much as possible. This way, you can plan your day perfectly and maintain that balance.

Moreover, sports are excellent for relieving stress after a workday – any of our players can confirm that! 


Link to our team. If you have any questions or would like to become part of the JET BI footbal team, please, write to Roman Litvin on Linkedin.


Roman Litvin
Salesforce Developer
image
Question to the expert
image

We have available resources to start working on your project within 5 business days

1 UX Designer

image

1 Admin

image

2 QA engineers

image

1 Consultant

image
Related Articles
All articles
image
Is Salesforce Winning the Public Sector Race?
An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.
28 August 2026
image
Why Your Salesforce Flows Are Agentforce's Biggest Problem
This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.
23 July 2026
image
How to Wire Multiple Salesforce Projects in One Org Without Breaking Everything
This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.
08 July 2026