Author: Kyo Logic

You can get reliable shop-floor visibility without buying a full ERP. A focused custom app can connect each job to its materials, operations, costs, and current status, giving the team one place to answer where the work is, what it is costing, and whether it will ship on time.
The value is not a prettier production board. It is a record that changes as the work changes.

A job traveler should not disappear into the shop

Job 4521 starts with an approved quote and a promised date. Planning releases the traveler. Material moves to cutting. The first operation finishes, but the paper traveler waits on a cart. The schedule still says the job is in cutting. Sales tells the customer everything is on track because no one has reported a problem.
At inspection, the team finds a dimensional issue. Two parts need rework. The note goes on paper, the cost goes nowhere, and the promise date becomes a guess.
A visible system records each transition where it occurs. The operator does not write a status in one place and ask someone else to update another. Starting, pausing, completing, scrapping, and moving material are the events that build the current picture.
Kyo’s article on gathering real-time production statistics explains why the useful report begins with reliable activity capture.

Can the shop answer three basic questions?

Every production system should answer:

Where is the job? Show the current operation, work center, queue position, and blocker.
What is it costing? Connect labor, material, outside services, scrap, and rework to the job.
Will it ship on time? Compare remaining work, required material, capacity, and the promise date.

Spreadsheets often answer one question at a time. A schedule may show dates but not material shortages. An inventory file may show quantity but not what is reserved. A costing sheet may be complete only after the job closes.
Visibility comes from relationships. Job 4521 should point to its operations, material demand, actual issues, quality results, and shipment. Each screen can stay simple because the records underneath are connected.

What does one source of truth look like?

Quote becomes job
↓
Job creates operations and material demand
↓
Shop activity updates status and actual cost
↓
Exceptions appear before the promise is missed
↓
Shipment closes the operational record
Materials belong in that flow. When receiving records a delivery, available inventory changes. When a job pulls material, on-hand and job cost change together. When unused material returns, both records are corrected through a controlled transaction.
Kyo covers that pattern in real-time inventory tracking. The point is not to make the number move faster. It is to make the movement explainable.

Build the screens around work, not around tables

An operator needs a short queue, clear instructions, required documents, and a fast way to report the result. A planner needs capacity, shortages, blocked work, and late-risk indicators. Sales needs a customer-facing status without access to internal production details.
One application can provide those different views while keeping one underlying job record. That is more useful than forcing every role into the same crowded dashboard.
The workflow also has to allow real exceptions. A job may skip an operation, return for rework, split into partial shipments, or wait on customer approval. Kyo’s article on customizing production steps and requirements shows why the system must reflect how the shop actually routes work.

Start with one value stream

Do not begin by digitizing every form in the building. Pick one product family or work center where visibility is poor and the business effect is clear. Define the status events, material transactions, and exceptions that matter. Pilot them with the people doing the work.
Measure practical outcomes: fewer status-chasing messages, earlier shortage detection, more accurate job cost, and fewer late surprises. Small production issues become large delays when the system hides them until the schedule is already broken.

Frequently asked questions

Do we need an ERP to track production in real time?

No. A focused application can capture production events and report current status. The right architecture depends on volume, integrations, devices, and availability requirements.

How does a custom app know where a job is?

Operators or connected equipment record defined events such as start, pause, complete, move, inspect, or ship. Those events update the job’s current state.

Can the app track materials with the job?

Yes. Receipts, reservations, pulls, returns, and scrap can be modeled as transactions tied to the job and inventory item.

What should we pilot first?

Choose a workflow with frequent status questions or costly late surprises, and include normal exceptions rather than testing only the ideal path.

Where to start

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England companies. We design shop-floor tools around the decisions each role makes, then connect those views to one controlled operational record.

If your team cannot answer where a job is without walking the floor, talk with Kyo Logic about a focused visibility pilot.

Disconnected manufacturing tools cost more than their subscription fees. When an order lives in QuickBooks, spreadsheets, email, and a whiteboard, the shop pays through duplicate entry, stale status, preventable expediting, and decisions made from conflicting information. A connected custom system reduces that tax by giving each business event one controlled home.
The problem is easy to miss because each tool works on its own. The cost appears in the spaces between them.

One order lives four different lives

A customer emails a revised purchase order. Sales updates the quote spreadsheet. Production is already using a printed traveler based on the first version. Purchasing has material demand in another workbook. Accounting creates the customer order in QuickBooks using the new quantity but the old promised date.
Nothing looks broken in isolation. Every file opens. Every team can point to a record. Yet the company no longer has one answer to a basic question: What did we promise?
Someone forwards the email.
Someone updates the traveler.
Someone finds the mismatch after material has been cut.
Kyo’s article on misaligned sources of truth in manufacturing explains why these conflicts become operational risk, not merely administrative inconvenience.

What does the disconnected-tools tax include?

