Web, mobile and e-commerce
Not every company needs an ERP.
We also build corporate websites, e-commerce, iOS and Android applications and desktop software. Interface design is done by our own team rather than bought in and coded up.
Web App Development
Scalable web platforms and SaaS products.
E-Commerce Development
E-commerce sites and ordering systems that sell.
Mobile App Development
Store-ready mobile apps for iOS and Android.
Desktop App Development
Desktop applications for teams that keep one screen open all day.
UI/UX Design
Interfaces people use without having to think.
There are no figures on this page, because the same job does not cost the same at two companies. But “it depends” is not an answer either. Below is which item pulls the price in which direction, one by one, so you can measure your own job against the list.
A site on the company’s own address, with content you manage yourself, written to be found rather than merely to exist.
- Number of templates
- The first driver is not how many pages but how many distinct layouts are designed. Fifty pages from one template cost less than five different ones.
- Whether design is from scratch
- Adapting a bought theme and designing an interface from nothing are far apart. Our own team does the design; where a theme is wanted instead, we say so plainly.
- Multiple languages
- A second language is not just translated text: URL structure, search metadata and content management are built for it from the start. Added later, it costs more.
- Content management
- Will you update the text yourself, or does it change once a year? Where no admin panel is needed, that cost never arises.
- Who holds the content
- If copy and images are ready on your side the schedule shortens. If they have to be written, that is a separate line and it shows in the price.
- Integrations
- Forms, email, booking, a CRM or a connection to an existing system — each link is counted separately.
A store running on your own infrastructure rather than rented from a platform, built together with payment, shipping, invoicing and stock.
- Products and variants
- Five hundred products cost little on their own; variants are the real driver. As size, colour, measure and bundle combinations multiply, both the data model and the interface get harder.
- B2C or B2B
- Selling to dealers is a different system from selling to consumers: accounts, price lists, statements and credit limits enter the picture. Wanting both widens the scope noticeably.
- Payment and shipping integrations
- Every payment gateway and every carrier is a separate integration, instalments and returns included. How many get connected moves the price directly.
- e-Invoicing and accounting
- Where an order should flow into invoicing and accounting on its own, an integration layer sits between them. Handled manually, that line never arises.
- Marketplace channels
- If stock and prices go to marketplaces, each channel is counted separately — and whether the link is one-way or two-way changes the price again.
- Multi-language, multi-currency
- Selling abroad brings tax rules, currency, customs documents and language structure into the architecture from the start.
Applications for iOS and Android, with store submission and the release management that follows as part of the job.
- One platform or two
- Android alone or iOS alone costs less than both. But starting with one and adding the second later costs more than planning for both from the outset.
- Whether a backend exists
- If there is already a system for the app to talk to, the job is the app. If not, the server side is built from nothing — often the larger half of the work.
- Offline capability
- Recording while disconnected and reconciling afterwards makes an app markedly harder. For apps used in the field it is not optional.
- Device capabilities
- Camera, location, notifications, barcode scanning, file access and payments — each is separate work and a separate item in store review.
- Users and permissions
- An app where everyone sees the same screen and one that needs role-based permissions are far apart.
- Store processes
- App Store and Google Play submission, account setup and version updates run throughout the job rather than at the end of it.
- Why no price list?
- Because very different jobs sit under the same heading. A corporate site with five templates and a single-page brochure are written on the same line and are not the same work. Once scope is settled we give a fixed price, and it does not move during the project.
- How is scope settled?
- On small jobs one conversation is enough. Where scope is genuinely unclear we run a paid technical assessment first, and you are left with a document that holds value whether or not you continue with us.
- Do you use themes or hosted platforms?
- If asked, yes, and we say so plainly. It is not our default: on a hosted platform you keep paying rent, and your store is yours only as far as that platform allows.
- What happens after launch?
- Defect fixes under warranty are free of charge. Continued development and technical oversight run under a separate maintenance agreement.
- Do you write the content?
- If copy and images are ready on your side the schedule shortens. If they have to be written, that is agreed as a separate line at the outset.
Tell us what you want built.
Let’s narrow the scope together. Once it is clear, we give a fixed price.