Connect FranConnect
In the client’s workspace, open Sources, add FranConnect and choose the account to sync. If you don’t have access to the account, send the client a connect link where the platform supports one.
CRM integration
Turn franchise CRM leads, opportunities, source attribution, franchise units, and tenant-defined custom fields into 75 governed metrics for dashboards, agent answers, and cross-channel reporting.
What you can do with FranConnect in Maven
Maven models FranConnect into 75 governed metrics from the semantic layer. Track Average Days in Current Stage, Avg Days to Close, Avg Deal Size, Average Forecast Probability and Avg Open Deal Age, break results down by Deal Name, Pipeline, Deal stage and Stage Probability, and report FranConnect alongside Google Ads, LinkedIn Ads and Google Analytics 4 without rebuilding exports or metric logic for every report.
What you can measure
Maven keeps FranConnect numbers consistent across dashboards, reports, and answers so the team is not debating which spreadsheet is right.
Average number of days open deals have remained in their current pipeline stage
Average days from creation to close
Average CRM deal amount calculated from deal amount divided by deal count
Average CRM forecast probability across deals that provide a forecast probability
Average age of currently-open deals in days (creation to today)
Average pipeline-stage probability across represented CRM deals
CRM deals whose stage outcome is won or lost
CRM deal-to-account associations where native account IDs are available
CRM deal association rows or summary counts, summed per deal
CRM deal-to-contact associations where native contact IDs are available
CRM deal amount for monetary CRM opportunities; FranConnect lead rows have no amount
CRM deals or franchise-sales leads at deal grain
Pipeline amount weighted by stage probability
Closed-won deals divided by all closed deals
Deals marked closed-won at the CRM stage outcome
CRM deal-to-account associations where native account IDs are available
CRM deal association rows or summary counts, summed per deal
CRM deal-to-contact associations where native contact IDs are available
Average native lead score across CRM leads that provide a score
CRM leads or contacts marked converted by native or inferred lifecycle evidence
CRM leads or contacts that resolve to ecommerce customer identity
Converted CRM leads divided by all CRM leads
CRM leads or contacts at lead/contact grain
CRM leads matched to ecommerce customers divided by all CRM leads
Qualified CRM leads divided by all CRM leads
CRM leads or contacts whose conformed lifecycle stage is marketing-qualified lead
Marketing-qualified CRM leads divided by all CRM leads
CRM leads or contacts marked qualified by native or inferred lifecycle evidence
CRM leads or contacts whose conformed lifecycle stage is sales-qualified lead
Sales-qualified CRM leads divided by all CRM leads
Current-stage snapshot observations in the CRM stage history surface
CRM stage/property history events plus current-stage observations
Cumulative closed deal amount as of the snapshot date.
Deals in the stage as of the snapshot date.
Cumulative closed-lost deals as of each snapshot date
Open deal amount in the pipeline as of each snapshot date
Open deals in the pipeline as of each snapshot date
Probability-weighted open pipeline value as of each snapshot date
Cumulative closed-won deals as of each snapshot date
Closed CRM deals with deterministic campaign attribution matched to paid delivery
CRM deals with deterministic campaign attribution matched to paid delivery
Won CRM deals with deterministic campaign attribution matched to paid delivery
Paid-media clicks represented in the paid-to-CRM surface
Paid spend divided by attributed CRM deals
Paid spend divided by attributed won CRM deals
Attributed deals backed by a deterministic identity match
Paid-media impressions represented in the paid-to-CRM surface
Paid-media spend on campaign-day rows with CRM attribution coverage; group or filter by spend_currency
Closed CRM deals with deterministic campaign attribution matched to paid delivery
CRM deals with deterministic campaign attribution matched to paid delivery
Won CRM deals with deterministic campaign attribution matched to paid delivery
Attributed deals backed by a deterministic identity match
Fractional conversion credit under the first-touch model by conversion touchpoint
Fractional conversion credit under the last-touch model by conversion touchpoint
Fractional conversion credit under the linear model by conversion touchpoint
Fractional conversion credit under the data-driven Markov removal-effect model by conversion touchpoint
Fractional conversion credit under the position-based model by conversion touchpoint
Fractional conversion credit under the data-driven Shapley-value model by conversion touchpoint
Fractional conversion credit under the time-decay model by conversion touchpoint
Canonical conversion/lead events counted through normalized last-touch weights
Source-neutral interactions that were answered
Average duration in seconds among answered interactions
Average session duration in seconds with each session counted once
Touchpoints that opened a session
Share of represented interactions that were answered
Source-neutral interactions represented as attribution touchpoints
Touchpoints that closed a session
Phone interactions that were neither answered nor sent to voicemail
Total interaction duration in seconds
Journey touchpoint events recorded before conversion credit allocation
Source-neutral interactions that reached voicemail
Questions you can ask
Maven’s agent answers in plain language with the right metric definitions applied automatically. These are real, verified questions it can run today.
What is our deal pipeline value by stage for deals created in the last 90 days?
Show closed deals by stage
Show average days to close by owner
Show average open deal age by owner
Show open pipeline by stage
Show won and lost deals in the latest pipeline snapshot by stage
Show closed amount by pipeline in the latest pipeline snapshot
How many ServiceTitan bookings did we get in the last 30 days?
Connection and sync
You connect FranConnect with API credentials from the FranConnect account. Maven stores them encrypted. Each FranConnect sync takes a fresh copy of the current records, so the workspace always reflects what is in FranConnect now.
Fields: account name, title, lead first name, lead last name, company name, alternate email, phone numbers, mobile numbers, fax numbers, extn, and 94 more
Fields: account name, system name, label, data type, is custom, is required
Fields: account name, franchisee no, center name, franchisee name, legal name, owner name, phone numbers, address, city, state, and 88 more
How it works
No SQL or warehouse setup. Connect the source, then build the client’s report by asking Claude or ChatGPT.
In the client’s workspace, open Sources, add FranConnect and choose the account to sync. If you don’t have access to the account, send the client a connect link where the platform supports one.
Maven pulls the client’s FranConnect data (3 objects) and models it into documented tables. No SQL, warehouse or pipeline setup.
Build the client’s report or deck by asking Claude or ChatGPT through the MCP, set alerts on what matters, and publish to the client’s portal once you approve it.
Works well with
FAQ
Maven exposes 75 governed FranConnect metrics, including Average Days in Current Stage, Avg Days to Close, Avg Deal Size, Average Forecast Probability, Avg Open Deal Age and Average Stage Probability — each defined once so it means the same thing in every report.
You can break FranConnect metrics down by Deal Name, Pipeline, Deal stage, Stage Probability, Stage outcome, Source Timezone, Close date and Forecast Probability, and more.
Yes. FranConnect sits in the same client workspace as sources like Google Ads, LinkedIn Ads, Google Analytics 4, Klaviyo and Shopify, so one report or question can use them together.
Maven syncs franchise-sales leads, lead field metadata and franchisee/unit master data from FranConnect.
Maven refreshes FranConnect on a schedule after the source is connected, and shows each source’s last sync time in the client’s workspace, so you can check the data is current before a report goes out.
Yes. Maven encrypts integration credentials and tokens, scopes access to the workspace, and uses the connection only to sync the reporting data needed for governed analytics.
Set up your first client, build their report by asking Claude or ChatGPT, and publish it to their portal.
Nothing is charged unless you subscribe.