What do you like best about SmartSuite?
SmartSuite’s greatest strength is its rare combination of enterprise-grade database architecture and a clean, modern UI/UX that makes adoption across multidisciplinary teams (from structural engineers to procurement and site installers) genuinely effortless.
Coming from a complex manufacturing, tensile fabric, and structural steel workflow environment, a few capabilities stand out for us.
Relational Power & Flexibility: Unlike more rigid traditional PM tools, SmartSuite lets us model intricate, cascading dependencies across engineering design approvals, raw material procurement, international shipping containers, and workshop fabrication stages without feeling boxed in. Linked records, rollups, and formula fields provide a strong relational backbone that feels closer to a custom-built enterprise app, while still keeping the agility of a no-code platform.
API & Automation Ecosystem: When native automations aren’t enough, SmartSuite’s robust API makes external integrations straightforward. We use webhooks to trigger GitHub Actions workflows, compile complex multi-app data, and auto-generate client-ready Gantt charts and fabrication packages.
Performance with Scale: Even while managing thousands of active tasks, material batch records, and complex scheduling dependencies across multiple international sites, the platform stays quick and responsive.
ROI & Customization: It effectively bridges the gap between high-end ERPs and simple task managers. We were able to replace multiple fragmented tools with a single centralized workspace, which drastically reduced administrative overhead and gave management real-time visibility into project health, workshop ETAs, and inventory allocations. Review collected by and hosted on G2.com.
What do you dislike about SmartSuite?
While SmartSuite is phenomenal for core relational data structure and workflow management, it has a few limitations when dealing with complex, multi-project engineering and construction scheduling:
Rigid Native Gantt & Scheduling Constraints: The native Gantt chart struggles when handling multi-project environments within a single table—auto-scheduling across multiple distinct projects often causes cascading conflicts. Furthermore, native task durations cannot easily exclude weekends or non-working days out-of-the-box without complex formula workarounds.
Limited Native Reporting & Exporting: Unlike dedicated tools like MS Project, exporting client-ready or internal fabrication Gantt charts natively doesn't offer the granular visual formatting required for formal engineering submittals.
Workaround Required for Advanced Visuals: Because native exports fell short for our structural steel and tensile fabric workflows, we had to bridge the gap by building custom backend Python/Plotly scripts triggered via webhooks to auto-generate the exact vector PDF schedules and WBS diagrams we needed.
Aside from these advanced scheduling and custom reporting hurdles, the platform's flexibility far outweighs the learning curve. Review collected by and hosted on G2.com.