Support Fusion

Smart integration platform connecting IT tools for MSPs and system integrators to automate ticket sync and reporting.

Website: https://suppfusion.com/

Cover Block

PUBLIC

Field Value
Name Support Fusion
Tagline Smart integration platform connecting IT tools for MSPs and system integrators to automate ticket sync and reporting
Headquarters Melbourne, Australia
Founded 2025
Stage Pre-Seed
Business Model SaaS
Industry IT Services Software / MSP Tooling
Technology Type Software (Non-AI)
Geography Oceania (expanding to North America and UK)
Growth Profile Venture Scale
Founding Team Co-Founders (2)
Funding Label Pre-Seed
Total Disclosed ~AUD $1,000,000

Links

PUBLIC

Executive Summary

PUBLIC

Support Fusion is a Melbourne-based integration platform that automates ticket and operational-data synchronization between the ITSM tools used by enterprises (ServiceNow, Jira, Zendesk) and the PSA tools used by managed service providers (ConnectWise, Autotask, HaloPSA), addressing a rekeying problem that has persisted in co-managed IT environments for over a decade [Crunchbase, 2025] [usehalo.com, 2026]. The company was founded in mid-2025 by brothers Greg and Steve Rudakov and went live publicly in July 2025 [Startup Daily, mid-2025] [suppfusion.com, July 2025]. Its differentiation rests on bi-directional syncing of tickets, statuses, comments, and attachments across a purpose-built MSP-to-enterprise topology, rather than the general-purpose workflow automation offered by horizontal tools [SourceForge, 2026]. The founding team pairs Steve Rudakov in the CTO seat with Greg Rudakov on the commercial side, and the company is actively hiring a founding engineer in Melbourne and a customer success lead on the US east coast [Stephen Rudakov LinkedIn, 2026] [ARN, 2026]. Support Fusion has raised approximately AUD $1 million in pre-seed capital led by Func Ventures and Exhort Ventures, with continued participation from Antler and a syndicate of operator angels including Toby Alcock and Ryan Spillane [techpartner.news, 2025]. Over the next 12 to 18 months the watch items are connector breadth (Syncro API support shipped recently), the conversion of MSP design partners into paying multi-tenant deployments, and whether the planned US and UK expansion produces the offshore revenue mix the round was sized for [suppfusion.com, 2026] [ARN, 2026]. The bet is narrow and concrete: own the ticket-sync layer between MSPs and their enterprise customers before a horizontal automation vendor decides the niche is worth a dedicated SKU.

Data Accuracy: GREEN -- Confirmed by Crunchbase, Startup Daily, techpartner.news, and the company's own site.

Taxonomy Snapshot

Axis Value
Stage Pre-Seed
Business Model SaaS (integration platform)
Industry / Vertical MSP tooling / IT service management
Technology Type Software (Non-AI)
Geography Headquartered Oceania; selling into US, UK, AU
Growth Profile Venture Scale
Founding Team Co-Founders (2), brothers
Funding ~AUD $1.0M pre-seed, led by Func Ventures and Exhort Ventures

Company Overview

PUBLIC

Support Fusion is an Australian software company built around a single, well-defined pain point: when an enterprise IT team co-manages infrastructure with one or more MSPs, support tickets and operational records have to be rekeyed by hand between the enterprise's ITSM platform and each MSP's PSA tool, producing duplicate work, drift in ticket status, and misaligned SLAs [Crunchbase, 2025]. The company was founded in mid-2025 by brothers Greg and Steve Rudakov and is headquartered in Melbourne [Startup Daily, mid-2025] [techpartner.news, 2025].

The public timeline is short but coherent. The company went live and announced its launch with backing from Antler in July 2025 [techpartner.news, 2025] [suppfusion.com, July 2025]. A AUD $1 million pre-seed round led by Func Ventures and Exhort Ventures, with continued support from Antler and several named angels, was reported later in 2025 [techpartner.news, 2025]. Product coverage has been expanding connector by connector, with Syncro API support announced as one of the more recent additions [suppfusion.com, 2026]. The company also appears as a named integration partner in HaloPSA's partner directory, which is a signal of at least one anchor PSA vendor treating Support Fusion as a reference integration rather than a competitor [usehalo.com, 2026].

Legal entity details beyond the Melbourne headquarters are not publicly disclosed in the captured sources. The company's near-term operational focus, per its own statements to Australian trade press, is on hiring engineering and customer success talent and on offshore expansion into the US and UK markets [ARN, 2026].

Data Accuracy: GREEN -- Confirmed by Startup Daily, techpartner.news, and the company website.

Product and Technology

MIXED

