Pipeline
Every opportunity, its stage, and what's gone quiet.
HubSpot, Pipedrive
Bespoke · built to work the way you already do
iTec HQ replaces the CRM, the job book, the ticketing inbox, the e-sign tool and the spreadsheets with one platform — built around how your business already works, then run for you.
You don't bend your business to fit the software. It's designed to work around you — not the other way around — so your team stays fast and nothing gets slower the day it goes live.
The problem
Most businesses we meet are paying for five or six tools that each solve one problem and create a seventh: nothing joins up. The client who logged a ticket this morning is a different record from the client on the quote, the contract and the invoice.
CRM
Deals live here, but the client's job history doesn't
Job / ticket system
Work lives here, but not what it's worth
E-sign tool
Signed contracts, with renewal dates nobody watches
Email marketing
A contact list that drifts out of sync from day one
Accounting
The only place profit is visible — a month late
Spreadsheets
The glue holding the other five together
6
logins for one client record
The same customer, entered by hand into every system, drifting apart from the day it's created.
1 month
before you know if a job made money
Job-level margin only appears once the bookkeeper reconciles — too late to change anything.
Nobody
owns the renewal date
Contracts sit in an e-sign tool that never tells anyone they're about to lapse.
What it is
One login, one client record, one set of numbers. Every module reads and writes to the same data, so a ticket, a job, a quote and an invoice all point at the same customer.
Every opportunity, its stage, and what's gone quiet.
HubSpot, Pipedrive
Dispatch, on-site photos, parts, hours and the signed report.
ServiceM8, simPRO
Inbound requests on an SLA clock, replying from your real address.
Zendesk, Freshdesk
The single client record everything else hangs off.
HubSpot CRM
Generate, send, sign and track to renewal.
DocuSign, PandaDoc
Cash, revenue, margin and who owes you — read nightly.
Xero dashboards, Fathom
Segmented email built from live client data.
Mailchimp
What's on the shelf, on the van, and below reorder.
Unleashed
Social publishing and the reach it actually earned.
Hootsuite, Buffer
Every ad network's spend against revenue it produced.
Four ad dashboards
Who's finding you, how, and what they do next.
GA4 tabs
The one screen the owner opens each morning.
Status spreadsheets
Per-module permissions on your existing logins.
Shared logins
A module you don't run doesn't appear in the nav and isn't billed. A five-van electrical contractor and a 34-person accounting practice run the same platform without paying for each other's features.
Your stages, your terminology, your reporting — built to match how your team already operates. A machinery dealer books a service job against a machine; an accountant opens a matter for a client. Nobody changes their process to suit the software.
Microsoft 365 or Google accounts. No new passwords to issue, and access follows the role — technicians see jobs and stock, never margin.
See it working
Every screen below is a real capture from the live demo — the same build a client uses, with invented data in it. Nothing here is an illustration of what it might look like.


Captured at each device's real viewport width. Field staff get the phone layout with a bottom bar; the office gets the full rail. Same data, same records, same login.

Finance
Cash, revenue, margin and recurring revenue read from your accounting system nightly — with its own history, so the trend survives even when the source only shows today. Overdue invoices come with a one-click chase.

