Real pilot results
Future case studies will state the fleet, workflow, time window, and measured result.
Dump Trucky is an early-access product. This page separates what is available in the current build from what is being developed, coming soon, or planned.
Status labels describe the current early-access roadmap. They do not promise a final release date or imply that a planned integration works with every fleet.
| Capability | Status | What that means |
|---|---|---|
| Dispatch, jobs, and loads | Available | Core records and load-centered execution exist in the current build. |
| Sources, materials, and customers | Available | Operational master data supports jobs, quoting, and load history. |
| Quick Quote / Quote Lite | Available | Whole-cycle operational pricing and source comparison inside Core. |
| Driver workflow and offline queue | Available | Focused field events, evidence capture, safe retry, and sync architecture. |
| Ticket photo and actual tons | Available | Capture and load linking are available; automated reading is still developing. |
| Real-world load exceptions | Available | Rejected, returned, transferred, disposed, partial, and corrected outcomes preserve history. |
| Actual versus estimated | Available | Planned and field results can be compared at the job and load level. |
| Hauling CRM | In development | Leads, opportunities, follow-up, pipeline, and job handoff are being built. |
| SMS tracking and customer proof | In development | Notification and customer-safe delivery experiences are being developed. |
| Ask Dispatch and deeper intelligence | In development | Explainable answers will sit on trusted deterministic operational metrics. |
| Ticket reading and automated auditing | In development | Photo reading, matching, and exception detection build on captured ticket records. |
| Quote Pro | Coming soon | CRM proposals will reuse Core pricing and add commercial presentation and acceptance. |
| Formal invoicing layer | Planned | A future commercial layer; Dump Trucky is not currently positioned as accounting software. |
| Mixed-fleet telematics | Planned | Flexible GPS, geofence, payload, fuel, and external-hardware signals where available. |
| Predictive maintenance | Planned | Future analysis depends on reliable equipment and telematics history. |
The answers below reflect the current architecture and early-access direction without inventing integrations, certifications, or final pricing.
Yes. Core is intended to help an owner-operator quote the whole cycle, organize loads, capture tickets, prove delivery, and understand profit without building a large office process.
Yes. The load-centered model supports multiple trucks and drivers, assignment protection, dispatch visibility, tickets, role separation, and an audit trail as the fleet grows.
The driver uses a focused mobile experience. The current approach is phone-friendly and offline-aware; final distribution and installation details will be set during rollout.
Driver events and evidence can queue locally. Safe retry and idempotent event handling are designed to prevent reconnects from creating duplicate deliveries, tickets, or events. Dispatch can see stale GPS age.
Customer-safe SMS tracking is in development. The planned flow provides status, ETA, a limited live location, ticket, tonnage, photos, and proof for only that customer's active delivery—without an app or login.
Yes, but available signals vary. Older trucks can use a driver's phone, standalone GPS, geofencing, external hardware, and available payload or air-suspension signals. Universal plug-and-play telematics is not promised.
No. It is the operational source of truth for quoting, loads, tickets, delivery evidence, and job economics. Formal accounting remains separate; future integrations or exports may support the handoff.
Payment processing is not part of the current early-access scope. No payment capability or final commercial terms are being claimed on this site.
Yes. Core stores the sources and materials relevant to your operation, along with pricing and operating assumptions used by jobs and Quick Quote.
Yes. Quick Quote is designed around load count, quoted payload, source, route cycle, costs, market boundaries, contribution, and truck-hour economics.
Yes. Ticket capture can record actual tonnage and associate it with the job, load, truck, driver, source, material, and customer.
Hauling and material delivery remain the core. The CRM can also capture adjacent driveway, pad, grading, or other site-work opportunities, and future Quote Pro can present optional scope.
Quote Lite—also called Quick Quote—is fast operational pricing inside Core. It answers what a hauling job should cost and make based on the whole load cycle.
Quote Pro is a coming-soon CRM layer for line items, proposals, options, revisions, scope, exclusions, terms, attachments, expiration, history, and acceptance. It will reuse Core pricing rather than become a second pricing engine.
The role and permission architecture is intended to keep owner financial visibility separate unless the owner grants access. Driver and customer views should not expose pricing or profit.
No. CRM manages the commercial path from lead through accepted work. Core manages jobs, loads, trucks, drivers, sources, execution, and tickets. Accepted work hands off into dispatch.
Start by describing fleet size, primary work, current dispatch method, and the biggest operational pain. The initial fit conversation determines which current capabilities match the operation and which roadmap items still matter.
Customer logos, testimonials, user counts, revenue claims, percentage savings, and case studies belong here only after they are real and approved.
Future case studies will state the fleet, workflow, time window, and measured result.
No private source, customer, ticket, or pricing data becomes marketing content without approval.
Available, in development, coming soon, and planned remain visibly different.
The fit conversation starts with what currently lives in texts, paper, spreadsheets, whiteboards, or another system.