Support Fusion sells a hosted integration platform whose stated job is to keep tickets and the data attached to them in lockstep across two normally disconnected sides of an IT delivery relationship. On the enterprise side it connects to ITSM systems including ServiceNow, Jira, and Zendesk; on the MSP side it connects to PSA platforms including ConnectWise, Autotask, and HaloPSA, with Syncro added as a more recent connector [SourceForge, 2026] [suppfusion.com, 2026]. The synchronization is described as bi-directional and covers tickets, statuses, comments, and attachments, which is the field-level coverage MSPs typically need to avoid manual reconciliation at the end of each shift [SourceForge, 2026].

The company frames the product as purpose-built for the MSP-to-enterprise topology rather than as a general workflow automation tool, and that framing matters for how the product is sold [usehalo.com, 2026]. General-purpose automation platforms (Zapier, Make) require a customer to design, maintain, and version their own workflows; vertical MSP automation platforms (Rewst) sit on the MSP side of the relationship. Support Fusion's positioning is that the integration itself, including field mapping, SLA reconciliation, and attachment passthrough, is the productized unit of value rather than a recipe the customer assembles [Crunchbase, 2025] [usehalo.com, 2026]. Pricing is published on the company website, which is unusual for early-stage B2B integration tools and suggests a self-serve or low-touch motion at the entry tier [suppfusion.com, 2026].

The underlying technology stack is not disclosed in the captured sources, and the company is hiring a founding engineer to work directly with the CTO in Melbourne, which suggests the engineering organization is still being assembled [Stephen Rudakov LinkedIn, 2026]. No AI or ML claims appear in the public material reviewed; the company is categorized internally as Software (Non-AI), and the product story is one of integrations and reliability rather than model-driven automation.

Data Accuracy: GREEN -- Confirmed by suppfusion.com, SourceForge, and HaloPSA's partner page.

Market Research and Opportunity

PUBLIC

The market that matters here is the operational seam between enterprise IT departments and the MSPs they outsource pieces of their estate to, a seam that has grown wider as both sides have standardized on different software stacks. Co-managed IT, in which an enterprise retains an internal service desk and contracts one or more MSPs to handle defined towers (endpoint, network, cloud, security operations), is now a mainstream delivery model, and ServiceNow on one side and ConnectWise or HaloPSA on the other have become typical anchor systems [Crunchbase, 2025]. The cited evidence does not include a named third-party TAM figure for the MSP-to-enterprise integration sub-segment specifically, so any sizing here should be read as analogous rather than authoritative.

The demand drivers the public commentary surfaces are concrete. First, MSP consolidation and private-equity rollups have produced larger MSPs with multiple PSA tenants and more enterprise-grade customers, which makes integration a board-level operations problem rather than a technician's spreadsheet [Startup Daily, mid-2025]. Second, enterprises increasingly require their MSPs to update tickets in the enterprise's own ITSM of record (typically ServiceNow) for audit and SLA reporting, which forces double entry unless an integration layer exists [Crunchbase, 2025]. Third, the PSA vendor ecosystem itself is opening more APIs (Syncro being a recent example), which both lowers the cost of building Support Fusion connectors and signals that PSA vendors see integration as additive rather than threatening [suppfusion.com, 2026].

Adjacent and substitute markets bound the opportunity. Horizontal automation platforms (Zapier, Make) substitute at the low end where a customer is willing to build and maintain their own flows. Vertical MSP automation suites (Rewst) substitute on the MSP side by automating internal MSP workflows, but typically do not own the bi-directional sync to the enterprise's ITSM. Custom middleware built by systems integrators is the historical substitute and is the option Support Fusion is most directly trying to displace by productizing what was previously a services engagement [usehalo.com, 2026]. Regulatory tailwinds are modest but real: enterprise SLA reporting and audit requirements push more ticket data into the enterprise system of record, which is exactly the sync direction Support Fusion automates.

Sizing claim Source
Pre-seed funding raised: AUD $1.0M [techpartner.news, 2025]
Connector coverage on launch: ServiceNow, ConnectWise, Jira, Halo, plus Autotask, Zendesk, Syncro [SourceForge, 2026] [suppfusion.com, 2026]
Geographic target post-raise: AU, US, UK [ARN, 2026]

Support Fusion is not betting on a market that needs to be created; it is betting on a workflow that exists today and is currently solved with manual labor or bespoke middleware. The risk in the sizing is not whether the pain exists but whether the willingness to pay sits with the MSP, the enterprise, or both.

Data Accuracy: YELLOW -- Pain point and connector coverage confirmed by multiple sources; no named third-party TAM figure available in the captured research.

Competitive Landscape

MIXED

