Web software

Bespoke software makes sense when the process is your edge: prices per customer, your own way of working, a link between programs that off-the-shelf products do not know about. If your process is the same as everyone else's in the trade — invoicing, payroll, standard bookkeeping — an off-the-shelf program is almost always the better choice. When that is the case, we say so at the first meeting.

An Excel spreadsheet is replaced in stages, not in one big switch. First we write down who enters what, who checks it and where the spreadsheet breaks; then we build the most painful step and move the data across instead of retyping it. The old and new ways run side by side until the numbers match, and only then is the spreadsheet retired.

Bespoke web software connects to any ERP, stock or accounting program — through an API, a regular file or direct access to its database. We check what and how yours exports before promising a date. At Radans, the warehouse software feeds the B2B store twice a day and gets every order back. We also connect to systems we did not write: a virtual fitting-room module we added to a client's clothing store reads its items, sizes and prices.

You own the code, the database and the data. You get the documentation, and the logins are in your name, so another developer can pick up where we left off. Upkeep is a separate contract, not a condition: you can keep it with us as website maintenance, hand it to another team or do without it.

The timeline for bespoke web software is set once the scope is written down, not before, because it depends on the number of steps and integrations. The first version covers one step and ships before anything else, so you work with it while we build the next. Whatever could stretch the timeline shows up during scoping: a program with no ready export, where the connection is written from scratch, or spreadsheets that need tidying first.

Yes, web software can run only inside a company's own network. The warehouse software we wrote for Zdradech is installed on a computer at the company that acts as the server; every other device opens it in a browser, and there is no access from outside. When a system has to be reachable from anywhere, it can run on ordinary shared hosting, with no server of your own.

You get our own analytics: visits, journeys through the site, funnels and click heatmaps per device type. It runs with no third-party scripts, stores no IP addresses and switches on only after the visitor consents, and the data stays on your server rather than in someone else's account. Google Analytics can run alongside it if you want it, and it too loads only after consent. It is not required.