Houston, TX · IT support · Legacy rescue · Logistics operations · Data & automation
We build, fix, and modernize the software your business runs on.
Stone Age Software runs IT for small and mid-sized Texas offices, from ten people up: Microsoft 365, the network, the servers and backups, the printer that keeps dropping offline, with 24/7 support. The engineer who answers the phone is the one who does the work. Legacy software, logistics integration and data are the firm's other three practices, one scroll down.
10+ yrs
of stacks supported
100%
of the code owned by the client
24/7
launch & cutover support
Not ready to write? See the four practices, or call 832-598-8234.
Free assessment, no obligation · An engineer replies within one business day
Already a client? Tickets have a number, a queue, an engineer, and response targets on the business clock Sign in Join with a company code
Help desk · live triage
The same 3×3 matrix the desk reads a ticket against. Targets run on the desk's business clock, 8 to 6 Central, Monday to Friday; they are targets the desk measures itself by, not a promise.
Who does it affect?
Has work stopped?
Priority
P4Low
Start where Monday's problem is
Enterprise IT Services
Active Directory and Entra ID, endpoints, the network, servers and backups, Microsoft 365, the help desk and the printer that keeps dropping offline: managed or co-managed, for offices from ten people up, with 24/7 support.
From Nobody's jobThe printer to Entra IDM365IntuneNIST CSF 2.0
Logistics Operations
A WMS, a TMS and an ERP each holding a different truth; EDI 940/945 and ASN 856 traffic graded by a retailer's routing guide; carrier rating, labels and tracking still re-keyed by hand. The practice wires them together and monitors the seams.
From SpreadsheetsBatch FTPRe-keying to X12EDIFACTRosettaNetCarrier APIs
Built & running in production
Client names and operational volumes stay confidential. The engineering decisions are described exactly as they were made, and where the site's own tracker timed the work, the case study says what it saved.
Reconciliation · B2B trading partners
Two systems held different quantities for the same parts, and the disagreement arrived as a spreadsheet attached to a recurring email. We turned it into a register that remembers — and that nobody is allowed to close by hand.
Integration · Inbound logistics
Inbound shipments were tracked by opening carrier websites one tab at a time. We replaced the tabs with live carrier integrations and a workflow that routes exceptions to the person who can fix them.
Optimization · Industrial hardware
Label printers wedged under load and needed power-cycling. The fix was understanding what the hardware actually does — and sending it about 150 times less data.
Controls · Reverse logistics
End-of-life material left the site on paperwork typed by hand. We rebuilt the chain end to end and added the control nobody had: detection of inventory added after the paperwork was already filed.
Legacy Rescue
Undocumented COBOL, Fortran or VB6, a vendor's abandoned product, a database that has outlived three teams, still carrying production. The practice reads it, puts a test harness around it, and replaces it one function at a time.
From COBOLFortranVB6AS/400 to RustGoPythonC#
Data & Automation
Power BI models with two versions of revenue, invoices and BOLs typed into the ERP by a person, a process that should be measured before it is automated, and data that is not allowed to leave the building.
From Two revenuesHand-typed BOLs to Power BISQLLlamaRAG
“I’m launching or running a small business.” That is a different practice with its own pages Small business & startups
How the work is engineered
Every modernization runs as a strangler. The legacy core keeps its role as system of record while an adjacent service, typically Rust or Go on the hot path and Python for orchestration, takes one responsibility at a time. Both sides run in parallel until their outputs reconcile to the row, the cutover lands in a quiet window with a rehearsed rollback, and the old path is retired only after the new one has carried live load. That is what a zero-downtime mandate means in practice, and it is the same procedure on a two-week fix and a two-year migration.
Outside the glass, the way it runs today. Under it, the way it runs after the cutover: the same business, the same data, one function at a time.
Drag the lens, or use the arrow keys.Drag the lens sideways, or tap a block.
Nightly COBOL batch→Event-driven services
On the logistics side the fluency is in the documents themselves. An X12 850 is answered by an 855, a 940 is closed by a 945, and an ASN 856 is built in the hierarchy the retailer's routing guide specifies and graded by it; EDIFACT and RosettaNet PIPs ride AS2, RNIF or SFTP; carrier rating, tendering, tracking and freight audit come in through the 204, 990, 214 and 210 or the carrier's REST API; and traceability is modeled so an FSMA 204 Key Data Element is captured once, at the Critical Tracking Event, rather than reconstructed from paperwork later.
Data stays where its owner wants it. Open-weight Llama- and Qwen-class models run on a workstation-class GPU inside the client's network, with no per-token fees and no document leaving the building; retrieval-augmented copilots answer from the client's own SOPs and manuals, with citations. The security practice behind every engagement is organized on the NIST Cybersecurity Framework (CSF) 2.0, work-for-hire IP is assigned to the client, and an NDA is signed before the first technical call.
The reading list is the point. COBOL and Fortran still earning their keep, Ada and SPARK from safety-critical work, Erlang, VB6 and the stacks that arrive when a specialist team moves on, carried into Python, TypeScript, Go, Rust, Java, C# or Zig, chosen for what the client runs and can hire for.
The pages behind this one are written for two readers: the supply-chain director who owns the retailer scorecard and the carrier spend, and the IT lead who owns the change window and the audit. Each pillar hub answers that reader's first question before it asks for anything.
Confidentiality
Fixing a system means seeing how the business really works, so everything shared on an engagement is treated as the client's: the name stays private, what is learned stays on the project, and a logo appears here only with written permission. The security practice behind that runs on NIST CSF 2.0.
A client appears in marketing only on written instruction, and the client list is confidential.
Records and documents shared for the work are used for that work alone.
The client's own NDA, mutual or one-way, signed as written before the first technical call.
Start the conversation
Describe what is slow, broken or at risk. The reply comes from the engineer who would do the work: an honest read on what it takes, within one business day, under NDA first if that is preferred. Free, no obligation.
