Plan2Win

This vendor makes no model claim of any kind, on any surface, and the product predates the category by roughly fifteen years. There is no assistant, no generation, no scoring and no recommendation engine; what is sold is a set of structured templates and a document generator running inside the customer's existing system of record.

The convention reserves the bottom band for a marketed claim that fails the removal test and places a competent product making no claim at the middle band, which is exactly this case. Worth recording as a contrast: in a sweep where almost every vendor leads with intelligence, two consecutive builds now sit here on the strength of making no such assertion at all.

Nothing in this product acts on its own, and the governance that does apply is inherited rather than built. Because the applications are native managed packages, every record they create is a custom object inside the customer's own Salesforce organisation, which means the org's existing profiles, permission sets, sharing rules, field level security and audit history govern who can see and change a plan without the vendor writing any of it.

That is a substantial control set arriving for free, and it is a genuine advantage of the deployment model. Held at the middle band because none of it is the vendor's own disclosure: no role model, approval step or oversight description appears in any material located, and the setup guidance leaves page layout and access decisions to the customer's administrator.

There is no model estate to disclose. No assistant, generation feature, scoring engine or recommendation function exists anywhere in the product, so the questions this axis normally asks about provider, family, version and hosting have no subject. Graded at the middle band as a structural non fit rather than as a withheld disclosure, and recorded here so a reader comparing this vendor against others in the category understands that the absence is the product rather than a gap in it.

Almost nothing, and what exists points backwards. An independent directory carries a rating above four out of five, and that same directory records the vendor's profile as inactive for more than a year and invites the company to reclaim it. No named customer, case study, quantified result or measurement basis was located on any surface.

The single statistic the vendor does deploy is not about its product at all: a claim that salespeople who do account planning are forty one percent more likely to achieve quota, which is a category research finding used as a purchase argument with no source, sample or date attached. Every user guide and overview document retrievable through the marketplace carries a copyright date of 2014 or 2018.

Structurally a non fit for this axis, graded on what is knowable, with the context carried here. This product sends nothing to anybody. It has no campaign engine, no mailbox connection, no dialer and no messaging surface of any kind; the pre call planning module prepares a representative for a conversation they will conduct themselves through channels the vendor never touches.

No statute, consent position or suppression mechanism is published because none of that apparatus applies to a planning template. Nothing here indicates poor practice and nothing this axis measures is available to assess.

No privacy policy is retrievable, and the reason is the sharpest finding in this build: the vendor's own website returns no content to an automated reader, while the licence terms published on the marketplace bind both parties to the terms and conditions as posted on that website. The governing contract incorporates by reference a document at an address that does not render. Set against that, the exposure is genuinely low and structurally so.

The applications are native managed packages, so the personal data they touch is the customer's own Salesforce records, held in the customer's own organisation under a data processing relationship the customer has already established with their platform provider. The vendor is not a separate processor of a separate copy. That architecture, rather than any published statement, is what holds this row at the middle band.

There is no third party data question to answer. This vendor sells no contact database, buys no lead data, operates no enrichment product, runs no scraper and connects to no external source. Every record the applications work with already exists in the customer's own system of record and was put there by the customer. Along with one other vendor graded this session, this is the cleanest baseline in the index.

Held at the middle band rather than higher because absence of exposure is not the same as a published position, and no statement about data handling, ownership or sourcing was located on any retrievable surface.

The distribution model is the most conformant available in this category. These applications are sold exclusively through the host platform's own official marketplace as native managed packages, which means listing required passing that platform's security review as a condition of publication, and operation happens entirely inside the boundaries the host platform defines.

Nothing scrapes, rotates an identity, rents an account, automates activity on a network the vendor has no arrangement with, or reaches outside the single environment it was built for. The vendor states the dependency plainly in capital letters, that every licensed user must hold a licence for the host platform.

Off the top band because the vendor publishes no conformance position of its own, and because the relationship rests entirely on one platform's continued goodwill with no stated position on what happens if the host changes its terms.

The cross client question that dominates this axis elsewhere in the index cannot arise here, and the reason is architectural rather than promised. There is no model, so there is no training corpus. There is no separate vendor side copy of the data, because the applications run as native packages inside each customer's own organisation, so one customer's account plans are not sitting in a shared store alongside anyone else's.

A deployment model that makes the question structurally impossible is a stronger answer than most of the assurances graded in this sweep. Held at the middle band because the vendor publishes no stewardship statement of its own, and because no terms of service or privacy policy could be retrieved to confirm what the vendor may do with anything it does hold.

