newlife. · CADlingua

Tell us what you need

If your problem deserves its own tool, tell us about it.

This is the newlife inbox. It is for the thing the market almost never has a product for: the process someone on your team holds together by hand because no software does exactly that. Describe it in plain language, no need to bring the solution, and we reply directly.

What we have already built

This is not a service catalogue: it is the ground we already know. If your case looks like one of these, we start ahead; if it looks like none of them, say so anyway and we will tell you frankly whether it is for us.

01 — en producción

Drawing translation

CADlingua came out of this work: translating the notes in a DXF or DWG without letting dimensions, part codes and tolerances become translatable text. It is the worked example of what happens when a specific friction turns into a product.

CADlingua →

02

ERP integration

Through the API when the ERP exposes one, and through RPA when it does not and the user interface is the only door. The order matters: an API is stable and screen automation is fragile by nature, so RPA is the answer when nothing else is left — never the first choice.

03

CAD and SolidWorks automation

Generating and reviewing drawings, properties, bills of materials, dimensions and tolerances through the COM API. The real difficulty is not calling the right method: it is keeping the session alive through modal dialogs, binding failures and a batch of hundreds of files without hanging at three in the morning.

Custom software, from the database to the browser
Backend, web interface and deployment, handed over as something your team can maintain without us. We prefer few dependencies and an explicit limit over a platform that impresses in the demo and that nobody dares touch in January.
AI applied to industrial engineering
Training for technical teams, and agents that do real work on the company’s own files and systems. The first thing we teach is when NOT to use a model: half the value lies in knowing where a deterministic automation is the better idea.
Test harnesses that tell the truth
Verification harnesses: they run the software against real cases and return pass or fail without anyone having to offer an opinion. They are the expensive part to build, and what separates “should work” from “works” — especially when the one claiming it is an AI.

Where this comes from

From years inside capital-equipment engineering for heavy industry, on international projects with deadlines that are not negotiable. In that setting, a badly translated drawing or a figure that never reaches the ERP is not paid for in a meeting: it is paid for on the shop floor, on site and in the delivery date. Every tool on this list started as a problem that cost real money.

What happens when you write

  1. An engineer reads it, not a salesperson. The first reply brings specific questions about your case — not a catalogue and not a request for a meeting.
  2. If your case is not for us, we say so plainly and, when we know, we point you where to look. A quick no is worth more than a polite yes.
  3. What you tell us is yours. We do not use it as a public example and we do not share it with anyone without your written go-ahead.

Tell us what you need

There is no form here, and that is deliberate: this site is static and has no server, so your message goes straight to a mailbox instead of into a database nobody checks. Tell us what happens today, what should happen, and with which files or systems — DXF/DWG, SolidWorks, the ERP, Excel. The more specific you are, the more useful the first reply will be.

Or copy the address: uhalveyy@gmail.com