Case Study
Case Study: Manufacturing RFQ-to-Shipment Automation
We built a connected set of automations for a contract manufacturer making machined and fabricated parts: RFQ intake that summarises each request for the estimator, a manufacturing CRM for quotes and reorders, customer PO to sales order entry, supplier PO follow-up and certificate packs for every shipment. Estimators start from a summary instead of a pile of files, customer service approves drafts instead of keying orders, and quality signs packs that are already assembled.
- Manufacturer type
- Contract manufacturer of machined and fabricated parts for B2B customers
- Team involved
- Owner, estimators, inside sales, customer service, buyers, quality manager
- Systems connected
- ERP, CRM, Microsoft 365 and SharePoint, quoting templates, n8n
- Delivery
- Scrum, 1-week sprints, about 8 weeks to full launch
The challenge
Where the practice started
RFQs arrived as emails with drawing packs, and estimators spent their first hour on each one working out what was being asked. Quotes went out slowly, and follow-up depended on memory.
Customer POs were keyed by hand into the ERP. Old revisions and price differences were sometimes caught only at shipment.
Buyers chased suppliers by email and phone, promised dates were rarely recorded, and late material surprised planning.
Certificate packs were assembled at the end of the day as trucks waited, and missing material certs held up shipments.
Goals
What the project had to change
- Every RFQ is summarised for the estimator on the day it arrives.
- Every quote and account sits in one pipeline with follow-ups and reorder alerts.
- Customer POs become checked draft orders, approved by customer service.
- Buyers see which supplier deliveries are at risk against job dates.
- Every shipment leaves with a complete certificate pack signed by quality.
What we built
What we built, as one connected system.
RFQ intake
We connected the RFQ inbox to a document reader that summarises parts, materials, finishes, certifications and due dates, flags unusual requirements and requests prices for outside processes from approved suppliers.
Service detailsManufacturing CRM
RFQs, quotes and ERP order history now feed one pipeline with quote follow-ups, reorder alerts and a weekly won and lost report.
Service detailsPO to sales order
Customer POs are read into draft orders, checked against part revisions, quoted prices and lead times, and posted to the ERP once customer service approves.
Service detailsSupplier follow-up
New POs go out with confirmation requests, promised dates are recorded, slipping deliveries are chased against job dates and bank-detail changes are held for a phone check.
Service detailsCertificate packs
Orders ready to ship trigger a pack with a draft CoC, material certs and inspection reports; missing documents are flagged the day before.
Service detailsArchitecture
How the manufacturer's workflows connect
- Input
- Logic and services
- AI step
- Data
- People
- Output
How it flows
- 1 RFQs, customer POs and ERP data feed one n8n instance.
- 2 AI steps read documents and replies; the CRM and SharePoint hold quotes, summaries and certificates.
- 3 Estimators, customer service and buyers approve drafts, and quality signs certificate packs.
- 4 Approved orders and promised dates are written back to the ERP, and every step is logged.
How it behaves
How the system behaves day to day
What customers see
- A confirmation and quicker quotes on RFQs
- Prompt order acknowledgements with any questions raised early
- Complete certificate packs with each shipment
What the office sees
- RFQ summaries and draft quotes for estimators
- Draft orders with mismatches highlighted
- A daily at-risk supplier list and draft cert packs
What the automation does
- Reads RFQs, POs and supplier replies
- Checks drafts against the ERP
- Logs every step and alerts the operations manager if anything fails
Edge cases and fallbacks
- A PO references an old drawing revision
- Flagged to customer service and engineering before the order posts.
- A supplier email announces new bank details
- Held and verified by phone; nothing reaches accounts payable as an instruction.
- A material cert is missing at ship time
- The shipment is flagged; nothing is substituted.
- An RFQ comes from a customer with export-sensitive drawings
- Kept out of AI steps under the rule agreed at discovery.
- The ERP or n8n has an outage
- Work falls back to the manual process, runs are retried and the operations manager is alerted.
Integrations
What we connected
Microsoft Dynamics 365 Business Central
ERPCustomers, items, sales orders and purchase orders for order entry, CRM sync and supplier follow-up.
Business Central API v2.0 (including salesOrders).
HubSpot
CRMAccounts, contacts, quotes as deals, follow-ups and reorder tasks.
HubSpot CRM REST API.
Microsoft 365 and SharePoint
Email and documentsRFQ, orders and purchasing inboxes; certificates and summaries.
Microsoft Graph API.
n8n
Automation platformRuns the workflows, self-hosted or on n8n Cloud.
Your own n8n instance; we hand over every workflow.
How we delivered it
Week by week, one workflow at a time.
Delivery timeline
Typical time to launch: about 8 weeks, then support
-
01
Discovery
Week 1
We followed RFQs, orders, purchasing and shipments through the office, mapped data flows, agreed AI rules for confidential drawings and set up ERP API access.
-
02
Design and access
Week 2
Summary and draft formats, check rules, wording approved by the team and test environments.
-
03
Sprint 1: RFQ intake
Week 3
Built and shadow-ran RFQ summaries against estimators' own notes; demo and sign-off.
-
04
Sprint 2: CRM pipeline
Week 4
RFQ intake went live. Connected RFQs, quotes and ERP history to the CRM.
-
05
Sprint 3: order entry
Week 5
The pipeline went live. Built PO reading and ERP checks; staff compared drafts line by line.
-
06
Sprint 4: supplier follow-up
Week 6
Order entry went live for the main customers. Built supplier requests, chasing and the bank-change hold.
-
07
Sprint 5: certificate packs
Week 7
Supplier follow-up went live. Built cert packs, CoC drafts and the day-before list.
-
08
UAT and handover
Week 8
The team ran user acceptance testing on every workflow, then we switched everything on, handed over the run book and trained the team.
-
09
Support
Ongoing
Weekly check-ins during stabilisation, then monthly care.
Who does what
What the team does, and what automation does.
Automation does
- Summarises RFQs and requests supplier prices
- Tracks quotes, follow-ups and reorders in the CRM
- Reads customer POs into checked draft orders
- Chases supplier confirmations and deliveries
- Assembles certificate packs and drafts CoCs
The team does
- Customer service approves orders and acknowledgements
- Buyers call at-risk suppliers and verify bank changes by phone
- Inside sales follows up quotes and reorders
Estimator or quality manager decides
- Estimators decide whether to bid and set every price
- The quality manager signs certificates and releases product
- Engineering approves revisions and technical claims
Compliance handled
Privacy, consent and safety, built in.
Confidential drawings
Files stay in the manufacturer's SharePoint, and agreed customers' drawings never go to AI steps.
Payment fraud controls
Supplier bank-detail changes are held and verified by phone, in line with IC3 guidance on verifying payment changes.
Source: www.ic3.govCertificates stay signed by people
CoCs are drafted automatically and signed by the quality manager.
Record retention for CE-marked products
Certificates for products sold in the EU are filed so they remain available for the 10-year retention period.
Source: europa.euContact data
Buyer and supplier contacts are used only for sales and purchasing, as described in the privacy notice.
Source: gdpr-info.euOutcomes
What changed for the practice
- Estimators start every RFQ from a one-page summary instead of a pile of files.
- Every quote and account sits in one pipeline, and overdue reorders reach the account owner.
- Customer service approves checked draft orders instead of keying them, and mismatches are caught before planning.
- Buyers see which deliveries are at risk against job dates before planning is affected.
- Shipments leave with complete certificate packs, signed by quality.
What we track
The measures the practice watches.
Time to quote
Time from RFQ received to quote sent.
Win rate
Quotes won by customer, part family and channel.
Order entry
Time from PO received to order posted, and mismatches caught before planning.
Supplier confirmations
Share of POs confirmed within two days and on-time delivery by supplier.
Certificate packs
Shipments leaving with a complete pack, and packs rejected by customers.
Cost estimate
What a project like this costs
-
Discovery and design
Process mapping, data flows, AI rules and the backlog for all five workflows.
$900 – $2,000
-
RFQ intake module
Capture, summaries, flags and supplier requests.
$800 – $2,000
-
CRM pipeline module
Source capture, ERP sync, follow-ups and reorder alerts.
$600 – $1,500
-
Order entry module
PO reading, ERP checks, drafts and acknowledgements.
$800 – $2,000
-
Supplier follow-up module
Requests, reply reading, risk list and bank-change hold.
$600 – $1,500
-
Certificate pack module
Matching, pack assembly and CoC drafts.
$700 – $1,800
-
Integrations
ERP, CRM, mailbox and SharePoint connections.
$300 – $500
-
Testing, UAT and launch
QA, user acceptance testing, launch and training.
$300 – $1,200
-
Total project estimate
$5,000 – $12,500
Optional monthly care after launch is quoted with your proposal. Typical range for a project of this scope: five workflows at our fixed per-workflow range. Every manufacturer gets its own fixed quote after a free call.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- n8n: Self-hosted Community edition on the manufacturer's server, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
- ERP and CRM: Each vendor's own plan.
- AI usage: Pay-per-use model fees, depending on the number and size of documents.
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
Tools we built
Free tools we built and use every day.
The Make It Flow platform
Website audits, monitoring and reports
- Website Security Scan FreeSSL, security headers, cookies and exposed file checks
- Email Deliverability Check FreeMX, SPF, DKIM, DMARC, MTA-STS and BIMI with ready DNS fixes
- SEO Audit FreeTitles, meta, headings, indexability, sitemaps and schema
- Website Monitoring Scheduled re-scans, score emails and 5-minute uptime alerts
Free website tools for practices
Services in this case study
RFQ intake & quote preparation
Every RFQ read on arrival: drawings, quantities, materials, finishes, tolerances flagged and due dates listed for the estimator, supplier prices requested for outside work and a draft quote ready to price.
From $1,000 · About 4 to 5 weeks Details
Manufacturing CRM & B2B account pipeline
RFQs, distributor and rep leads, and repeat-order accounts in one manufacturing CRM, with quote follow-ups, reorder reminders from ERP history and a weekly view of quotes won by customer and part family.
From $1,000 · About 4 weeks Details
Customer PO to sales order entry
Customer purchase orders read from email and portals into draft sales orders, checked against part revisions, prices and lead times in the ERP, with an acknowledgement sent once customer service approves.
From $1,000 · About 4 weeks Details
Supplier PO confirmations & delivery chasing
Purchase orders confirmed, late deliveries chased and supplier certificates requested automatically, with a daily list for buyers of what is at risk against job dates and any bank-detail change held for a phone check.
From $1,000 · About 4 weeks Details
Certificates of conformance & quality records
Shipment packs with CoCs, material certs and inspection reports assembled per order, nonconformance and corrective action records kept together, and calibration and maintenance dates reminded before they lapse.
From $1,000 · About 4 to 5 weeks Details
Estimator or quality manager decides
-
AI in Manufacturing: RFQs, Order Entry, Quality Docs and Maintenance LogsAutomation · 8 min read
-
RFQ to Quote Process: A Step-by-Step Workflow for ManufacturersAutomation · 8 min read
-
Manufacturing SEO: How B2B Manufacturers Get Found by BuyersSEO · 10 min read
-
How to Stop Scammers Spoofing Your Email DomainEmail Deliverability · 7 min read
-
What Are AI Agents? A Plain-English Guide for Small BusinessesAutomation · 10 min read
Free 20-minute call
Want this built for your manufacturer?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
Sources we checked
Rules and product facts on this page come from these pages, checked in November 2026. This is general information, not legal advice; confirm the rules that apply to your practice with your own adviser.
- EU Your Europe: CE marking obligations
- 21 CFR 820.10 (quality management system requirements)
- FBI IC3 PSA: Business email compromise
- GDPR Article 13
- UK PECR regulation 22
- EU AI Act, Article 50
- n8n pricing
- Business Central API v2.0: create salesOrders
- Epicor Kinetic open REST API
- SAP Business One Service Layer API reference
- Odoo External RPC API
- Katana API: creating a sales order
- Paperless Parts API
- Fulcrum: Paperless Parts integration update
- HubSpot API overview
- QuickBooks Online API: create invoices
- Google autocomplete phrasing checked for keywords (manufacturing CRM, RFQ automation, sales order automation, purchase order follow up, certificate of conformance software, AI chatbot for manufacturing, manufacturing website design)