Change your ERP by describing what you want

The vendor's team changes it for you. You explain what you need, they scope it, quote it and build it. This works, but every change is a small project, and small changes wait in line behind big ones.

Your admin changes it with a builder tool. Faster, as long as you have someone who knows the tool and has the time. In most 40-person shops that's the same person who also runs IT, purchasing and the forklift.

You describe it and Milo builds it. The person who needs the change asks for it, in the words they'd use with a colleague. Milo reads how your Tangle is set up, builds the change, and shows you the result before it goes anywhere.

We built Tangle around the third way. There's no configuration quote and no change order for everyday changes.

An illustrative example, not a list of specific product features.

Meridian Welding's foreman wants to know why the laser keeps sitting idle. Today, downtime gets a note on a clipboard, if it gets written down at all.

Before: The owner asks the office to "add a downtime field". It goes on a list. Three weeks later, someone builds a spreadsheet.

With Milo: The foreman types, "Add a downtime reason code field to shop floor time entries." Milo builds the field with a short list of reasons, in a sandbox. The foreman opens the preview, clocks a test entry, asks for one more reason ("waiting on material"), and approves it. The next morning the operators pick a reason when the laser stops.

A week later, the owner asks for a dashboard showing downtime by machine and reason. Same process.

1. Describe. Write the change in plain English.
2. Build. Milo reads your Tangle setup and builds the change in a sandbox.
3. Preview. Try it in a safe browser session, using it the way your team would.
4. Apply. It goes live only after a person approves it.

Milo never changes your live system without your approval. Every change is built in a sandbox and tested there first, so you can try it with real work before your team sees it. Approval checkpoints and user-level environments are part of every change by default.

• Screens and forms: shop-floor logs, inspection checklists, custom order intake.
• Fields: custom fields and calculated fields on the records you already use.
• Workflow boards: quote approvals, work-order routing, purchasing sign-offs.
• Dashboards and reports: late work orders by department, job cost against quote, whatever your Monday meeting needs.
• Automation rules: flag orders over a threshold, notify a foreman, or update a status when a step completes.
• AI-powered tools: for example, parsing purchase order PDFs or writing a shift brief from today's schedule.

• "Create a quote approval workflow for orders over $25,000."
• "Add a downtime reason code field to shop floor time entries."
• "Build a dashboard showing late work orders by department."
• "Generate a foreman shift brief from today's schedule."
• "Parse these purchase order PDFs and match lines to inventory parts."

• It won't change your live system on its own. Every change waits for a person to approve it.
• It won't fix messy data by itself. If part numbers are duplicated or routings are out of date, Milo can help you find the problems, but someone who knows the shop has to decide what's right.
• It doesn't replace us. Bigger projects, like a new integration or moving off an old system, are still work we do with you.

Milo is included for Office Users. Shop Floor Users work with what's been built.

See Tangle pricing

"Tangle is able to bend every which way and that's been the best aspect of working with this software, the potential to create virtually everything we need." Dhimo, General Manager, Yarl Metal Fabrications