The firm
Sixteen years, one principal.
Robles Industries LLC has been building technology for other people's businesses since 2010. It is a small firm on purpose, and it is structured so that staying small does not mean staying unserious.
Structure
Two names, one company.
Robles Industries LLC is the parent entity. It holds the company's interests, carries the federal registration, and is the contracting party for government work.
Div42 is the commercial consulting and product practice. When a private client engages us for architecture, development, or a project rescue, that work runs through Div42. When a federal or state buyer puts us on contract, it is Robles Industries LLC on the document.
Same people either way. The separation is legal and administrative, and we mention it here so nobody has to wonder why two names appear on the same engineer's email signature.
Parent and federal entity
Robles Industries LLC
Government contracting, holding company, San Antonio, Texas. Established 2010.
Commercial practice
Div42
Consulting, product development, project rescue for private clients.
Principal
Frank R. Robles
Principal and Managing Member
Frank founded Robles Industries in 2010 and has run it since. His work spans defense, healthcare, legal technology, financial services, and enterprise software, in roles that have ranged from writing the code to running the company.
He served as COO and CTO of a legal services marketplace through its acquisition, and was development lead on an Air Force AFWERX SBIR Phase II delivering hands-free immersive training systems. He currently works as fractional CTO for operating companies that need senior technical judgment without a full-time hire, and leads technology and operations at a medical services support company.
The reason that history matters to a buyer is narrow: he has been on both sides of the table. He has been the executive who inherited a system nobody could explain, and he has been the engineer explaining it. Most of what we do well comes from having been in the first position often enough to build for it.
How we work
Four commitments, and what they cost us.
- 01
The people you meet do the work
No capture team, no bench rotation, no senior architect who disappears after the orals. If someone is in the room during scoping, they are on the project.
- 02
Written scope before code
Every engagement starts with a specification we both sign. It is the document we get measured against, and it is how a change of scope becomes a conversation rather than an argument at invoice time.
- 03
You can fire us and keep the work
Source, pipeline, architecture document, and runbook are yours throughout, not at the end. We would rather earn the next phase than hold the last one hostage.
- 04
We say no
To work outside our competencies, to set-asides we are not eligible for, and to timelines we cannot hit with people we would put in front of your contracting officer.
Every one of these limits how much work we can take in a year. That is the trade. A firm our size can either scale headcount and accept that the average engineer on your project is someone we hired last quarter, or it can stay small and turn work away. We chose the second, and it is worth telling you plainly so that you can decide whether it suits your requirement.
Work with us.
Government buyers start on the contracting page. Everyone else can just write.