Process mapping
We identify the trigger, required information and owner of each step.
In this document05
Solutions / MyForge Labs
Less copying. Better handovers.
From enquiry forms to records, from bookings to notifications. Connect the tools between which information currently moves by hand.
01 / The starting point
Sound familiar?
An enquiry must be entered into several tools, a colleague notified separately, and progress tracked by hand.
APIs & events
We work with the capabilities of your existing systems, handling duplicate events and failed handovers.
Visible failures
Automation status and failures can be traced; critical decisions can retain human approval.
02 / In practice
Start with the business process
We connect one clearly bounded process first. Tests and daily use guide further work.
Related work
- KGC-Bérlés ↗Live business platform · kisgepcentrum.hu — Customer e-mail notification when a booking is confirmed, recorded request decisions and repair tracking in the customer account. Online rental requests are confirmed by staff.
- Ajánlat-radar ↗Research prototype · synthetic data — Incoming quote items in a comparison matrix and gap list, with the source next to every value. Not a production client system.
Scope & handover
What do you get?
One bounded workflow
We name the trigger, inputs, owners and completion state. For example: an enquiry becomes a recorded task and an acknowledgement.
Integration with failure handling
We exercise duplicate events, missing information and interrupted handovers. Failures reach someone who can act on them.
Handover for daily use
Workflow documentation, access requirements, test results and a way to continue manually. Subscriptions and maintenance are listed separately in the proposal.
When is a rule enough?
When inputs and decisions are clear, we design a rule-based integration. AI may help interpret free text; uncertain results go for review. We clarify an inconsistent process before automating it.
A useful starting point
Bring a concrete example: where information arrives, where you copy it, who checks it and what happens when it fails. We check API availability at the start.
03 / Working together
Let’s define
what we’re building.
The proposal defines features, deliverables, connected systems and the acceptance criteria.
What we need to get started
- The goal, the users and the current challenge.
- The existing website, tools and content.
- Your intended timing and budget.
How do we get to a proposal?
After a short discussion, we describe the proposed solution and stages. We clarify the scope of third-party subscriptions, content, hosting and future improvements separately.
Explore the price calculator ↗Take the 2-minute check →
projects / atlas.workspace
Project Atlas
06 / REAL PROJECTSLook behind the interfaces. Explore the solutions, inspect real screenshots and put two projects side by side.
9 projects
Choose up to two to compare.Client project
KGC-Bérlés
The complete system behind kisgepcentrum.hu: web shop, equipment rental, service intake, parts search and customer accounts — one platform shared with the in-store kiosk and staff workspaces.
- Find parts directly on the diagram
- One customer journey, several workspaces
Live business platform · kisgepcentrum.hu
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
Research collaboration
Kinda · Balance
A workplace wellbeing platform that grew out of the instruments of a doctoral research project: research questionnaires, management reports and the Balance module, which rewards healthy habits.
- A research instrument and a company product in one system
- Wellbeing you can follow in forints
Live platform · research collaboration with the University of Pécs Faculty of Health Sciences
In-house R&D
Ajánlat-radar
Automated processing of incoming supplier quotes, designed around a machine-parts distributor’s workflow: items extracted from e-mails, PDFs and spreadsheets feed a comparison matrix, with the original source behind every number.
- Traceable extraction
- Quotes made comparable
Research prototype · synthetic data
Own product
Közös
A shared space for parents living apart: expenses, handovers, children’s requests and documents in one place, with two-sided approval.
- Two-sided approval as the principle
- A separate view for the child
Live · private, invitation-only family use
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. In September 2026 the system gained the web shop, the full service workflow and customer accounts, and went into production.
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
The complete system behind kisgepcentrum.hu: web shop, equipment rental, service intake, parts search and customer accounts — one platform shared with the in-store kiosk and staff workspaces.
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. In September 2026 the system gained the web shop, the full service workflow and customer accounts, and went into production. The platform has been running in production at kisgepcentrum.hu since September 2026, 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
The complete system behind kisgepcentrum.hu: web shop, equipment rental, service intake, parts search and customer accounts — one platform shared with the in-store kiosk and staff workspaces.
## 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. In September 2026 the system gained the web shop, the full service workflow and customer accounts, and went into production.
The platform has been running in production at kisgepcentrum.hu since September 2026, 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 platform has been running in production at kisgepcentrum.hu since September 2026, 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. Zoom with Ctrl/⌘ + scroll, pinch, double-click, the − / + buttons, or the +, − and 0 keys while the graph is focused. Zooming in reveals the names, then the roles, then what each connection carries. Drag the background or use the arrow keys to pan.
Browse the nodes and connections 13 · 18
Connections · what each one carries
- Source knowledge → Project
context for the next task - Project → Gemini
brief.md - Gemini → NotebookLM
research-notes.md - NotebookLM → SSP
sources.md - SSP → BMAD + Claude
agreed-brief.md - BMAD + Claude → Development
implementation-plan.md - Development → Codex
change-set.diff - Codex → Verification
review-notes.md - Verification → Crystallization
verification.md - Crystallization → Approval
learning-proposal.md - Approval → Propagation
approval.md - Propagation → Source knowledge
reviewed-knowledge.md - Source knowledge → NotebookLM
versioned Markdown sources - Source knowledge → Skill library
Retrievable lessons - Skill library → BMAD + Claude
Brief, decisions, tasks - Skill library → Development
Reviewable implementation - Skill library → Verification
Real user journeys - Codex → Development
Feedback to development
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.
