The code is yours
Your repository, your accounts, your infrastructure, from the first commit. No proprietary framework you can only maintain by paying us forever.
We learned to build software by repairing hardware.
Pytronic Labs is the remote software studio of Pytronic, C.A., an electronics and computing company in Mérida, Venezuela. Understanding where we came from explains a lot about how we approach a codebase.
For more than a decade, Pytronic, C.A. has repaired the machines other people’s businesses depend on: laptops, monitors and televisions, desktop computers, UPS units, printers and plotters. Board-level work, mostly: the kind where you measure before you replace, because guessing is expensive and a customer is waiting.
Along the way we kept running into the same second problem. A client would bring in a failing machine and mention, almost in passing, that the real bottleneck was not the hardware at all. It was the spreadsheet three people edit simultaneously. The stock count that is always wrong. The quotes typed out by hand, one at a time, every day.
So we started building software, first for ourselves, then for people who asked. A corporate site, a store, a learning platform, a professional platform with sixteen financial calculators in it. Each one solved a real problem for a real operation, which is a different discipline from building something impressive for a portfolio.
Pytronic Labs is that work, offered deliberately. Remote, in English or Spanish, priced in USD, available to anyone whose timezone overlaps ours, which is most of the Americas and the mornings of Europe.
Diagnose before you replace. Measure before you claim. It is how you approach a dead
motherboard, and it turns out to be exactly how you should approach an application
nobody wants to touch.
How we operate
Five commitments we don’t negotiate.
These are not values-page decoration. Each one is written into how we quote, build and hand over, and you can hold us to all of them.
Plain language, always
You will never receive a status update you need a developer to interpret. If we cannot explain a technical decision in a sentence you understand, we have not understood it well enough ourselves.
Visible every week
A working URL and a written update every Friday, from week two. Silence between kickoff and delivery is where projects go wrong, so we remove the silence.
We will talk you out of work
If an existing tool solves your problem for $30 a month, that is what we will tell you. Selling a build you did not need is a good quarter and a bad decade.
Done means deployed
Not “finished on our machine”. Running in production, monitored, backed up, documented, with someone on your side who knows how to operate it.
Repair over replace
A decade of electronics work taught us that most things labelled broken are diagnosable. We apply the same default to inherited codebases.
Who you work with
A small team, on purpose.
We take on two projects a quarter. That isn’t scarcity marketing; it’s the number at which the person who scoped your project is still the person building it.
Wilmer Mogollón, Founder
Economist, lawyer and university lecturer, with an M.Sc. in Quantitative Economics and a faculty role at Universidad de los Andes. He works in Python and R daily for econometric modelling and data analysis, and he is the reason Pytronic’s software work leans towards systems that have to be numerically correct: pricing rules, financial logic, reporting people make decisions with.
He is on your scoping call, and he is the person who signs off on what gets delivered. mogollonwilmer.com
The engineering side
Behind the founder is the Pytronic, C.A. technical team: specialists in electronics and computing who have spent more than ten years diagnosing systems under time pressure, for customers who need an honest answer rather than a comfortable one. For software work we operate as a tight unit: one lead engineer accountable for your project end to end, with the rest of the team available for review, testing and specialist input.
What you will not get is a sales contact who disappears after signature and a delivery team you have never spoken to.
Where we are
Mérida, Venezuela, a university city in the Andes, GMT-4. That timezone is the same working day as New York and Toronto, an hour ahead of Bogotá and Mexico City, and a productive overlap with the European afternoon. Work is remote by default; invoicing is in USD; we operate in English and Spanish.
The wider group
Pytronic is four things.
Labs is the newest of them. The others are how we know what businesses actually need.
Pytronic Repairs
Board-level electronics and computing repair in Mérida. The original business, still running.
Pytronic Tienda
Online store for components, parts and equipment, with stock control built in.
Pytronic Edu
Technical training delivered online, with enrolment-gated course material.
Pytronic Labs
Remote software engineering. Custom Django applications for clients anywhere.
You are here
Let’s talk
Work with people who have to live with what they build.
Every platform in our portfolio is one we still maintain. That is a strong incentive to write software that doesn’t fall over, and it’s the standard we apply to your project too.