Projects · Built & running in production

Systems that had to work
on Monday morning.

Every project below is software that runs a real operation — not a prototype and not a portfolio piece. Client names and operational details are withheld under confidentiality. The engineering decisions are described exactly as they were made.

Our own software

One system we can name

Everything below belongs to somebody who paid for it, which is why the names are missing. Contactio is ours, so the mechanism, the price and the map of what it reaches are all on its own page.

Contactio

Hand it a web address and nothing else. It reads the site, drafts a capability profile you are free to rewrite, then ranks NAICS codes drawn from the official 2022 list instead of recalled by a model.

  • SAM.gov and Grants.gov for what is open, USAspending for who already won it, and two state open-data portals for the rest — public endpoints read from the outside, not partnerships
  • Seven single-purpose agents rather than one long instruction — the single instruction produced blank keyword lists, codes off no official register, and a whole result set stuck on nought
  • Any six-digit code absent from the official register is discarded on the way back, so it never reaches a screen
  • A second agent briefed to argue against the strong matches, with the deterministic score standing behind the first when the model cannot answer
  • Built for the firm that was quoted five figures a year by the incumbent platform and walked away from the meeting

Built under the rules we would put on your work

The deploy runs the checks before anything ships, and the page describing the product is itself gated: a claim on it that stops matching the code fails the build.

  • Every database call parameterized, with no ORM in between, so the query you read is the query that runs
  • A token on every posted form, and any address you paste checked against private and loopback ranges before it is fetched
  • Saved credentials encrypted ahead of storage, and redisplayed as a hint with most of the characters withheld
  • An offline verification suite the deploy runs first, covering the scoring, the agent panel, and whether one account can see another account's rows
  • Two front ends over one back end, and the server-rendered half is the whole product rather than a stub

Read the Contactio page →

Integration & data movement

Getting systems that were never meant to talk to each other to agree, on a schedule, without a person in the middle.

Integration · Inbound logistics

Knowing where the freight actually is

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.
Automation · Warehouse systems

Automating a system that has no API

The warehouse platform offered no write interface, so every transaction went in by hand. We automated the screens themselves — carefully enough to trust with live inventory.
Automation · Inventory transfers

The order builds itself from the attachment

Inventory transfer requests arrived as spreadsheets attached to email, in as many shapes as there were requesters, and were keyed in line by line. Now the attachment becomes a validated, reference-numbered order on its own.
Planning · Outbound fulfilment

Turning a flat order backlog into a plan the floor can pick

A daily backlog feed said what had been ordered — not what could be built, released or picked. We built the pipeline that turns it into a wave plan, a queued pick order, and a screen that says where each one got to.
Reconciliation · B2B trading partners

Variances that only close when they're actually gone

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.
Documents · Returns processing

Return paperwork the receiving system accepts first time

Returns had to be announced to the warehouse system by hand-filling a hundred-column vendor template. We build the document from the check-in itself, check every line against the customer's item master, and track each upload through to accepted or failed.

Operations platforms

Whole systems that replaced spreadsheets, inboxes and the knowledge that lived in one person's head.

Platform · Multi-year build

One application that replaced a decade of spreadsheets

A warehouse ran its floor on shared spreadsheets, emailed reports, and tribal knowledge. We replaced all of it with a single internal platform — and kept it running while people worked.
Casework · Damage & exceptions

Exceptions that open their own case file

A damage or count discrepancy is a claim, and a claim is worth whatever evidence is attached to it. We built the casework — photo capture at the point of discovery, a case that assigns and escalates itself, and a PDF report that goes out with the pictures already in it.
Workflow · Intake & approvals

A request queue where the approvals set the status

Internal software requests arrived by email and were approved in conversation. We built an intake form, a board and a three-role approval gate where the votes move the card — and gave requesters a private link so they can follow and edit their own request without an account.
Inventory · Consumable supply

Knowing you'll be out of stock before you are

Packaging and floor consumables were tracked on a shared spreadsheet, and the first reliable sign of a shortage was an empty shelf. We built a scanned stockroom with a background service that projects each item's stockout date against its lead time — and emails only when something new goes wrong.

Why these read the way they do

Case studies usually lead with a number. These lead with the problem, because the numbers belong to the clients who paid for the work.

What we can't tell you

Client names, site locations, system names, volumes and dollar figures are all covered by confidentiality obligations we intend to keep. If a competitor's case study names a client, either they got written permission or they shouldn't have.

We'd rather show you the reasoning than borrow credibility from a logo. On a call we can go considerably deeper on approach, architecture and what we'd do differently — without crossing that line.

The same rule governs the numbers. Every figure on these pages is a property of the software itself — route counts, retry limits, poll intervals — because those are ours to publish. What the software did to a client's cost or headcount is theirs, and it stays with them.

Production, not proof-of-concept

Everything here ran daily, under load, with people depending on it during their shift.

The failure modes are the story

Anyone can describe the happy path. What matters is what the system does at 3am when a dependency is down.

No rip-and-replace

Almost none of this involved replacing a system. It involved making the systems already in place work together.

Get in touch

Recognize your operation in any of these?

A free assessment gives you a clear picture and a prioritized plan — no commitment.

Prefer to talk?

Call 832-598-8234 or email msco@stoneagesoftware.com. Houston, Texas — serving Houston, The Woodlands, Conroe, Sugar Land, Katy, Pearland, and the Greater Houston metro.

What happens next

We read your message, an engineer replies with questions or a straight answer, and if it's worth a call we book one. No drip campaign, no handoff to sales.

No obligation — we reply within one business day. This form sends your details to Stone Age Software LLC so we can respond to you. See our privacy policy for how we handle them. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.