ExpoMed 2026 took place on 3 and 4 September at the Hilton convention center in San Salvador. It was the event's fourth edition and the first held outside Honduras, where it started. According to its general director, Nino Rivera, the Salvadoran edition brought together 68 speakers and roughly 1,500 attendees, with participants from Mexico, Honduras, Colombia, Spain, Puerto Rico, Chile, Cuba and the United States.
GadDev was one of the sponsors, with a stand in zone F of the floor plan. Next to us were medical equipment distributors, laboratories, imaging centers and clinics. A software agency in that aisle needs an explanation, and the explanation is the part worth writing down.
Why a medical trade show and not a tech one
At a tech event you talk to peers: other developers, other agencies, people who already know what an API is. It is comfortable and it moves nothing.
At an industry event you talk to the person who runs the operation. The one who knows how many appointments fall through in a week, who signs payroll, who has three notebooks and a WhatsApp group standing in for a system. That conversation is uncomfortable at first and it is the only one that produces real work, because the problem gets described in terms of operations rather than in terms of tools.
There is a market reason too. El Salvador's health sector is investing. At the event's opening, the representative from the Ministry of Tourism noted that in 2025, 4 % of international visitors came to the country for some kind of health procedure. A clinic that starts serving patients from abroad runs into its internal processes before it runs into its medical capacity, and that is where a system comes in.
We are not a healthcare agency, and saying so matters
A significant share of what we have put into production is in the health sector. That gives real technical depth, and it does not make us specialists in one industry.
We say it because the difference is practical, not rhetorical. The pattern we solve in a clinic is the same one we solve in a restaurant taking reservations, in a professional services firm tracking cases, and in a school handling enrollment: information living in several places at once, a process that depends on somebody remembering, and decisions made without data because assembling it takes two days. The symptoms read the same in any of those industries, and we list them in six signs manual work is already costing you money.
The depth comes from having put systems into daily use by real people, not from a vertical. Whoever claims to specialize in one industry is usually describing the only kind of project they know how to do.
What we brought to the stand
We did not bring a catalog of modules. We brought a short diagnostic, a few minutes long, designed for one purpose: to separate the person whose problem a system solves from the person whose problem a system will make worse.
A trade show stand is not the place to sell a build, and trying to sell one there is the fastest way to lose the conversation. What can be done in five minutes is to understand where somebody's operation breaks, tell them whether that is software or not, and propose a second conversation when it is. If you found us there and a question went unanswered, that second conversation is a thirty minute call.
Three things you see from inside and not from a demo
When we have built systems for this sector, three points never show up in a demo and they decide whether the system gets used or abandoned.
Scheduling is not a calendar. The hard part is not storing the appointment: it is the confirmation, the reschedule, the patient who does not arrive and the gap that is left. That lives outside the system, in somebody's phone, and it is where a generic tool falls short. The operational side of this we wrote up in putting WhatsApp into your operations.
Permissions are an architecture decision. Who can see what, what gets logged, and who can change a record that was already entered. In a business with several roles and more than one location, that is not a user setting: it is part of the design from day one.
Billing has to reconcile with everything else. Issuing DTE, El Salvador's electronic tax document regime, from your own system is a different problem from issuing it through a third party, and it is an architectural constraint rather than a final module. We cover it in what integrating DTE really involves.
None of the three is solved by choosing a better product. They are solved by deciding, and deciding requires somebody who understands both the business and the build.
Who we told did not need us
This is the part a trade show post usually leaves out.
A good share of the people who describe an operational pain do not need custom software. If the process is standard, the team is small and there are no local integrations to solve, a subscription product does the job at a fraction of the cost. And if the problem is that nobody owns moving something forward, no system will move it forward: it will record in more detail that it did not. That case, more common than it sounds, we cover in when you need better process, not more software.
Saying it at a stand costs a sales opportunity and saves a project that was going to fail. We prefer that.
What comes next
The work we have published, with each client's permission, is on work, and the full scope of what we build is on custom systems.
If you met us at ExpoMed, or if you did not go and that aisle would have interested you, the discovery call runs thirty minutes, it is free and carries no obligation. It is used to understand your operation and tell you frankly whether a system is the answer. You can book it here.
Does this apply at your company?
30 minutes, no obligation, to review your case and decide whether there's anything to build.