Services for manufacturers and job shops

Manufacturing workflow automation for the office around the shop floor

Make It Flow builds automated business solutions for contract manufacturers, machine shops, fabricators and B2B product makers: a manufacturing CRM for distributors, reps and direct accounts, RFQs summarised for the estimator, customer purchase orders read into draft sales orders, supplier confirmations chased, certificates of conformance assembled for each shipment and an AI assistant that answers product and order questions from approved data. Estimators, buyers and quality managers keep every decision.

The ERP stays the source of truth

Parts, revisions, orders and stock live in Epicor, Business Central, SAP Business One, Odoo or whatever you run. We read and write only through the APIs and imports the vendor offers, and drafts wait for a person before they post.

Engineering and quality judgement stays human

Automation reads drawings and documents, lists what it found and chases what is missing. Estimators set prices, engineers approve revisions and quality managers sign certificates and close nonconformances.

Drawings and customer data protected

Customer drawings and specifications are often confidential or export-sensitive. We keep each workflow inside systems you control, limit what goes to AI providers and agree the rules with you in writing.

Services

Manufacturing process automation, from RFQ to shipment.

Each one is a focused project with a fixed quote, a written plan and a handover you own.
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... How we built it

Case Study

Case Study: Manufacturing RFQ-to-Shipment Automation

Read the full case study

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.

RFQ inbox Drawings, specs Orders inbox Customer POs ERP Parts, POs, lots n8n Five workflows AI reading RFQs, POs, replies CRM pipeline Quotes, accounts SharePoint Certs, summaries Office team Review, approve Quality manager Signs packs ERP updates Orders, dates
  • Input
  • Logic and services
  • AI step
  • Data
  • People
  • Output

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.

Platform integrations

The software you already use, connected.

Practice systems, CRMs, phones, payments and reviews, connected through documented APIs, webhooks, n8n and custom code.
All integrations

Microsoft Dynamics 365 Business Central

ERP

Customers, items, sales orders and purchase orders for order entry, CRM sync and supplier follow-up.

Business Central API v2.0 (including salesOrders).

Epicor Kinetic

ERP

Parts, quotes, orders, POs and lots.

Epicor Kinetic REST API, which exposes business objects and BAQs.

SAP Business One

ERP

Orders, items, business partners and purchase orders.

SAP Business One Service Layer (OData).

Odoo

ERP

Sales orders, purchase orders and products.

Odoo external API, available on Custom plans; confirmed per project for your version.

Katana

Manufacturing ERP

Sales orders, manufacturing orders and purchase orders for smaller manufacturers.

Katana API (developer portal).

JobBOSS²

Job shop ERP

Quotes, jobs and orders.

Connection method confirmed per project.

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 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. 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. 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. 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

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

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

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

Tech we work with

Any language, any stack.

Make It Flow delivers automated business solutions: workflows, integrations, AI assistants and the apps around them. Our team works in whatever language and stack fits the job and the systems you already run.

Automation

n8nWebhooksREST and GraphQL APIsScheduled jobs and queues

Backend

PythonPHP and LaravelNode.js and TypeScriptJava

Data

SQL (MySQL, PostgreSQL)Google Sheets and AirtableData sync and ETLReporting dashboards

Frontend and mobile

JavaScript and TypeScriptTailwind CSSJava and Kotlin for AndroidBrowser extensions

AI

Claude, Gemini and OpenAI modelsRetrieval on your own documentsModel Context Protocol (MCP)Evaluation sets

Cloud and DevOps

DockerLinux serversGitHub ActionsMonitoring and backups

FAQ

Manufacturing workflow automation answered.

Here it means software handling the repetitive office steps around production: summarising RFQs, entering customer POs as draft sales orders, chasing supplier confirmations, building certificate packs for shipments and keeping maintenance and calibration dates visible. Planning, pricing, engineering and quality decisions stay with people.

Our fixed quotes are $1,000 to $2,500 per workflow, $2,500 to $7,500 for an AI product and order assistant, and $5,000 to $15,000 for a B2B manufacturing website with RFQ upload. A connected set of five workflows usually lands between $5,000 and $12,500. ERP, n8n and AI usage are billed to you directly.

Microsoft Dynamics 365 Business Central through its API, Epicor Kinetic through its REST API, SAP Business One through the Service Layer, Katana through its API and Odoo through its external API where your plan allows, plus Paperless Parts, HubSpot, Microsoft 365 and QuickBooks Online. Systems such as JobBOSS², ProShop and Fulcrum are confirmed per project.

No, it is a service. We build workflows on n8n and the systems you already pay for, then hand them over. We do not automate machines or PLCs; this is office and data automation around production.

Yes. We work remotely with manufacturers worldwide, and we keep the paperwork side of rules such as EU CE marking documentation, GDPR and UK GDPR, and US quality system rules in view. The responsible people make the compliance calls.

A single workflow usually goes live in three to five weeks, including a shadow run on real RFQs or orders. A connected set is delivered in one-week Scrum sprints in about eight weeks.

Free 20-minute call

Show us where orders get stuck

Book a free 20-minute call. Walk us through one RFQ or one customer PO from inbox to shipment, and we will tell you plainly which steps are worth automating and give you a fixed quote for them.

Book a free 20-minute call