Frequently asked questions

TFLIT is the software development practice of Tillmann Lang from Tübingen: custom software, web and app solutions for companies, universities and the public sector in Baden-Württemberg. Behind the name is deliberately not an agency with rotating teams, but one developer who accompanies projects from the first idea through implementation to ongoing operation. That means short paths, direct communication and responsibility in one pair of hands. Delivered projects include the culture platform Kultio, the internship platform PraktiMatch for Esslingen University and the free BFSG check as a tool for digital accessibility. Technically, the focus is on modern web technologies such as Next.js, mobile apps with Flutter and digitalizing workflows that currently live in emails and spreadsheets. If you want to know whether your project fits, a short initial call is the easiest way to find out.

Yes, the collaboration works fully remotely, across Germany. The base is Tübingen, and in-person meetings in the Neckar-Alb region and greater Stuttgart are possible at short notice. Most projects run largely digitally anyway: coordination via video calls, shared boards for requirements, quick emails or chat messages and regular demos of the current state. Precisely because you talk directly to the developer at TFLIT, nothing gets lost in remote communication: there are no intermediate layers of project management and sales where information trickles away. For kickoff workshops or important milestones I am happy to come by in person where the distance allows. In the end, what matters is not the location but clear communication and reliable results. Just write where you are based and what it is about, and we will find the right format.

TFLIT works with modern, maintainable technologies: on the web mainly React and Next.js, in the backend Node.js with systems such as Payload CMS and relational databases like PostgreSQL, and for apps native iOS development and cross-platform Flutter. This selection is deliberately focused: instead of learning a new toolkit for every project, I rely on a proven stack that I run in production myself and can maintain for years. Still, the technology always follows the project, not the other way around: an internal process application has different requirements than a public platform with high traffic. What matters to me is that solutions remain understandable, extensible and safely operable in five years, without depending on exotic niche tools. If you already have an existing codebase, I check in advance whether a takeover into this stack makes sense.

TFLIT offers custom software, web development, app development for iOS and with Flutter, process digitalization, and maintenance and support. Custom software means tools that fit your workflows exactly, such as specialist applications, portals or internal tools. Web development ranges from a fast company website to a complex web application with login, roles and integrations. For apps, that means native iOS applications or cross-platform Flutter apps for iOS and Android from a single codebase. Process digitalization starts where emails, Excel lists and paperwork rule today and replaces them with lean digital workflows. Maintenance and support keep existing solutions secure, current and extensible. For municipalities, universities and public authorities there is a dedicated offer that considers procurement, data protection and accessibility from the start. The best starting point is the service that matches your biggest bottleneck.

Yes, you can also commission individual building blocks, for example just the app, just the backend or just an integration. Not every project needs a complete solution: sometimes a working system already exists and only a cleanly connected frontend is missing; sometimes the design is done and it is purely about the technical implementation. Working alongside your existing team or an agency is also possible, for example as reinforcement for a clearly defined part. What matters is a clean cut: we clarify upfront where TFLIT's responsibility begins and ends, which interfaces exist and who runs operations. That way even a partial project stays maintainable and you avoid a patchwork of unclear responsibilities. Just describe briefly which building block you are missing, and you will get an honest assessment of whether and how it works as a partial project.

Yes, existing applications can be taken over, maintained and further developed. The process is proven: first I get an overview of the code, infrastructure, dependencies and documentation in an assessment. Then you get an honest evaluation of the application's condition, the existing risks and what a takeover involves. Common first steps are updating outdated dependencies, setting up backups and monitoring, and closing obvious security gaps. Sometimes the analysis shows that a gradual replacement makes more sense than maintaining the existing system; I will tell you that openly too, including a workable path to get there. Importantly, you no longer need contact with the original developer; access to the code and hosting is usually enough. Send me a few key facts about the application and we will discuss the takeover in concrete terms.

The collaboration runs in clear stages: initial call, requirements, usable first version, step-by-step extension. In the initial call we clarify the goal, users and constraints: what should the software do, who works with it, what defines success? From that comes a concept with an honest estimate of scope and effort. Then development proceeds iteratively: you get a working version early that you can test yourself, and we extend it based on your feedback. This rhythm has two advantages: progress is visible at all times, and wrong turns show up while they are still cheap to correct. At every step you help decide which features matter next. After launch I can take over hosting, monitoring and further development if you want, so the solution keeps running reliably long term. The easiest entry point is a short, no-obligation initial call.

Costs depend on scope and complexity; after a short initial call you get a transparent estimate without hidden costs. The main cost drivers are the number of features and user roles, integrations with other systems, requirements for design and accessibility, and the desired degree of automation. A focused web application is accordingly cheaper than an extensive platform with many integrations. To keep the budget under control, we cut the project into stages: first comes the core that delivers the most value; later stages follow once the solution has proven itself. That way you do not pay for features on suspicion. We agree the billing model upfront, depending on the project either a fixed price per stage or time-based with a clear frame. Send me a short description and you will get an honest first assessment.

