Technology that drives your business

BITESOFT starts with a conversation, not a specification. Just describe the problem or the idea and we work out the rest together. In the first meeting we ask how work is done in your company today, what keeps jamming and what you want to change. The scope comes out of that. You don’t need a finished brief, a feature list or technical knowledge, because that part is our job. If it turns out the problem can be solved without an implementation, we say so plainly instead of pushing a project on you. The first conversation is free and commits you to nothing.

In practice these conversations start with a sentence like „we retype invoices by hand”, „we don’t know whether we have a backup” or „the shop can’t see warehouse stock”. That is enough. After the call you get a short summary from us: what can be done, in what order, what is urgent and what can wait. If you come to us with something we don’t do, we say so right away and, if we know someone, point you in a direction.

BITESOFT quotes after understanding the need, not from a price list. For websites, stores and applications what matters most are the features and the integrations with systems you already run, because those decide how much work it takes. For IT support we look at the number of users, devices and systems, and at the response time you expect. Before we give a figure we do a short review of your environment, and that review is free. You get the quote as a scope broken into stages, so you can see exactly what you are paying for and what could be done later. We never bill hours outside the agreed scope without your approval.

The biggest driver of price is usually not the feature itself but the state of the system we have to connect to: the ERP version, whether an API exists, the quality of the data and whether anyone kept documentation. That is why the review comes before the quote, not after. Projects are billed by stage, ongoing support monthly. In both cases you know upfront what is in scope and what would be a separate engagement.

BITESOFT takes on both one-off projects and ongoing support, and we don’t bundle the two. You can order just a KSeF implementation, just a shop-to-ERP integration or just an invoicing panel, with no retainer attached. If after launch you want us to stay and look after the environment, we agree that separately, based on how many users and systems we actually cover. Many companies start with a single project and only move to ongoing support months later, but that is always your decision, never a condition of working with us.

We run such a single project exactly the way we run a large implementation: we agree the scope, show progress along the way and hand over documentation and instructions for your team at the end. We don’t leave behind a solution nobody but us can operate, and we don’t make the system depend on our continued presence. If you later want to develop it yourself or with someone else, you have everything you need.

BITESOFT is a Warsaw-based IT company working B2B, run by two founders with over twelve years of experience each. We do IT outsourcing, meaning we take on the role of the IT department for companies that don’t want to build one in-house. The second area is implementations and integrations: KSeF in Comarch, WAPRO and Symfonia, ERP migrations, syncing online stores with warehouse systems. The third is custom development, that is applications and panels built when a ready-made product simply doesn’t exist on the market. On top of that come backup and disaster recovery, Microsoft 365 and Intune, plus security audits and GDPR compliance.

We work mainly with small and mid-sized companies that have no IT department of their own, or one too small to carry an implementation. Our edge comes from combining two skill sets in one team: administration and infrastructure on one founder’s side, programming and integration on the other’s. That means we don’t bounce you between vendors when a problem sits on the boundary between the server and the application.

BITESOFT implements KSeF in Comarch, WAPRO and Symfonia, and when the vendor ships no ready module, we build our own. We did exactly that for a warehouse system whose supplier never planned KSeF integration: we built a panel for sending structured FA(3) invoices and collecting UPO confirmations, based on MS SQL and Docker, live in twelve days. We start by checking what your ERP can actually do and how invoices flow through the company, because that decides whether configuration is enough or code has to be written. We also handle KSeF certificates, their limits and bulk corrections.

If your ERP has a ready KSeF module, configuration, testing on a pre-production environment and training for the accounting team is usually enough. If there is no module, or it only works partially, we build an intermediate layer that pulls documents from the system, sends them to KSeF and stores the UPO where accounting looks for it. Before launch we always check how corrections and duplicates behave, because those are what most often derail implementations.

BITESOFT replies to inquiries within 24 hours, with no obligation on your side. That first reply usually contains a few clarifying questions or a suggestion to talk briefly, because a form alone rarely lets anyone quote responsibly. If the matter is urgent, an environment outage or a deadline set by regulation, say so plainly in the message or call us, and we will get back to you the same day. For ongoing IT support the response time is set in the contract and depends on how critical the systems we look after are.

We have no call centre and no sales department, so the person replying is one of the founders, the same person who will later do the work. That sometimes costs an extra hour, but it means the first answer already has substance rather than being generic. If we need more time to look into something, we say so directly and give you a date instead of going quiet.

BITESOFT stays, because a system keeps living after launch. Once it is running we take over monitoring, respond to tickets and plan the next steps, but we don’t lock that into a rigid retainer – we set the scope around what actually needs watching. In practice that means updates, keeping an eye on logs and errors, fixes after changes in third-party systems, and developing features as processes in your company change. We will also tell you honestly when something isn’t worth doing, and the final call is always yours. We care about the relationship, not the single project.

The most common pattern is that after launch we shift into a lighter mode: monitoring runs in the background and we reach out when something needs attention, or when a change is coming that is better planned ahead. Accounting system updates and legal changes are the usual examples, because with KSeF and ERP the deadlines are set by legislation. We would rather warn you three months early than fight a fire in the final week.

BITESOFT tests restores, not just the making of copies. A backup nobody has ever restored is only a feeling of safety, so for every client on ongoing support we run periodic trial restores on a test environment and record the result. We work mostly on Veeam, with replication and snapshots, and for Comarch Optima we add Zabbix monitoring so a failure doesn’t wait for a user to report it. We also measure how long a restore actually takes, because that is the number that matters on the day of an outage, not the number of copies made. You get the test report in writing.

When planning copies we look at two things people rarely ask about: how much data you can afford to lose and how long the company can run without the system. Those two answers decide whether a nightly copy is enough or replication is needed, and where we keep an off-site copy. A backup sitting on the same server as the data protects against none of the most common scenarios: encryption, fire and theft.

BITESOFT helps companies use AI while reducing the risk of company documents and client data ending up where they shouldn’t. We start by checking which AI tools the team already uses and from which accounts, because AI is often at work in a company before anyone has rolled it out. Then we write an AI usage policy, configure Microsoft 365 and Copilot, meaning file permissions, sensitivity labels and where prompts are processed, and finally train the team and leave the training records behind.

For especially sensitive data, for example in law firms and medical practices, we check whether an EU business cloud is enough or whether a language model running on a server in your office is needed. We say plainly which route makes sense, because a local server is an expense measured in tens of thousands of zloty.

BITESOFT is based in Warsaw and the surrounding area, and serves companies across Poland remotely. Most of the work, that is KSeF implementations, integrations, custom development, server administration and Microsoft 365, we do fully remotely, because it doesn’t require being on site. In Warsaw and the surrounding area, where our office is, on-site work is also possible: hardware checks, workstation setup, work on physical infrastructure. We agree the scope and the format before we start, so it is clear what happens remotely and what happens at your place. Travel beyond the Warsaw area is quoted individually.

Working remotely does not mean email-only contact here. We set up a standing communication channel and, on larger implementations, short recurring progress calls. Clients outside the Warsaw region get exactly the same support scope as local ones, with one difference: work that needs hands on site is planned ahead or arranged with a local service partner whom we coordinate remotely.