Rekeying time. The same customer, part, quantity, and date are entered in multiple places. That work creates no new value and introduces opportunities for error.
Version disputes. People spend time proving which spreadsheet, attachment, or message is current. Decisions wait while the team reconstructs history.
Late exceptions. A shortage or delay sits inside one tool until someone manually carries it to the person who can act.
Unreliable costing. Material, labor, rework, and outside services arrive on different schedules. The real margin appears after the team has already quoted the next job.
Customer trust. Sales gives an answer based on the system it can see. Production knows something different. The customer experiences the mismatch.
One more spreadsheet often feels cheaper than changing the process. Kyo’s piece on when one more spreadsheet becomes a bottleneck shows when that trade stops working.

Why is a bigger ERP not automatically the fix?

An enterprise ERP can connect broad business functions, but it also brings a broad implementation. A custom manufacturer running quotes, jobs, and materials across separate tools may need a focused system for quote-to-job flow, shop status, materials, and exceptions, while keeping accounting or another specialized product in place.
Replacing four disconnected tools with one oversized system can trade one problem for another. If the workflows do not match the shop, people rebuild the old process in side spreadsheets.
The better starting question is: Which facts must remain connected from the customer’s request through shipment? Build or select the system around those facts and define clean boundaries with every tool that remains.

What would a connected custom system change?

Customer revision received
↓
Controlled order version updated
↓
Material demand and production plan recalculate
↓
Affected roles see the exception
↓
Customer promise is confirmed or changed
The app does not need to perform every function. It needs to make ownership clear. Accounting can remain authoritative for financial transactions. The custom system can own the operational job, material requirements, and status. The integration should pass defined facts with a visible failure queue.
Kyo’s article on FileMaker as an affordable ERP alternative gives another view of how smaller manufacturers can buy the control they need without adopting enterprise weight.

Measure the cost before choosing the cure

For two weeks, track how often people re-enter the same data, ask for status, correct a mismatch, expedite material, or discover a change late. Record the minutes and the business effect. Include supervisors and operators, not only office staff.
That evidence shows where connection matters first. It may point to one workflow, such as order revision control, rather than a complete system replacement. A bounded first project is easier to test and more likely to earn adoption.

Frequently asked questions

What are disconnected manufacturing tools?

They are systems or files that hold related operational information without a reliable shared record or controlled exchange.

Are spreadsheets always a problem in manufacturing?

No. Spreadsheets are useful for analysis and temporary work. Risk rises when they become the authoritative system for a shared, changing operation.

Does a connected system have to replace QuickBooks?

No. Accounting can remain in QuickBooks while a custom operational system manages jobs, production, and material flow through a defined integration.

How can we estimate the hidden cost?

Track duplicate entry, correction, status-chasing, expediting, and late discovery for a representative period, then attach labor and business impact to each event.

Where to start

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England companies. We connect the records and handoffs that run the shop while preserving the systems that still do their jobs well.

If the same order has a different answer in every department, contact Kyo Logic to map the smallest connected workflow that would remove the conflict.

Manufacturers can get quotes out faster without underpricing by capturing the same cost inputs in a repeatable model, reusing relevant history, and recording assumptions that production can later test. Speed should come from structure, not from removing the detail that protects margin.

Custom and contract shops often feel forced to choose: quote fast and guess, or quote carefully and lose the opportunity to a quicker competitor. A connected process removes much of that trade.

The rush quote starts with incomplete information

A prospect sends a drawing and asks for pricing by tomorrow. Estimating needs material, quantity breaks, setup, run time, outside processing, inspection, packaging, and margin. The closest past job is buried in a folder, and its actual labor was never compared with the estimate.

The estimator knows the work but spends the morning rebuilding inputs. Under time pressure, one outside-service fee is left as a placeholder. The quote goes out. The shop wins the order and discovers the missing cost after production begins.

Fast quoting is not mainly a typing problem. It is a data-reuse and handoff problem.

Which inputs should every manufacturing quote capture?

A structured quote can separate:

• Material: item, grade, size, quantity, yield, scrap factor, and current price basis.
  
• Labor: setup and run assumptions by operation or work center.
  
• Outside services: process, supplier estimate, freight, and expected lead time.
  
• Quality and documentation: inspections, testing, certificates, and customer-specific requirements.
  
• Commercial assumptions: quantity breaks, lead time, validity, margin, and exclusions.

Kyo’s article on capturing client-provided materials, specifications, and requirements shows why the intake record should preserve the details that drive price and production.

The model should make missing information visible. It should not silently turn an empty field into zero cost.

How does a past job make the next quote better?

New request received

↓

Comparable jobs found by part, process, material, or customer

↓

Estimate and actual results compared

↓

Assumptions adjusted for the new quantity and conditions

↓

Approved quote becomes the production job

Past jobs are useful only when their actual results are trustworthy. The estimator should see estimated versus actual material, setup, labor, scrap, and outside service. A similar job with a large variance deserves investigation, not blind reuse.

The explanation matters too. A note such as “first article required two fixture changes” gives the number context that a raw total cannot.

The clean handoff prevents the second round of entry

When the customer accepts, the approved quote should create or populate the operational job. Customer details, part and revision, quantity, required date, operations, material assumptions, outside services, and quality requirements should move through a controlled handoff.

That avoids rekeying and preserves what the business sold. Production can see which assumptions were approved and flag a change before it becomes unplanned work.