Yes, for SMEs in Baden-Württemberg there are funding programmes for digitalization, for example via L-Bank. Depending on the programme, funded measures include introducing new digital solutions and digitalizing processes. The most important point in practice: the application must be filed before the project starts. Anyone who commissions first and seeks funding afterwards usually walks away empty-handed. I am not a funding consultant, but in the initial call I point out programmes that could fit your project and supply the documents you need for an application, such as a comprehensible project description and effort estimate. The decision on funding lies with the respective funding body. If funding is relevant for you, raise the topic early: then we plan the project start so the application deadlines can be met.

TFLIT's focus is Baden-Württemberg: Tübingen as the base, plus Reutlingen, Esslingen, Metzingen, Herrenberg, greater Stuttgart and the Neckar-Alb region. Within this radius, in-person meetings are possible at short notice, from the kickoff workshop to on-site acceptance. That is particularly valuable at the start of a project, when requirements and workflows are best understood directly at the future users' workplace. Beyond that, I work remotely across Germany: video calls, shared boards and regular demos replace the drive without the quality of coordination suffering. Mixed formats are common too, for example an in-person kickoff workshop followed by remote collaboration. For the public sector in Baden-Württemberg, regional proximity additionally eases collaboration around procurement and ongoing operation. Your location is rarely an obstacle, so when in doubt just ask briefly.

Yes, in the region in-person meetings are possible at short notice and without fuss. From Tübingen, the cities of Reutlingen, Esslingen, Metzingen, Herrenberg and greater Stuttgart are quickly reachable; an on-site meeting can usually be arranged within a few days. In-person meetings are most useful at the start of a project, when we get to know requirements, workflows and users, and at important milestones or trainings. In between, the collaboration runs efficiently remotely: short video calls instead of long drives, demos of the current state directly in the browser, coordination via email or chat. So you get the best of both worlds: personal contact where it adds real value, and fast digital paths in everyday work. You can book meetings directly online or request one informally by email; for urgent topics just give me a quick heads-up and we will find a slot promptly.

Yes, there are regional references, among others PraktiMatch with Esslingen University and a digitalization project for a municipality in Baden-Württemberg. PraktiMatch is a platform that brings students and internship placements together and is in productive use in the university environment. There is also Kultio, a platform for local culture experiences, developed as an own product, which shows how a project comes together from UX to operations in one pair of hands. Such references are more than logos on a website: they prove experience with the requirements of universities and the public sector, from data protection and accessibility to coordinating multiple stakeholders. Specific details, contact persons and documented eligibility proof are available on request, for example as part of tender procedures. If you want to see a reference from your own field, just ask.

Yes, the public sector is one of TFLIT's core target groups, including the formal and legal requirements such as GDPR and accessibility. Concretely, that means experience from university projects such as PraktiMatch with Esslingen University and from a municipal digitalization project in Baden-Württemberg, plus familiarity with how public-sector clients work, from needs assessment and eligibility proof to documentation. Public projects differ from purely commercial ones: there are more stakeholders, clearer formal requirements and often longer decision paths. The collaboration is designed for that, with traceable planning, clean documentation and reliable availability. For municipalities, universities and public authorities there is a dedicated offer page with details on procurement, data protection and accessibility. If you are planning a project inside an administration or university, a short conversation is the easiest way in.

Yes, GDPR-compliant processing and accessibility according to BITV 2.0 are part of the work from the start, not afterthoughts. For data protection that means: a data-minimizing architecture, EU hosting on request, a data processing agreement as soon as personal data is involved, and technical measures such as encryption and access control. For accessibility I follow BITV 2.0 and WCAG: semantic HTML, keyboard operability, sufficient contrast, understandable forms and screen reader compatibility. Since 28 June 2025 the German Accessibility Improvement Act (BFSG) additionally obliges many private-sector offerings to be accessible; for public bodies accessibility was mandatory even before that. The free BFSG check at /tools/bfsg-check gives a first impression of an existing website's status. If you have specific requirements from a tender, the best way is to go through them together.

Municipalities in Baden-Württemberg can award contracts up to €100,000 net directly, without a formal tender procedure; this rule applies since 1 January 2025 and is limited until 1 October 2027. For a software project within this range that means: clarify the need, obtain a quote, commission directly. This saves months of procedural effort and makes smaller digitalization projects economically viable. Above the threshold, or in formal procedures, I take part in tenders and provide the required eligibility proof and references. Important: the applicable procurement rules and your administration's internal thresholds are always decisive; this is not legal advice. In practice, the collaboration usually starts with a no-obligation conversation about the need, followed by a comprehensible service description and a transparent quote. Just get in touch and we will clarify the right route for your case.