Support Fusion is positioned as a vertical, productized integration layer between MSP PSA tools and enterprise ITSM platforms, and its competition splits into three groups: horizontal automation platforms, MSP-native automation suites, and bespoke custom middleware.

Company Positioning Stage / Funding Notable Differentiator
Support Fusion Purpose-built bi-directional ticket sync between MSP PSAs and enterprise ITSMs Pre-Seed, ~AUD $1M Productized connectors with field-level mapping for tickets, statuses, comments, attachments
Zapier Horizontal workflow automation across thousands of SaaS apps Late-stage, profitable Breadth of connectors and self-serve recipe builder
Make Visual workflow automation, more complex branching than Zapier Late-stage Visual scenario builder with deeper logic primitives
Rewst MSP-native automation platform sold to MSPs Series A reported Deep MSP workflow library on the PSA side

The segment-by-segment map is straightforward. Zapier and Make are horizontal and sell to anyone; they are credible substitutes for an MSP that is willing to assign an engineer to build, document, and maintain its own ticket-sync flows. Rewst sits inside the MSP, automating the technician workflow, but is not primarily focused on owning the bi-directional sync into a customer's ServiceNow tenant. Custom middleware, often built by the same systems integrators who sit on PSA partner programs, remains the default for large enterprise-MSP relationships and is the option Support Fusion is most directly trying to convert into a SaaS line item.

Where Support Fusion looks defensible today is in two places. The first is connector quality in a narrow corridor: the value of bi-directional sync is judged by edge cases (attachments, threaded comments, custody of SLA timers, status round-tripping), and a vendor that has solved those for the specific MSP-to-enterprise pair tends to be hard to displace once installed [SourceForge, 2026]. The second is distribution through PSA partner programs; appearing as a named integration partner on HaloPSA's site is the kind of placement that produces qualified inbound from MSPs already standardized on that PSA [usehalo.com, 2026]. Both edges are real but perishable: connector quality erodes if a horizontal vendor decides to ship a vertical template, and PSA partner placement is contingent on the PSA vendor not building the integration in-house.

The most exposed flank is on the horizontal side. Zapier in particular has the distribution and the connector library to ship a managed "MSP ticket sync" template if it sees enough demand, and would not need to match Support Fusion's depth to win the long tail of small MSPs. Rewst is exposed in a different way: if it expands its automation surface to include enterprise-side ITSM endpoints, the line between Support Fusion's product and a Rewst module becomes thinner. The 18-month scenario worth watching: Support Fusion wins if it converts two or three reference deployments at large MSPs into PSA-vendor co-sell motions, because that locks in distribution before a horizontal player notices. It loses ground if a major PSA vendor (HaloPSA or ConnectWise) ships a first-party ITSM connector and treats it as table-stakes, because that compresses the standalone product into a feature.

Data Accuracy: YELLOW -- Subject row confirmed; competitor rows are categorical descriptions based on public knowledge of the named vendors rather than on captured citations specific to each.

Opportunity

PUBLIC

If Support Fusion executes, the prize is becoming the default integration layer between every enterprise ITSM and every MSP PSA, a position roughly analogous to what Workato or Tray achieved in the broader iPaaS category but in a narrower, stickier corridor.

The single largest plausible outcome is that Support Fusion becomes the assumed connective tissue in any co-managed IT contract, sold either directly to the MSP as a per-customer line item or jointly with the PSA vendor as a certified add-on. The evidence that makes this reachable rather than aspirational is that the underlying problem (manual rekeying between ServiceNow and PSA tools) is acknowledged by the PSA vendors themselves, including a partner placement on HaloPSA's site, and that the MSP industry has consolidated into larger operators with the budget and incentive to pay for productized integration rather than maintain custom middleware [usehalo.com, 2026] [Crunchbase, 2025]. The $1M pre-seed is sized for that thesis: the company has explicitly stated that it is using the round to add a US east coast customer success hire and to push into the US and UK markets where the largest MSPs operate [ARN, 2026].

Growth scenarios

Scenario What happens Catalyst Why it's plausible
PSA-vendor co-sell Support Fusion becomes the recommended ITSM connector for one or more major PSA vendors and is sold through their partner programs A formal certification or marketplace listing with HaloPSA or ConnectWise Already listed as a named integration partner by HaloPSA [usehalo.com, 2026]
Land-and-expand inside large MSPs A handful of large MSPs standardize on Support Fusion across their enterprise customer book, producing per-tenant expansion revenue A reference deployment at a top-50 MSP that other MSPs benchmark against MSP consolidation has produced larger buyers with multi-tenant integration needs [Startup Daily, mid-2025]
Enterprise-led pull Enterprise IT teams demand that their MSPs use Support Fusion to update the enterprise ServiceNow tenant directly An audit or SLA-reporting requirement at a Fortune 1000 customer Enterprise SLA and audit requirements are the underlying driver of the rekeying pain [Crunchbase, 2025]