Kyo’s article on connecting online orders to billing, inventory, and shipping demonstrates the broader value of carrying structured information through the order lifecycle.

Approval rules should follow risk

Not every quote needs the same review. Set approval thresholds around margin, total value, unusual material, new processes, expedited lead time, or missing cost inputs. A routine repeat job can move quickly. A first-time aerospace part with outside testing should receive the attention its risk deserves.

The system should record who approved the quote and which version the customer accepted. When the request changes, create a new version instead of overwriting the original assumptions.

After the job closes, compare estimate with actual and route meaningful variance back to estimating. That feedback protects future pricing. Kyo’s discussion of custom ERP solutions for manufacturing shows how one operational data model can connect those stages.

Frequently asked questions

What is the fastest way to improve manufacturing quoting?

Standardize required inputs, expose missing information, and make comparable estimate-versus-actual job history easy to find.

Should a quote use current material prices?

The company should define its price source, effective date, validity period, and treatment of volatile material. Those rules should be visible in the quote.

Can quoting software prevent underpricing?

It can reduce missing inputs and apply approval rules, but it cannot remove commercial judgment or guarantee a profitable outcome.

What should happen when a quote is accepted?

The approved version should hand customer, part, quantity, operations, materials, requirements, and promise information into the job without uncontrolled reentry.

Where to start

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England companies. We turn quoting knowledge into a repeatable workflow that helps estimators respond faster while keeping the assumptions visible.

If your best estimator rebuilds every quote from memory, talk with Kyo Logic about a structured quote-to-job workflow.

Kyo Logic has six free FileMaker add-ons and demo files you can download today: a container data exporter for FileMaker Server, a calendar invite creator, a rich text editor, a custom import tool, a multi-file uploader, and a SendGrid email add-on. Each one solves a problem we kept rebuilding for clients, and each one now has a refreshed page with clearer install notes and a simpler download.

Picture a Monday morning. Sales wants to attach six photos to a quote record without doing it one at a time. Operations wants a supplier spreadsheet imported without a developer on the call. Accounting wants Friday’s signed PDFs sitting in a shared folder, not stuck inside FileMaker. None of these is a big project. Each is the kind of small, recurring friction that eats an afternoon a week. These tools are our answer to that kind of work.

What is in the set

Data File Export demo. A free demo file that writes PDFs, images, and documents out of container fields from a server-side script, with no plug-ins. Use it when a scheduled script on FileMaker Server needs to drop files into a folder another system reads.

Calendar Invite Creator. Turns a meeting on a FileMaker record into a standard .ics invite your attendees can accept in Outlook, Apple Calendar, or Google Calendar. Use it when appointments live in FileMaker but people live in their calendars.

Rich Text Editor. Gives users a familiar formatting toolbar for notes, templates, and client-facing text. You set it up once and reuse it on as many fields as you need.

Custom Import Tool. Friendly column labels, saved templates, and a preview step before anything touches your real records. Use it when the people doing imports are not FileMaker developers.

Multi-File Uploader. Attach photos, PDFs, spreadsheets, and drawings to a record in one step, then preview, download, or delete them from a simple portal.

SendGrid Email add-on. Moves FileMaker email off fragile SMTP (the older mail-server sign-in method) and onto an authenticated sending service, attachments included.

Which one should you start with?

Start with the problem that costs your team the most time each week. If files are stuck inside FileMaker, start with Data File Export or the Multi-File Uploader. If outside data is the bottleneck, start with the Custom Import Tool. If communication is the gap, the Calendar Invite Creator and SendGrid add-on close it.

How the downloads work

Each page has a short form. Fill it in and the file arrives in your inbox right away, with a follow-up a few days later in case you want help fitting it into your own solution. Every file is a working FileMaker file you can open, test, and copy from.

What this could look like in your solution

These tools are starting points. Most teams end up wanting a version shaped to their own records, layouts, and approvals. That is the work Kyo Logic does every day as a Claris FileMaker partner: taking a pattern that works in a demo file and making it fit the way your operation actually runs. If you want a second set of eyes before you start, book a free Data Health Check.

Frequently asked questions

Are these FileMaker add-ons really free?

Yes. Each file is free to download and use in your own FileMaker solutions. You only fill in a short form so we can email you the file.

Which versions of FileMaker do they work with?

Each tool page lists its own requirements. The set was built or refreshed between 2025 and 2026 on current versions of FileMaker.

Can I change the add-ons to fit my own solution?

Yes. They are unlocked FileMaker files, so your developer can open the scripts and layouts and adapt them.

Can Kyo Logic install or customize one for us?

Yes. Kyo Logic builds and extends FileMaker solutions for teams of every size, and these add-ons are a common starting point for that work.

Quick takeaways

• Six free FileMaker tools are available now, each on its own page with install notes.
• Pick the one tied to the task that costs your team the most time each week.
• Every download is a working file you can open, test, and adapt.
• If you want help fitting one into your own solution, Kyo Logic can take it from demo to production.

To stop missing manufacturing delivery dates, connect each customer promise to material readiness, real capacity, and current production status. Then surface risks while the team can still resequence work, expedite the right item, or reset the commitment. A promise date stored only on an order is not a schedule.

