Forschungsmittel.com

Context

Client: Forschungsmittel.com — B2B funding advisory platform in Germany. Industry: B2B consulting, public funding, innovation. Scope: connected product system — public website, client dashboard, internal team workspace, document workflows and operations command center.

We built Forschungsmittel.com as more than a public website: a conversion-focused B2B platform connected to a client dashboard, internal team workspace, document workflows and operational command center.

The platform helps the business turn website enquiries into structured funding projects — with client access, project status, document requests, internal notes, team responsibilities and operational priorities managed in one place.

• 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 website was designed as a B2B platform for trust, clarity and conversion — not just as a brochure site. It supports:

The website creates the entry point. The product layer handles what happens after a qualified lead becomes an active project.

Website Layer Screens

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

2. Product Layer — Client and Internal Workspace

On the client side, the dashboard shows: • project status • qualification score • estimated fit • next-step recommendation • visible team requests • document requirements • upload areas • activity history On the internal side, the team works with:

3. Operational Command Center

Instead of forcing the team to search through individual projects, the command center surfaces what needs attention now. It brings the following into one operational view:

This turns the platform from passive project storage into an active execution tool for the team.

1. Technical Architecture

The platform logic is centralised around real project data rather than page-level state. The public website, client dashboard and internal workspace all resolve into the same product system, with Neon/Postgres as the central data layer. Core architecture elements: • Centralised project data model in Neon/Postgres • Role-based access for clients and internal team members • Structured project records, notes, activity feed and status history • Document request, upload and review workflows • SMTP communication flows for access and notifications • Reminder and priority logic for internal operations • Unified product logic instead of disconnected forms and ad-hoc admin panels

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.

Outcome

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 B2B website that explains the offer and brings clients into the qualification flow
• A client portal with visibility into project status, qualification score, estimated fit and next steps
• An internal team workspace for structured handling of documents, responsibilities, deadlines and next steps
• An operations command center that surfaces what needs attention now
• Activity history and traceable internal events across every project
• One connected product system instead of a website plus manual back office

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.