Software development

Custom software development

We develop web applications, Windows programs and mobile apps. We plan the features around the work they need to do and the systems you already use.

Platforms
Web, Windows, mobile
Interface and text
Bulgarian and English
Hosting
On our servers until you choose otherwise. The code is yours
Working since
2018

What you get

You receive an application with the agreed features and distribution method. It can include accounts, payments, an admin panel, reports and automated emails. We also build integrations that exchange data between a website, accounting software and other systems.

Around the code, the same studio does the interface design, the text in Bulgarian and English, the app-store and installer builds, the hosting, and SEO if strangers need to find the product.

Web app, Windows program or mobile app?

We choose the platform around where and how the software will be used. A web application opens in a browser. A Windows program can work closely with local files and system features, as SnapQio does. A mobile app can make use of the camera, notifications and other phone features. Offline access, installation and device support are part of that decision.

The platform choice also determines installation, updates and publication. Read the details for Windows software and mobile applications.

How a build runs

  1. A conversation about what happens today, who will use the software, and which systems it has to talk to.
  2. A written scope with the price and the date in it. Code starts once both exist.
  3. A working version early, changing where you can see it. A screen you dislike in week two is a small fix; once payments, data and two languages hang off it, it is a large one.
  4. Checks on real phones, tablets and the computers it will run on, then launch and hosting.

The fuller version is on how we work.

What moves the price of custom software?

Six decisions move the price of custom software: accounts, recurring payments, a second language, files from other companies' systems, shipping to Windows or the app stores, and the admin panel. Each project is quoted once its scope is written.

Accounts include registration, login, password recovery and access permissions. We also plan how user data will be managed and deleted.

For payments, we plan checkout, payment confirmation, refunds and invoices. Subscriptions also need renewals, cancellations and handling for unsuccessful charges. Payment processing fees are a separate running cost, set by the provider.

Another language requires translation and editing, layout checks and a review of every message in the app. We plan for it from the start when it is part of the scope.

File imports require work for each supported format, including validation and handling of incomplete data. Dekloro, for example, reads reports from Revolut, Trading 212 and Binance. Changes to those formats can require updates to the importer.

Shipping to Windows adds a code-signing certificate, issued only after the organisation behind it has been validated, and a second build when the program must run on ARM64 as well as x64, as SnapQio does. Even a signed file can trigger a SmartScreen warning until it builds reputation, and Microsoft's documentation says an Extended Validation certificate no longer skips that wait (SmartScreen reputation).

For the admin panel, we agree on which data you need to view, what you will edit and which staff members will have access.

Whether to build at all is a separate sum; custom software or off-the-shelf works it through over several years.

How long does it take?

The delivery date goes into the written scope and depends on four things: how many outside systems the software connects to, who writes the text, whether there are accounts and payments, and how many languages it speaks. The schedule also allows for app-store review. Apple reviews every app and every update and says 90% of submissions are reviewed in under 24 hours (App Review); Google Play sends some apps to an extended review of up to seven days, longer in exceptional cases (Play Console Help).

For an integration, we review the existing system documentation and test its available features. Access to a test environment helps us check data exchange before the final estimate. Unresolved dependencies are recorded in the scope.

Who owns the code, and where it runs

You own the code. Its full change history, the domain, the text and the images come with it, and so does access to every account the product depends on: registrar, payment provider, app-store profile, analytics. The handover includes a short written note of where each piece lives and how a new version goes out.

By default the software runs on our servers, and keeping it updated, backed up and monitored is our job. If you would rather host it yourself, now or in three years, we move everything across and set it up with you. The contract clauses worth having either way are in who owns the code when a studio builds it.

The maintenance plan covers compatibility updates, dependencies and connected services. We discuss these ongoing costs alongside the initial build.

Three builds you can open

Riomera, SnapQio and Dekloro are live; the other three projects are on the work page.

ProjectWhat it isWhat the build had to include
RiomeraWellness platform in Bulgarian and EnglishAccounts, paid subscriptions, content in both languages, an assessment of about two minutes that starts without a card
SnapQioWindows screenshot and screen-recording tool, plus the site that sells itHotkey capture, annotation, blur, OCR, 60 FPS recording; x64 and ARM64 builds; offline use, no account; sharing is optional
DekloroBulgarian investment-tax calculatorRevolut, Trading 212 and Binance reports turned into the annual return line by line, FIFO, in EUR, without a broker password

Caption: Core features from three of our software projects.

Before the first invoice

How much does custom software development cost?

Each project is priced once its scope is written, because a short brief can hide a big job. The quote is split into lines, so you can see what accounts, payments, a second language or store distribution add.

Do you build mobile apps as well?

Yes, with the App Store and Google Play builds included. Versetio, the family activity app we built for children aged 6 to 14 and a parent, shows how small a good first version can be: onboarding asks only for a first name or nickname and an age range.

Can the software connect to the programs we already use?

Yes, when the other program has an API or at least exports a file. The link can be a nightly import from an accounting program or a live two-way connection with a supplier's system.

Can we move it to our own hosting later?

Yes, at any point. The code, the domain and the accounts are already yours, so moving is a handover: we copy everything across, set it up with you, and check it runs before switching anything off on our side.