Mold/Die Maintenance & Shot-Count Tracker
Track every mold, die, and fixture by cumulative shot/cycle count and trigger scheduled maintenance before the count that historically causes defects or tool damage - so expensive tooling gets serviced proactively, with a supervisor approving every tool pull.
A private web app where production logs shots per run, counts accumulate per tool, maintenance fires at your thresholds, the tool-room supervisor approves and schedules the down-for-service, and every service resets the counter - with a full exportable maintenance history.
Before you start
- A list of your molds/dies/fixtures with their maintenance thresholds (or the numbers in your head)
- A way you currently record shots/cycles per run (a sheet, a press counter, a paper log)
- Free Vercel, Supabase, and Resend accounts (the plan walks you through them)
The problem this kills
Tooling crashes are expensive and almost always avoidable. A mold that should have been cleaned at 50,000 shots runs to 70,000, starts flashing or short-shooting, and now you're scrapping parts - or worse, a die galls and you're looking at a refurb bill and a line that's down for a week.
The maddening part: the shot count was right there. It was sitting in a press counter, a run sheet, or someone's notebook - just never added up against a threshold and never put in front of the person who could pull the tool in time.
Spreadsheets try to do this and fail in the same ways every time: counts don't accumulate reliably, the same run gets entered twice, thresholds live in someone's memory, and nobody gets a nudge until a part comes out bad. There's no record of who approved a tool pull or when the last refurb actually happened.
What you'll build
A small, private web app for your tool room and production floor that:
- Keeps a register of every mold, die, and fixture with its own maintenance thresholds - and supports multiple thresholds per tool (a minor clean at one count, a major refurb at a higher one).
- Lets production log shots per run (typed in, or imported from a CSV/Sheet pulled off your press counters).
- Accumulates the count per tool automatically and shows how close each one is to its next service.
- Fires a maintenance trigger the moment a tool crosses a threshold - and emails the tool-room supervisor.
- Puts a human approval gate in front of every tool pull: the supervisor reviews the triggered maintenance, approves and schedules the down-for-service, and only then is the tool marked for pull.
- Records the maintenance as done and resets the counter for that threshold, with notes on what was found.
- Keeps a complete, exportable maintenance history - every shot entry, every trigger, every approval, every service.
What's inside the Implementation Plan
The plan is a single runbook you paste into an AI coding agent (Claude Code), which then builds the tool with you step by step.
It opens by interviewing you about your shop - your tools, your naming and numbering conventions, your thresholds, your run volumes, and your messy exceptions - and reflects a short tailored spec back for your thumbs-up before it builds anything. You get a tracker shaped around your tooling, not a generic template.
From there it walks through every step - data model, login, the log-shots screen, the threshold engine, the supervisor approval gate, email alerts, and the history export - each ending with a ready-to-paste prompt. No prior coding needed.
The governance it includes (this is the point)
This isn't a toy spreadsheet replacement. Every build includes:
- Login so only your team can open the tool.
- Row-level security so each plant/organization only ever sees its own tooling and history.
- A complete audit trail - who logged which shots, who approved which pull, and exactly when.
- A human-in-the-loop approval gate - shot counts draft a maintenance trigger; a supervisor reviews and approves before any tool is marked for service. The system never pulls a tool on its own.
- Duplicate guards so the same run/shot entry can't be counted twice (dedupe key = tool + run/shot entry).
Who it's for
Tool-room supervisors, maintenance teams, and process engineers in molding, stamping, and casting operations - anyone responsible for keeping expensive tooling alive and the right person tracking when it's due for service.
You've got this - paste the first prompt and let the agent interview you.