What compounding looks like. The flywheel in this category has three loops. Connector breadth compounds because each new PSA or ITSM connector makes Support Fusion viable in a larger share of co-managed contracts; the recent addition of Syncro API support is an example of the loop turning [suppfusion.com, 2026]. Distribution compounds through PSA partner programs, because once a PSA vendor lists a certified integration partner, every new MSP that adopts that PSA encounters Support Fusion as the assumed answer. And per-tenant economics compound inside MSPs: once an MSP has installed Support Fusion for one enterprise customer, the marginal cost of attaching it to the next customer's ServiceNow tenant falls, which is the structural reason MSP integration tools tend toward winner-take-most outcomes within a given PSA ecosystem.

The size of the win. A credible reference point for the upside is the broader iPaaS category, where public peers and acquired companies have reached multi-billion-dollar valuations on the back of horizontal connector libraries. The MSP-to-enterprise corridor is narrower than horizontal iPaaS but stickier, because the buyer is operationally dependent on the integration once it is in production. If the PSA-vendor co-sell scenario plays out and Support Fusion attaches to even a single-digit percentage of co-managed enterprise contracts globally, the resulting ARR base would put it in the range historically associated with strategic acquisition by a PSA vendor or a larger ITSM player (scenario, not a forecast). The pre-seed round and the offshore hiring plan are consistent with management aiming at that outcome rather than a lifestyle business [ARN, 2026] [techpartner.news, 2025].

Data Accuracy: YELLOW -- Headline opportunity and scenarios grounded in cited evidence; comparable valuations are illustrative analogues rather than forecasts.

Sources

PUBLIC

  1. [Startup Daily, mid-2025] IT collaboration startup Support Fusion raises $1 million pre-Seed for offshore ambitions | https://www.startupdaily.net/topic/funding/it-collaboration-startup-support-fusion-raises-1-million-pre-seed-for-offshore-ambitions/

  2. [techpartner.news, 2025] Support Fusion launches, rolls out integration platform for MSPs and SIs | https://www.techpartner.news/news/support-fusion-launches-rolls-out-integration-platform-for-msps-and-sis-618743

  3. [techpartner.news, 2025] Support Fusion raises $1 million in pre-seed round | https://www.techpartner.news/news/support-fusion-raises-1-million-in-pre-seed-round-624623

  4. [suppfusion.com, July 2025] Support Fusion targets a fundamental gap holding back MSP-enterprise service delivery | https://suppfusion.com/blog/support-fusion-targets-a-fundamental-gap-holding-back-msp-enterprise-service-delivery

  5. [suppfusion.com, 2025] Support Fusion (company website) | https://suppfusion.com/

  6. [suppfusion.com, 2026] Announcing Syncro API support | https://suppfusion.com/blog/announcing-syncro-api-support

  7. [suppfusion.com, 2026] Support Fusion pricing plans | https://suppfusion.com/pricing

  8. [Crunchbase, 2025] Support Fusion - Crunchbase Company Profile & Funding | https://www.crunchbase.com/organization/support-fusion

  9. [Crunchbase, 2025] Support Fusion - Financial Details | https://www.crunchbase.com/organization/support-fusion/financial_details

  10. [Crunchbase, 2025] Pre Seed Round - Support Fusion - Crunchbase Funding Round Profile | https://www.crunchbase.com/funding_round/support-fusion-pre-seed--d34d18a7

  11. [LinkedIn, 2026] Greg Rudakov - Support Fusion | https://www.linkedin.com/in/grudak/

  12. [LinkedIn, 2026] Stephen Rudakov - Support Fusion | https://au.linkedin.com/in/srudakov

  13. [SourceForge, 2026] Support Fusion Reviews in 2026 | https://sourceforge.net/software/product/Support-Fusion/

  14. [usehalo.com, 2026] Support Fusion Integration | HALO | https://usehalo.com/integration/support-fusion-integration/

  15. [Tracxn, 2026] Antler - 2026 Investor Profile, Portfolio, Team & Investment Trends | https://tracxn.com/d/venture-capital/antler/__PtNIc9EeX2eEO1Uq12rJHvqdFnEIU7D_gH6v0WhzYP8

  16. [ARN, 2026] Support Fusion pre-seed and offshore hiring coverage (referenced via captured facts) | https://www.arnnet.com.au/

Articles about Support Fusion

View on Startuply.vc