Custom software development
We deliver custom software from the first analysis to long-term operation — web applications, company information systems and mobile applications. For multinationals and early-stage startups alike. The source code is yours once the project is done.
Send us a brief
Which page is right for you?
Web application development
Need an application for customers, suppliers or partners?
Information systems development
Looking to digitise internal agenda and processes for your employees?
Custom software development
Not sure exactly which solution would suit you best? We're happy to help.
What custom software is and when it pays off
Custom software is built around your processes — from the data model through the screens to the connections with surrounding systems. You are not buying a licence to a finished product and bending your work to fit how a vendor imagined it. You pay for the development, and you own the result.
It does not always pay off. For an agenda a commonly available product covers completely — accounting, e-mail, attendance in a small team — a boxed solution is cheaper and faster. Custom development makes sense where standard software constrains you: you have a process that is your competitive advantage, or an agenda that lives in spreadsheets and e-mail precisely because it fits no product.
In practice it is nearly always a combination. Accounting stays in a finished system, what makes you different gets built, and the two are joined by an API. Exactly where that line falls is the main subject of the opening analysis.
| Criterion | Boxed product | Custom software |
|---|---|---|
| Processes | You adapt to the product | The product adapts to you |
| Cost | Lower entry, per-user licences | Higher entry, then no licences |
| Ramp-up | Weeks | Months, but live in stages |
| Evolution | You wait for the vendor roadmap | You set the priorities |
| Data and code | In the vendor's hands | Yours, source code included |
| Integrations | Only what the product supports | Anything with an interface |
Three routes we deliver custom software by
Depending on who works in the software and where it runs, a project takes one of three directions. Most engagements combine two of them on one backend and a shared API — you do not have to decide up front, the analysis settles it.
Web applications
Applications in a browser for people outside your company — customers, suppliers, partners. Client and supplier portals, reservation and ordering systems, dispatching. No installation, on any device.
Web application developmentInformation systems
In-house systems for the agenda of your employees — connected to ERP, with roles and permissions, migration of data from the existing solution and user training.
Information systems developmentMobile applications
Where work happens in the field, offline mode is needed, or the phone's hardware is — scanner, camera, GPS, notifications. Cross-platform for iOS and Android on the same backend.
Mobile application developmentIf you are still validating a product idea, look at application development for startups. If you already have a prototype generated with AI tools, start with an audit of AI-generated projects before you build production on top of it.
Custom software across industries and platforms
Four projects that show the range — a large university system, a mobile app for the public, a web-and-mobile combination and a fully automated dispatching system. More in our references and case studies.
Academic system for a private university
For the University of New York in Prague we built a large system for study and administrative agenda — enrolment, timetables, grading, payments and communication with students. The project runs long-term and grows as the school's needs change.
Result: the study department handles the whole agenda in one system instead of parallel spreadsheets and paper.
UNYP case studyMobile application for a pharmacy network
An app where a customer finds the nearest pharmacy and checks whether a medicine is in stock. If it is not, the pharmacy orders it and notifies the customer. The project included connecting to the stock systems of individual pharmacies.
Result: customers no longer ring round pharmacies; the notification comes to them.
Magistra case studyWeb and mobile application for hunting associations
The complete agenda of game management — records, hunting plans, reports and statutory returns. The web side handles administration and reporting, the mobile app records data in the field, where there is often no signal.
Result: the report is created out in the district, not typed up from paper at home in the evening.
eMyslivost case studyAutomated taxi dispatching system
A dispatching system built for maximum automation — connected to driver and passenger mobile apps and to the telephone exchange. The system assigns rides and resolves situations a person used to handle.
Result: a substantial share of orders completes without a dispatcher touching it.
Modrý Anděl case study
Software engineering, not just coding up a brief
The source code is yours. No vendor lock-in
A transparent budget and a clear pricing model
Analysis first, methodology to match the project
Three routes we deliver custom software by
How the cooperation works, from enquiry to handover
This is how an engagement runs from your side — what gets signed when, when you pay and what you hold at each point. The technical phases of the build are described in more depth for web applications and information systems.
Enquiry and first consultation
We meet over what you need to solve. We do not want a finished brief — a description of the problem and an idea of who will use the software is enough. There is no charge and nothing to sign.
Phase output: a first estimate of scope and order of magnitude, plus a recommendation on where to go next.
Analysis and specification
For larger engagements a separate, paid process analysis follows. Its output is yours — you can take it to another supplier, and that is the intent, not a concession.
Phase output: a functional specification, an architecture proposal and a firm estimate.
Quote and contract
Based on the specification you get a quote with a pricing model, a schedule and milestones. The contract covers source code handover, confidentiality and what happens if the cooperation ends.
Phase output: a signed contract with clear milestones and a billing plan.
Development in iterations
You have one contact responsible for the project and access to the task system. At the end of each iteration you see a working part on a test environment. The methodology follows how stable the brief is — agile or Waterfall.
Phase output: software arriving in increments, not one delivery at the end.
Handover and acceptance
Acceptance testing against the specification, deployment to production, training. Once paid, the source code and property rights transfer to you along with the repository, documentation and infrastructure access.
Phase output: software in service and the full handover package in your hands.
Operation and further growth
Most clients continue — with a service agreement and development driven by priorities from real use. It continues because it makes sense, not because you have nowhere else to go.
Phase output: an agreed response time and a development plan for the period ahead.
Pricing models and what a budget is made of
Typical engagements here run from around CZK 700,000 for smaller tools to millions or tens of millions for company-wide systems. Concrete ranges by type of solution are on the web applications and information systems pages; this is how the price is formed and billed.
Fixed price
a bounded brief
A firm sum
When the scope is written into a specification and we do not expect it to shift substantially during development. We carry the estimating risk, you get budget certainty. Changes beyond the specification go through an amendment.
Time and materials
long-term development
A monthly cap
When priorities shift with what real use shows. We bill days actually worked against an agreed monthly cap with ongoing reporting, so the budget cannot run away without your knowledge.
Dedicated capacity
from three months
An agreed number of days
A reserved team with fixed monthly capacity working only on your priorities. It makes sense for a large product in long-term development, where you need to plan people rather than individual jobs.
What is in a budget that people do not expect
- Analysis is 5 to 15 % of the budget depending on how prepared a brief you bring — the less is settled, the larger the share.
- Project management and testing take roughly 12 % on top of the programming itself; without them software is written, not delivered.
- An integration costs whatever the other system's interface costs — days for a documented API, weeks for a CSV export from 2009.
- Migrating data from the existing solution is its own phase with its own budget, not a line item added free at the end.
- Cloud operation, backups and monitoring are monthly costs that continue after the work is handed over.
- A service agreement after launch is priced separately and follows the guaranteed response time.
These models can be combined, and on larger projects we usually do: a fixed price for the analysis and first release, further development time and materials. For an indicative figure for your own brief, the software development price calculator takes two minutes and asks for no contact details.
Calculate an indicative priceWhat a handover contains and what to ask any supplier
The most expensive mistake in choosing a supplier only shows up when you want to leave. So here is exactly what a handover includes with us — and the questions worth putting to anyone you approach. The full approach is in our guide on how to choose a quality software supplier.
The handover package
Once the project is completed and paid for, property rights and source code transfer to you. Concretely, that means:
- The Git repository including its full commit history, not a zip of the latest version.
- Technical documentation, a description of the data model and an overview of integrations.
- Access to infrastructure, domains and third-party services transferred to your own accounts.
- A documented, automated deployment process, so a new version never has to go live by hand.
- Commonly available open source technologies — no closed in-house framework tying you to us.
The questions that separate suppliers
Answers to these differ between suppliers more than anything else, and tell you more than references do.
- Who exactly will work on the project, and how long will those people stay on it?
- Who owns the source code, and what precisely is included in the handover?
- What happens if we end the cooperation — could someone else take the project over?
- How was the estimate produced, and what happens if the scope changes during development?
- How is testing done, and who carries the cost of bugs found after deployment?
Frequently asked questions about custom software development
Technologies we work with
We choose technologies for how long the project has to last, not for what is currently fashionable. Backends on Ruby on Rails and Node.js, frontends on React and TypeScript, data in PostgreSQL. An API-first approach means new software connects to your existing ecosystem and one interface serves both web and mobile. It is also a combination that is easy to hire for — if you ever want to take the project over with your own team, you will not be left looking for people who do not exist.
Considering custom software?
Start with the problem, not the solution. In the first consultation we go through the process, the users and the connections to your existing systems, and tell you straight whether custom development pays off or whether a finished product will do.