Skip to content

Offer: what we build, how long it takes, on what terms

3 items

What you order and on what terms

Three parts of the order card: the situations companies come to us with, what each type of project covers along with its typical timing, and how payment is split into three stages. The timing and the build price come after the analysis and stay fixed for the agreed scope.

01

Who this is for

Three situations companies come to us with, and what usually follows. If yours is different, write it in your own words in the form.

0103

Situation 016–14 weeks

A program for the company

You have a process that today lives in spreadsheets and e-mails: orders, jobs, inventory, schedules. You need a system with accounts, permissions and a change history, where everyone sees their own tasks and nobody overwrites someone else's data.

You have
a process living in spreadsheets and e-mails
You need
a system with accounts, permissions, change history
You get
Program for the company · 6–14 weeks
a fixed price after the analysis · what we build and how long it takes →
Situation 023–10 weeks

Connecting systems

You have a working shop, warehouse or accounting system and want to connect it to a sales portal, payments, a courier or a partner, without copying data by hand and without a second place where the same data lives.

You have
a working shop, warehouse or accounting system
You need
a connection to a portal, payments, a courier or a partner
You get
Connected systems · 3–10 weeks
a fixed price after the analysis · what we build and how long it takes →
Situation 0310–20 weeks

Platform

You have an idea for a platform with users, content and payments and want to build it so it can be maintained after launch: with roles, moderation and backups, not just a screen to demo.

You have
an idea for a platform with users, content and payments
You need
roles, moderation and backups from day one
You get
Platform · 10–20 weeks
a fixed price after the analysis · what we build and how long it takes →

And one more thing:We also build ordinary company websites, and three of them have been running for years: see the gallery of work.

02

What we build and how long it takes

Four types of project we build, with the typical time each one takes and a link to a place where that kind of work is already running in public.

0203

Project typeTypical time from the start of the build · scale 0–20 weeksProof
01Company website2–4 weekslive

What it usually includes

A site that presents the company and collects enquiries: what you offer, a contact form, news or a portfolio, your own web address and mailboxes, and visibility in Google. You edit the content yourselves, without calling us.

Proof

Three sites we built: LUMAC, Ogrodowe Sprawy, Ogrody Luizy

see these sites →
02A program for running orders and jobs6–14 weekslive

What it usually includes

Staff accounts with permissions, a list of jobs or orders with stages, a change history, printouts and spreadsheet export, e-mail notifications.

Proof

FufuTool: the team and the list of jobs waiting to run

see it in our system →
03Connecting your system to a portal or to payments3–10 weekslive

What it usually includes

A connection to a sales portal, payments, a courier or a partner: data flowing both ways, a second attempt after a failure, a log of everything that happened, and an alert when something does not match.

Proof

FufuTool: publishing to Allegro and zaflache

see it in our system →
04Platform with users and payments10–20 weekslive

What it usually includes

Signing up and signing in, roles from ordinary user to administrator, content added by the users themselves, card payments or a monthly subscription, a screen for the administrator, and checking of what people post.

Proof

zaflache: accounts and roles

see it in our system →

a fixed price after the analysis for every type · click a row to see what it covers

Time counted from the start of the build, after the analysis, for what the second column lists. The timing for your own project comes only after the analysis, on the terms below.

Price

from PLN 2,000 net

We price every project on its own: after the analysis you get one fixed figure, not an open-ended guess.

how we bill →

Notes

A company website is the first row of this table and runs on the same rule as every other type: a fixed price after the analysis. Its proof is three sites we built rather than a screen inside one of our own systems, which is why its link leads to the gallery of work.

For systems we have not worked with before, such as a warehouse and accounting system (an ERP) or KSeF, Poland's national e-invoicing system, we connect the same way we connect to any other: the analysis first establishes what they actually open up, and only then do we give a date. We do not claim we have done it already.

03

Terms

Three stages, each paid for separately. We set every amount for the project in hand after the analysis: we publish no hourly rates, no analysis prices and no monthly fees.

0303

01

Analysis

1–2 weeks at a price set before it starts. You get drawings of the screens, a list of the data the system will hold, a schedule, a list of risks and a fixed price for the build; the result is yours, even if we do not go further.

Time
1–2 weeks
Billing
a fixed price set before the start
Result
screen drawings, the list of data, a schedule, a list of risks

the result is yours, even if we don't go further

02

Build

A fixed price after the analysis, or billing by the hour at the rate written in the contract. You pay stage by stage: each stage once you have accepted a working version.

Billing
a fixed price after the analysis, or an hourly rate from the contract
Payment
by stage, each after a working version is accepted
Result
a working version after every stage

30 days of free fixes after acceptance included

03

Maintenance

A monthly fee matched to the work: constant checking that the system is running, backups we load back to prove they work, updates, a pool of hours and a response time written into the contract.

Billing
a monthly fee matched to the work
Scope
constant checking, backups we load back, updates
In the contract
a pool of hours and a response time

response time written into the contract

In every contract

  • An account holding the code and its full change history (the technical name: a repository) is yours from day one.
  • Transfer of copyright to the code after payment for each stage.
  • A non-disclosure agreement (NDA) on request, even before you describe the project to us.
  • A written contract with a schedule and a list of acceptances.
  • 30 days of free fixes after acceptance included, plus the statutory warranty on the terms of the contract.

What we do not promise

  • A deadline before the analysis.
  • A connection to a portal that has refused us access. Without its consent nobody can build it — neither we nor anyone else.
  • Hours without a report on what they produced.
  • A project without a decision-maker on your side.
  • A first, stripped-down version of a system without a maintenance plan.

If your project fits here, that doesn't mean it's bad; it means we're not the best fit for it.