Structurally a non fit for this axis, graded on what is knowable, with the context carried here. No content produced by this product reaches a prospect or customer automatically. Plans are internal documents written by representatives for their own managers and reviewers, and the one output that can leave the organisation is a generated document a person chooses to send. No machine composes anything, no tracking pixel is described, and no analytics observe a third party.

There is consequently nothing for an artificial intelligence disclosure obligation to attach to, and the absence of a position on it is a fact about the product rather than a gap in the vendor's candour.

Total depth on exactly one platform and nothing anywhere else, which is a design choice with a real cost. Within the host environment the integration is as deep as it gets, since the applications are native rather than connected: plans read live opportunity and contact records, sections can be embedded directly into standard account and opportunity page layouts by an administrator, both interface generations are supported, and the whole thing works on mobile because the host platform does.

Outside it there is nothing. No second system of record, no marketing platform, no analytics tool, no workflow broker, no published interface, no webhooks and no developer documentation were located. The dependency is stated in capitals as a purchase condition, and it functions as a hard boundary: a buyer not already committed to that one platform cannot use this product at all.

The deployment model is stated plainly and it is the most favourable answer available on this axis. The vendor publishes, in capital letters, that its applications are designed to work within the host platform environment and that every licensed user must hold a licence for it, which means the software is installed as a managed package into the customer's own organisation rather than hosted separately by the vendor.

The practical consequence is that data residency follows the customer's existing platform tenancy, in whatever region they already selected and already diligenced, and no separate vendor side location question arises for the records themselves. A buyer inherits a residency posture they have already approved.

Off the top band because the vendor makes no residency statement of its own, publishes nothing about any vendor side processing, support access or telemetry that might sit outside that boundary, and offers no documentation on what an administrator should verify.

No certification, audit, attestation, penetration test, control set, security page, trust centre, status page or vulnerability route was located anywhere, and the vendor's own website returns no content, so nothing could be checked there either.

What holds this above the floor is a third party gate the vendor genuinely passed rather than asserted: publication on the host platform's official marketplace requires clearing that platform's security review, which examines the package's code and permissions, and continued listing requires maintaining it.

Beyond that, running as a native package means the host platform's own encryption, authentication and access controls apply to every record, so the customer's existing security posture extends over the application by construction. Both of those are inherited assurances rather than published ones, which is precisely why this sits at the middle band and not higher.

A real published price and unusually candid terms, both hosted somewhere other than the vendor's own site. The marketplace listing states fifteen dollars per user per month, names the host platform editions it works with, and offers a thirty day trial through a self serve button, while the vendor's own overview document quotes an annual equivalent and states that quantity discounts begin above thirty five licences.

Three terms are disclosed plainly and all three run against the vendor's interest: licences are not refundable, there is no automatic renewal so the customer must actively choose to continue, and the vendor reserves the right to change the price at any time without notice with the new rate applying at renewal. Upgrades are included at no charge with the honest caveat that the customer bears the cost of installing them and of redoing any customisations.

Off the top band because the consulting and training services carry no published rate, because the price lives on the host marketplace rather than on a vendor page a buyer can find, and because the terms and conditions the contract incorporates by reference sit at a website address that returns nothing.

The structural position is better than the published one. Because the applications are native, every plan is stored as a custom object record inside the customer's own organisation, so the data is already sitting in a database the customer controls and can query, report on and extract using the host platform's own standard export tooling without asking the vendor for anything. Document generation adds a second route, letting any plan be produced as a portable file for circulation.

Against that, no export statement, retention period, deletion timeline or post termination provision was located, and the terms of service could not be retrieved. The unaddressed risk is specific to this deployment model and material: uninstalling a managed package ordinarily removes the custom objects it introduced, so a departing customer who has not extracted their plans first may lose them at the moment of leaving, and nothing published warns of that.

Structurally a non fit for this axis, graded on what is knowable, with the context carried here. The product operates no sending infrastructure whatsoever: no campaigns, no connected mailboxes, no sequences and no dialer. Its entire output is internal documents and structured records inside the customer's own system of record.

No warmup, authentication, pacing, bounce handling, complaint threshold or reputation monitoring is published because none of that apparatus has anything to govern, and nothing in the material read suggests otherwise.

The buyer is defined by dependency rather than by description, and that definition is at least unambiguous. The vendor states in capital letters that every licensed user must hold a licence for the host platform and that the applications require its professional edition or above, which is an unusually clear statement of who cannot buy this, delivered as a purchase condition rather than as marketing.

Three products map to three planning horizons, from the individual call through the account to the territory, and the vendor positions the templates as methodology neutral, which is a real fit statement for organisations that have already committed to a selling framework of their own.

Beyond that the coverage half is empty: no industry, region, country, language, customer count, seat band or company size appears anywhere, and the only quantitative signal available is a third party record of roughly three employees.