How are we doing against the plan? A simple question, until you have several businesses, different systems, and a hiring plan that keeps moving.
Our Fall releases bring more of that picture together in QFlow: where growth is coming from, whether the team can deliver the plan, and what that growth costs.
Next month’s pipeline review should explain what changed in the business. Asking an AI assistant to work out the analysis again introduces another question: did the business change, or did the way we measured it?
A Recipe saves the sources, selection rules, and calculations you’ve agreed on. Run those steps against fresh data for the next review. When the question changes, review the proposed edits to the analysis.
A ghosted qualification call doesn’t tell you whether the opportunity is over. What happened next? Did the rep follow up? Did the prospect reply, return to a productive conversation, or disappear?
QFlow brings activity, campaign, and opportunity records into that investigation. Build the analysis around the part of the selling process you want to understand, then examine the evidence before changing it.
Multi-entity support is publicly available.
Large, acquisitive organizations often have no medium- or long-term plan to consolidate their CRMs. That can be a sensible choice. A services business and a subscription software company may have different customers, sales processes, and ways of earning revenue. Putting them in the same system won’t necessarily make either business easier to run.
Their teams still need to plan and forecast. Management still needs to understand the group. QFlow lets you plan and analyze those businesses together while each continues using its own CRMs, ERPs, and GTM tools.
The analysis can be exact and the final deliverable can still depend on memory.
An analyst opens last month’s deck, replaces charts, adjusts the commentary, fixes the appendix, and hopes every formatting decision survived the copy. The numbers may come from a governed process. The finished work does not.
Today we are introducing QFlow Organization Skills: private, versioned workflow packages that teach Codex and Claude how your company turns QFlow results into decks, workbooks, reports, and forecasts.
Claude and Codex can turn business data into a board deck in minutes. Give them raw finance, sales, and marketing data, and they can also make ungoverned analytical choices at the same speed.
The risk is not the final formatting. It is allowing an AI assistant to decide what pipeline, bookings, revenue, or conversion mean from raw tables and exports.
QFlow Desktop is now out of beta for macOS and Windows. It connects QFlow’s governed data, deterministic tools, Agentic Recipes, and organization skills to Codex, Claude Desktop, and Claude Code. QFlow governs and executes the analysis. The assistant builds the deck, workbook, or memo.
The July releases connect more of the revenue engine in one operating model.
A CRO can ask whether the selling motion has enough capacity to produce the plan. A CFO can follow bookings into recognized revenue and accounting actuals. RevOps can find where conversion slows, see how new reps build pipeline, and resolve renewal ambiguity before it enters the forecast.
They are valuable, but they are built around the conversation. They can summarize what a buyer said, identify an objection, and surface a moment from a call. They do not have the full opportunity, account, and contact history. They do not know how the deal moved through the funnel. And they cannot reliably connect qualitative evidence to finance-grade measures such as ARR.
A transcript is evidence. It is not, by itself, win-loss analysis.
QFlow’s Win-Loss Agent connects that evidence to the rest of the go-to-market record. It determines why deals were won or lost, measures how much revenue is attached to each reason, and lets leaders inspect the source material behind every conclusion.
Someone asks RevOps for the funnel. Not a dashboard full of activity counts, but the actual motion from first response to meeting, qualified opportunity, and outcome.
The data exists, but it does not live in one place. The CRM holds opportunity stages, lifecycle changes, and forecast movement. The marketing automation system holds campaign responses and pre-opportunity engagement. Gong, Salesloft, Clari, and similar platforms hold calls, meetings, conversation activity, and outcomes.
Each system describes a fragment of the same journey. A CRM stage, campaign response, meeting disposition, and activity label may represent one conversion point without sharing a name or timestamp convention. A polished funnel built from any one source can be complete and still be wrong, including a data warehouse.
We are introducing the new QFlow Conversions Agent. It turns those scattered events into one reusable conversion dataset, aligning what happened across the revenue engine with the motion RevOps expected to happen.
A bookings forecast says what may close. A revenue forecast says when and how those bookings become revenue.
The distinction matters. A subscription company recognizes recurring revenue across a contract term. A B2B2C or consumption business depends on usage, realization, and unit price. A hybrid company may add implementation services, hardware, or another one-time charge. Put every stream on the same curve and the top line may look tidy, but it will not describe the business.
We’re pleased to announce that the QFlow Revenue Agent now models the full path. It forecasts bookings, translates them through the way each stream earns revenue, and replaces projections with accounting actuals as months close.
