About TechinFlow

TechinFlow B.V. is based in Haarlem. Because the company is new, this site shows no founding dates, counters or client logos that suggest a long track record. Everything it does say, you can check. The founder's profile links to his public code on GitHub and to his own text on LinkedIn.

Our field is software that works with location and data. That means map viewers and geo-applications that use the Dutch government's open geodata, portals on which organisations publish datasets, and data platforms that bring together information from different systems. We also build custom web applications and advise on technology choices and architecture. The full offer is on the services page.

The focus is on small and medium-sized government bodies and organisations with a public task. They often deal with the same frameworks: transparency of information, digital accessibility, municipal architecture agreements and procurement rules. How those frameworks apply to Dutch municipalities is set out on software for municipalities (in Dutch).

TechinFlow was founded by Tekin Uslu. On his LinkedIn profile he writes, in Dutch: "Sinds 2006 bouw ik aan de brug tussen geo-informatie, data engineering en IT-architectuur" (roughly: since 2006 I have been building the bridge between geo-information, data engineering and IT architecture). That is his own statement. On GitHub his account dates from 2014, with among other things his own repositories for a map viewer based on OpenLayers and an address search on the PDOK Locatieserver, the Dutch national geodata platform's search service.

The page on Tekin Uslu lists what can be verified publicly about his work, with links to the sources. It also states what is deliberately left out. We do not name the founder's employers or clients, because we cannot give a publicly verifiable source for them and because such work was not done by TechinFlow.

The texts on this site were drafted with AI tools. Facts and code examples have been checked against the cited sources on the stated date. The texts have not yet been reviewed for content by Tekin Uslu. Please report errors to info@techinflow.nl; we will correct the page. More on this is in the colophon (in Dutch).

Below is the default approach we write into a proposal; the actual agreements for each assignment are made with you. An assignment starts with the client's question and what already runs. Only then do we choose technology. Often part of the solution turns out to exist already, for example in the national geodata services of PDOK or in an open source component. In that case we propose building on it rather than making something new.

1. We record the question, the existing systems and the constraints, such as information security, accessibility and who will handle maintenance later.
2. We propose a clearly bounded scope, with the technology we would use and why.
3. We propose agreeing exit requirements up front, with the starting point that source code, configuration, data in open formats and documentation go to the client.
4. We build in short steps that you can see and test along the way.
5. We hand over with documentation, so that your own team or another party can continue.

If you are preparing a public tender, one extra rule applies. What you receive from us during preparation is written so that you can share it with all bidders. The guide to requirements for a GIS viewer tender (in Dutch) is an example.

What we do: custom software, web and app development, GIS and map applications, open data portals, data platforms, hosting and maintenance of what we build, and advice on technology and architecture. We prefer to work with open standards and open source, and we connect to existing systems when that is better for the client.

What we do not do:

• Publish counters or percentages that we cannot substantiate.
• Show logos or names of organisations unless that organisation was itself a client of TechinFlow and gave written permission.
• Present the work of others, or work of the founder from before TechinFlow, as work of the company.
• Show details of internal systems or screens belonging to clients.
• Rebuild an off-the-shelf package when that package already solves your problem well.

If TechinFlow is not the right party, for example because you are looking for a licensed product with a large supplier network, we say so in the first conversation. That saves you and us time, and it avoids a project that has to be turned around halfway.

Buyers rightly ask about references. Because TechinFlow is a new company, we are straightforward about this. Projects the founder carried out before TechinFlow are not references of TechinFlow B.V. This site therefore shows no client names, case studies or logos.

Once TechinFlow has completed assignments of its own, we will share references in a tender on request and with the client's permission. That lets you judge them in the right context and lets the client decide what may be said about the work. A new assignment may include an optional agreement on a reference mention after delivery. That agreement is never a condition for a price or discount, and in public-sector contracts the client's procurement terms prevail.

If you want to know what you can ask for in a tender for a map viewer or data portal, read the guides in the knowledge base (in Dutch). For a first conversation, use the contact page. Do mention if it concerns a tender, and we will take that into account from the start.