What Dill users actually want

One user processes 25-30 lien waivers per day and explicitly states that Dill's speed advantage over Textura makes a big difference at that volume. Current workflow reduced per-waiver time from 5 minutes to 2 minutes (60% improvement), but that still translates to 50-60 minutes of daily waiver processing for high-volume users. If a user can review and approve 10 waivers in a single batch action instead of individually clicking through 10 separate flows, you could cut that time in half again.

Credit teams report that sales reps used to constantly ask where is this application, and applications stalled because reps moved on to the next opportunity without visibility into draft status. Dill solved half the problem by providing application visibility, but it's still a pull model — reps have to remember to check the portal. The credit team can now proactively identify drafts, but that still requires them to reach out to sales.

Implementation takes 2-4 weeks, and ERP integration is described as critical to improving customer payment experience. You support major systems like Epicor Prophet 21, QuickBooks Desktop, and Advantive, but each new customer on a custom or niche ERP likely requires bespoke integration work. That creates deployment friction and delays time-to-value, which is a competitive disadvantage when competitors can deploy faster.

Users describe waiver signing as instant — it takes 2 seconds, just click and go straight to the waiver. But the evidence doesn't indicate whether those users are signing from a desktop at the office or from a mobile device on a job site. Construction contractors are often in the field, and if the signing experience isn't mobile-optimized, you're creating friction for the exact users Dill is trying to serve.

Sensitive data (SSNs, EINs) was previously accessible to multiple employees across branches with no centralized control. Dill now centralizes credit applications, but the evidence doesn't confirm whether role-based permissions or audit logging are in place to prevent unauthorized access. This is a compliance and trust issue — if a data breach occurs or an employee misuses sensitive data, Dill and its customers are exposed.

Users process 25-30 waivers per day, and waiver processing is described as instantaneous with pre-populated forms eliminating manual data entry. But the evidence suggests each waiver request still requires some setup — selecting the customer, specifying terms, attaching invoice details. For repeat customers, that setup is redundant.