Methodology
This evaluation took me about 3 weeks to complete. 1 week of research and data collection, 1 week of scoring, and 1 week of writing.
I’ll explain how it worked, what it can measure, and what it can’t.
The KANO framework and why I used it
I scored all 15 vendors against a 105-feature KANO reference framework covering every major email signature management capability across 3 buyer segments.
KANO classifies features into 3 tiers.
Basic (must-haves whose absence disqualifies a vendor), Performance (differentiators that improve satisfaction proportionally), and Delighters (aha moments whose presence drives purchase excitement).
The weights reflect what buyers in each segment actually care about.
Derived from 20 enterprise sales call recordings, 127 documented buyer pain points, and review-based research across G2, Capterra, and Trustpilot.
The highest-weight features tell you where each segment’s buyers draw the line.
At SMB, auto-provisioning (10 of 100 points) is the single biggest differentiator, the “set it and forget it” moment that drives purchase.
At enterprise, multi-brand architecture (7.3 points) reflects the aha moment that enterprise CMOs and IT directors respond to most strongly.
These weights aren’t arbitrary. They’re grounded in what buyers have said under research conditions.
Feature coverage scores
Each feature is scored YES (100% of feature value), PARTIAL (50%), NO (0%), or UNCLEAR (0%, treated as absent until verified).
I ran each of the 15 vendors through the full feature set using product documentation, vendor help centers, pricing page analysis, and published feature coverage assessments.
I flagged features where documentation was ambiguous or conflicting and noted those as UNCLEAR rather than inferring.
Experience scorecard
Feature coverage alone doesn’t capture the experience of using a product.
I separately scored each vendor on 3 dimensions.
User Experience (editor quality, setup friction, UI intuitiveness), Support Quality (responsiveness, documentation, escalation reliability). User Satisfaction from Results (whether users achieve what they came for).
Scores are 1–5 per dimension.
These scores are based on MM+Enterprise buyer reviews only.
Trustpilot and AppSumo are excluded because both platforms structurally over-represent individual and SMB self-serve subscribers whose commercial relationship concerns.
Billing disputes and cancellation friction are not representative of how mid-market or enterprise accounts are managed.
G2 is the primary source; Capterra is secondary with the acknowledgment that it includes some SMB buyers.
Segment fit ratings
Segment fit ratings (Strong / Good / Moderate / Weak) are not automatically derived from scores.
They incorporate the score plus product architecture considerations, buyer profile match, and competitive positioning.
A vendor can score 73 in enterprise.
Receive a Moderate fit rating because 2 of the features it’s missing are hard procurement blockers for the majority of enterprise buyers.
The fit rating is the human judgment layer on top of the math.
Segment ordering
Within each segment section, vendors are ordered by fit rating first (Strong → Good → Moderate), then by composite score within each tier.
This preserves the fit rating as the primary signal while differentiating within tiers.
The result is that in some cases a lower-scoring vendor ranks above a higher-scoring one, because their fit tier is higher.
I think this is the right call: a 91.70 Good-fit vendor shouldn’t rank above a 91.65 Strong-fit vendor just because the score is marginally higher.
What this evaluation can’t measure
I want to be direct about what this can and can’t tell you. I scored features, not UI aesthetics.
I scored support quality from reviews, not from a structured test of each vendor’s support team.
I used current pricing page plan names but not exact dollar amounts.
Those change frequently, and publishing a number that’s out of date within 3 months serves no one.
I didn’t evaluate roadmaps, sales negotiation flexibility, or implementation partner ecosystems, all of which matter in real buying decisions.
Functional and automated, but not the event-driven SCIM protocol.
I flagged this as a gap in WiseStamp’s entries above.
I’ve seen how much that distinction matters to enterprise IT buyers, and getting it right in a published evaluation is important.
Note:
Last updated: May 2026.
- Feature data and pricing reflect research conducted in May 2026.
- All pricing should be verified directly with vendors before budgeting.
- Feature coverage status may change with product updates.
