Brief
You describe the users, the job to be done, current tools and any hard date or constraint. A page is enough.
The Netherlands is used to English-language vendors and sharp product questions. Hirvex Technologies fits that pattern: direct communication, written decisions, EU hosting when needed. Dutch-language UI is available as a scoped translation effort.
Who this is for. Dutch product companies, scale-ups and operators with existing English working culture.
These are the patterns that show up before a useful first release—not abstract “digital transformation” language.
English by default. iDEAL or other local payments only with the PSP you already use. Privacy artefacts before production data. Pairing hours that match CET.
Scope is confirmed in discovery. This is the shape of work we are equipped to deliver—not a menu you must buy in full.
A useful brief is better than a long one. If you can answer most of the following, we can propose a first slice instead of a theatre estimate.
How an engagement runs
You describe the users, the job to be done, current tools and any hard date or constraint. A page is enough.
We reply with clarifying questions and a first-release outline: modules, roles, integrations and what “done” means.
Named engineers work in visible increments, with staging you can click and a weekly written status.
Launch, handover and a support path. The system is yours to operate—not a black box we disappear from.
Commercial currency is defined in the proposal.
On-site travel is a project expense and is planned when it adds value. Remote is the default.
Send the users, the job to be done and any hard constraint. We will answer as engineers—not with a canned brochure.