Web and business system development in Latvia.

Corporate websites, business systems and bespoke solutions.

Development work starts with the question of what the system will have to do in three years, not with a choice of technology. We pick the technology to fit the project rather than the other way round — in practice that means a corporate website and an internal business system are rarely built with the same toolset, even when both end up with the same client.

We work with the systems and data you already have rather than insisting on starting from scratch. In most projects something in the company already works — accounting, inventory, a client list in a spreadsheet. That data is company value, and migration is part of the project rather than a footnote at the end. We check data quality at the start of a project precisely because duplicate client records discovered a week before launch mean a postponement.

Typical projects in this category: a corporate website with content management, a client or partner portal, a booking or application system, an internal record-keeping system, an integration layer between existing systems. Several of them keep growing for years after launch — the Dispo B2B travel platform is one such case, where the original scope was a fraction of what the system contains today.

The work runs in stages with a visible result at each. We offer a fixed price where the scope really can be determined in advance; where it cannot, we say so and work in stages with a separate estimate for each.

• PHP
• Laravel
• Symfony
• Odoo
• JavaScript

Keeping existing systems running without surprises.

Maintenance is what decides whether a system is still an asset after three years or has already become a liability. It covers security updates, backups with tested restores, availability monitoring and performance optimisation. A backup that has never been restored is not a backup — we test them rather than assume.

We also take over systems built by someone else. Often that is the first step towards understanding what is going on in there: a takeover starts with an audit recording which technology versions are running, which of them no longer receive security updates, where the code and access live, and what would happen if the server disappeared tonight. That document is frequently the first time the company has a complete list of what it owns.

Performance is addressed with measurements rather than impressions. We start from real user data — where the site is slow, on which devices, in which countries — and fix what affects the majority. The typical gains come from images, database queries and caching, not from changing framework.

Maintenance is offered as a monthly agreement with a defined response time. It can be cancelled, and access stays with you — deliberately, as with every other service here.

• Hosting
• Security
• Monitoring

User interfaces, visual identity and prototypes.

Design in this practice is not a separate service bought for appearance. It is a way of reducing development cost: we validate a prototype before development, because changes are cheap at that stage and are not cheap after launch. In practice that means a clickable prototype that can be shown to real users before the first line of code is written.

For business systems, interface work is mostly about how many steps the most frequent task takes. A screen that looks modern but needs seven clicks where two would do is, to the person using it, worse than the old one. So we start by counting the frequent tasks, not by choosing a colour palette.

For public-facing sites the work also covers visual identity — typography, colour, image treatment — and a design system that lets the site grow without every new section looking different. A design system is not a luxury: without one, every subsequent addition needs its own design work.

Where a company already has brand guidelines we work within them. Where it does not, we propose the minimum set the project actually needs rather than a full brand book that costs more than the site.

• UI/UX
• Brand
• Prototypes

Online stores, integrations and technical search optimisation.

In an online store project, development is the smaller part. The larger part is integrations: the payment provider, courier services with real-time pricing and label printing, the accounting system, inventory levels, VAT handling for cross-border sales. These are also where projects most often stall, so we scope them before starting rather than along the way.

Depending on scope we work with off-the-shelf platforms (WooCommerce, the Odoo store) or build to order. Off-the-shelf is the right decision more often than companies assume; a bespoke store is justified when the sales process itself is unusual — B2B with individual pricing, configurable products, or an approval flow.

Search optimisation here means technical groundwork and content, not promises about first place: an indexable structure, canonical URLs, structured data for products, mobile performance, hreflang for multilingual stores, and clean redirects after a migration. Measurable targets are defined in advance, and they are visibility and conversion rather than the position of one keyword.

If e-commerce is a standing line of business for you rather than a single project, say so on the call — that is a long-term arrangement with a different rhythm.

• SEO
• Online stores
• Integrations

Code, documentation and access stay with you.

In every project the code lives in your repository, the domain and hosting are registered in your name, and documentation is handed over with the system. If the engagement ends, the system keeps running and another team can take it over without a separate negotiation with us.

This is not generosity but a practical condition: a vendor holding the access keys earns, over the long run, from the client being unable to leave. This practice earns from clients staying because they want to.

Portfolio.

The portfolio spans logistics, travel, retail, business systems and services. Two projects have full case studies written up; those are currently published in Latvian only, and we are glad to walk through either of them in English on a call.