Engineering
Custom web applications and marketing sites, native iOS and Android apps, Shopify Plus stores, AI agents shipped to production, code modernization of legacy systems, and DevOps work for the platform underneath all of it.
Scope in writing, then code
Software engagements go sideways at one of two moments. Either the scope wasn’t agreed in enough detail before the first sprint, or the technology was picked before anyone understood what the work actually had to do. An extra week spent on the scoping document costs less than three months spent building the wrong thing on the wrong stack.
The technology gets chosen after the requirements are understood. The framework, language, CMS, database, infrastructure — all decided once we know what the system has to do, what it has to integrate with, and what the team that will run it after handover already knows. Default stacks exist; you can swap any of them on a per-engagement basis once the scoping conversation says so.
What we build for clients
Each card opens its own page: how the scoping engagement runs, what gets delivered, and where the build pricing tier starts.
Scope, build, hand over
Paid scoping
Discovery is a paid engagement. We map features, user journeys, API dependencies, data models, and operational constraints. The output is a written scope document and a fixed-price quote. If the scope says it, the price covers it; if it doesn’t, scope changes get re-quoted in writing and signed off before any work happens against them.
Build in sprints
Two-week sprints with working code at the end of each one. Architecture decisions are written down as ADRs (decision, alternatives considered, rationale) so the team you hand the project off to can understand why things are the way they are. Tests get written alongside the code as it ships, so the test suite reflects the codebase the day the build is done.
Hand over with documentation
Code, infrastructure as code, deployment pipelines, environment configuration, runbook. Hand-over includes a walkthrough with whoever will own the system afterwards. You can take it in-house, keep us on a maintenance retainer, or move it to a different vendor — the project is structured to make all three viable.
Where each service starts
Project work is fixed-price after the paid scoping conversation. Retainers run month-to-month after any initial commitment period you choose.
Web Development
Marketing sites from €5,000. Web applications from €15,000. Hourly retainer for ongoing work: €250 / hr.
Mobile Development
iOS, Android, and cross-platform apps — from €25,000 for a focused MVP.
Shopify Plus
Custom theme and app builds from €15,000. Migration from another platform from €25,000.
Modernization & AI-Ready
Audit at €5,000 fixed (delivered in one week). Modernization projects from €25,000.
AI Agents
Pilot at €15,000 fixed-price (4-week build). Production deployments from €30,000.
DevOps
Internal developer portal (IDP) from €15,000. CI/CD + observability from €8,000. DevOps-as-a-Service from €4,500 / month.
Build engagements — questions we hear most
How do you choose the tech stack?
The stack is chosen during the paid scoping engagement, once we understand the project’s requirements — what needs to be built, who uses it, how it scales, and what your team already works with. We present the options and trade-offs before any code is written. Cloud, hosting, database, and tooling are all part of that conversation.
Who owns the code?
You do. Everything we write goes into a repository you own from day one. The build is yours; the infrastructure-as-code is yours; the deployment scripts are yours. If you decide to take the project in-house or move it to a different team, the handover is a standard Git repository transfer with a written walkthrough of the architecture.
How are mobile apps delivered?
Mobile projects are delivered with fixed-price scope, project management, code review, and QA included. You have one point of contact and an agreed scope before work begins.
What does your QA approach look like?
Tests written alongside the code as it ships. Code review on every change. Sprint demos to whoever from your team is closest to the user. Staging environment that mirrors production for any integration-sensitive work. Phased production rollouts with rollback documented and tested as part of the deployment design.
Can you maintain a system after the build is done?
Yes — maintenance retainers are available at the hourly rate (€250 / hr for web, €250 / hr for infrastructure) with a monthly minimum that scales with the system size. Alternatively, the project is structured for a clean handover so you can take it in-house or move it to a different team without our involvement.
Describe what you’re trying to build
Walk us through the project — what it does, who uses it, what it has to integrate with. We’ll come back with a written summary and, where the requirements are clear, a proposal for the paid scoping engagement that defines the build.
Contact us → See pricing →