Estimating for building-supply dealers.
Lunica drafts the quote from the request, in your sheet, at your margins. Your estimator reviews and sends.
Sales & estimatingUpdated Oct 202620 ERPs
See it work.
Click through the steps. Fictional data; the real thing runs on your ERP.
Attached material list for the detached garage at Lot 14 Birchwood. Need pricing by Friday.
Customer, project, due date and the material list, from the estimating mailbox.
The problem.
A request for quote is an email with a material list or a set of drawings attached. The estimator reads it, finds each item in your ERP’s item file, checks cost, applies the house markup for that customer, and builds the quote in the same Excel sheet the yard has used for years. Then a revision comes in.
The desk writes over a thousand quotes a year. Most of the time goes into reading and retyping, not into the pricing decisions that win the job.
How it works.
- 1
The request becomes a card
Forwarded into the estimating mailbox or opened by hand: customer matched to the customer file, project, due date, attachments. The estimator sees it on the desk with the due date on it.
- 2
Lines are read and mapped
Items read out of the material list or taken off the drawings, mapped to the item file in your ERP, with the matches a person should check flagged. A drawing is measured into regions the estimator confirms before anything is priced.
- 3
Costed and priced
Cost from your ERP, price from your versioned markup policy by customer and category. Supplier quotes you hold are priced from where you have them. The estimator sees the margin per line, not just the total.
- 4
The quote, in your sheet
The house Excel sheet and its PDF, versioned. The estimator reviews, downloads and sends from their own mailbox, and enters it as a quote in your ERP. Revisions are a new version, not a new file.
How it connects to your ERP.
Lunica reads the item file and the customer file through its database or data warehouse, under an account that can only read: current cost, the price level and markup each account carries, and the quotes already in your ERP’s history, so a revision is priced against what went out last time. Supplier quotes you hold are read from the share or mailbox where you keep them.
Nothing lands in your ERP without a person and nothing is sent on its own. The quote is written into your own sheet and PDF; the estimator sends it from their own mailbox. It goes into your ERP as an import file where your ERP takes one, or keyed by your team from what Lunica prepared, and Lunica records the number afterwards so the pipeline and your ERP agree.
What a week looks like.
- Reading and retyping stop being the job.
- Every quote is priced on the same policy.
- Revisions keep their history.
- Pipeline, hit rate and expiring quotes in one view.
Questions
Does it send the quote?
No. It tells the estimator a quote is ready. The estimator sends it from their own mailbox.
Does it write to your ERP?
No. Lunica reads your ERP and prepares the quote. A person enters it as a quote in your ERP, and Lunica records the number afterwards.
What about takeoffs from drawings?
Drawings are measured into regions a person confirms before anything is priced.
Will it match our sheet?
It writes your sheet, not ours. The output is the Excel file your customers already recognise, plus a PDF.
Pass-through quotes from a manufacturer?
Attached and priced from the supplier’s quote on file, with its validity date tracked.
Where does it run, and what does the model see?
On one server inside your network, beside your ERP, reading through its database or data warehouse, under an account that can only read. The model sees the request, its attachments and the items it is matching, not the whole item file.
Available for.
Each version is written in that system’s own terms: its screens, its files, its codes.
Own your AI. Own your software.
Thirty minutes with the people who build it. Bring your ERP.