Software development · Eindhoven
Software development company in Eindhoven.
QalbIT builds custom software, business websites and mobile apps for Eindhoven companies from Ahmedabad, India: engineering and manufacturing teams around the Brainport region whose internal tools have not kept pace with the machines on the shop floor, and the agencies, retailers and service businesses that need a website or a first product built to a written scope. There is no QalbIT office in Eindhoven and no Netherlands entity, and this page sets out exactly what that changes.
Eindhoven is where a remote partner loses the least to the clock of any market we serve. The Netherlands sits 3.5 to 4.5 hours behind Ahmedabad, so a Dutch working day falls entirely inside ours rather than only a slice of it. The rest of this page covers what that overlap is worth, GDPR, and where a local studio is honestly the better hire.
2018
Building software since
120+
Projects delivered
3.5–4.5h
Time difference, Ahmedabad to Eindhoven
5.0
Clutch rating, 8 reviews
Get your free estimate
Three quick questions: scope, approach and a price range back within 48 hours. No sales call required first.
Definition
What a remote software partner actually does for an Eindhoven company
QalbIT builds custom software, websites and mobile apps for Eindhoven companies as a remote engineering partner rather than a local studio. Two things shape most projects here: a manufacturing or engineering process the software has to fit exactly, and EU data protection rules that apply the moment personal data is involved. We design for both, working from Ahmedabad, India, with a time difference small enough that a Dutch working day sits entirely inside ours.
The difference that matters is not the engineering. It is the contract, the clock and who is accountable for what.
A studio in Eindhoven or Tilburg sits inside your own legal system: someone can be at your office on Thursday, the invoice carries Dutch VAT, and procurement has nothing unusual to read. A remote partner sits outside that. It changes three things: how the working day lines up, what your compliance contact has to document, and who carries which obligation once personal data is in scope.
None of the three is a reason to stop. Each has a known answer, and each is cheap to settle before a contract and expensive to discover after the first supplier review.
We are the remote option, and we would rather set out the case here than have it surface after a deposit.
At a glance
Core focus
Custom software, business websites, WordPress builds, mobile apps and integrations
Engagements
First builds · rebuilds of software you have outgrown · integrations with ERP and machine data · standing engineering pods
Delivery
Remote from Ahmedabad; your working day overlaps ours by 3.5 to 4.5 hours, every day of the week
Eindhoven position
No office, no staff, no Netherlands entity
Ownership
Repositories, cloud accounts and IP in your name, assigned as the work is created
Definition
Local studio vs freelance developer vs remote engineering partner
Three purchases that get compared on price when they are not the same purchase.
Eindhoven or Dutch studio
Registered with the KvK, on Dutch hours all day, able to sit in your office. You are buying proximity and a domestic invoice. Best when the work is stakeholder-heavy, needs someone on a factory floor, or runs through procurement that expects a local supplier.
Freelance or ZZP developer
One person billed by the day into a process you already run. You are buying capacity; architecture, review and release stay with you. Best when you already have someone technical who can direct another pair of hands.
Remote engineering partner
A small senior team that owns a defined build, works most of your day from outside the country, and hands over the repository at the end. There is no Dutch entity, so the contract and the data-protection position are handled properly at the start. Best when you know what the system must do and want it built well the first time.
We are the third. Where one of the first two suits you better, we say so on the first call rather than after a deposit.
Fit
When a remote partner is the right call for an Eindhoven team, and when it is not
Most vendor pages argue one side of this. Here is the version with both sides on it.
Hire a remote partner when
- You can describe what the system has to do, and someone on your side can decide without a committee.
- The work is a defined build or rebuild rather than an open-ended programme with a moving sponsor.
- A few hours of live contact each day is enough, and the rest can run on a written handover.
- You want the source, the deployment pipeline and the documentation in your own hands when it is finished.
- Personal data is in scope in the ordinary way, and your compliance contact is willing to set the rules and check our evidence against them.
Hire locally instead when
- A procurement rule or a client contract requires a supplier established in the Netherlands or the EU.
- People have to be physically present: a factory floor cutover, a hardware install, a shop fit-out.
- Your security policy forbids any access to production data from outside the EU and the work cannot be done against masked data.
- Delivery has to run inside Dutch office hours only, with no written handover accepted.
- The engagement is really staff augmentation under your own architect, in which case a freelancer will serve you better and cost you less management.
What that looks like in the Brainport region
Eindhoven runs on a supplier network already: engineering and manufacturing companies here are used to working with specialist partners who are not in the same building, because the region’s own high-tech supply chain works that way. The parts of a remote software engagement that worry a careful buyer are the same parts we settle in writing before the build: where data sits, who can reach production, what is logged, how a release is approved and reversed. We would rather hand a reviewer engineering evidence than a capability deck. We turn down Eindhoven projects that fall in the second list. A remote build where a local studio was the right answer costs a great deal more than the fee, and it is visible by the third sprint.
Next step
Not sure which list you sit on?
Send us what the system has to do, what data it will hold and what your procurement rules say. We will tell you honestly which list you belong in, including when the answer is a studio closer to home.
Comparison
Remote partner vs a Dutch studio vs a freelance developer
Every row below is a real difference, including the ones we lose. There is no day-rate row: we have no sourced figure for what Eindhoven studios or freelancers charge, and inventing one would be worse than leaving the column blank. We will run this against your actual scope, your data profile and your procurement rules rather than the generic case.
| Eindhoven or Dutch studio | Freelance (ZZP) developer | QalbIT (remote partner) | |
|---|---|---|---|
| Can be in your office | Yes | Often | No |
| Live hours on Dutch time | Full working day | Full working day, usually | 3.5 to 4.5 hours behind, inside your whole working day |
| Who owns the architecture | The studio | You do | We do, reviewed with your technical lead |
| Who owns testing and release | The studio | You do | We do, with your sign-off as the gate |
| Contract and currency | Domestic, EUR | Domestic, EUR | Your contract, invoiced in EUR or USD as agreed |
| Source code and IP | Varies by contract | Yours | Yours, assigned as the work is created |
| Security and due-diligence questionnaires | Routine | Rare | Completed by us, on request |
| Tenders requiring an EU-established supplier | Eligible | Depends on registration | Not eligible |
| Team continuity | Moves with studio workload | One person, availability varies | Small, senior, named in the proposal and unchanged |
01
The "No" and "Not eligible" rows are the point.
A comparison table where one supplier wins every row is a brochure. The rows above are honest reasons to hire someone else, and it is better to find them here than four months into a contract.
02
Hosting and engineering location are separate questions.
Your platform can run on infrastructure in an EU region, under your own account, while the engineers writing it sit elsewhere. That distinction settles most of a due-diligence conversation.
03
A freelancer and an engineering partner are not substitutes.
A single contractor is capacity added to a process you already run. If nobody on your side is holding architecture, review and release quality, that capacity produces code faster than it produces a working system.
04
Tender eligibility is binary.
If a client flow-down or a procurement rule requires an EU-established supplier, no amount of engineering quality substitutes for it. Ask us on the first call and the answer comes back the same day.
What we build
Software we build for Eindhoven companies
Systems that share one record, so a production figure, an order or a customer record moves through operations and finance without three people retyping it.
Platforms
Operations platforms for engineering and manufacturing teams
Production tracking, quality checks, scheduling and reporting built around a process on the factory floor, usually replacing a spreadsheet and a tool nobody supports any more.
Websites
Business websites and WordPress builds
A fast, well-structured website in WordPress or as a custom build, easy for your own team to edit afterwards without calling us for every text change.
SaaS
SaaS products and MVPs
Multi-tenant products with billing, roles and usage limits, shaped for a founding team that needs paying users before the next funding conversation.
Mobile
Mobile apps for people away from a desk
One Flutter codebase across iOS and Android for field engineers, technicians and drivers, built offline-first because a factory floor or a van rarely has reliable signal.
Integrations
APIs and integration engineering
Wiring an ERP, a machine data feed or a payment provider to the systems around it, with queues, retries and a reconciliation view so a failed message is visible rather than silent.
Cloud
Cloud environments and delivery pipelines
AWS accounts in your name, in an EU region, infrastructure as code and staged releases, with the access logs and change history a supplier review will ask you to produce.
Cost
How much does software development cost in Eindhoven?
Custom software for an Eindhoven company is priced on scope, integration count and how much of the process is genuinely specific to the business, not on headcount. At QalbIT, fixed-scope projects start from $6,500, dedicated engineers from $3,200 per engineer per month, and a scoped MVP or website typically from $5,000. A written scope with the exclusions named comes back within 48 hours of the first call, and a first release usually lands 6 to 14 weeks after that scope is signed.
Those are our own floors, and they are the only figures on this page about what software costs. Search the question and you will find ranges spanning an order of magnitude, published with nothing behind them. We are not adding to that pile.
We also do not publish what a Dutch studio or a freelancer charges, because we have no figure we could attribute to anyone. Ask three suppliers for a quote on the same written scope and you will have better information than any page on this subject can give you.
What we do instead is scope first: a discovery call, a written scope with the exclusions listed, and a fixed price for phase one before you commit to anything beyond discovery. Below is what actually moves the number, so you can test any quote you receive, ours included.
Try the software development cost calculatorWhat moves the number
Scope of the first release
The largest single driver. One workflow built properly beats four built thinly, and a first release that does one job well is far easier to fund a second phase from.
Integration count and quality
Each connected system adds scope, and not equally. A documented REST API is straightforward. A machine or ERP feed with no clean export needs a middleware layer of its own.
Data protection evidence
Retention rules, deletion that reaches backups and an audit trail are engineering work with their own timeline. Designed in from the start they are modest; retrofitted after a request they are a project.
Roles and approval rules
Two user types is a data model. Eight, with delegated approval and segregation of duties, is a system in its own right.
Platform count
Web only, web plus one mobile platform, or web plus iOS and Android with offline sync. Each step adds build, test and release work.
Data migration depth
Moving master records is routine. Moving years of production history, reconciled against the old system, is a workstream that deserves its own estimate.
How we work with Eindhoven teams
A delivery process built around a 3.5 to 4.5 hour offset
The Netherlands sits behind Ahmedabad, not ahead of it, so your working day falls inside ours rather than only a slice of it. Every call, demo and decision lives inside that overlap.
Discovery and written scope
One call to walk through how work moves today, who touches it and where it breaks, then a written scope with the exclusions named. The document is yours whether or not you hire us.
A scope, a first-phase price range and the name of the engineer who would lead the build.
48 hours
Prototype and architecture
A clickable prototype in week one, so your operations lead argues with real screens rather than a document. Alongside it: data model, access control, hosting region and rollback path, agreed before anyone opens an editor.
Approved screens, an architecture your technical lead can read, a data-handling position agreed in writing.
1–2 weeks
Build in fortnightly slices
Working software demoed every two weeks, against your real records rather than dummy data, checked against the scope in front of you.
Working modules validated against real operational scenarios, and a backlog shaped as you went.
6–14 weeks, scope-dependent
Harden, then release
Permissions, load behaviour, backups, monitoring and a tested rollback are signed off before anything reaches your users.
A release your reviewer can accept, with the evidence attached rather than described.
2–3 weeks
Run and extend
Monitoring, a support window matched to your day, and the next slice of roadmap chosen from what people actually use.
A platform that keeps earning its place, and a team that can hand it to yours whenever you want it.
Monthly, 30 days notice
Eindhoven runs CET in winter and CEST in summer; Ahmedabad stays fixed at UTC+5:30. That is a 3.5 to 4.5 hour offset, small enough that your entire working day sits inside ours. Stand-ups, demos and decisions happen whenever you would hold them, and a written handover closes anything left over.
Book a scoping callWhere we fit best
Eindhoven projects we take on
These are the engagements that work well from a distance. The ones that do not are listed higher up the page, and we mean that list.
First build
Replacing the spreadsheet that runs the floor
Production tracking, quality checks and scheduling held together by workbooks and one person who knows the exceptions, rebuilt as a system with roles, approvals and a history of who did what. For operations and engineering teams at growing companies.
Modernisation
Rebuilding software you have outgrown
An old desktop tool or an early web application rebuilt as a maintainable platform, without losing years of records or retraining everybody in a weekend. For companies stuck on a system nobody supports any more.
Compliance
Bringing an existing system up to GDPR properly
Adding retention enforcement, deletion that reaches backups, consent records and an audit trail to a platform built before anyone asked for them. For teams facing a review, an audit or a new data protection lead.
Extension
Extending what you already own
Custom modules, portals and integrations layered on top of an ERP or a machine data system, so you keep the system of record and lose the retyping around it. For companies extending rather than replacing a core system.
Industries
Sectors we build for around Eindhoven
Operational software is industry-shaped. These are the sectors where the process knowledge transfers, and where we have already answered the compliance questions once.
High-tech and precision manufacturing
Production tracking, quality management and supplier coordination for the engineering firms in the Brainport ecosystem, where a single part can move through several specialist suppliers before it is assembled.
Automotive and mobility
Fleet, testing and component-tracking tools for the automotive and mobility companies clustered in the region, where a change in one system has to be visible everywhere else that depends on it.
Medical technology
Device data, study and quality workflows for medtech teams whose systems carry their own validation requirements, built with an audit trail from the first record rather than added afterwards.
Professional and business services
Client portals, reporting and back-office systems for the agencies and consultancies selling zakelijke software and services into the region’s manufacturing base.
Retail and e-commerce
Order management, stock and storefront integrations for retailers and brands, with card data kept out of your systems entirely by tokenising at the processor.
Education and research spin-outs
Internal tools and the first commercial platform for a research team or university spin-out turning a tool it built for itself into something worth selling.
If your sector is not on that list, the question we ask first is the same one: what does a day of this work look like, and where does it break?
Next step
Your process is the reason the off-the-shelf tool does not fit.
That is usually what starts a custom build in the first place. Describe the process and we will tell you whether it justifies the project, or whether configuring what you already own would do.
EU compliance
Building software for Eindhoven: GDPR and data protection
These are the obligations that shape how a system is built for a Netherlands company, and the questions a supplier outside the EU has to answer before you sign anything. We are engineers rather than your lawyers: this is what we build, not legal advice about what applies to you.
EU GDPR and the Dutch implementation act
Any Eindhoven system holding personal data sits under the EU General Data Protection Regulation, in force since 25 May 2018, and the Dutch implementation act, the Uitvoeringswet AVG, enforced by the Autoriteit Persoonsgegevens. The principles that reach the code are lawful basis, purpose limitation, data minimisation, storage limitation and accountability, alongside the rights of access, rectification, erasure, restriction and portability. For software that means a data inventory that matches what the system actually stores, retention rules enforced by the system rather than remembered, deletion that reaches backups and exports, and an audit trail that shows who read a record as well as who changed it. Where we process personal data on your behalf we sign your processor terms, and any transfer of data outside the EU is agreed with your compliance contact before it happens. Whether a data protection impact assessment is needed, and the transfer position for a supplier in India, are decisions for your own compliance function. We build the machinery that lets you honour the decisions they make. Sources: Regulation (EU) 2016/679 (GDPR) · Uitvoeringswet AVG · Autoriteit Persoonsgegevens.
Personal data
PCI DSS, kept out of your code
The cheapest way to handle card data is to never hold it. We tokenise at the payment provider, so the card number is captured by the provider’s own hosted field and your platform stores a token, the last four digits and a brand. Your application never sees a primary account number, which keeps the bulk of PCI DSS scope out of the code we write. Your PCI obligations remain yours, and the right self-assessment questionnaire depends on how you take payments. We build to keep the scope small and say plainly when a requested feature would widen it. Sources: PCI DSS v4.0.1 · PCI Security Standards Council.
Payments
Vendor due diligence and ISO 27001
Dutch enterprise buyers, and manufacturing firms in particular, will often ask a supplier about ISO 27001 alignment or send a security questionnaire before signing. We answer with what we actually operate: named access with least privilege, change management through pull request and review, environment separation, logging and retention, backup and restore testing, staged releases and a documented offboarding step when an engineer rolls off. We do not hold an ISO 27001 certificate. Where a buyer’s policy requires one from the supplier itself, we say so on the first call rather than let a questionnaire discover it later. If your policy requires a specific certification or an attestation report, raise it before the estimate. We will give you our current position plainly. Sources: ISO/IEC 27001:2022, referenced for context, not claimed as held.
Vendor risk
We build systems that produce this evidence natively rather than bolting a compliance module onto software that resists it. Where a deadline or an audit is driving your timeline, that date is where we start planning backwards from.
Working with us
Hiring a vendor outside the Netherlands: the honest version
Your finance, legal and security contacts will each have a short list of questions about a supplier outside the country. Here is ours, with the answers.
The contract
We sign your contract with the jurisdiction, liability and termination clauses your legal team prefers. We do not ask clients to contract under the law of another country, and we do not run engagements on an exchange of emails.
Governing law
Currency and invoicing
Invoices are raised in euros or US dollars, as agreed in the contract, against the milestones or the monthly rate written into it, with the purchase order reference your finance system needs. VAT treatment of a non-EU supplier is a matter for your accountant; we provide whatever supplier details your finance team needs to record it correctly.
EUR or USD
Intellectual property
Code, designs, documentation and infrastructure definitions are assigned to you as they are created, not on final payment. Repositories, cloud accounts and domains are opened in your name from the first commit.
Assignment
Confidentiality
An NDA is in place before you share anything sensitive. Use yours or use ours, mutual is the normal case. Nothing about your project is used as a reference without your written agreement.
NDA
Insurance and security questionnaires
Certificates of insurance are provided on request. Security questionnaires are completed by the people who would do the work, not by a sales team.
Vendor risk
No local entity, and what that rules out
QalbIT has no Netherlands entity, no Eindhoven office and nobody who can be in your building on Thursday. Where a procurement rule or a client flow-down requires an EU-established supplier or work performed inside the Netherlands, we are not eligible, and you will hear that on the first call rather than after a proposal.
The limit
None of that is a reason to avoid a remote partner. It is a reason to handle the paperwork properly at the start instead of assuming it away.
Tech stack
Technology we use for Eindhoven builds
Business systems live for a decade, so we choose technology a new engineer can read in an afternoon and your future team can maintain without us.
Backend and business logic
- Laravel (PHP 8) for modular business systems with strong audit trails.
- Node.js and NestJS where integrations and event-driven flows dominate.
- Queues, schedulers and retries for syncs, alerts and report generation.
Interface and usability
- Next.js and React, server-rendered where search traffic matters.
- Keyboard-first data entry for screens people live in all day.
- Flutter for one mobile codebase across iOS and Android, offline-first.
Data and integrations
- PostgreSQL and MySQL with constraints that protect data integrity.
- Versioned records and append-only audit trails where evidence is required.
- REST and GraphQL integrations with ERPs, machine data feeds and processors.
Security and delivery
- AWS accounts in your name, in an EU region, defined in Terraform.
- Least-privilege access, logged, with break-glass reviewed after use.
- Staged releases through GitHub Actions, every one reversible.
Already running a system nobody wants to touch? We extend what works and put in writing, before any code is written, which parts should be left exactly where they are.
Outcomes
What the project should actually change
Not projections. These are the operational changes the build is meant to produce, and how you would know whether yours did.
| What changes | How you would measure it |
|---|---|
| One record of the truth across systems | Variance between the system and a physical or manual count |
| Work moves without being retyped | Hand-offs that still require a person to copy a value |
| Approvals are enforced rather than remembered | Share of transactions with a complete approval trail |
| Data requests are answered from the system | Hours to produce an access, deletion or audit response |
| Incidents can be scoped precisely | Time to establish which records were reached, and by whom |
| Managers see position without asking anyone | Time from question to answer |
A note on sourcing
A note on sourcing
We do not quote market figures on this page: not Dutch salary bands, not studio rates, not failure-rate statistics that circulate without a traceable primary source. The only numbers here are our own, and each one names where it comes from.
Why QalbIT
Why Eindhoven companies keep us on the project
Building this kind of software since 2018
120+ engagements delivered for 50+ clients since 2018, across web, mobile and platform work. Clutch 5.0 from 8 reviews, Google 4.9 from 18 reviews, and 100% job success on Upwork. Those are the four figures we can evidence, and the four we quote.
The smallest time difference we work across
A 3.5 to 4.5 hour offset means your entire working day is live time with the people writing the code, not a queue of tickets answered overnight.
We say what we are
No Eindhoven office, no Dutch staff, no Netherlands entity and no implied presence anywhere on this site. The compliance and paperwork sections exist because we would rather lose a deal at the scoping call than at a supplier review.
The named engineers are the ones who build it
Whoever appears in the proposal writes the code. No part of your build is handed to another firm, and nobody is quietly swapped mid-sprint to cover another account.
We will tell you to hire locally
When a Dutch studio is genuinely the better answer, you hear it on the first call. It costs us a project and saves you a year.
QalbIT did a great job turning my idea into a real product. What I really appreciate is how well they understand my requirements, even when I'm not fully sure how to explain or finalize things. They listen patiently, guide me when I'm stuck, and always try to find the right solution. I really enjoy working with their team and I'm definitely looking forward to continuing our work together in the future.
FAQs · Software development in Eindhoven
Questions Eindhoven teams ask before they start
Overlap hours, budgets, GDPR, paperwork and who owns what, answered the way we would answer them on a call.
Talk to the teamNext step
Let us scope the first release.
Tell us how work moves through your business today, where it stalls, and which date cannot move. We will map it, name the system that earns its place first, and put an honest price range against a phased plan. If a Dutch studio is the better answer, that is what the reply will say. A written scope with the exclusions listed comes back within 48 hours, yours to keep either way.