Revenue Intelligence & Forecasting
F

Fullcast

Fullcast is a revenue operations platform positioned around a plan to pay loop: design territories and set quotas, model capacity and headcount scenarios, route leads and accounts to the right rep in real time, validate the forecast against live pipeline signals, and calculate commissions that recalculate whenever a territory, quota or deal changes. It sells modularly across four named products covering planning and routing, revenue intelligence and forecasting, sales coaching, and commissions, with managed services and a data desk carrying a three hour service level available alongside.

Model providers are named openly and an agent action layer runs over the Model Context Protocol so changes can be requested in plain language rather than queued with operations. Founded 2016 by Bala Balabaskaran, formerly vice president of go to market technology and operations at Salesforce, with Ryan Westwood, founder of Simplus. Named customers include Gong, Rubrik, Lenovo, Thermo Fisher, Asurion, TechTarget and Urban Outfitters.

Last VerifiedAugust 20, 2026
Compare Fullcast with other vendors
Founded
2016
Headquarters
Categories
revenue-intelligence, sales-enablement, sales-engagement
Assessment

Capability Axes

AI Capability
AI CentralityAI CentralityWhether AI is the product or a feature veneer. The removal test: peel the AI label off, and does anything sellable remain?
CC on AI CentralityAI features on a conventional platform. Peel the AI label off and the product still works roughly as before.
Vendor Published

The headline calls this a purpose built engine for revenue leaders, and the removal test leaves most of the product standing. Territory carving against rules, quota allocation, capacity and ramp modelling, real time routing by policy and commission calculation are deterministic optimisation and rules work, and the company built its reputation on doing them without spreadsheets from 2016, well before the current model generation.

What the model genuinely adds sits in one of the four products: reading live pipeline signals to validate a forecast, flagging deals at risk, and surfacing where a seller is stuck. That is real and it is additive. A buyer who removed the model layer would lose forecast validation and coaching signals and would keep the planning, routing and pay engine that the platform is named for.

Autonomy and Oversight ModelAutonomy and Oversight ModelWhat the system does without a human. Draft for review, auto send, or fully agentic, and what contains a bad run.
BB on Autonomy and Oversight ModelThe human in the loop posture is described substantively (draft versus auto send, approval flows) but the failure containment story is incomplete.
Vendor Published

Auditability is treated as a product property rather than a compliance afterthought, and it recurs across the material: complete audit trails for every change to a plan, routing decisions logged for compliance, changes audited end to end, and agent actions described as traceable and audited. There is also a real approval gate, since a go to market plan is designed and then executed at the moment it is approved rather than taking effect as it is edited.

Both of those are more than most vendors here publish. Off the top band on one thing the vendor is proud of. The agent layer is explicitly sold as letting a team make a change in plain language instead of queuing a request with operations, which removes the human gatekeeper that the approval step depends on, and nothing published describes what an agent may or may not alter, what permission model constrains it, or how a change is reversed.

AI Disclosure and Model TransparencyAI Disclosure and Model TransparencyWhat models power the product, whether AI generated outreach discloses itself, and whether scoring and routing logic is explainable.
BB on AI Disclosure and Model TransparencyMeaningful disclosure of the model stack or the disclosure posture, with one real gap, commonly silence on whether AI authored outreach identifies itself.
Vendor Published

Model providers are named outright, which remains rare across this corpus: the platform is stated to connect with OpenAI, Gemini and Claude. The architecture is described rather than gestured at, with an open protocol acting as the action layer across the platform so that a team or the assistants they already use can query or change plan data conversationally, and with the forecasting agents reading live deal signals instead of polling reps for sentiment.

The vendor also draws a boundary that most do not, stating that agents run on those external models and on the customer's own governed plan data. Off the top band because no model version is named and no accuracy figure is published for the two functions that matter most, forecast validation and deal risk detection. The five percent forecast accuracy figure appears in a marketing outcome block rather than as a stated model performance measure, and no fallback behaviour is described for when a signal is wrong.

Operational and Outcome EvidenceOperational and Outcome EvidenceMeasured outcomes with a stated basis: replies, meetings, pipeline, win rates. Logos are not evidence and prestige is not measurement.
BB on Operational and Outcome EvidenceReal outcome evidence published, with named customers and numbers, but the measurement basis is incomplete: population, period, or definition unstated.
Vendor Published

