Next.js + React
The shared web foundation for the catalogue, customer portal and staff interfaces.
In this document11
← All projects
CASE STUDY / KGC-Bérlés
Turn equipment discovery into a connected customer journey.
We built Kisgépcentrum’s digital platform around the work of the store. Customers find equipment, identify parts or open a request; counter and service staff continue with the relevant information. The catalogue, portal, kiosk and display studio are different interfaces to this business environment.
- Project status
- Business platform · ongoing development
- Focus
- Business platform · Interactive parts search · Kiosk + CRM
01 / CONTEXT
The business challenge
A single machine can be linked to a rental request, accessories, spare parts and a service case. The challenge was to preserve that context when a customer moves from the website to the store, or another team member takes over the conversation.
THE DESIGN DECISION
The case is the organising principle: clear status for customers, context for staff decisions and access suited to each role.
WORKFLOW / KGC-Bérlés
How the user journey comes together.
- 01 / CUSTOMER
Find equipment or parts
Connected catalogues and the desktop parts diagram help define an itemised request.
- 02 / STAFF
Continue with the case context
The staff workspace brings the customer conversation and the next action into the same case.
- 03 / PORTAL
Follow the conversation
The customer sees replies and request decisions in their portal; rental proceeds with staff confirmation.
02 / IMPLEMENTATION
How we approached it
We started with customer journeys: what visitors need to do, which information is required and who makes the next decision. Connected catalogues support a customer portal and role-specific staff workspaces. Parts diagrams lead to itemised enquiries, while the portal separates customer conversations from internal coordination. An in-store kiosk and a display programme editor support the physical customer experience.
Innovation in practice
The decisions behind the functionality
Find parts directly on the diagram
Selecting a part in an exploded diagram builds an enquiry with its part number and quantity. Parts search is available in the desktop interface.
One customer journey, several workspaces
Rental, shop, service and parts requests feed into shared case management. Customers see their own history while internal discussions remain with staff.
The web catalogue, on the shop floor
The touch-screen kiosk offers the same equipment, detail pages, date selection and request flow, with its own virtual keyboard.
A studio for in-store screens
Build programmes from images, video and text slides. Separate publication, per-screen playlists and weekly schedules support content management.
QR customer lookup with verified access
The portal’s customer code and QR equivalent help staff find an account at the counter. Access to historical cases is granted separately for each case.
Change requests remain part of the case
Customers can request extensions, changes or cancellation in the portal. Staff decisions and explanations appear in the customer’s conversation; the related business operation is handled separately.
See the tools in use.
Behind the interface
Technologies and architecture
The shared Next.js and React application provides distinct views for customers, the counter, service staff and display management. Node.js endpoints use Prisma models and a PostgreSQL database. An interface to the separate parts engine connects diagrams to itemised enquiries; development of the larger ERP remains a separate workstream.
Node.js
Server-side data handling and the web application’s own API endpoints.
TypeScript
Typed interfaces and business workflows in a shared codebase.
PostgreSQL + Prisma
Persistent business data, related data models and database operations.
Tailwind CSS
Consistent responsive components across customer and in-store interfaces.
Playwright
Automated browser checks for important screens and customer journeys.
DELIVERY / PROJECT SCOPE
What we built
- Equipment and product catalogues with linked rental options
- Desktop parts search with diagram selection, an itemised basket and enquiries
- Customer portal, shared customer records and case-based conversations
- Counter, service and administrator workspaces
- Customer-code/QR lookup, verified case access and recorded request decisions
- Touch-screen kiosk with equipment pages, calendar and virtual keyboard
- Display Studio with a media library, playlist editor and scheduling
Our role
Customer-facing and internal web application development: catalogues, request submission, customer records, case-based communication, and counter and service views. The scope also includes the parts-engine interface, kiosk interaction, and editing, publishing and scheduling display programmes.
Project status
The featured modules have been implemented and development continues. Online rental requests require staff confirmation. Full ERP synchronisation, online card payments and automatic invoicing are separate workstreams; acceptance testing on the physical shop kiosk remains outstanding.
Explore KGC-BérlésMore work
Innovation prototype
Poparch
An architectural plan-processing prototype: supported vector PDFs become editable quantities, cost estimates and professional exports.
Working prototype · private demo
Explore the project — Poparch
Client project
Strabor
A customer application for a tradesperson’s daily work: estimates, appointment requests, photos, messaging and service administration.
Public website and customer application
Explore the project — StraborYOUR NEXT STEP
Which workflow should we rethink together?
projects / atlas.workspace
Project Atlas
06 / REAL PROJECTSLook behind the interfaces. Explore the solutions, inspect real screenshots and put two projects side by side.
6 projects
Choose up to two to compare.Client project
KGC-Bérlés
From equipment discovery to the customer portal: rental, parts enquiries, store operations and display management in one web platform.
- Find parts directly on the diagram
- One customer journey, several workspaces
Business platform · ongoing development
Innovation prototype
Poparch
An architectural plan-processing prototype: supported vector PDFs become editable quantities, cost estimates and professional exports.
- Turn a PDF into editable data
- Keep the expert in control
Working prototype · private demo
Client project
Strabor
A customer application for a tradesperson’s daily work: estimates, appointment requests, photos, messaging and service administration.
- Keep the job and the conversation together
- Control capacity and pricing directly
Public website and customer application
Club project
BPSE
Digital tools for the pétanque community: tournament organisation, team score entry, spectator standings and shared sports information.
- Different roles, one tournament
- From paper to the right mobile screen
Public application
Client project
TEXTURA Salon
A custom bilingual salon website connecting its real space, stylists and services to a direct booking journey.
- A route to the chosen stylist
- Keep the next mobile step within reach
Public website
Client project
Foxxi
Developing an established clinic website: editable WordPress pages, two treatment areas and a coherent Hungarian–English patient journey.
- Editing behind an established appearance
- Two specialties with clear decision paths
Public website
No matching project.
Try a different capability or clear the filters.
compare / projects
Clearer side by side.
Compare the demonstrated capabilities and current status. Each project was built for a different purpose.
Select two projects from the cards above.
Includes your filter and selected projects.
MYFORGE / DELIVERY LABINTERACTIVE STUDIO DEMO
Great software starts
with better decisions.
We understand the business problem, design the system and build it in steps you can inspect. Step inside the studio: choose a project and explore how research, human decisions and AI-assisted development connect.
RESPONSIBILITY AND DELIVERABLEGemini + NotebookLM
Sources, open questions and an SSP brief.
WHAT DOES THIS GIVE YOU?
Clarity before commitment.
Clarifying the goal and constraints together helps decide what belongs in the first usable version.
Before the next stageWe agree which problem to solve and how we will know it has been solved.
SPECIALIST ROLES. SHARED CONTEXT.
Responsibilities follow the selected stage.The right tool for each part of the work.
Gemini + NotebookLM
Research and sources
KGC-Bérlés
Which source supports each claim?
A single machine can be linked to a rental request, accessories, spare parts and a service case. The challenge was to preserve that context when a customer moves from the website to the store, or another team member takes over the conversation.
BMAD + Claude
Planning and work breakdown
KGC-Bérlés
How does the brief become a checkable plan?
Customer-facing and internal web application development: catalogues, request submission, customer records, case-based communication, and counter and service views. The scope also includes the parts-engine interface, kiosk interaction, and editing, publishing and scheduling display programmes.
Codex
Review and tests
KGC-Bérlés
What evidence will verify the change?
Does the desktop parts diagram lead to the right part number and itemised enquiry?
SSPThe shared foundation for development
01 / Goal
From equipment discovery to the customer portal: rental, parts enquiries, store operations and display management in one web platform.
02 / Context
A single machine can be linked to a rental request, accessories, spare parts and a service case. The challenge was to preserve that context when a customer moves from the website to the store, or another team member takes over the conversation.
03 / Constraints
Customer-facing and internal web application development: catalogues, request submission, customer records, case-based communication, and counter and service views. The scope also includes the parts-engine interface, kiosk interaction, and editing, publishing and scheduling display programmes. The featured modules have been implemented and development continues. Online rental requests require staff confirmation. Full ERP synchronisation, online card payments and automatic invoicing are separate workstreams; acceptance testing on the physical shop kiosk remains outstanding.
04 / Checkable outcome
Suggested acceptance question · verification pending
Does the desktop parts diagram lead to the right part number and itemised enquiry?
PROJECT DOCUMENT · ILLUSTRATIVE SAMPLE
Defining the brief
The goal, context and acceptance criteria in one place.
# KGC-Bérlés / brief.md
> ILLUSTRATIVE SAMPLE · Based on public portfolio information. Not a client brief or approved project plan.
## Research · Gemini + NotebookLM
Reviewing the sources leads to a checkable brief. This example uses the portfolio and does not start live research.
## SSP / Goal
From equipment discovery to the customer portal: rental, parts enquiries, store operations and display management in one web platform.
## SSP / Context
A single machine can be linked to a rental request, accessories, spare parts and a service case. The challenge was to preserve that context when a customer moves from the website to the store, or another team member takes over the conversation.
## SSP / Constraints
Customer-facing and internal web application development: catalogues, request submission, customer records, case-based communication, and counter and service views. The scope also includes the parts-engine interface, kiosk interaction, and editing, publishing and scheduling display programmes.
The featured modules have been implemented and development continues. Online rental requests require staff confirmation. Full ERP synchronisation, online card payments and automatic invoicing are separate workstreams; acceptance testing on the physical shop kiosk remains outstanding.
## SSP / Checkable outcome
Suggested acceptance question; verification pending:
- [ ] Does the desktop parts diagram lead to the right part number and itemised enquiry?
## Next handover · BMAD + Claude
- [ ] Separate sources, facts and open assumptions
- [ ] Review the SSP goal, constraints and acceptance criteria together
- [ ] Approve the implementation direction and verification approach
## Learning loop
Research may also start from previously approved lessons. A new finding needs a source, crystallization and an approved destination before propagation.
## Status and limits stated in the portfolio
The featured modules have been implemented and development continues. Online rental requests require staff confirmation. Full ERP synchronisation, online card payments and automatic invoicing are separate workstreams; acceptance testing on the physical shop kiosk remains outstanding.
Source: https://www.myforgelabs.com/en/case-studies/kgc-rental/The project ends. The knowledge stays.
Research can also use lessons that have already been reviewed and approved.
Outcome and test evidence
Record the actual result, environment and limits.
Crystallization
Select and check the lasting lesson within the raw experience.
How it becomes knowledgeApproved propagation
After review, to an approved destination: a project document, decision or shared knowledge.
The approval pointBack to research, with better context.
Gemini + NotebookLMknowledge / connected.workspace
Connected systems. Knowledge that compounds.
INTERACTIVE EXAMPLEMyForge Superintelligence connects project context, specialised AI roles and developer decisions. A valuable lesson from one project becomes retrievable knowledge for the next.
01 / knowledge graph
The architecture of shared knowledge.
Select a node for details. Drag to rearrange, or use arrow keys while focused. The list below also works on mobile.
Browse the nodes 13
capabilities / reusable methods
Methods selected for the work at hand.
02 / discord handoffs
From a client request to a reviewed solution.
Every handoff has an owner, a purpose and a tangible output. This scripted example illustrates Discord-based collaboration: follow the request through research and development to human approval.
project-handoffReady to play
CURRENT HANDOFFAn idea starts a shared conversation
Output
client-request.mdWaiting for a human decision.
Approval continues only this local example.
The loop is complete.The next task can start from reviewed knowledge.
MYFORGE / ERP In development · a closer look is coming soon
One business. Connected operations.
We have been developing an ERP that connects equipment rental, service, inventory and sales. Its purpose is to keep the history of an asset, partner or work order available at the next business step. A closer look at the development is coming soon.
KGC ERPSystem layersARCHITECTURE
WORKSPACE
The daily workspace
Staff interfaces suited to each role
React + ViteBUSINESS LOGIC
Business workflows
Rental · service · inventory · sales
Node.js + NestJSDATA & JOBS
The operational foundation
Related data and queued background work
PostgreSQL + Prisma · Redis + BullMQShared foundation: roles, organisational separation and traceable operations.
BUSINESS MODULES / 01—05
Workflows connect across business functions.
Rental and equipment
The equipment journey from pricing through checkout and return to its related contract. Rental operations have their own business module.
Service and work orders
Repair tasks, work orders and warranty cases are organised as connected workflows in dedicated service modules.
Inventory and sales
Modules cover products and stock movements from goods receipt and stocktaking to sales operations.
Partners and documents
Partner records, business documents and related communication provide context for the same case.
Access and organisations
Roles, audit trails and separated organisational workspaces define who can access each part of the business data.
ENGINEERING / STACK
The engineering behind the operations.
A modular TypeScript monorepo with a Node.js and NestJS API, React–Vite workspaces, PostgreSQL–Prisma data handling and Redis–BullMQ background jobs. Dedicated access and tenant layers separate data belonging to different organisations.
- Node.js + NestJS
- A modular server-side API and business services.
- TypeScript
- Shared types and explicit data contracts across the monorepo.
- React + Vite
- Browser-based staff workspaces.
- PostgreSQL + Prisma
- Relational business data and typed database access.
- Redis + BullMQ
- Queued background jobs and scheduled processing.
In development. More to share soon.
The ERP in development is a separate project from the KGC-Bérlés web application. Modules and integrations are progressing incrementally; a public demonstration and operational rollout are separate delivery steps.
MYFORGE / WORKSPACE SETTINGS
Your workspace.
Arrange this website around the way you like to explore. Changes appear immediately.
These settings apply only to this website. Layout preferences stay on this device; form entries are not saved here.
03 / Keyboard shortcuts
- Ctrl / ⌘ K
- Quickly open a file
- Ctrl / ⌘ ⇧ P
- Actions and settings
- Ctrl / ⌘ B
- Toggle the sidebar
- Ctrl / ⌘ J
- Toggle the terminal
- Ctrl / ⌘ ⇧ X
- Toolkit
- Ctrl / ⌘ ⇧ T
- Reopen a closed tab
- Alt ⇧ ← / →
- Reorder tabs
- Delete
- Close the selected tab
Workspace shortcuts do not run while you type in a form field.
Every setting stays within this website.
LOCAL DEMO
❯ bmad Research · Gemini + NotebookLM
MyForge Workspace. Type help · Local navigation commands.
// Demonstration events.
Workspace opened. Choose a project or play the BMAD demonstration.
