Net-Base Contact

Contact, project kickoff and initial technical alignment

The right start for a software project is a clear discussion of objectives, existing assets, dependencies, and risks.

Request. Inventory. Next step.

Collect project inquiries in a structured manner and cleanly prepare the technical onboarding.

Project inquiry Inventory Rückmeldung Nächste Schritte

Clearly identify the concern

Ziele, bestehende Systeme und fachliche Reibungspunkte lassen sich früh sauber ordnen.

Technische Richtung prüfen

Wir schaetzen ein, ob Modernisierung, Erweiterung oder Neuaufbau für den Fall sinnvoller ist.

Nächste Schritte fixieren

The inquiry results in a tangible starting point rather than a vague initial communication.

Project kickoff

How we begin our collaboration

Appropriate Service and Technology Paths

Key deep dives on this topic

The right start for a software project is a clear conversation about objectives, existing systems, interfaces and risks.

Use this page for project inquiries concerning custom software development, modernization of existing applications or portals with process logic. For ongoing operations and incidents there is a separate support channel.

Quick access to the right contact

  • Project inquiry: Are you planning a new system, a modernization or a portal? Use the form on this page.
  • Callback: If you prefer to speak, briefly indicate a time window — we will get in touch.
  • Existing system / incident: Please use our support page so operational requests reach the right team more quickly.

How we typically start

  1. Understand the initial situation
    Which processes should be improved, which systems are in place and where is friction currently occurring?
  2. Assess the technical direction
    We determine whether extension, modernization or a clean rebuild is economically preferable — including dependencies, operations and interfaces.
  3. Define next steps
    You will receive a clear picture of which project scope, which architecture and which starting point are realistic (including risks and sensible preparatory work).

Project inquiry

Briefly tell us which processes, legacy applications, interfaces or platform goals are relevant. We will contact you for an initial technical exchange focusing on architecture, operations and realistic implementation steps.

Helpful to start: Goal/problem, existing systems (e.g. ERP, database, interfaces), desired timeframe, operation/hosting (if specified) and whether user groups or roles already exist.

Response: Typically within 1–2 business days.

Note: The inquiry will be stored internally and forwarded to our contact mailbox. Details can be found in the Privacy Policy.

Existing system or ongoing operations?

If it is not a new project but concerns questions about existing applications, support cases, updates, integrations or technical incidents, please use the dedicated support page. This keeps project initiation and ongoing support internally separated — and ensures your request reaches the right team faster.

Direct contact

Net-Base Software GmbH
Weißerlenstraße 3
91058 Freiburg i. Br.

E-mail: info@net-base-software-gmbh.de
Contact route: The quickest way is via the form on this page. If requested, we will reply by e-mail or arrange a callback.

Focus: Custom software development, portals, modernization and technical operational responsibility.

Any questions in advance about getting started, architecture, or services?

The FAQ center categorizes typical questions about project initiation, modernization, portals, Delphi, C# and technical responsibility prior to the initial meeting.

Next step

If you have a specific modernization, API, or platform question, we should define the technical scope early and precisely.

Net-Base evaluates existing systems, data paths, interfaces and target platforms not in isolation, but in the context of domain logic, operations and future expansion.

  • Current state, target state and technical risks are assessed jointly.
  • REST, data access, portals and rollout are not deferred to later phases.
  • You can see early which path is economically and operationally viable.