We build custom software for manufacturers and distributors. Usually the first piece is quoting: pulling the specs, the pricing and the past jobs together so your team can send an accurate quote the same day.
Redbroch has done hands-on work inside a manufacturer, sitting with the people who quote, take orders and answer the phone. The problems below are the ones that came up again and again.
“Can you quote 250 of the mounting bracket from last spring, but in stainless and with a second hole pattern?”
Closest past jobJob 2214, same bracket in mild steel
ChangeMaterial to 304 stainless, add one punch pattern
PricingCurrent price list and material cost
Lead time3 weeks, from current shop load
SourcesJob 2214Price listMaterial cost sheet
Review and approveEdit
Illustration with made-up data. A person approves every quote.
Sound familiar?
The work is there. The answer is scattered.
Most growing manufacturers and distributors run on an ERP, a shared inbox, a folder of spreadsheets and a few people who remember everything else.
01
Custom quotes take days.
Anything off standard means digging up a similar job, checking material and labor, asking around for the latest price and building the quote by hand. Meanwhile the customer is getting numbers from someone else.
02
One estimator knows how to price it.
One estimator carries years of judgment about what a job takes. When they are out, quotes wait. When they retire, a lot of that judgment leaves with them.
03
Specs and pricing are everywhere.
Specs in PDFs, pricing in a spreadsheet, the last order in the ERP, the exception in someone’s email. Sales and the floor spend the day asking each other where things are.
Built around what you already run
Your ERP
Shared inboxes
Spreadsheets and price lists
Spec sheets and drawings
Shared drives
What we build
Quotes and orders
Quoting assistant
A first draft of the quote, ready for a person to approve
It reads the request, finds similar past jobs, applies your price lists and costing rules, and drafts a quote with its working shown. Your estimator reviews, adjusts and sends. Nothing goes to a customer without a person signing off.
Order intake
Emailed POs into the ERP without retyping
Purchase orders arrive as PDFs and email bodies in every format. The tool pulls the lines, matches part numbers and customers, and stages the order in your ERP for review. Anything that does not match is held and flagged.
Answers and visibility
Cited assistant
Answers about specs, SOPs and past jobs, with the source attached
Sales and floor staff ask in plain language and get an answer that links to the spec sheet, procedure or job record it came from. People can check the answer in one click, and the knowledge stops living in one inbox.
Reporting
The numbers you ask for every week, pulled from the ERP
Quote turnaround, open orders, margins by customer or product family, backlog. Pulled on a schedule from the systems that already hold it, so nobody rebuilds the same spreadsheet every Monday.
These are examples of what an engagement can produce. Which one comes first depends on where the work actually piles up in your business.
How an engagement works
Small first. Then expand.
Each step is useful on its own, and you decide whether to take the next one.
Short discovery
We sit with the people who quote, enter orders and answer questions. We look at the ERP, the inbox and the spreadsheets as they really get used, and come back with a short list of what is worth building and what is not.
A demonstration on your own sample
We build a working demonstration on a small sample of your quotes, orders or spec sheets that you choose to share, or on synthetic data shaped like them. You see it handle your kind of work before committing to anything larger.
A small first build
One tool, scoped tightly, running in your environment for one team. We stay with the people using it while it settles in and fix what the first weeks turn up.
Expand when it earns it
Once the first build is in use, we agree on the next one: another product line, another team or another process. Scope and price are agreed before the work begins.
What you can expect from us
People approve. Your data stays yours.
A person approves anything that leaves the building.
Quotes, order confirmations and customer replies are drafts until someone on your team approves them. The approval step is part of the design from the first day.
Your data stays yours.
We agree on what information is needed, who can see it, where it may be processed and how it is retained and deleted before we use any of it. Pricing and customer lists are treated as the sensitive records they are.
It works with the systems you have.
We start with your ERP, your email and the files your team already uses. Where another service or local hardware would help, we agree on the design and access first.
You can see how it got the answer.
A drafted quote shows which past jobs and price lists it used. An answer links to the document it came from. Anything that cannot be traced gets flagged for a person.
Start a conversation
Tell us where the quotes get stuck.
Call, text or email Samuel directly. A first conversation is half an hour, and you do not need a technical specification to start one.