The named evidence here is among the strongest in the index. Fourteen enterprise logos are published including Gong, Rubrik, Lenovo, Thermo Fisher, Asurion, TechTarget, Urban Outfitters and a global consultancy, three case studies carry a named person with their title and employer, and eight testimonials each carry a name, a role and a company rather than a first name and an initial. An annual benchmarks report and a published book sit alongside.

What holds it off the top band is a specific and unusual gap: the names and the numbers never meet. A separate block publishes nine outcome figures, covering incremental revenue of ten to twenty percent, eighty percent less planning time, ten percent higher win rates, forecast accuracy within five percent, twenty five percent less pipeline slippage and commission disputes falling from twenty two percent to zero, and not one of them carries a sample, a method, a period or a customer.

A comparison table of costs without the product against upside with it is pure assertion. On one product page the vendor states that it guarantees improved seller quota attainment. A vendor with this customer list is in a position to attach a number to a name and has chosen not to.

Compliance and Risk
Outreach Compliance PostureOutreach Compliance PostureHow the product handles regulated outreach: consent, DNC scrubbing, opt out mechanics, caller ID conduct, and the public enforcement record.
CC on Outreach Compliance PostureCompliance is mentioned as the customer’s responsibility, with little or no product enforcement described. The tool can be run lawfully, and nothing about it helps.
Vendor Published

This platform sends nothing to a prospect. It plans coverage, assigns ownership internally, forecasts and pays, so the sending axes reach it only structurally and this grade reflects what is knowable rather than any compliance failure. The one place the axis brushes the product is routing, where a lead arriving from a form or a campaign is assigned to a rep under service level rules, and the vendor does publish that routing decisions are logged for compliance purposes.

Nothing addresses acceptable use of the platform's outputs, or any duty attaching to the contact records that flow through the routing engine. Graded on the absence of a stated position rather than on evidence of a problem.

Data Privacy PostureData Privacy PostureGDPR and CCPA posture: lawful basis, data subject rights handling, DPA availability, subprocessor disclosure.
CC on Data Privacy PostureA standard privacy policy exists and answers none of the questions this product category specifically raises.
Vendor Published

The published routes exist and are easy to find: a privacy policy, cookie preferences, a route to restrict the sale or sharing of personal information, a responsible disclosure channel, and badges asserting compliance with European and United States privacy law. None of those documents was read in this pass, so retention, lawful basis and processor detail are unestablished. What holds this at the middle band rather than higher is a gap the product shape makes conspicuous.

This platform holds employee data of an unusually sensitive kind: individual quotas, attainment against them, ramp schedules, capacity assumptions about who will be hired or replaced, commission calculations, and coaching assessments naming where a specific seller is stuck. Nothing published addresses the rights of those employees over that data, its retention, or their access to it. A compliance badge is a self assertion; an attestation covering worker data is what this product would need.

Data Licensing and ProvenanceData Licensing and ProvenanceWhere the data comes from and on what legal footing: licensed, contributed, public record, or scraped, and who stands behind the answer.
CC on Data Licensing and ProvenanceData is described by its size and coverage with its origin unstated. The provenance question is answerable only by asking the vendor.
Vendor Published

No contact database is sold, built or resold, and the platform's raw material is the customer's own records, pipeline and compensation plans, so provenance sits with the buyer. Two things keep this off the higher band. The vendor publishes a data hygiene and enrichment use case and a managed data desk operating under a three hour service level, and no source, supplier, coverage or accuracy standard is stated for whatever enrichment adds to a customer's records.

That is the same unresolved shape recorded against other systems of record in this index. Separately, the managed services arm places the vendor's own practitioners inside the customer's records as an operating model rather than an exception, and nothing published describes the access boundary that applies to them.

Platform Terms ExposurePlatform Terms ExposureWhether the product operates inside the terms of the platforms it touches, and the restriction risk a buyer inherits when it does not.
BB on Platform Terms ExposureThe method is described and mostly conformant, with one real ambiguity the vendor does not resolve, or conformance asserted without the partnership evidence that would settle it.
Vendor Published

Integration runs through sanctioned interfaces into systems the customer already licenses, named as Salesforce and ServiceNow, plus an open protocol interface the vendor publishes itself. No browser extension harvests another product's screen, no account credential is borrowed, nothing is rotated or paced to slip past another company's limits, and the platform sends no messages that a carrier or network could act against.

Off the top band because no conformance position is stated: nothing addresses what happens to a customer's plans and routing rules if a connected system of record changes its access terms or its object model, which matters more here than for most vendors because the entire product writes ownership and assignment back into that system.