On-time delivery is trust. One late job can damage a customer relationship that took years to build.

Why does a believable promise become late?

Sales commits to Friday based on a normal lead time. Planning puts the job on a whiteboard. A required component is due Wednesday, but the purchase order slips. Cutting loses half a shift to rework on another job. Inspection becomes a queue. Each team knows part of the story, but no shared view recalculates the risk.

On Thursday afternoon, the job is still two operations from complete. The customer learns only after asking.

The missed date is the final event. The causes appeared earlier as a late material receipt, a capacity conflict, a stalled operation, or a quality exception.

Kyo’s article on why small production issues become big delays shows why early visibility changes the response.

A promise date needs an operational chain

Customer requirement accepted

↓

Material and outside-service dates confirmed

↓

Operations scheduled against real capacity

↓

Shop activity updates remaining work

↓

Exceptions change the projected completion date

A shared schedule should distinguish the requested date, committed date, planned completion, and current projected completion. Those values answer different questions. Hiding them in one field prevents the team from seeing whether a commitment is drifting.

The production record also needs a definition of “complete.” A job may leave the last machine but still require inspection, documentation, packaging, or an outside process. The schedule should include every step required to ship.

Which warning signals matter before a job is late?

The team does not need more notifications. It needs a short exception list tied to action:

• Required material is not available by the operation need date.
• An operation has not started by its planned time.
• Reported scrap or rework threatens the required quantity.
• Remaining work exceeds available capacity before the promise date.
• An outside service has no confirmed return date.
• A required approval or inspection is still open.

Kyo’s article on gathering real-time production statistics describes the activity data that makes these warnings credible.

Each exception should have an owner and a next review time. Otherwise, the dashboard becomes another place where late work is displayed without being managed.

Schedule from status, not from a weekly reconstruction

A schedule is only as current as its inputs. If operators report completion at the end of the week, the system cannot warn the planner on Tuesday. Capture start, pause, completion, quantity, and blocking reason close to the work.

That does not require a complicated interface. A station may show the ready queue and a few clear actions. The system can calculate remaining work and risk from those events.

Planning also needs controlled ways to resequence jobs. A rush order may be the right decision, but the software should show which existing promises it displaces. Capacity is not created by changing a color on a board.

Kyo’s guide to production planning with FileMaker workflow automation explains how structured status and planning can remain connected.

Tell the customer before the customer asks

Even a strong system cannot prevent every delay. Material shortages, equipment failures, quality problems, and changed customer requirements still happen. The operational advantage is recognizing the effect early.

Sales can contact the customer with a specific explanation, a revised date, and options. That is different from discovering the problem when the promised shipment does not arrive.

Track the reason for each changed commitment. Over time, management can see whether misses come from quoting, purchasing, capacity, quality, outside services, or status capture. Fixing the recurring cause improves more than one schedule.

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England companies. We connect customer commitments to real shop activity, so teams can manage delivery risk before it becomes a broken promise.

Frequently asked questions

What is the difference between a promise date and a projected date?

The promise date is the commitment made to the customer. The projected date is the system’s current estimate based on material, capacity, status, and remaining work.

Can production software guarantee on-time delivery?

No. It can improve planning, visibility, and response, but actual delivery also depends on suppliers, equipment, quality, staffing, and operating discipline.

What status should operators record?

Capture only what supports decisions, commonly start, pause, complete, quantity, scrap or rework, and a blocking reason.

What should a late-job dashboard show?

Show the affected promise, current operation, remaining work, material or capacity constraint, risk reason, owner, and next action.

An MES records and controls what actually happens on the shop floor. For many small manufacturers, the useful core is work-order status, operation tracking, scrap and yield, material traceability, and a current view of what is late. A full enterprise MES is overkill when the shop needs that focused control but cannot justify the implementation weight surrounding it.

The acronym can make the decision sound larger than it is. A 45-person machine shop does not wake up wanting an MES. It wants to know whether Job 8104 cleared inspection, why the second shift is waiting, and which customer promise is now at risk.

An MES connects the plan to the work being done

An ERP usually holds commercial and planning information such as orders, purchasing, inventory, and finance. An MES focuses on execution: the operations, people, machines, material, quality events, and timestamps that turn an order into a finished product.

The boundary varies by system. The business outcome is more important than the label. When a planner releases a work order, the floor needs an accurate sequence. When an operator starts or completes an operation, the status should change. When scrap occurs, the cause and quantity should connect to the job. When a lot of material is consumed, traceability should follow it.

Our article on integrating with a production application shows how operational systems can connect without forcing every function into one monolith.

Which MES capabilities matter to a small shop?

Most 20-150 person manufacturers should start with four questions:

1. What should each work center do next? The queue needs priorities, requirements, and current readiness.
2. Where is each job now? Status should come from work activity, not a meeting or a manually rebuilt report.
3. What happened during production? Quantity, scrap, downtime, inspection, and notes need to stay with the job.
4. Can we trace the material and process? Lot, heat, batch, or component records should connect to the finished item where the business requires it.

