Forschungsmittel.com - Funding Platform and Operations Workspace

Context

This project was never only about a website, and it was never only about an internal tool. Forschungsmittel.com needed both: a strong public-facing B2B platform that explains funding opportunities clearly, and a real product layer that helps clients and the internal team manage the project after the first qualification step.

The public website had to support trust, clarity, structured information architecture, and conversion. At the same time, the business needed a funding workflow system around project evaluation, client access, document collection, communication, and ongoing team handling.

So the product was designed as a connected system from the start: public website, analytics-driven project intake, client dashboard, internal workspace, and operational command center built as one coherent platform.

• Public website and product logic were designed together, not as separate disconnected phases
• B2B focus: funding analysis, qualification, project handling, and next-step orchestration
• Operational scope: website + project product layer + team control center

Public Website Layer

The public-facing part of Forschungsmittel.com still matters as a major part of the case. We designed and implemented the website layer as a structured B2B platform for trust, SEO, decision support, and conversion into the funding process.

The case is stronger because both layers were built together: the site creates trust and entry, the product layer handles the operational continuation.

Website Layer Screens

Selected screens from the public B2B website layer, which handles positioning, information architecture, credibility, and conversion into the funding process.

Product Layer

Around the website, we built a real Förderplattform with a client dashboard, internal team workspace, and operational state model for the whole project flow. After the funding analysis, the system stores the project in the product database, generates a structured evaluation, creates client access, and moves the lead into the team's active workflow.

On the client side, this became a live project dashboard: with funding score, approval probability, next step, status, visible requests from the team, document requirements, activity history, and secure file uploads. The client no longer sees 'a form and an email' but an actual working environment with visible project state.

On the internal side, the team works in a unified workspace rather than scattered admin tools. Status, pipeline stage, responsibilities, team updates, client tasks, document requests, upload reviews, internal notes, and audit events all sit in one operational system.

Operational Command Center

A major addition was the command-center layer for the team. This turns the system from a passive project repository into an active operations product that shows what requires attention today.

This is where the product moves beyond 'project storage' and becomes a daily execution tool for the team.

Technical Architecture

The platform logic is centralized in Neon/Postgres and structured around real project data, not page-level state. That allows the public website and the authenticated product layer to operate as one system.

The important architectural point is not only the stack itself, but that website conversion, project qualification, and internal operations all resolve into the same product system.

What the System Actually Supports

The platform is already product-grade in daily use, with operational entities and workflows that support real project handling rather than just lead capture.

Product Layer Screens

Selected screens from the client dashboard, team workspace, and command-center layer used for daily project operations.

Result

Forschungsmittel.com now works on two levels at once: as a strong public B2B website and as a real operational funding platform.

The public layer explains, positions, and converts. The product layer qualifies, organizes, communicates, and moves projects through the next step. Together they form a connected funding operating system rather than a website plus a few disconnected backoffice screens.

• A public funding website with clear structure, trust, and conversion logic
• A client-facing product layer with transparent project state
• A unified team workspace for internal handling
• An operational command center for daily priorities
• One platform that supports both acquisition and execution

The key value is not that the project 'became a platform' after the website. The website and the platform were built as one system with different layers of the same product.