Robles Industries LLC · San Antonio, Texas Small business · SAM registered Doc. RI-ORG-2026-01 · Rev. C Issued 17 Sep 2026
Robles Industries
PurposeOrganization, principal, and operating commitments Issued 17 Sep 2026 · Rev. C

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.

1.0

Organization

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 it is stated here so nobody has to wonder why two names appear on the same engineer's signature block.

Parent entity
Robles Industries LLC Government contracting and holding company. San Antonio, Texas. Established 2010.
Commercial practice
Div42 Consulting, product development, and project rescue for private clients. div42.com
2.0

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 from 2015 to 2025, 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.

Before Robles Industries he co-founded NanoSpace, later Yipes Communications, where he originated the metro Ethernet carrier model in 1998; founded Neopolitan Networks and CityNAP; and ran the OakStone Ventures seed fund. He holds two US patents in data communication.

Principal profile · career record: NanoSpace and Yipes, Neopolitan Networks, CityNAP, OakStone Ventures, Operational Technologies, Austin Board of Realtors, DigitalTown, where it started.

Written contact
Secure form
Telephone
512-900-4871
Based
San Antonio, Texas. Central time.
2.1

Recommendations

Quoted from public LinkedIn recommendations, complete sentences only.

“If I had to use one word to summarise Frank it would be 'integrity'. Frank does what he says he'll do.”

Karen Louise Floyd · Worked with Frank on the same team, 2018

“Frank impressed me with his broad and deep IT experience, complemented by a great business head and first-class people skills. Frank is calm, organized, and a mentor to his teams.”

Mike Cartwright · Met Frank during the acquisition of Got.Law by DigitalTown

“His leadership really helped us get everyone from development to sales more focused on bringing a commercially viable product to market after several lackluster attempts.”

Faris Oweis · Worked with Frank, 2020

“Frank presented countless system upgrades that improved efficiencies and produced tangible results.”

Steven Yavorsky · Austin Board of REALTORS®

“Thanks to Frank we efficiently started the finance modeling process for the start-up company.”

Olga Batiukova · Finance director, SanityDesk

“Frank had the vision, passion and patience to transform and nurture a local ISP into a National Service Provider that defined a new category.”

Michael Ferguson · Chief infrastructure partner at Yipes

“Frank is unequaled in his knowledge of cutting edge LAN/WAN technologies, and delivers his expertise in an unpretentious manner.”

Patrick Hickey · Client, Kana, hosted by NanoSpace and Yipes

“They are by far the best ISP we have dealt with.”

Suresh Reddy · Client of Neopolitan Networks

“There was never an ambiguous state of things when Frank is in charge.”

Luis Trivino · Reported to Frank directly
3.0

Operating commitments

Four commitments, each with what it costs us stated next to it. A commitment with no cost attached is a slogan.

  1. Scope

    A specification we both sign. It is the document the work is measured against.

    Gate: Signed specification

  2. Design

    Current-state assessment, target architecture and a threat model, before build.

    Gate: Design review

  3. Build

    The people from the scoping room. Source and pipeline sit in your accounts throughout.

    Gate: Acceptance against the spec

  4. Handover

    Architecture document and runbook, so the work can come in house without a transition contract.

    Gate: Close

Principal of record, in the room at scoping and accountable through close

Figure 3.1 Engagement sequence, scope to handover.
  • 3.1 The people you meet do the work

    Costs us: the ability to bid work we cannot personally staff.

    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.

  • 3.2 Written scope before code

    Costs us: two to three weeks before the first line is written.

    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.

  • 3.3 You can fire us and keep the work

    Costs us: the lock-in most firms in this market rely on.

    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.

  • 3.4 We say no

    Costs us: revenue, in most quarters.

    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.

4.0

Work with us

Government buyers start on the contracting page. Everyone else can just write.