That focused set already changes how a shop runs. our guidance on gathering real-time production statistics explains why timely operational records are more useful than a report reconstructed after the shift ends.

What could a right-sized flow look like?

A laser operator signs into a work-center screen and selects the next ready job. The system records the start. A material scan confirms the correct lot. The operator reports the completed quantity and two scrapped pieces. Quality receives the inspection task. The job moves to bending only after the required check passes.

Work order released

↓

Ready operation appears at the station

↓

Material and activity are recorded

↓

Quality result controls the next step

↓

Planner sees live status and exceptions

No one has to turn a whiteboard photo into a customer update. The record is created by the work itself.

When is a full MES warranted?

A full MES may be justified when the company has many sites, highly automated equipment, complex scheduling, strict electronic records, extensive genealogy requirements, or a need for validated standard capabilities across plants. It may also be appropriate when an enterprise customer or parent company mandates a specific platform.

The shop should evaluate implementation ownership as carefully as the feature list. Who will define routings, maintain integrations, govern master data, train users, review exceptions, and support the floor outside office hours? An MES is an operating system, not a dashboard subscription.

When is a custom app the better fit?

A focused custom app can be a sound choice when the shop needs visibility and traceability for a defined process, wants to preserve existing accounting or ERP tools, and can improve in stages. FileMaker can provide purpose-built screens, barcode workflows, connected records, and reporting without forcing the company to adopt capabilities it will not use.

That does not mean every custom app is automatically simpler. The solution still needs deliberate architecture, performance testing, permissions, backups, and an owner. The value comes from aligning the system with the real shop while keeping the scope controlled.

The same logic appears in our article on custom ERP solutions for manufacturing: implement the operational control that changes decisions, then expand from evidence.

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England companies. We help smaller shops separate the MES capabilities they genuinely need from the enterprise package they may never use.

Frequently asked questions

What is the difference between an MES and an ERP?

An ERP generally manages business planning and transactions, while an MES focuses on executing and recording shop-floor work. Their responsibilities often overlap and must be defined for the specific systems.

Does a small manufacturer need an MES?

It may need MES-like capabilities without needing a full enterprise MES. Start with the production decisions and traceability gaps the shop cannot manage reliably today.

Can FileMaker be used for MES workflows?

FileMaker can support focused shop-floor applications. Suitability depends on scale, integrations, device needs, availability requirements, and validation obligations.

What should an MES pilot include?

Use one real product family or work center, include normal exceptions, and measure whether status accuracy, traceability, and response time improve.

Manufacturing job costing falls apart in a busy month because labor, material, scrap, and outside-service entries arrive after the work. The shop makes its next pricing decision before it knows what the last job truly cost. The fix is to capture actual cost as part of production, tie every transaction to the job, and review margin exceptions before closeout.

Volume does not create the weakness. It exposes a costing process that depends on spare time.

The profitable rush order that was not

A long-time customer needs a rush order. Estimating uses a similar job from last year, adds material, applies the normal labor rate, and sends the quote that afternoon. The shop wins the work.

Then the schedule changes. Setup takes two extra hours. A partial material shipment forces a second receiving and handling cycle. Three parts fail inspection and need rework. An outside processor adds an expedite fee. The job ships on time, and everyone considers it a success.

Two weeks later, accounting closes the job. The margin is nearly gone.

The problem was not the quote alone. The team could not see actual cost moving while it still had choices.

Why does busy production make the number worse?

Manual job costing asks people to record work after they finish the urgent work. During a busy month, time tickets are completed from memory, material pulls are written on paper, and scrap notes wait for a supervisor. Outside invoices arrive after shipment.

Each delay separates cost from the event that created it. Missing entries make an active job look healthy. Late entries turn into an unpleasant closeout report.

Kyo’s article on small production issues becoming large delays applies to cost as well as schedule. A small variance becomes expensive when no one sees the pattern early.

What should update the job as work happens?

Estimate approved

↓

Material reserved and purchased

↓

Labor and setup recorded at the operation

↓

Scrap, rework, and outside services added

↓

Projected margin compared with actual progress

Labor capture should fit the floor. An operator may start and stop an operation, report a completed quantity, or allocate time across jobs. Material cost should follow receipts, pulls, returns, and substitutions. Quality events should distinguish normal production from scrap and rework.

Kyo’s article on custom ERP solutions for manufacturing describes how connected operational records support these decisions without requiring a full enterprise suite.

Real-time costing is an exception tool

No manager needs to stare at every cost entry. The system should surface jobs whose labor, material, scrap, or outside service is moving beyond an approved threshold.

A supervisor sees that setup hours are twice the estimate while the first batch is still running. The team can check the fixture, process, or assumption before the remaining quantity is produced. Estimating sees the reason and can use it on the next quote.

This creates a learning loop:

• Estimate records the assumptions.
• Production records the actual work.
• Exceptions capture why the result differed.
• Closeout updates the reference used for future estimates.

The data becomes operational memory, not a score delivered after the game.

How do you fix job costing without slowing the floor?

Start with the largest sources of variance. If material is already accurate but labor and rework are not, do not redesign inventory first. Put capture at the point where the event occurs and minimize required input.

