Clients and requests
Customer and supplier records, requests, conversations and responsible people.
From customer request to quotation, order and delivery — with commercial information in one place.
Open original screenshot ↗Small teams often keep client requests, supplier prices, quotations and deadlines in separate tools. That makes it harder to understand the next step, ownership and estimated margin.
I structure the product around the real commercial journey: client → request → quotation → accepted order → supplier and team coordination. The interface keeps the day’s work and decisions visible.
Customer and supplier records, requests, conversations and responsible people.
Product catalog, quantities, discounts, sales prices, purchase costs and estimated gross margins.
Customer quotation documents show selling prices while supplier notes support purchasing and attachments.
Accepted quotations become orders with linked tasks, owners, dates and a calendar.
Overview of requests, offers, orders and estimated margins for operational follow-up.
A demonstration product catalog, social drafts, previews and simulated publishing or scheduling.
This project focuses on organizing commercial data and workflows. My wider automation approach includes n8n, approval steps and AI-assisted drafting; these should be connected and validated for a particular client rather than assumed to be active in the ERP demo.
React, TypeScript, TanStack, SQLite demo storage, Product catalog, Workflow design.
The demo uses fictional data. Saving, calculations and documents work in this demonstration copy; email, WhatsApp, account connections and social publishing are simulated. Actual invoicing is handled in a separate invoicing system. Real integrations are configured per client.
Interested in how I approach access, private documents and AI data flows? Read my security principles.
Open demonstration ↗Explore version 1.0 with a public demonstration account. Use fictional data only.
Download login details ↗