AI Safety and Data StewardshipAI Safety and Data StewardshipThe cross client boundary: whether customer data trains models that serve competitors, plus retention and deletion posture.
CC on AI Safety and Data StewardshipSecurity language exists but the training question, the one this axis turns on, is unanswered: a buyer cannot tell whether their pipeline data improves a competitor’s instance.
Vendor Published

The vendor answers the auditability question well and the stewardship question not at all. Actions are described as traceable and audited and agents are said to run on the customer's own governed plan data, which is a boundary of a kind, but nothing published states whether customer plan data, pipeline history or compensation records contribute to model improvement, and no cross tenant statement exists.

The named architecture sharpens the question rather than settling it: plan and pipeline data is passed to three external frontier model providers, and nothing addresses what those providers retain, under what terms, or whether a customer can decline a particular one. The data at stake includes individual compensation and performance assessments, which is a higher sensitivity class than most vendors in this index handle.

Recipient Disclosure and AuthenticityRecipient Disclosure and AuthenticityHow the product presents itself to the people it targets: whether automated outreach and AI agents disclose themselves, whether sender personas are real, and whether personalization is grounded in verifiable fact. Measured as known compliance with Article 50 of the EU AI Act, in force since August 2, 2026, which requires AI systems that interact with individuals to disclose that fact.
CC on Recipient Disclosure and AuthenticityNothing published on whether recipients are told they are dealing with software. For a product whose AI talks to prospects, silence here is now a regulatory posture, not a style choice.
Vendor Published

Nothing in this product contacts a prospect, so the usual form of the axis does not apply and no impersonation, synthetic voice or manufactured persona exists anywhere in it. The second form applies squarely and is unaddressed. Models here assess named employees: they surface where an individual seller is stuck, define what good looks like for that person, model attainment probability against their quota, and inform decisions about territory, coverage and pay.

Nothing published states whether a rep is told a model produced an assessment about them, whether they can see it, or whether they can contest it, and the European transparency obligations that took effect in August 2026 are not mentioned. The people most affected by this platform's output are the customer's own staff.

Integration and Deployment
Ecosystem and Integration DepthEcosystem and Integration DepthDocumented depth of CRM and stack integration: objects, sync direction, API surface, marketplace presence that matches the claims.
BB on Ecosystem and Integration DepthSolid primary CRM integration documented, with depth unstated at the edges (sync direction, custom objects, failure behavior).
Vendor Published

The standout is the agent interface: the Model Context Protocol is published as the action layer across the whole platform rather than as a demonstration, so plan data can be queried and changed by whichever assistant a team already uses. That is the fifth such interface recorded in this index and one of the few positioned as core architecture rather than a feature announcement.

Named connections to three external model providers sit alongside it, with a dedicated integrations page and a managed services arm. Off the top band on breadth, and the gap is sharper than it looks: only two systems of record are named, Salesforce and ServiceNow, for a platform whose entire proposition is unifying a go to market motion, and no public interface reference, webhook catalogue or object level description of what writes back was located.

Deployment Model and Data ResidencyDeployment Model and Data ResidencyWhere the product runs and where customer data lives, including residency options for EU buyers.
CC on Deployment Model and Data ResidencyCloud hosted is the whole public answer. Region and residency questions require a sales conversation.
Vendor Published

No hosting region, data centre location, infrastructure provider, residency option, single tenant path or processor register was located on any public page. A trust portal exists on its own subdomain and is the stated route to audit documentation, so the structure through which residency would normally be published does exist and was not opened in this pass, and this row should be re verified there rather than treated as settled.

The absence matters more than usual because the platform holds compensation and individual performance data for organisations that include large regulated enterprises, and because plan data is passed to external model providers whose own processing locations are equally unstated.

Security Certifications and Trust CenterSecurity Certifications and Trust CenterVerifiable security posture: enumerated current certifications and a trust center an outsider can actually read.
BB on Security Certifications and Trust CenterCertifications named and plausible with a gap: no trust center, stale dates, or asserted without enumeration.
Vendor Published

A service organisation attestation at type two is stated, and the important part is the route rather than the badge: the vendor publishes that the full audit history and the report itself are available at a trust portal on its own subdomain. That is the distinction this axis turns on, since a report a buyer can reach is worth more than one asserted in a footer.

A responsible disclosure channel is published, along with compliance claims for European and United States privacy law and routing audit logs described as a compliance feature. Off the top band because the evidence stops at the one attestation: no information security certification under an international standard, no audit period or date, no auditor named, no penetration testing statement, no status page and no sub processor list, and the report availability was asserted rather than verified in this pass.