Use job and operation identifiers that people can scan or select quickly. Set clear rules for indirect labor, shared setup, partial quantities, and returns. Review missing or impossible entries daily while the work is fresh.

The quote should use the same cost categories the job will report. Kyo’s article on connecting customer orders to billing, inventory, and shipping shows why downstream work becomes cleaner when the handoff begins with structured information.

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England companies. We design costing workflows that fit the work people already perform and show margin risk early enough to change the outcome.

Frequently asked questions

What costs should a manufacturing job include?

The model commonly includes direct material, labor, setup, outside services, scrap, rework, and allocated overhead. The exact method should match the company’s accounting policy.

Does real-time job costing replace accounting?

No. It provides an operational view during the job. Accounting remains authoritative for formal financial treatment and closeout.

How can operators record time without extra paperwork?

Use a short workflow at the job or operation, often supported by barcode scanning, clear defaults, and exception-based corrections.

What should management review first?

Focus on active jobs with material, labor, scrap, or outside-service variance large enough to threaten margin or delivery.

Many small manufacturers do not need separate ERP and CRM systems connected by a fragile web of imports and sync jobs. One custom app can often manage customers, quotes, jobs, materials, and order status in a single relational core.

Separate systems still make sense when each product handles a mature, specialized function well. The decision is about operating reality, not software categories.

What is the hidden tax of two systems?

A sales representative updates a promised date in the CRM. Production changes the schedule in the ERP. Customer service checks one system, then messages someone who uses the other. Two dates now exist, and neither feels safe enough to give the customer.

Someone has to re-enter the account.

Someone has to reconcile the order.

Someone has to decide which status is right.

Integration can reduce that work, but every connection has rules, failure modes, and ownership. If a customer name changes, which system wins? If an order fails to sync, who sees the error? If a salesperson creates a duplicate account, how is it merged without breaking job history?

The larger cost is the time people spend managing the boundary.

What belongs in one unified app?

For a 20-150 person custom manufacturer, the important records often form one connected chain.

Account

↓

Contact and opportunity

↓

Quote and revision

↓

Customer order

↓

Job and routing

↓

Materials and outside services

↓

Shipment and invoice reference

A custom app can keep those records related. Sales sees the customer, open quotes, expected work, and communication history. Production sees the approved order, job requirements, material readiness, and due date. Management sees backlog, conversion, late-job risk, and customer concentration.

One record changes, and every role sees the current result according to its permissions.

That is not a CRM bolted onto an ERP. It is one operating model expressed through different screens.

How does a unified workflow look?

A Connecticut contract manufacturer receives a request for a repeat part with a modified inspection requirement.

The account manager opens the customer record and creates a quote from the prior job. The app carries forward approved part details but requires the new inspection requirement to be reviewed.

Engineering confirms the revision.

↓

Estimating updates labor and outside-service assumptions.

↓

Sales sends the approved quote.

↓

The accepted quote creates the order and job.

↓

Purchasing sees the required material and certification.

↓

Production reports status against the same job.

↓

Customer service answers from the same record.

No spreadsheet handoff. No argument about whether the CRM or ERP has the correct due date. No duplicate customer record created just to start production.

Where does FileMaker fit?

FileMaker can model accounts, contacts, quotes, jobs, materials, operations, documents, invoices, and communications as related records. It can present a sales workspace to one user and a production workspace to another without splitting the underlying truth.

The app can also connect to systems that should remain specialized. Accounting software can stay responsible for the ledger. An ecommerce platform can stay responsible for online orders. A shipping platform can stay responsible for labels and carrier transactions.

The custom app becomes the operating layer that connects the business process.

When is integration the right call?

Keep separate systems when each one is trusted, the ownership boundary is clear, and the integration can be governed.

A separate CRM may be right when sales needs advanced marketing automation, territory management, forecasting, or a large ecosystem of sales tools. A separate ERP may be right when the company needs complex financials, multi-site planning, formal MRP, global supply-chain controls, or industry modules a custom app should not recreate.

Define the contract between systems:

• Which system owns each record?
• Which fields are allowed to move?
• What event triggers the exchange?
• How are errors surfaced?
• How are retries handled?
• Who reviews duplicates and conflicts?
• What audit trail proves what happened?

A connection is reliable when a person can tell that it failed. Silent sync is not a control.

Could one app become too large?

Yes. A custom app can become difficult to maintain if every request is added without ownership, documentation, testing, and release discipline.

Build one module at a time. Name the owner. Define the records it can change. Test the handoff. Retire the spreadsheet it replaces. Measure whether the result improved cycle time, accuracy, or visibility.

A first release might connect accounts, quotes, and jobs. Inventory and quality can come later. Each release should solve a complete problem.

How should a manufacturer decide?

Start with the handoffs, not the product demos. List every point where someone copies data, waits for a status, resolves a mismatch, or asks which system is right.

Then test three options:

1. Improve the existing integration. Best when both systems are trusted and the main problem is a small number of poorly designed exchanges.
2. Consolidate the operating workflow in one custom app. Best when the same people move repeatedly between sales and production records and two-system complexity creates daily friction.
3. Keep specialized systems and add a focused operating layer. Best when the CRM and ERP must remain, but users need one place to coordinate the workflow.

