We actually read these.
Ideas submitted here go to the product team, not into a void. Add yours, vote on others, and comment on what matters to your business.
Talk to our Product Managers live: every other Monday, 1:00–2:00 PM ET → https://www.d-tools.com/cloud-product-office-hours
Reporting and data export today are uneven across the platform. Some lists support CSV export, others don't. There is no built-in mechanism to construct custom views, build dashboards, or run cross-module reports — so users routinely fall back to Excel or external BI tools to answer basic operational questions about their own business. The intent of the platform is to be the system of record for project, financial, and operational data, but reporting gaps push users to copy that data out and rebuild reports outside, which dates the moment anything changes.
CSV / Excel export from every list and table — accounts, projects, service calls, time entries, invoices, payments, purchase orders, items — with the columns the user is currently viewing, plus all underlying fields available as an option.
A report builder that lets users construct custom views, charts, and dashboards from a library of components (KPI cards, time-series charts, pivot tables, lists) without engineering involvement.
Cross-module reports that join entities — e.g., per-project profit and loss including change orders, technician hours, and material costs; work-on-the-books vs. billed; technician efficiency; callback rates per technician or per call type; service-contract renewal / churn.
Configurable filters, date ranges, grouping, and sorting per report.
Scheduled report delivery — automatic runs on a daily / weekly / monthly cadence with results emailed to a configured distribution list.
Save and share reports across the team (with permission controls) so everyone runs from the same definitions.
API / webhook access to the same data sets so shops with their own BI stacks can pull from the platform programmatically rather than re-entering data.
Reporting is the surface where the platform's claim of "system of record" actually gets tested. If the data lives here but users have to export it to answer business questions, the platform sits one layer below where decisions are made — and over time, decisions drift to whatever tool does support reporting. Closing the gap turns the platform into the place owners and controllers run their week from, which raises stickiness across every other module. The cross-module piece especially matters: per-project P&L, technician callback rates, service-contract renewal numbers, and similar reports are exactly the questions owners ask, and they require joins across modules that no external tool can do without re-keying.
What reports or exports do you need that don't exist today? Drop a comment with your specific scenario. The more concrete examples we collect, the better we can shape this into something useful.
