Designing a quotation builder estimators actually use
JU Estimating CRM was the second venture inside Dina Holdings. The quotation builder is the surface our users live in for hours every day. Here are the design decisions that took it from a forgettable tool to one estimators ask to keep open when they switch tasks.
Decision one. Side-by-side form and live A4 preview
The single most-requested change from estimators using off-the-shelf CRMs is "show me what the PDF will look like as I type." Most CRMs treat the quote as a print job. The estimator types into form fields, hits export, and only then sees whether the layout broke. This is the wrong loop. We rebuilt it as a side-by-side. Form on the left, live A4 preview on the right, every keystroke rendering into the PDF that will ship. The PDF and the preview are the same document. There is no surprise on export.
Decision two. Section numbers belong in the database, not on the page
Off-the-shelf quotation tools print 03, 04, 05 next to every heading because the database stores them that way. Estimators do not want those numbers in front of the client. They want the document to read like a proposal. We removed the section numbers from the rendered output entirely. The data model still uses them for ordering and reference. The client never sees them.
Decision three. Every status change captures a remark
The most consequential field in a quotation pipeline is not the price. It is the reason a quote was disapproved. Generic CRMs let an estimator drag a card from Sent to Disapproved with one click. The reason is lost forever. We prompt for a remark on every status change. No remark, no status change. The result is a years-long history of why bids were lost, broken down by client, by GC, by trade. That history is the most valuable analytical surface in the product.
Decision four. The logo never stretches
This sounds trivial. It is not. Every estimator we interviewed had been embarrassed by a stretched logo on a sent quote at least once. Off-the-shelf tools place the logo in a flex container that distorts on tall logos. We containerise the logo in a true square box that always preserves aspect ratio. Boring engineering. Big trust impact.
Decision five. PDF export is true A4, not "approximately"
Most browser-side PDF exports use html2canvas plus a default page size. The result is close to A4 and off by a millimeter or two, enough that the document looks wrong when stacked next to a real A4 proposal. We export at 595.28 by 841.89 points exactly, the W3C definition of A4. The output stacks cleanly in any client folder, on any printer, in any country that uses A4.
Decision six. New versus old client breakdown is a first-class chart
Estimating firms grow by retaining clients. The dashboards in most CRMs show new lead volume but never the more useful split, which is how many quotations came from clients you have worked with before. We computed and rendered that split as a first-class chart, broken down by clients, quotations, projects, approved and disapproved counts, and lifetime revenue. The chart drives a different operating conversation than the generic deal pipeline ever did.
The right chart changes the operating conversation.
Decision seven. Activity log filters on what users actually care about
The activity log on a quotation tool is usually a compliance feature. We made it a working feature. Filters on date range, entity type, and action mean an estimator can ask "what did my team do on this client last quarter" and get an answer in two clicks. Underwriters and auditors who later see the log conclude, correctly, that the firm operates with discipline.
What we deliberately left out
We did not build native messaging. Estimators have email. We did not build a meeting scheduler. Estimators have calendars. We did not build an e-sign flow. Estimators use whatever the GC requires. Adding those features would have diluted the product and increased the surface area without changing the work that matters.
Why this is the operating philosophy of Dina Holdings
Every venture in our portfolio is designed to take the work of one buyer seriously. JU Estimating CRM is the working example of what that looks like applied to one product. Estimator does the same on takeoff. Pixel Architecture does the same on contractor websites. Pixel Labs Studio does the same on the shared infrastructure. The discipline is the same. The buyer is different.
JU Estimating CRM is licensable to other estimating firms with custom branding and managed hosting. Open the venture page.