Company founded
GMA Corporation was founded
At the moment the company started, Kurukhill was already an active client. That set the direction early: we were not building presentation pages, but systems that serve real business work.
About us
We build software people have to work in.
GMA Corporation builds custom business systems: software that serves how a company actually operates, rather than filling a generic template with content.
Most business problems are not solved by making a website prettier.
Most enquiries start with “we need a website”. By the end of the conversation it usually turns out that is not what is missing: something is being tracked in a spreadsheet, someone is copying data from one place to another by hand, and nobody can see in one place where a process stands.
That is the part we build. Payroll and workforce administration, booking systems, online stores and customer-facing interfaces — software people log into every day, and which has to change alongside the company using it.
This means most of the work is invisible: data model, states, permissions, process boundaries. The interface is the end of that — important, but not what decides whether the system will work.
Company path
How operation became system.
These milestones are not about visible campaigns. They show how the work became more precise: turning business processes into software that can be used every day.
012024December 022025January Infrastructure
Own server put into operation
We purchased and deployed our professional server machine, serving our clients' websites and systems. From that point on, infrastructure became part of our responsibility too.
032025January New client
Katadent joined the portfolio
With Katadent, the client base expanded and the working method became clearer: interface, content and underlying operation are not separate projects, but one system.
042025March Booking platform
Balatoni Szállások
In the Balatoni Szállások project, search, property presentation and booking logic moved into one shared system. Behind the guest-facing experience, data connections and states became central.
052025May Webshop
Balkanpowersports
Balkanpowersports joined our work as a parts and powersports-focused webshop. The main task was building the product structure, searchability and ordering path precisely.
062025July Drop-based shop
InsomniaCrüe
InsomniaCrüe brought a different rhythm as a drop-based webshop: a visual world that can change campaign by campaign, while the ordering logic stays stable.
072025December Own system
Smartmunka development began
Smartmunka started as more than a public interface: it was built as operational business software, with workforce data, processes and internal operation behind it.
082025Year end Year-end summary
From portfolio to operating system
By the end of the year the projects no longer looked like separate websites: booking, webshop, customer-facing surfaces, server operation and business logic were increasingly moving in the same direction.
092026March Application
Smartmunka application
With the Smartmunka application, the system moved closer to everyday use: workforce administration and the related processes were no longer only a desktop surface, but an app-like experience too.
102026May Entry system
QR-code entry system
The QR-code entry system direction began: fast identification, a simple access point and operation that connects physical presence with the digital record.
112026June New project
Robinson Pizzéria
Robinson Pizzéria opened another customer-facing and operational direction. The focus stayed the same: a digital surface that does not only appear online, but serves daily operation.
Principles
Where we don't compromise.
These are not promises about results; they are the rules of how we work. If one of them does not suit your project, it is worth saying so at the start.
- 01
Process first, screen second
A system becomes usable when the data structure and state handling behind it are right. The interface is a consequence of that, not the starting point.
- 02
Fewer systems, not more
The goal is not one more tool to keep open. If a new system does not remove work, it has not solved anything.
- 03
What ships, works
We build in working pieces so there is something to try. That way a misunderstanding surfaces in weeks, not months.
- 04
Handover is not the end
A system starts working when it goes live. Operation and further development are part of the same job.
- 05
Technical decisions in the open
We explain what we are building and why, and what it costs to change later. We name the trade-offs, not just the benefits.
- 06
One team, one owner
Public interface, internal administration and the logic behind them from the same team. There is no handover point where the intent gets lost.
How we work
Five steps, none of which can be skipped.
The order is not a matter of style: every step builds on the previous one, and the last one does not end at handover.
- 01
Mapping
We walk through the process as it works today: who does what, where the data is created and where it stops. That is what reveals what actually needs building.
- 02
System design
Data structure, states, roles and an outline of the interfaces. The contentious questions are settled here, not during development.
- 03
Development
We build in working pieces, so there is something to try out and respond to. Any drift from the plan shows up early.
- 04
Rollout
Go-live, data migration and training the people who will use it. The system is done when they are genuinely working in it.
- 05
Operation
Monitoring, fixes and the next development rounds. A working system is not a finished project but a running service.
Contact
Got a process that needs a system?
Describe how it works today and where it breaks down. In the first round we look at what is worth building at all — and what isn't.