Commercial and Operational
Commercial TransparencyCommercial TransparencyWhether a buyer can budget without a sales call. Published pricing graded on completeness, not on the price itself.
DD on Commercial TransparencyBook a demo is the entire commercial disclosure. In a category this competitive, silence on price is a choice, and this grade records it.
Vendor Published

A page titled Plans and Pricing exists and contains neither a plan price nor a plan. What it does publish is more than most vendors in this band manage, and it is worth recording precisely because it is a distinct variant: the vendor names the pricing metric for each of its three suites, so a buyer learns that planning is charged by users, that commissions are charged by number of payees and plan complexity, and that routing is charged by volume and policy complexity.

Two chargeable add ons are named, premium support and a sandbox environment. What is missing is every number. No rate, tier, band, minimum, currency, example or range appears anywhere, and every route converts to a demo request. Naming the meter without the rate tells a buyer how the bill will scale and nothing about what it will be, so budgeting remains impossible, which is the test this band applies. One defect on the same page: the routing suite reproduces the planning suite's four pain points verbatim, so the product is sold against problems that belong to a different product.

Exit and Data PortabilityExit and Data PortabilityWhat happens when a customer leaves: completeness of data export, rights to enriched or licensed data after termination, deletion commitments, and auto renewal mechanics, graded from published terms and documentation.
CC on Exit and Data PortabilityExport exists as a feature claim while the terms that govern exit, data rights after termination, deletion, and auto renewal mechanics, are not published anywhere a buyer can read.
Vendor Published

Website terms of service and a privacy policy are both published and linked from every page, so governing documents exist and this clears the bottom band, which is reserved for vendors whose only legal text is a website notice. Their substance was not read in this pass, so no export format, post termination retention window, deletion timeline or return mechanism is established.

The practical position deserves credit and is genuinely unusual for this category: the platform writes territory, ownership, quota and assignment back into the customer's own system of record as it operates, so the operational output of the product accumulates outside the platform by default. The planning artefacts themselves, the scenario models, carving rules and compensation plan designs, have no described route out.

Deliverability and Sending DisciplineDeliverability and Sending DisciplineThe operational craft of sending: warmup, rotation, volume governance, spam rate monitoring, and what happens when reputation degrades.
CC on Deliverability and Sending DisciplineDeliverability is invoked as a benefit with no documented mechanism. For senders this is the axis where marketing most outruns evidence.
Vendor Published

The product operates no sending infrastructure of any kind and reaches no prospect inbox or handset, so this axis applies only through the general rule that vendors are still graded on what is knowable. There is no domain or number reputation at stake, no warmup, throttling or bounce handling to assess, and no complaint surface. The grade records the absence of an applicable surface rather than a weakness, and it should be read that way when this vendor is compared against sending categories.

Segment and Market CoverageSegment and Market CoverageWho the product actually serves, evidenced: segments, geographies, languages, and customers that match the claim.
BB on Segment and Market CoverageSegment focus is clear and evidenced with a gap in geographic or language specifics.
Vendor Published

Segmentation is expressed in several dimensions at once and each is concrete. Five industries carry their own pages, covering healthcare, financial services, business software, media services and private equity portfolios. Six buyer roles carry their own pages, covering the chief revenue, financial, information and operating officers plus sales and revenue operations teams, which is a more precise account of a buying committee than most vendors attempt.

The published customer list corroborates an enterprise and upper mid market centre of gravity. Off the top band because the review platform badges the vendor displays span small business, mid market and enterprise simultaneously, which claims the whole market rather than describing a place in it, and because no headcount band, seller count or deal size is named anywhere.

Commercial

Pricing

Vendor-published figures are labeled as such. Figures labeled “Estimated” are derived from third-party sources and have not been confirmed by the vendor.

No pricing data has been verified for this vendor. Pricing information will be published here once confirmed through vendor disclosure or third-party estimation.

Contact us

Found a vendor we missed? Have feedback on the index? We’d love to hear from you.

GTM Tech Index

An independent reference for evaluating the software revenue teams use to find, win, and keep customers. No vendor pays for inclusion, placement, or rating.

Index Status
Last index update
August 20, 2026
The GTM Tech Index is an editorial reference, not a law firm or a regulator. Compliance postures are assessed from published sources and public records, and nothing on the index is legal advice. Figures labeled “Estimated” have not been confirmed by the vendor. See the Methodology page for evaluation standards and limitations.
© 2026 GTM Tech Index
3801 N Capital of Texas Hwy, Ste E240 · Austin, TX 78746