QDF Support & Maintenance
Pricing & Plans

Support for your Quick Data Flows (QDF)
That Power Your Day-to-Day Operations

Choose the support level that matches how critical the QDF is to your business
and how much change it must absorb over time.

QDF plans

Lifeline

Foundation

Alignment

Plan intent

Defines what Fruition is responsible for owning after the QDF is live.
Keep QDF alive
Keep QDF running
Keep QDF correct as business changes

Price /QDF/month
(billed annually)

Monthly cost per QDF, billed annually.
$290/ month
$790 / month
$1,890 / month
QDF plansLifelineFoundationAlignment
Plan intent

Defines what Fruition is responsible for owning after the QDF is live.

Keep QDF aliveKeep QDF runningKeep QDF correct as business
changes
Price / QDF / Month
(Billed Annually)

Monthly cost per QDF, billed annually.

$290 / Month
$790 / Month
$1,890 / Month
Operational oversight

What Fruition checks proactively without waiting for a ticket.

NO (reactive only) Monthly runtime check + alert
handling
Bi-Monthly runtime and data/output
correctness check + alert handling
Incident acknowledgement

Maximum time to confirm and start handling a reported issue.

Up to 3 business days this is for testing Up to 1 business dayNext business day
Issue resolution scope

What Fruition fixes when an issue occurs: execution
failures only, or execution plus incorrect results.

Best effortFix execution failures onlyFix execution failures and
incorrect outputs
Bug & failure fixes

Fixes for errors that stop the QDF from running.

YesYesYes
Third-party API / platform
breaking changes

Coverage for changes introduced by external
systems that break the QDF.

NOUp to 1 / quarterUp to 2 / quarter
SOP-based adjustments

Changes driven by updates to how the business operates.

Up to 1 / monthExecution-aligned only, up to 3 / monthMeaning-aligned based on
SOP evolution, up to 6 / month
Attribute / mapping updates

Changes to existing fields and how they map between systems.

Up to 1 / monthUp to 4 / monthUp to 10 / month
Trigger or outcome refinements

Changes to what starts the QDF or what actions it produces.

NOUp to 1 / monthUp to 4 / month
Cross-team coordination support

Whether multiple teams can rely on the same QDF and its outputs.

NOUp to 1 dependency
(handoff only)
Up to 3 dependencies
(shared data meaning)
QDF-to-QDF dependency handling

Whether one QDF can safely depend on another QDF’s output.

NO NOUp to 2 dependencies
Communication channels

How you interact with Fruition at this support level.

Support ticketEverything in Basic +
Slack channel
Everything in Foundation +
dedicated PM
Urgent response

Optional faster response during business hours.

NONOAvailable (Add-On)
After-hours / White-Glove

Optional support outside standard business hours.

NONOAvailable (Add-On)

$290/ month

QDFs are designed around how your business actually operates—not platform limitations.
If you want to ensure this fits how your SOP and processes really work, we’re here to align it with you.

How QDF Support Works

Each QDF is supported independently. You choose a support level per QDF, based on how critical that flow is and how much change it needs to handle over time.

This page applies only to QDF-level support. QDF support is designed for companies running individual automation flows, whether those flows connect two systems directly or use flow-level CDHS capabilities as part of the logic.

If your company runs CDHS as a shared operating layer across multiple flows, teams, or departments, QDF support is not sufficient. In that case, support must be provided at the CDHS system level, which is covered under CDHS System Support (Orchestration).

CDHS support focuses on operating the system that governs multiple flows.

What Our Clients Say

FAQs — QDF Support & Management

Is this support required after a QDF is launched?
No. Support is optional, but recommended for any QDF that is operationally important or expected to change over time.
Yes. Each QDF can be supported at a different level based on its criticality.
Foundation keeps the QDF running. Alignment keeps the QDF correct as business rules, data meaning, and SOPs evolve.
It means fixing cases where the QDF does not run or complete, without changing data meaning or business logic.
Examples include wrong field values, incorrect mappings after a system change, misrouted records, or outcomes that no longer match the current SOP.
Yes, as long as CDHS is used at the flow level only. This page does not cover system-level CDHS operation.
When CDHS governs multiple QDFs, shared data models, events, or cross-department dependencies. In that case, QDF support is not sufficient.
Additional work can be scoped separately, or the QDF can be moved to a higher support tier.
Yes. These are optional add-ons available for Alignment support.
Yes. Support levels can be adjusted as the importance or complexity of a QDF changes.

Ready to Keep Your QDF Running?

Whether you need basic reliability, consistent uptime, or full alignment with your evolving business—there’s a support plan designed for your QDF’s role in your operations.

Choose the level that matches how critical this flow is to your team.

© All Rights Reserved (C) Fruition Inc.

Schedule a Time with our Expert!

— Fill out the Form and let's meet —

Fill out the form below to book your meeting to get your HubSpot Audit Report.

Schedule a meeting
Your HubSpot Onboarding Plan.

** Schedule to have you High level plan for free.

Funnel Types List

Register and Get the Funnel List type

Provide you with a complete overview of the type of funnel and how to manage it. 

JOIN OUR LIVE EVENT!

Wednesday, October 18th
10AM (PST)

Webinar Topic: Fix the Leak with Streamline Your Revenue Path with RevOps Funnels. 
How to seamlessly guide prospects through your company’s journey,

  1. Utilize the Funnels in Revenue Operations
  2. How to Prevent Bleeding Prospects and Customers in Your Company’s Journey
  3. How to Automate the Process for Enhanced Efficiency

RevOps Knowledge Sharing!

Fill out the form below, and blogs, videos and content will come directly to your inbox.