Project Foundry

Production & manufacturing assistant

A manufacturing assistant, built like a co-worker.

Connect the tools a plant already runs on. Automate the repetitive work that slows manufacturing down.

The product is a wrapper around the assistant: it does the work, and the app is how you ask for it and see what happened. It connects to existing systems, works real tasks, and never acts without approval.

Book an Assessment See what it does ↓

Why we are building it

Help manufacturers see value from the AI tools that already exist.

What we are building

An assistant that connects existing tools and performs tasks within a manufacturing plant.

The goal

An assistant that adds value to your workflows, simple to use, and easy to understand.

01 · Tasks

What the assistant can do.

The assistant can take on a number of tasks that are routine across manufacturing. Tasks start by auditing how the work is done today, then turning that into something repeatable: a task that runs on a schedule, on a trigger, or when you ask for it.

Task

Supply chain

Open Order Report

Problem: Sending open purchase order lines out to suppliers is a repetitive task.
Impact: Repetitive, non-value-add work that takes up production buyer time.
Solution: Pulls every outstanding order out of the ERP so the list is not rebuilt by hand. You get a summary of what each supplier still owes you, plus a draft email to each supplier carrying their own lines, ready to send.

ReadsERP

You get · Workbook and draft emails

See it running

Task

Supply chain

Past Due Report

Problem: Past due POs are found the reactive way: production is already short, or somebody pulls the report by hand to go looking.
Impact: The ERP reflects that a line is past due and nothing more. Someone still has to chase every supplier for a status before any of it means anything.
Solution: Proactively identifies every past due PO instead of waiting for production to raise it, and scans supplier email for what has already been said about each one. The status and the next step are on one screen.

ReadsERPSupplier email

You get · Table on screen

See it running

Task

Supply chain

Invoice Discrepancy Investigation

Problem: Invoices go unpaid because the records disagree, while the message that would clear up the discrepancy is sitting in email.
Impact: Time goes into reviewing every discrepancy by hand, and invoices that get paid late put pressure on the supplier relationship.
Solution: Investigates each discrepancy as a three-way match between the invoice, the receiving documents, and the purchase order, then pulls in what the supplier said by email. You get the full picture of why an invoice does not match.

ReadsERPSupplier email

You get · Findings on screen

See it running

Task

Supply chain

Promise Watch

Problem: The ERP holds a date nobody has confirmed, while the truth about where the parts actually are is sitting in email.
Impact: The delay is not realized until the stale date finally comes due and production feels it, even though the supplier already said enough to see it coming.
Solution: Scans supplier email for anything that flags a PO and raises it against the order book, then names what to correct in the ERP so the dates you plan against stay true.

ReadsERPSupplier email

You get · Table on screen

See it running

Task

Supply chain

Inventory Risk Triage

Problem: Inventory gets managed reactively. What is short, what is late, and what still needs to be bought sits across parts, jobs, and open orders, so a discrepancy is found when somebody trips over it.
Impact: The production buyer carries it. Recognizing the discrepancy is the work; placing the order is the easy part that comes after.
Solution: A daily read on what needs to be bought. Checks every stocked part against what the jobs have committed, what is on the shelf, and what is on order. Flags what comes up short, what lands too late, and what runs out inside its own lead time, with the job each one holds up.

ReadsERP

You get · Table on screen

See it running

Task

Supply chain

Order Confirmation Check

Problem: Order confirmations come back by email and get a glance at best. Whether the supplier actually confirmed the quantity, the price, and the date, nobody checks line by line.
Impact: A mismatch hides until it comes back as a wrong delivery or a wrong invoice, when it is expensive to unwind and the material is already on the truck.
Solution: Checks every open purchase order against what the supplier's emails actually confirmed: quantity, price, and date, line by line. You get what was never confirmed and where a confirmation disagrees with the order, so the mismatch gets settled now instead of at the invoice.

ReadsERPSupplier email

You get · Table on screen

See it running

Task

Supply chain

Supplier Price Review

Problem: Price creep goes unnoticed. A part gets a little more expensive one order at a time, and the notice, if there ever was one, is buried in email.
Impact: Nobody can see the trend from inside a single PO, so increases get paid without ever being questioned, year after year.
Solution: Lines up what you pay for every purchased part against what you paid before, plus any price-change notices in the supplier's email. You get what got more expensive, what that costs you a year, and which increases nobody announced.

ReadsERPSupplier email

You get · Table on screen

See it running

Task

Supply chain

Supplier Scorecard

Problem: Supplier calls run on impressions. The delivery record is scattered across a year of receipts nobody assembles, so the loudest recent problem stands in for the whole year.
Impact: Without the record there is no leverage in the conversation, and the suppliers who quietly deliver never get credit for it.
Solution: Builds each supplier's record from the ERP: deliveries on time or late over the last year, the open book today, and whose prices moved, with how fast they answer email beside it. One standings table, worst record first, so you walk into a supplier call knowing the record.

ReadsERPSupplier email

You get · Table on screen

See it running

02 · Ask Mack

Chat directly with your systems.

Prompt in plain English to understand the data sitting inside your systems and act on it.

Open order questions

ERP

Counts, suppliers, parts, quantities, and dates across the live open order book.

How many open purchase order lines are there?
What is due this week across the open book?

Past due questions

ERP

Which open lines are past their due date right now: by supplier, by count, by age.

Which suppliers have the most past-due lines?
What is the oldest late line on the book?

Purchase order status

ERP

The current open lines of one purchase order: quantities ordered and received, due and promised dates.

Where is PO-4711?
Has anything been received against PO-4711?

Part lookup

ERP

Whether a part number matches anything on the open book, and which lines cover each match.

Which POs cover part KD-1042?
Do we have anything on order for the 316 gasket?

Supplier lookup

ERP

Which suppliers match a name, and each one's open-line count and nearest due date.

What do we have open with Apex Fasteners?
When is the next delivery due from Hutchins?

Supplier email questions

Supplier email

What the supplier has actually said about a purchase order or a part, quoted rather than paraphrased.

Did the supplier say anything about PO-4711?
Has the supplier explained the price increase?

Scope and system status

No outside system

What it can answer right now, which reports run as tasks, and whether the connected systems are responding.

What can you do for me today?
Is the ERP answering right now?

03 · What it connects to

Connects to the systems you already work in.

The tasks and the answers only ever say what your data says. It is not built to replace your systems. It is built so you get more work done with them.

Your ERP · Read only

The open order book, purchase orders, receipts, invoices, parts, and suppliers. It reads. There is no way for it to write back, so running a task cannot change a record.

Supplier email · Read only

Scoped to one supplier address. It can read a message and quote it back to you. It cannot send, reply, draft, or delete, and a request written inside a message is something to report, never an instruction it follows.

Nothing else, yet

On-hand inventory, sales orders, and the calendar are not connected. They are shown as not built rather than described as though they work.

See where Project Foundry fits in your plant.

Book an assessment to map the workflows Project Foundry can take off your team's plate, then see what a first build looks like.

Book an Assessment Explore manufacturing →