Bezpieczna Kancelaria was created by a four-person team.
The system is being developed in collaboration with law firms.
The expertise of a penetration testing specialist shaped the system's architecture.
A system for law firms should not be based solely on a list of features prepared by a technology team. It must reflect how lawyers actually work, the responsibility involved in handling cases, and the particular value of the information clients entrust to their law firms.
BezpiecznaKancelaria.pl combines two types of experience: many years of building advanced IT systems and knowledge gained through direct collaboration with law firms.
We did not start by asking: “What features should modern software for lawyers have?”
First, we wanted to understand:
- what a typical working day at a law firm looks like,
- where delays and errors occur,
- which tasks take up time unnecessarily,
- how lawyers store documents,
- how they keep track of hearings and other deadlines,
- how they divide work within the team,
- when technology helps and when it creates more problems.
Only then did we begin building the system.
Paweł Gościcki - lead founder and creator of Bezpieczna Kancelaria
My name is Paweł Gościcki. I am the lead founder and creator of Bezpieczna Kancelaria.
I have been designing and building IT systems for over 25 years. I have worked on solutions that had to handle large data sets, complex processes, and environments where stability and predictability directly affect users.
This experience taught me that a good system cannot rely solely on an impressive interface and a long list of features.
It must be designed as a whole.
Every component should work with the others. Data must be properly protected. Permissions must be clear. Integrations must not result in a loss of control. Users should understand what happens to their information and the consequences of the actions they take.
These requirements are even greater for a system designed for lawyers. Law firms work with documents whose disclosure could have serious consequences for clients. They store personal data, litigation materials, legal strategies, correspondence, and information protected by professional secrecy.
That is why Bezpieczna Kancelaria was designed from the start not as just another office application, but as a secure, integrated workspace for law firms.
A four-person team with complementary expertise
Bezpieczna Kancelaria was built by a four-person team.
For security reasons, we do not publicly disclose the identities of the other people involved in building the system or the detailed division of their technical responsibilities.
This does not mean that the system was built anonymously or without a clear direction. As the lead founder and creator of the project, I am responsible for its concept, development, and key product decisions. The other team members contribute the specialist expertise needed to build, secure, and maintain a sophisticated SaaS application.
In this case, a small team offers a major advantage. It keeps decisions consistent and reduces the risk of individual parts of the system being developed independently, without understanding their impact on the rest.
We do not build the calendar, documents, integrations, and AI agent separately. We are designing a single environment in which all these components must work together securely.
Security reviewed by a SaaS application penetration testing specialist
One of the key people on the team is a specialist with many years of professional experience in penetration testing SaaS applications.
His role was not limited to testing the finished product before launch. His knowledge of how web applications are attacked shaped decisions made during the design of the system architecture.
This included:
- user authentication methods,
- access and permission management,
- restricting access to data,
- document processing and storage,
- communication between individual system components,
- how integrations with external services work,
- reducing the potential attack surface.
This is an important distinction.
Security was not added to a finished application as a separate module. Nor is it merely a claim published on the website. It has been one of the core criteria for technical decisions since development began.
No web application can honestly be guaranteed to withstand every future attack. A system can, however, be designed to limit potential vulnerabilities, reduce the attack surface, and avoid relying on a single security mechanism.
This is how we approach security at Bezpieczna Kancelaria: as an ongoing process, not a one-off task performed before product launch.
A system built together with law firms
Technology experience alone is not enough to understand a lawyer's work.
That is why we worked with several law firms while building Bezpieczna Kancelaria. We examined how they organize their daily work and the problems faced by lawyers, trainee lawyers, assistants, and administrative staff.
We did not limit ourselves to asking users which features they wanted.
We observed real processes:
- how documents reach the law firm,
- where they are subsequently saved,
- how the team finds materials related to a specific case,
- how hearings and other deadlines are tracked,
- how meetings are scheduled,
- how tasks are assigned,
- how employees check lawyers' availability,
- how people working on the same case collaborate,
- how many different applications must be opened to complete a seemingly simple task.
This allowed us to see the difference between the formal process and how work is actually done.
Problems most often arise in everyday tasks. A document is saved in the wrong place. A deadline is copied manually between systems. Important information reaches only one person. A colleague sees too many details in a shared calendar. Room bookings are managed outside the system. A lawyer has to remember which application contains a specific piece of information.
Bezpieczna Kancelaria was created to minimize these risk points.
We did not build a collection of unrelated features
Many systems grow by adding more modules. Each may work correctly on its own, but users still have to connect the information and manage the entire process themselves.
We took a different approach.
Bezpieczna Kancelaria is designed as a single environment where documents, cases, deadlines, team collaboration, integrations, and AI tools operate as parts of the same process.
The calendar is one example.
It is not just for entering dates. It can connect law firm schedules with Google, iCloud, Portal Informacyjny Sądów, and the court hearing schedule. It lets users invite one person or an entire team to an event, share availability without revealing a confidential meeting title, and book conference rooms based on their capacity, floor, available hours, and time zone.
We take the same approach to documents.
This is not just about providing space for file uploads. A document must be protected, correctly assigned to a case, available to authorized users and ready for use in subsequent processes without creating uncontrolled copies.
The same principle applies to artificial intelligence.
AI should assist lawyers, not take control of the law firm
From the outset, we knew that an AI agent could significantly improve a law firm's work. It can help find information, prepare a draft document, schedule a deadline, organize data or perform a task described in natural language.
However, this does not mean that the agent should have unlimited access to all documents, cases and information in the system.
In Bezpieczna Kancelaria, the system prepares the context needed to perform a specific task. The agent receives the information it needs to prepare a response or carry out an instruction.
This may give users the impression that the agent understands the entire law firm and navigates its various areas independently. In reality, its operation is controlled by the system we designed.
We control how the agent is used - the agent does not control how the law firm operates.
We believe that artificial intelligence should support a lawyer's professional judgment, but cannot replace it. The final decision, document approval, acceptance of a change or performance of a significant action should remain in human hands.
Data protection should stem from the architecture
We do not want users to simply take our word for it that their data is secure.
That is why document protection in Bezpieczna Kancelaria stems from the system's architecture. Files are encrypted using the user's password, so that access to their content remains under the user's control.
This approach is particularly important for a law firm.
A system administrator should not automatically have unrestricted access to document content simply because they maintain the application from a technical perspective. Security cannot rely solely on terms of service, an internal procedure or an assurance that no one will look at the data.
That is why we design solutions so that access restrictions stem from technical mechanisms, not just organizational declarations.
How we develop new features
The development of Bezpieczna Kancelaria does not begin with the question of what would look good in marketing materials.
We start by analyzing a specific problem encountered in a law firm's work.
We examine:
- who performs the task,
- how it is currently performed,
- what information the user relies on,
- where an error may occur,
- who should have access to the data,
- which actions require approval,
- whether the new feature creates additional risk,
- how to connect it with the other parts of the system.
We then design a solution and assess it from both usability and security perspectives.
Only then do we build the feature.
This approach requires more work than rapidly adding new modules. However, it allows us to build a consistent system that does not shift the responsibility for connecting processes onto the user.
Four principles behind Bezpieczna Kancelaria
Security from the outset
Every feature is assessed not only for usability, but also for its impact on data access, permissions and potential vulnerabilities.
User control
A lawyer should know who has access to information, what action will be performed and when their approval is required.
One consistent system
Documents, calendars, cases, teams, integrations and the AI agent should work together. Users should not be forced to manually transfer information between multiple separate tools.
Technology supports a lawyer's professional responsibility
The system can speed up work, reduce repetitive tasks and assist with data analysis. However, it should not conceal the consequences of actions or take over final professional decisions.
Who we build Bezpieczna Kancelaria for
BezpiecznaKancelaria.pl is built for lawyers who want to use modern technology without giving up control over their documents, deadlines and the way their law firm operates.
For teams that do not want to manage cases across several disconnected applications.
For law firms that understand security goes beyond an account password.
For lawyers who want to use artificial intelligence but expect it to operate within clearly defined boundaries.
For professionals who need a system suited to the responsibilities of legal practice.
We build the system with lawyers and for lawyers
Bezpieczna Kancelaria was not created in isolation from the day-to-day work of law firms.
Its principal founder and creator is Paweł Gościcki. The system was built by a four-person team that includes an experienced SaaS application penetration testing specialist in a key role. We designed individual solutions based on experience gained while working with several law firms and observing the problems they face in their daily work.
We combine technology expertise, a security perspective and lawyers' practical knowledge.
We are not building a system just to look modern.
We are building a work environment that law firms can trust with their documents, deadlines, processes and day-to-day organization - without giving up control over them.
Paweł Gościcki Principal founder and creator of BezpiecznaKancelaria.pl