Modernize in place. Keep the parts that work. Replace the gaps that force people to manage the system by hand.

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England businesses. A useful discovery session maps the customer-to-cash workflow, identifies the authoritative records, and determines whether consolidation or integration creates the cleaner model.

Related reading

• Integrating ERP and CRM for a Unified Manufacturing Solution
• Tailoring CRM Systems to Meet Manufacturing Compliance Standards
• CRM Cleanup: Using FileMaker to Standardize, Merge, and Validate Customer Data

Frequently asked questions

Can one custom app replace both ERP and CRM?

For many small manufacturers, one custom app can manage the connected customer, quote, order, job, material, and status workflows they use every day. Complex financial, planning, marketing, or global requirements may still justify specialized systems.

What is the main risk of separate ERP and CRM systems?

The main risk is conflicting data and unclear ownership. Duplicate entry, failed syncs, and different status values can make employees distrust both systems.

When should ERP and CRM stay separate?

Keep them separate when each platform handles a mature specialized function well, the source of truth is defined, and the integration has visible errors, retries, ownership, and audit history.

If you deal with physical inventory, you’ve likely run into an issue where your team has wasted valuable time hunting for an item that was already shipped. It’s listed in the inventory but was packed up hours ago. Your database just didn’t reconcile it yet.

Your manufacturing inventory count is usually wrong because the system records periodic totals while the shop runs on continuous movement. Every receipt, pull, return, substitution, scrap event, and shipment changes the available quantity. If those transactions are late or missing, yesterday’s correct count becomes today’s false promise.

The fix is a process the team can follow at the point of movement, supported by cycle counting and a clear exception queue. Blaming the annual count team will not repair the daily system.

The spreadsheet drifts the moment work starts

At 7:00 a.m., the inventory file shows 240 pieces on hand. A technician pulls 40 for Job 1902 and writes the quantity on a traveler. Receiving places another 100 on the shelf but waits to update the spreadsheet. Quality quarantines 20. A second job takes 30 from the same location.

By lunch, the file still says 240. The shelf contains 250 pieces, but only 230 are available. Purchasing sees the old number and delays an order. Planning promises material to a job that cannot use all of it.

The count is not failing because people cannot subtract. It is failing because physical events and system events are separated.

Kyo’s article on why inventory feels off even when it is tracked explains how apparently small timing and status gaps accumulate.

Inventory should be a transaction history, not an edited total

A trusted inventory balance can be calculated from controlled movements:

Opening balance

↓

Receipts and approved adjustments

↓

Job pulls, returns, scrap, and transfers

↓

Shipments and other issues

↓

Current on-hand, allocated, quarantined, and available quantities

Users should not casually overwrite the total. If a correction is necessary, record an adjustment with a reason, actor, and timestamp. That preserves the explanation for the next review.

Kyo’s guidance on tracking inventory in real time shows how deliveries and returns belong in the same operational flow.

What makes shop-floor inventory capture work?

The transaction needs to be easier than the workaround. Use clear item and location identifiers, barcode scanning where it helps, sensible defaults, and short role-specific screens. A material pull should ask for the job, item, quantity, location, and any required lot identifier, not a page of unrelated fields.

Define edge cases before rollout:

• Can one job pull from multiple lots?
• How are unused pieces returned?
• What happens when material is moved between locations?
• How is scrap distinguished from a normal issue?
• Who can adjust a balance, and who reviews it?

The answers become workflow rules. Without them, the new system simply digitizes the ambiguity.

Cycle counting catches drift before year-end

An annual wall-to-wall count can correct balances, but it does not explain why they drifted. Cycle counting reviews a manageable group of items throughout the year. High-value, high-use, or high-risk items can be checked more often.

The useful output is not only the corrected quantity. It is the pattern: repeated errors at one location, returns that are not recorded, units of measure that confuse users, or jobs consuming material under the wrong item.

Kyo’s article on automating year-end inventory audits with FileMaker provides a broader review framework. Daily transaction discipline and cycle counts make that annual process smaller and more credible.

Wrong inventory numbers create downstream costs

A bad balance becomes a stockout, an expedite fee, a delayed operation, excess purchasing, or a missed quote. It also trains people not to trust the system. Once planners call the floor before every decision, the software has stopped being the source of truth.

An exception desk can help rebuild trust by showing negative balances, overdue receipts, unposted material, unusual adjustments, and jobs whose allocations exceed available stock. Kyo’s real-time exception desk for orders and inventory illustrates that management pattern.

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England companies. We design inventory workflows around physical movement, so the system balance can support planning rather than merely document last month’s count.

Frequently asked questions

What is the difference between on-hand and available inventory?

On-hand is the physical recorded quantity. Available inventory typically subtracts allocations, quarantine, or other restrictions according to the company’s rules.

Why not let users edit the inventory total directly?

Direct edits erase the reason for the change. Controlled transactions and adjustments preserve history and make errors easier to investigate.

