The company and answers before the contract

Not under the company name yet. FufuLabs has been in the KRS register since 24 August 2026; before that we built systems with accounts, roles, payments and connections to other systems for ourselves: zaflache.pl and fufutool.pl (the "Products" page), and we built websites for clients back in 2023–2024 (the gallery of work on the home page). That is why we start every engagement with an analysis at a price agreed up front: the screen drawings, the list of data, the schedule, the list of risks and the fixed build price are yours even if we do not go on together (the "Offer" page, the section on terms). We take on the risk of a first joint project, not you.

The code is written by the co-founders, the same two people who look after zaflache and FufuTool. Client projects take priority during working hours; our own products get fixed windows outside of that. The contract names the person leading the project, the response time, and how often we show progress, as described on the "Process" page. On larger projects we bring in vetted subcontractors, always with your knowledge and consent; responsibility for the result stays with the company.

The project keeps moving on your own resources, not ours. From day one the code sits in an account of your own that holds it together with its full change history (the technical name: a repository), and the specification, the setup instructions and the task board live with you too. The other person already knows the project, because both of us work in the same code from the start, and every change is described in the list of changes, in your own language.

The contract has a handover clause: if we cannot continue, we hand over the full set of materials and every password within the deadline written into the contract, and you can pass the project to anyone you choose. Nothing in it exists only in our heads or only on our own computers.

Because every system is different: a program for five people with one connection to another system and a payments platform for thousands of people differ in size by an order of magnitude, and a price list would hide that difference. Instead we give you two things: the lower bound where projects start (the "Offer" page), and the rule of a fixed price after the analysis. After the analysis you get one figure for an agreed scope, not an open-ended guess; you do not pay extra for surprises during the build, because catching them during the analysis is our job.

We set the build price after the analysis, and it stays fixed for the agreed scope. It depends on four things: how many roles and permissions there are (who sees and changes what), how many of your existing systems we have to connect to and whether you can give us access to them, payments and invoicing, and what already exists today: spreadsheets, a working system, or code to take over. The timing is worked out from the same four. Typical timings are on the "Offer" page. The price of the analysis itself is set before it starts and does not depend on what it finds.

Yes, before you describe anything. Send us your version, or ask for ours at [email protected]; we sign in this order: the agreement first, the project description after. We treat your description as confidential even without such an agreement: it goes only to the company mailbox and is not stored anywhere outside e-mail (see the Privacy policy in the footer).

You do. From day one we set up an account in your name that holds the code together with its full change history (the technical name: a repository), so the code is yours from the very first change we save, not from the final handover. Copyright to the code passes to you after payment for each stage, as written into the contract. The exceptions are free, openly licensed libraries, which we use on their own terms, and our own internal tools, for which you get a licence without a time limit; both lists are attached to the contract.

Yes, after a paid review that takes 1–2 weeks and has a fixed price, like the analysis. In it we go through the code, the database, the passwords, the backups and the way new versions are released, and at the end you get a report with a list of risks and a plan: what to take over as it is, what to fix first, what not to touch. The report is yours even if you have someone else carry out the takeover. We do not take over systems without access to the code and the database.

By default we build new systems in TypeScript on a Postgres database, the same as zaflache and FufuTool (the "Products" page). We connect to your shop, your accounting or your warehouse system through whatever door it opens to other programs, once the analysis has shown that the access and the documentation let us do it safely. For systems we have not connected to before, such as a warehouse and accounting system (an ERP) or KSeF, Poland's national e-invoicing system, we follow the pattern that already connects FufuTool to outside portals; we do not claim we have done it already. And we do not rewrite a working system into our favourite technology just because it is our favourite.

In stages, after each acceptance. You pay for the analysis up front, at a price set before it starts. The build is split in the schedule into stages with a described result; we invoice after each stage is accepted, not by the hour, unless you choose to be billed by the hour at the rate set in the contract. Looking after the system after launch is billed as a monthly fee. Payment terms are written into the contract.

First a period of free fixes, described on the "Offer" and "Process" pages: faults reported in that time are put right at no extra charge. After that you choose one of two paths: a monthly fee for looking after the system (constant checking that it is running, backups we load back to prove they work, updates, a pool of hours for changes, a response time written into the contract) or a full handover of everything: the code, the setup instructions, every password, and a list of the outside pieces it relies on. Both options are in the contract from the start, so the decision can wait until after acceptance.

Fully remotely, across Poland and abroad; the analysis meetings are held online. We speak and write Polish and English; the documentation, the contract and the list of changes are kept in whichever of the two you choose. We work on Warsaw time; for clients in other time zones we write a meeting window into the contract.

Yes. An ordinary company website is the first row in the table of what we build (the "Offer" page), on the same terms as everything else: a fixed price after the analysis. You get the pages that present the company, a form for enquiries, your own web address and mailboxes, work so the site shows up in Google, and content you can edit yourselves without calling us. Three such sites from 2023–2024 are in the gallery of work on the home page. If the site is meant to grow later into something bigger, with accounts, payments or a program for running orders, say so when you describe the project and we will build it so the bigger part can be added without starting over.

Yes. We do not publish a phone number, so that every enquiry leaves a written trail, but the form has a phone field marked "if you would rather talk". Leave a number and two sentences about the project; we call back within the same time we take to answer in writing (the "Process" page). You can also write to [email protected] and suggest a time to talk.