.png&w=384&q=75){kind=small}
“When your marketing team exports data to Google Sheets for reporting instead of using CRM dashboards, it means they don't trust the data. Shadow spreadsheets are the most reliable indicator of a broken platform.”
On diagnosing broken CRM implementations
Nick Hugh
Founder, AI Expert & Fractional CTO, Marshall Tech
Nick Hugh, AI Expert & Fractional CTO at Marshall Tech, Sydney
Last updated:
Related resources
Move from this quote into the person, proof, and longer explanation behind it.
Insight
RevOps Explained: What Revenue Operations Actually Means for Your Business
Revenue Operations (RevOps) aligns sales, marketing, and customer success under a single operational framework. The goal is eliminating data silos, automating handoffs, and creating a single source of truth for revenue metrics. Companies with mature RevOps see 10–20% faster revenue growth and 30% lower customer acquisition costs.
Updated 26 Feb 2026
Open resourceInsight
Data Hygiene Guide: Getting Your Data AI-Ready
Data hygiene is the practice of ensuring your business data is accurate, consistent, complete, and accessible. It's the prerequisite for AI implementation, reliable automation, and trustworthy reporting. Businesses with poor data hygiene waste 20–30% of employee time on manual data wrangling and get unreliable results from any AI or automation tools they deploy.
Updated 26 Feb 2026
Open resourceExpert
Nick Hugh
Nick Hugh, AI Expert & Fractional CTO at Marshall Tech, Sydney
Updated 9 Apr 2026
Open resourceInsight
5 Signs Your CRM Needs a Rescue
The five signs your CRM needs rescue: workflows failing silently, pipeline reporting you can't trust, lead response times exceeding 24 hours, team members maintaining shadow spreadsheets, and three or more failed attempts to fix the same issues. If any two apply, a 3-week rescue sprint will save months of accumulated damage.
Updated 26 Feb 2026
Open resourceCase study
True Protein: CRM Rescue & Revenue Operations Rebuild
True Protein's CRM had broken workflows, unreliable pipeline reporting, and 48-hour lead response times. Marshall Tech completed a 3-week rescue sprint that rebuilt lifecycle stages, fixed automation with custom APIs, and restored accurate forecasting with significant operational cost reduction.
Updated 26 Feb 2026
Open resourceInsight
Platform Migration Checklist: How to Switch Without Downtime
A successful platform migration requires four phases: discovery (2 weeks), parallel build (4–8 weeks), controlled cutover (1 week), and stabilisation (2 weeks). The key to zero-downtime migration is running both systems in parallel, with a rollback plan at every stage. Most migration failures come from skipping the parallel phase.
Updated 26 Feb 2026
Open resource