How often should a manufacturer cycle count?

Frequency should follow item value, movement, risk, and observed variance. A company may count critical items often and stable items less frequently.

Can barcode scanning fix inventory accuracy?

It can reduce identification and entry errors, but only when the underlying locations, units, transaction rules, and user workflow are sound.

Yes. For many small custom and contract manufacturers, a purpose-built FileMaker app can cover the jobs, materials, quoting, and shop-floor visibility they actually need without forcing the business into a full enterprise ERP rollout.

That does not mean every shop should avoid ERP. The right question is not, “Do we need every ERP module?” It is, “Which workflows must we control now, and what is the simplest system that can control them?”

What does ERP mean in a 20-150 person shop?

A plant manager at a 60-person manufacturer needs to know whether a job is on schedule, which materials are missing, what changed on the latest drawing, and whether the customer can get an accurate delivery date.

Customer request

↓

Quote and promised date

↓

Job and routing

↓

Materials and purchasing

↓

Shop-floor status

↓

Shipment and invoice

Large ERP products can manage that flow, along with dozens of functions the shop may never use. A custom FileMaker app starts with the handoffs that cause delays, duplicate entry, and missed commitments.

The five modules that usually matter first

1. Job tracking

Every order needs one visible source of truth. Sales, production, purchasing, and management should see the same job number, priority, due date, current step, and owner. Customer service should not need to send three messages before answering a delivery question.

2. Materials and inventory

The system should show what a job requires, what is on hand, what is allocated, and what must be purchased. The goal is to prevent a scheduled job from reaching the floor without a required component.

3. Quoting

A useful quoting module connects customer requirements, material assumptions, labor estimates, outside services, margin, and revision history. When a quote becomes an order, the team should not re-enter the same information.

4. Shop-floor status

Operators and supervisors need a simple way to report what is happening. That might be a workstation, tablet, barcode scan, or mobile screen. The interface should fit the work.

5. Customer order visibility

A customer may only need a reliable status, an approved document, or a notification when a milestone is complete. FileMaker can support those controlled views while keeping internal data private.

Where does a custom FileMaker app win?

A custom app wins when the business process is specific, valuable, and difficult to represent in a generic template.

A quoting team might price the same part differently based on material source, tooling availability, or a customer-specific inspection plan. A production team might schedule work around shared equipment, outside processing, and partial shipments. Those details are the process.

FileMaker can model related customers, quotes, jobs, parts, materials, operations, and documents in one system. It can also exchange approved data with accounting software such as QuickBooks when the accounting package should remain the financial system of record.

FileMaker manages the operating workflow

↓

QuickBooks manages the general ledger

↓

The integration passes approved customers, invoices, payments, or job costs

The business keeps the tools that work and replaces the spreadsheets, email chains, and disconnected trackers between them.

What about cost?

A “$1M ERP” is rarely just a software license. The full cost can include implementation, consulting, data migration, integrations, training, process redesign, support, and employee time.

A custom FileMaker project also has costs. It requires discovery, design, development, testing, training, and ongoing ownership. The difference is scope. A focused app can target the workflows that create the most value first, then expand based on evidence.

The honest comparison should include five questions:

• How many people need access?
• Which processes must change?
• How much historical data needs to move?
• Which systems must remain connected?
• Who will own the system after launch?

A shop should choose FileMaker when a bounded custom system can solve the operating problem with less complexity and a clearer path to adoption.

When is full ERP the better choice?

A manufacturer may need a full ERP when it has complex multi-entity financials, global supply-chain requirements, standardized industry modules, extensive regulatory controls, or a large internal team prepared to run the platform.

There is also a middle path. FileMaker can extend an existing ERP instead of replacing it. It can provide a better shop-floor interface, manage a specialized workflow, or connect a process the ERP handles poorly.

The goal is not to replace a system that works. The goal is to remove the gaps that keep people working around it.

What could a first release look like?

Start with one workflow that has a measurable cost.

Sales enters the approved order

↓

Planning creates the job and routing

↓

Purchasing confirms material readiness

↓

Operators update the current step

↓

Customer service sees the same status

↓

Management reviews late-job reasons

The first release should answer four questions reliably. Is the job ready? What is blocking it? Who owns the next action? Is the promised date at risk?

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England businesses. The practical starting point is a workflow review, not a product demo.

Related reading

• Maximizing Manufacturing Efficiency with Custom ERP Solutions
• Why FileMaker is an Inexpensive Alternative to ERPs
• Integrating ERP and CRM for a Unified Manufacturing Solution

Frequently asked questions

Can FileMaker be used as an ERP?

FileMaker can support ERP-style workflows such as quoting, jobs, materials, inventory, production status, and customer visibility. Whether it should replace a full ERP depends on the company’s financial, operational, regulatory, and integration requirements.

Is a custom FileMaker app cheaper than ERP?

It can be when the business needs a focused set of workflows. Compare implementation, migration, integrations, training, support, and internal ownership, not just license fees.

When should a manufacturer choose full ERP instead?

Full ERP may be the better fit when the company needs complex financials, global supply-chain controls, standardized industry modules, or a governed platform across many locations.