16 June 2026 · 9 min read
Off-the-shelf CRMs break when your job lifecycle, quoting, and field ops do not fit SaaS defaults. When Brisbane service businesses should configure HubSpot or Salesforce, when to build on the Spine, and when spreadsheets are honestly cheaper.
Custom CRM searches in Brisbane usually mean: our job workflow is not linear, we quote weird bundles, contractors need a portal, or finance needs job costing that SaaS cannot flex to without six-figure Salesforce.
Three honest options: configure a platform, build a thin custom layer on a stable spine, or keep spreadsheets until pain exceeds budget.
Standard lead → quote → job → invoice with minor custom fields.
Team will adopt HubSpot, Zoho, or Dynamics if you enforce data entry.
Integrations are Zapier-simple — no multi-tenant contractor portals.
Job is the centre: enquiries, tasks, documents, communications, and invoices must share one workspace ID.
Contractor or customer portals with approval gates and audit.
Industry modules (events, facilities, trades packs) must attach without re-platforming yearly.
North Ark builds on the Spine operating model — CRM that feeds operations, not a disconnected pipeline view.
Thin MVP on existing spine patterns: 6–12 weeks for coordinated CRM, portal, and core workflows.
Salesforce-scale configure projects: often $80k–$200k+ and still fight adoption.
Spreadsheets: $0 until error cost exceeds build — usually when headcount crosses ~15 ops staff.
Who owns product decisions weekly — not just IT?
What job states must never be skipped (compliance, deposits, SWMS)?
Which integrations are must-have day one vs phase two?
Will MSP host BAU while product evolves — or do you need a long-term build partner?