Field Service
Dispatch through to invoiced. Technicians capture photos, parts and hours on site; the completion report is generated from that record rather than typed up again afterwards.
Industries
These are builds we've already done. The demo runs all four side by side — flip between them and watch the records, the language and the reporting change.
Contracted SLAs, recurring revenue, and a helpdesk that is the whole product.
Renewal dates and per-client profitability stop living in someone's calendar and a spreadsheet.
Core modules
Capital equipment cycles that run 6–18 months, against an installed fleet under warranty.
A call about a serial number resolves instantly — machine, service history and warranty on one record.
Core modules
High job volume, crews on the road, and quotes that go cold if nobody chases them.
Job cards, site photos and van stock come off paper. Job-level margin is visible inside the month.
Core modules
Engagements, matters and a compliance calendar that drives most of the year.
WIP stops being invisible until month end, and engagement letters get re-signed on time.
Core modules
Not one of these four? That's normal. The four in the demo are the ones we've built most often — the platform isn't limited to them, and your build will have something specific to your trade.
Client story
An Australian machinery business — supplying, commissioning and servicing aluminium and PVC fabrication machinery, with field service to an installed base across NSW and nationally.
Fason ran their sales on HubSpot and their service work largely on email and paper. We scoped their build, replaced HubSpot outright rather than plugging into it, migrated their contacts, deals and notes across, and now run the platform for them. Their team works in it daily — reps in the pipeline, technicians in service.
Fason GroupReplaced
HubSpot
Retired at cutover, not plugged into. Contacts, deals and notes migrated across.
Modules they run
What they don't run
Finance
Fason didn't need it, so it was never built and it isn't billed. Their accounting stays where it was.
“We're really happy with it. It's tailor-made for what we actually do, and it's going to make us far more efficient.”
How it works
This isn't software you buy and then spend six months configuring. We scope it against how you actually operate, build it around that, move your data across and keep running it — typically two to four weeks from first conversation to switch-over.
2–3 days
We sit with the people doing the work — not just the owner — and map what actually happens. Which systems are load-bearing, which are habit, and what breaks when someone's away. You get a written scope with the module set and what each one replaces.
1–3 weeks
We build your instance: your modules, your terminology, your stages and your reporting. You see it working on real screens as it goes, not at the end — so you tell us what's wrong while it's still cheap to change.
2–4 days
Clients, contacts, open jobs, contracts and history come across from whatever they're in now — including the spreadsheets. We run both systems in parallel until you're confident, then switch the old ones off.
Ongoing
We host it, back it up, monitor it and keep building. New module, new report, new integration — it's the same team who built it, not a support queue in another timezone.
Security, privacy & resilience
Every module runs on one platform, which means one place your client data lives — so how it is secured, where it sits and what happens when something breaks are design decisions, not afterthoughts.
The eight mitigation strategies are built into the platform's design — patching, application control, MFA, restricted admin privileges and backups — not bolted on after.
Built to the Australian Privacy Principles: collection limits, access and correction rights, and a defined retention position on every record type.
Logging and alerting designed so an incident can actually be assessed inside the 30-day window the scheme requires.
Hosted in Sydney. Your data does not leave the country, and you can export all of it at any time in a format you can use.
These are the standards the platform is built to, not certifications held. We'll walk your IT people or auditor through exactly how each one is implemented.
Sign-in runs through your own Microsoft 365 or Google tenant, so your MFA and conditional access policies apply — we never issue a second set of credentials. Access is per module: a technician sees jobs and stock and never sees margin.
Point-in-time backups with a tested restore path, not a backup nobody has ever restored from. Infrastructure is defined in code, so the platform can be rebuilt rather than repaired.
Client data stays in one system instead of being copied into five. Marketing email carries recorded consent, sender identification, a working unsubscribe and a suppression list, as the Spam Act requires.
Xero, Microsoft 365, Google and your ad accounts connect through scoped, revocable credentials. We read what the platform needs and nothing else.
Why us
iTec HQ was designed and built by former corporate IT executives with more than twenty years in the technology industry — people who have run resilience, security and integration at a scale where getting them wrong has consequences. That is why disaster recovery, security, privacy and integration sit at the front of the design rather than being added once something goes wrong.
iTec HQ started as the system we built to run iTec Help — the helpdesk our engineers work in, the agreements our clients sign, the numbers we manage against. Fason Group was the first client we built it for.
The people who scope your build are the people who keep it running. Nothing gets handed to an offshore support queue.
Xero, Microsoft 365, Google, your ad accounts. We replace the tools that aren't earning their keep, not the ones that are.
You're not charged more for adding the apprentice. Scope is scope.
Questions
Two to four weeks for most builds, from the first conversation to running on it. Longer if your operation is genuinely complex — more modules, more entities, or data that needs untangling before it can move. We'll tell you which you are at the scoping call rather than discovering it halfway through. Either way you see working screens as we go, so you're never waiting to find out what you're getting.
We migrate it. Clients, contacts, open jobs, contracts and history come across, including whatever lives in spreadsheets. We run old and new in parallel until you're confident nothing was lost, then decommission the old tools.
You own your data outright and can export all of it at any time. The platform itself is licensed and maintained by us — that's what keeps it patched, hosted and improving rather than frozen the day the build finished.
Hosted in Sydney, with your data staying in Australia. The build follows the ACSC Essential Eight mitigation strategies and the Australian Privacy Principles under the Privacy Act 1988. Sign-in runs through your own Microsoft 365 or Google tenant, so your existing MFA and conditional access policies apply — we don't issue a second set of credentials. Access is per module, so a technician sees jobs and stock and never sees margin. Backups are point-in-time with a tested restore path, and infrastructure is defined in code so the platform can be rebuilt rather than repaired. To be precise: these are standards we build to, not certifications we hold — happy to walk your IT people through the implementation.
Bespoke. The demo shows four builds we've done, not four templates you pick from — the modules, stages, terminology and reporting are built around how your business already runs. That's the whole point: the system works around you rather than making you work around it, so your team stays as quick as they are today instead of slowing down to feed a tool.
That's the normal case. The demo shows four industries we've already built for; your business will have something specific to it. Custom modules and workflows are part of the build, not a change request afterwards.
No. Finance reads from Xero on a schedule rather than replacing it. We only replace tools that aren't earning their keep — usually the CRM, the job book, the e-sign tool and the marketing platform.
As a build plus an ongoing platform fee, sized to the module set and the migration — not per user, so growing your team doesn't grow the bill. We'll give you a fixed number after the scoping call, before you commit to anything.
Next step
Tell us what you're running now and where it hurts. If iTec HQ isn't the right answer we'll say so — we'd rather tell you on a call than halfway through a build.
Prefer email? hello@itechelp.com.au