Website buyer-fit audit · boldsign
2026-11-10 08:06 · success · score 68· by danjebaraj · reviewed by danjebaraj on 2026-11-10· backend claude-code 2.1.311 (claude-opus-5-5)
Checklist: demand-gen/web/website-buyer-fit-audit.md
Summary
Headline
boldsign.com scores 68% (34/50 on the items that could be checked) for midsize and enterprise buyer fit. Its pricing, integrations and core security facts are strong. The weak spots are the paths a buying committee needs:
- No "Book a demo" in the navigation.
- Compliance, SLA and procurement documents are spread across the Legal Center, with no single trust or procurement page.
- Uptime figures conflict from page to page.
- Case studies have no labels and no midsize+ outcomes.
- No accessibility statement was found.
9 of 15 documented objections are fully answered where the objections file says they should be.
Score
68 / 100. 3 of 28 items were not checked (S7.1, S8.1, S8.2) and are left out of the denominator.
Top 3 actions
- Align uptime and SLA claims, then put them on the security page. Today the security page says "99.9% durability", the SLA PDF says 99.99%, and the API and enterprise pages say 99.999%. Product marketing needs to hear about this today. (S1.3, S1.4, objection 14)
- Build one trust/procurement hub off the security page. It should link the SOC 2 overview and request form, HIPAA, DPA, sub-processors, responsible disclosure, the SLA, NIST and TX-RAMP, and offer a security questionnaire, W-9 and MSA on request. Also confirm the wording of the "PCI DSS Level 1" badge. (S1.2, S2.2, objection 2)
- Add "Book a demo" to the main navigation, and add a company-size field to the contact form for routing. (S2.1, S2.4)
Findings
Website buyer-fit audit: boldsign, https://boldsign.com/, 2026-11-10
Run by: Claude
| Section | Score | Points | Biggest gap |
|---|---|---|---|
| S1 Trust | 83% | 10/12 | Compliance and SLA documents only in the Legal Center; uptime figures conflict |
| S2 Enterprise paths | 63% | 5/8 | No "Book a demo" in nav; no procurement hub; form doesn't route by size |
| S3 Deployment and integration clarity | 75% | 6/8 | Cloud-only model not stated plainly; no data-flow diagram |
| S4 Pricing-page clarity | 80% | 8/10 | No terms/renewal/invoice links; no worked cost-at-scale example |
| S5 Case studies | 25% | 1/4 | No industry or size labels; no midsize+ quantified outcomes |
| S6 Objection coverage | 50% | 2/4 | Objection 9 unanswered; 5 partial; FAQPage covers 13 of 19 pricing FAQs |
| S7 Performance | 100% | 2/2 | Core Web Vitals not checked (PSI rate-limited); scored on S7.2 only |
| S8 Accessibility | 0% | 0/2 | No accessibility statement; S8.1 and S8.2 not checked |
| Overall | 68% | 34/50 |
Item results
| Section | Item | Score (0/1/2) | URL or "not found" | Note |
|---|---|---|---|---|
| S1 | S1.1 Security page | 2 | https://boldsign.com/security/ | Encryption, regions, pen testing covered. Responsible disclosure is a separate page not linked from here |
| S1 | S1.2 Compliance and report requests | 1 | https://boldsign.com/soc2-overview/ | SOC 2 Type 2, GDPR, HIPAA, NIST, TX-RAMP pages exist only in the Legal Center. The "PCI DSS Level 1" home badge vs "payments handled by Stripe" needs confirming |
| S1 | S1.3 Support SLA and tiers | 1 | https://boldsign.com/files/shared/boldsign-service-level-agreement-sla.pdf | 24x5, 24 business-hour response, 99.99% uptime; PDF only; no tiers |
| S1 | S1.4 Status page | 2 | https://status.boldsign.com/ | Linked from the security page. Uptime figures conflict across pages |
| S1 | S1.5 Customer logos | 2 | https://boldsign.com/ | Samsonite, Ryanair, Hyatt, Sony and others. Permission not verifiable |
| S1 | S1.6 Third-party reviews | 2 | https://www.g2.com/products/boldsign/reviews | Also https://boldsign.com/boldsign-reviews/ |
| S2 | S2.1 Contact sales and demo in nav | 1 | https://boldsign.com/contact-us/ | Contact Sales in header; no Book a demo |
| S2 | S2.2 Procurement documents | 1 | https://boldsign.com/legalcenter/ | DPA, sub-processors, SOC 2 form, evaluation pack. No questionnaire, W-9 or MSA |
| S2 | S2.3 SSO, roles, audit logs | 2 | https://boldsign.com/esignature-for-enterprise/ | Entra ID SSO and SCIM, custom roles, IP restrictions, audit trails. SAML not named |
| S2 | S2.4 Short forms routed by size | 1 | https://boldsign.com/contact-us/ | 6 fields; no company-size field |
| S3 | S3.1 Deployment options | 1 | https://boldsign.com/esignature-for-enterprise/ | Cloud regions and embedding described; cloud-only not stated |
| S3 | S3.2 Platforms and integrations | 2 | https://boldsign.com/integrations/ | 8 integrations; 5 SDKs |
| S3 | S3.3 API and docs one click | 2 | https://boldsign.com/esignature-api/ | Links https://developers.boldsign.com/ |
| S3 | S3.4 Architecture/data flow | 1 | https://boldsign.com/security/ | Microservices, backups, AATL; no diagram |
| S4 | S4.1 Pricing model | 2 | https://boldsign.com/electronic-signature-pricing/ | Clear tiers. Page source has two different price sets (visible vs JSON-LD) |
| S4 | S4.2 Free/trial eligibility | 2 | https://boldsign.com/electronic-signature-pricing/ | Free plan, 30-day trial, sandbox, non-profit, all with limits |
| S4 | S4.3 Enterprise path | 2 | https://boldsign.com/electronic-signature-pricing/ | Contact Sales, Request a quote, calculator |
| S4 | S4.4 Licensing/renewal terms | 1 | https://boldsign.com/electronic-signature-pricing/ | Auto-renew FAQ only; no terms link; no invoice/PO |
| S4 | S4.5 Cost-at-scale FAQ | 1 | https://boldsign.com/electronic-signature-pricing/ | Estimate FAQ and calculator; no worked per-user vs flat-fee example |
| S5 | S5.1 Labelled/filterable | 0 | https://boldsign.com/customer-stories/ | No filters or labels |
| S5 | S5.2 Midsize+ with outcomes | 1 | https://boldsign.com/customer-stories/ | Quantified outcomes only in small-business stories |
| S6 | S6.1 Objections answered at placement | 1 | see table below | 9 Y, 5 Partial, 1 N |
| S6 | S6.2 FAQPage markup | 1 | https://boldsign.com/electronic-signature-pricing/ | 13 of 19 visible Qs marked up; legality page fully marked; Rich Results Test not run |
| S7 | S7.1 Core Web Vitals | not checked | n/a | PSI API HTTP 429; GSC not authorized |
| S7 | S7.2 No broken key paths | 2 | see raw/pages-checked.json | 14 key pages and the SLA PDF loaded; no full crawl |
| S8 | S8.1 Keyboard and focus | not checked | n/a | No interactive browser |
| S8 | S8.2 Contrast/alt automated check | not checked | n/a | No Lighthouse/axe available |
| S8 | S8.3 Accessibility statement | 0 | not found | Not in the Legal Center; no search result |
Objection coverage
| # | Objection | Listed placement | Answered there? (Y/Partial/N) | FAQ markup? (Y/N/n/a) | URL |
|---|---|---|---|---|---|
| 1 | Legally binding in every country | FAQ | Y | Y | https://boldsign.com/electronic-signature-legality/ |
| 2 | Will this pass our security review | security | Partial | n/a | https://boldsign.com/security/ |
| 3 | Keep data in EU/Canada/Australia | security | Y | n/a | https://boldsign.com/security/ |
| 4 | HIPAA BAA | pricing | Y | n/a | https://boldsign.com/electronic-signature-pricing/ |
| 5 | SSO and provisioning | pricing | Y | n/a | https://boldsign.com/electronic-signature-pricing/ |
| 6 | Cost with hundreds of senders | pricing | Partial | Y | https://boldsign.com/electronic-signature-pricing/ |
| 7 | Over the envelope allowance | pricing | Y | Y | https://boldsign.com/electronic-signature-pricing/ |
| 8 | Which features cost extra | pricing | Y | n/a | https://boldsign.com/electronic-signature-pricing/ |
| 9 | Why less expensive / the catch | FAQ | N | N | not found |
| 10 | Around in five years | FAQ | Partial | N | https://boldsign.com/about-us/ |
| 11 | Moving templates and history | comparison | Y | not checked | https://boldsign.com/docusign-alternative/ |
| 12 | Embedded, branded signing | product page | Y | n/a | https://boldsign.com/esignature-api/ |
| 13 | Salesforce, HubSpot, storage | product page | Y | n/a | https://boldsign.com/integrations/ |
| 14 | Uptime and support commitment | security | Partial | n/a | https://boldsign.com/security/ |
| 15 | Invoice on annual agreement | pricing | Partial | n/a | https://boldsign.com/electronic-signature-pricing/ |
Objection coverage = 9/15 = 0.6 (only full "Y" counts).
Fix list (highest impact first)
| Priority | Fix | Section | Owner role | Effort (S/M/L) |
|---|---|---|---|---|
| 1 | Reconcile uptime figures (99.9% durability / 99.99% SLA / 99.999% API and enterprise FAQ) to the contractual SLA; publish the SLA as HTML linked from the security, pricing and enterprise pages | S1 | Product marketing | S |
| 2 | Add a compliance and trust block to the security page: SOC 2 overview and request form, HIPAA, GDPR, NIST, TX-RAMP, responsible disclosure; confirm "PCI DSS Level 1" badge wording | S1 | Product marketing | M |
| 3 | Add "Book a demo" with a scheduler to the main navigation | S2 | Marketing ops | S |
| 4 | Create a procurement page: DPA, sub-processors, SLA, Terms, security questionnaire, W-9 and MSA on request | S2 | Marketing ops | M |
| 5 | Add a company-size or expected-senders field to the contact form and route midsize+ to sales | S2 | Marketing ops | M |
| 6 | Add FAQ answers for objections 9 (why less expensive), 10 (longevity and data export) and 15 (invoice/PO) | S6 | SEO lead | S |
| 7 | Extend pricing FAQPage markup to all 19 visible questions; validate with the Rich Results Test | S6 | SEO lead | S |
| 8 | Add a worked per-user vs flat-fee cost example; link Terms, renewal and upgrade terms from pricing | S4 | Product marketing | S |
| 9 | Tell product marketing about the two price sets in the pricing page source (visible vs JSON-LD) | S4 | Product marketing | S |
| 10 | State the deployment model plainly (cloud SaaS, regions, embedded via API); publish a data-flow diagram | S3 | Product marketing | M |
| 11 | Label and filter customer stories by industry and size; commission 2–3 midsize+ stories with quantified, customer-reported outcomes | S5 | Product marketing | L |
| 12 | Publish an accessibility statement and VPAT/ACR | S8 | Web developer | M |
Not checked
- S7.1 Core Web Vitals: the PageSpeed Insights API returned HTTP 429 Too Many Requests. Google Search Console wasn't authorized for this run.
- S8.1 Keyboard navigation and focus: no interactive browser was available.
- S8.2 Contrast and alt text (Lighthouse/axe): no browser, and the PSI API was rate-limited.
- Partly checked:
- S6.2: the Rich Results Test was not run, so FAQPage presence was read from the page source only.
- Objection 11: FAQ markup on /docusign-alternative/ wasn't checked.
- S7.2: 14 key pages only, not a full crawl.
- Mobile rendering wasn't audited, only desktop HTML.
- Logo permissions can't be verified from the public site.
Proposed changes (need approval)
All of these are website changes. None were made.
Reconcile the uptime figures and publish the SLA as an HTML page linked from the security, pricing and enterprise pages (S1.3, S1.4).
Add a compliance/trust block to the security page and confirm the PCI DSS badge wording (S1.1, S1.2).
Add "Book a demo" to the main navigation (S2.1).
Build a procurement documents page (S2.2).
Add a company-size field and routing to the contact form (S2.4).
Name SAML/OIDC and the supported IdPs; say whether an admin activity log exists (S2.3).
Add a cloud-only deployment statement and a data-flow diagram (S3.1, S3.4).
Fix the pricing page source so the JSON-LD prices match the visible table; add terms/renewal/invoice links and a worked cost example (S4.1, S4.4, S4.5).
Add customer story labels and filters; add midsize+ outcome stories (S5.1, S5.2).
Add the missing FAQs and extend FAQPage markup (S6.1, S6.2).
Publish an accessibility statement and VPAT (S8.3).
Repo follow-up (not edited in this run):
_reference/objections/boldsign.mdhas TODOs this audit can close:- SOC 2 request link: https://boldsign.com/compliance-request-form/
- HIPAA page: https://boldsign.com/hipaa-overview/
- SLA: https://boldsign.com/files/shared/boldsign-service-level-agreement-sla.pdf (99.99% monthly)
- Migration proof: https://boldsign.com/docusign-alternative/
The owner should update it after review.
Data sources
- Live site, fetched logged out on 2026-11-10 (desktop HTML via WebFetch). The 14 pages and the SLA PDF are listed in
raw/pages-checked.json. _reference/objections/boldsign.md(15 objections) and the BoldSign section of_reference/pricing-and-licensing.md.- Web search: the BoldSign accessibility statement (no boldsign.com result) and BoldSign migration content.
- PageSpeed Insights API: failed (HTTP 429).
- Raw files:
raw/pages-checked.json,raw/objection-coverage.csv. - The run parameters' date range (2026-10-13 to 2026-11-09) doesn't apply to this point-in-time site audit. Metrics use the audit date as their period.
- Remember to add these results to the team's shared results log (location TBD).
Findings
| ID | Item | Status | Severity | Effort | Recommendation | Checklist |
|---|---|---|---|---|---|---|
| S5.1 | Case studies filterable or labelled by industry and company sizeneeds approval Score 0. https://boldsign.com/customer-stories/ is a grid of cards with no filter, sort, search, industry label or company-size label. | fail | medium | M | Add industry and company-size labels and filters to the customer stories page. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S8.3 | Accessibility statement publishedneeds approval Score 0. Not found. The Legal Center (https://boldsign.com/legalcenter/) lists no accessibility statement or VPAT, and a web search for a BoldSign accessibility statement returned no boldsign.com result. | fail | medium | M | Publish an accessibility statement (WCAG 2.2 AA target, known gaps, contact) and a VPAT/ACR for the signing experience, and link both from the Legal Center. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S1.2 | Compliance certifications with how to request reportsneeds approval Score 1. SOC 2 Type II (https://boldsign.com/soc2-overview/, request form https://boldsign.com/compliance-request-form/), GDPR, HIPAA (https://boldsign.com/hipaa-overview/), NIST 800-53 and TX-RAMP Level 2 pages exist, but only in the Legal Center. The security page names SOC 2 and GDPR, does not mention HIPAA, and does not explain how to request the SOC 2 report. The home page shows a 'PCI DSS Level 1' badge, while the security page says card payments are handled by Stripe and card data never reaches BoldSign servers. That reads as the payment processor's certification, not BoldSign's. | warn | high | M | Add a compliance block to the security page (or a trust-center hub) linking SOC 2 overview and request form, HIPAA, GDPR, NIST and TX-RAMP. Ask product marketing to confirm the PCI DSS Level 1 badge wording. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S1.3 | Support SLAs and support tiers statedneeds approval Score 1. A Support and Maintenance SLA PDF (last updated Feb 2025) at https://boldsign.com/files/shared/boldsign-service-level-agreement-sla.pdf states 24x5 support, guaranteed response in 24 business hours, 24-hour escalation response, and 99.99% monthly uptime with exclusions. It is linked only from the Legal Center as a PDF. The security page gives no SLA and no support tiers are described. | warn | high | S | Publish the SLA as an HTML page linked from the security, pricing and enterprise pages, and state which plans it covers. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S2.1 | Contact sales and Book a demo visible in main navigationneeds approval Score 1. The header has a 'Contact Sales' button (https://boldsign.com/contact-us/) but no 'Book a demo' or 'Request demo'. A demo / walkthrough CTA appears only on https://boldsign.com/esignature-for-enterprise/. The contact page points to self-help demos or contacting sales. | warn | high | S | Add a 'Book a demo' CTA to the main navigation, with a scheduler. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S2.2 | Procurement and security-review documents offeredneeds approval Score 1. Offered: DPA (https://boldsign.com/dpa/), sub-processors (https://boldsign.com/subprocessors/), Terms of Use, SOC 2 request form, Security Management Report PDF, and an 'enterprise evaluation pack (PDF)' on the enterprise page. Not found: a standard security questionnaire (e.g. CAIQ/SIG), W-9/vendor forms, MSA. All are spread across the Legal Center with no procurement hub. | warn | high | M | Create a single procurement/security-review page that links these documents and offers a pre-filled questionnaire, W-9 and MSA/order form on request. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S6.1 | Every objection in _reference/objections/boldsign.md answered at its listed site placementneeds approval Score 1. 9 of 15 objections are fully answered at their listed placement, 5 are partial (#2 security review, #6 cost at scale, #10 vendor longevity, #14 uptime/support, #15 invoice/annual) and 1 is not answered (#9 why less expensive). See raw/objection-coverage.csv. | warn | high | M | Add FAQ answers for #9, #10 and #15. Put the SOC 2 request path and the SLA on the security page (#2, #14). Add a worked cost example (#6). | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S2.4 | Forms are short and route by company sizeneeds approval Score 1. https://boldsign.com/contact-us/ has 6 inputs plus reCAPTCHA (name, email, company, optional phone, interest App/API/Both, message). It is short but has no company size, seat or volume field, so it can't route by size. | warn | medium | M | Add one company-size or expected-senders field and route midsize+ submissions to sales with a scheduler. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S3.1 | Deployment options stated plainlyneeds approval Score 1. The enterprise page and security page describe cloud hosting with region choice (US, EU, Canada, Australia) and embedded signing via the API. No page states plainly that BoldSign is cloud-only (no self-hosted or private-cloud option). The API page doesn't mention deployment. | warn | medium | S | Add one plain sentence on the enterprise and security pages: deployment model, regions and embedding options. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S3.4 | Architecture or data-flow overview for IT/securityneeds approval Score 1. The security page describes a containerized microservice architecture, a multinode fault-tolerant database with hourly backups kept 30 days, and AATL-signed documents with LTV. There is no data-flow diagram on the security, enterprise or API pages. | warn | medium | M | Publish a one-page architecture and data-flow diagram (where documents are stored, processed and sent, plus sub-processors) for security reviewers. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S4.4 | Licensing, renewal and upgrade terms linkedneeds approval Score 1. A FAQ entry covers auto-renewal and cancellation. The pricing page doesn't link Terms of Use or upgrade/downgrade terms; the Legal Center is reachable only from the navigation. Invoice and purchase-order payment isn't mentioned. | warn | medium | S | Link Terms of Use, the SLA and the renewal/upgrade policy from the pricing page, and state whether annual invoice/PO billing is available. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S4.5 | Pricing FAQ answers cost-at-scale questionsneeds approval Score 1. The pricing FAQ includes 'How do I estimate my cost?', 'What is the Pay As You Go option in BoldSign?', 'How are envelopes counted?' and 'Which plan is best for me and my team?', and links a calculator. The audit found no worked example comparing per-user plans with the flat-fee plan for a large sender base. | warn | medium | S | Add a worked example (for example 200 occasional senders vs 20 frequent senders) contrasting Business and Premium, without hard-coding prices outside the price table. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S5.2 | Some case studies show midsize+ organizations with customer-reported outcomesneeds approval Score 1. Of the first 15 stories, none report a quantified outcome, and most are small businesses or individuals. Quantified outcomes appear only in smaller-company stories further down (for example 'saving $1,000+ yearly', 'nearly 30x'). Payroc and NHPCO (enterprise page) are larger organizations, but the audit saw no quantified outcomes for them. | warn | medium | L | Commission two or three midsize+ stories with customer-reported, quantified outcomes and feature them on the enterprise page. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S6.2 | FAQPage structured data on visible FAQ answers, validatedneeds approval Score 1. The pricing page FAQPage JSON-LD covers 13 of the 19 visible questions. It leaves out 'Who is a user?', 'How does API pricing work?', 'How are envelopes counted?', 'Can I test BoldSign's API?', 'Will my documents be secure?' and 'Which plan is best for me and my team?'. The legality page has FAQPage markup matching its 13 questions. The Rich Results Test was not run (no tool available in this run). | warn | medium | S | Extend the pricing-page FAQPage markup to all visible questions, then validate with the Rich Results Test. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S7.1 | Core Web Vitals Good on home, pricing, product and demo pages Not checked. The PageSpeed Insights API returned HTTP 429 Too Many Requests, and Google Search Console needs authorization that isn't available in this run. | not-checked | medium | S | Rerun with PageSpeed Insights (with an API key) or with GSC Core Web Vitals access. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S8.1 | Keyboard navigation and visible focus on navigation and forms Not checked. This run had no interactive browser, so keyboard navigation couldn't be tested. | not-checked | medium | S | Test manually or with a browser-driven tool on the next run. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S8.2 | Color contrast and alt text pass an automated check against WCAG 2.2 AA Not checked. Lighthouse/axe couldn't be run: there was no browser, and the PageSpeed Insights API was rate-limited (HTTP 429). | not-checked | medium | S | Run Lighthouse or axe on home, pricing, contact-us and enterprise pages. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S1.1 | Security page: data handling, encryption, hosting regions, pen testing, responsible disclosureneeds approval Score 2. https://boldsign.com/security/ covers AES-256 double encryption, GCP/Azure hosting in US East, EU, Canada and Australia, regular penetration testing plus third-party code reviews, WAF, backups. The security page itself has no disclosure process, but a Responsible Disclosure page exists at https://boldsign.com/responsible-disclosure/ (linked from the Legal Center). The home page links to /security-policy/. | pass | high | S | Link the Responsible Disclosure page from the security page. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S1.4 | Uptime or status page linkedneeds approval Score 2. https://status.boldsign.com/ is linked from the security page and the SLA. Uptime figures conflict across pages: the security page cites '99.9% durability over a year', the SLA says 99.99%, the API page cites 99.999% uptime, and the enterprise page says '99.99% monthly' in the body and 99.999% in its FAQ. | pass | medium | S | Tell product marketing today; align every uptime figure to the contractual SLA. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S1.5 | Customer logos and references, with permission Score 2. The home page and https://boldsign.com/esignature-for-enterprise/ show logos for Samsonite, Ryanair, Hyatt, Sony, Crumbl Cookies, Payroc and Cost Plus. Permission can't be verified from the public site. | pass | medium | S | None for the site. Product marketing confirms logo permissions are on file. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S2.3 | SSO/SAML, role-based access and audit logs explainedneeds approval Score 2. The enterprise page, security page and pricing page cover SSO (Business plan and up), user provisioning with Microsoft Entra ID via SCIM 2.0 (pricing page), custom roles and permissions, IP restrictions, and per-document audit trails. 'SAML' isn't named and no organization-wide admin audit log is described. | pass | medium | S | Name the SSO protocols (SAML/OIDC) and supported IdPs explicitly. Say whether an admin activity log exists. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S4.1 | Pricing model clear: tiers, per user/flat, what's includedneeds approval Score 2. https://boldsign.com/electronic-signature-pricing/ shows Essential (free), Growth and Business (per user), Premium (flat fee, unlimited users, 250 envelopes/month) and Enterprise API (base plus usage), with envelope allowances and a feature table. The page source holds two different price sets for Growth/Business/Premium: the visible table and the JSON-LD offers. | pass | medium | S | Tell product marketing about the two price sets in the page source so the JSON-LD matches the visible prices. Don't guess the correct values. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S4.3 | Enterprise/volume path with contact-sales CTA Score 2. The pricing page has 'Contact Sales' and 'Request a quote' (https://boldsign.com/contact-us/), plus a pricing calculator (https://boldsign.com/esignature-pricing-calculator/). | pass | medium | S | None. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S1.6 | Third-party reviews linked Score 2. The home page links G2 (https://www.g2.com/products/boldsign/reviews), the Company menu has 'Customer Reviews' (https://boldsign.com/boldsign-reviews/), and the enterprise page shows a G2 badge. The home page JSON-LD has an aggregate rating of 4.7 from 474 reviews but doesn't name the source. | pass | low | S | Optional: add Capterra or another second review source. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S3.2 | Supported platforms, frameworks and integrations listed Score 2. https://boldsign.com/integrations/ lists Salesforce, HubSpot, Xero, Zapier, Power Automate, Dropbox, Google Drive and OneDrive. https://boldsign.com/esignature-api/ lists SDKs for .NET, Python, Java, Node.js and PHP, plus a Postman collection. | pass | low | S | None. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S3.3 | API and docs one click from product pages Score 2. The home page has 'Explore eSignature API'. The API page links https://developers.boldsign.com/ and the integrations page links the getting-started guide. | pass | low | S | None. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S4.2 | Free, trial or community option explained with eligibility Score 2. The pricing page explains: Essential free plan (25 envelopes/month, 5 until business details are verified for personal email), a 30-day trial with no credit card and reduced limits for public email domains, a free API sandbox (watermarked, deleted after 14 days), and non-profit terms. | pass | low | S | None. | demand-gen/web/website-buyer-fit-audit.md#checklist |
| S7.2 | No broken links or 404s on key paths Score 2, limited scope. All 14 key pages fetched in this run returned content: home, security, pricing, contact-us, legalcenter, customer-stories, esignature-api, integrations, electronic-signature-legality, soc2-overview, hipaa-overview, about-us, esignature-for-enterprise and docusign-alternative, plus the SLA PDF. This was not a full link crawl. | pass | low | S | Run a full crawl (for example Screaming Frog) on the next audit. | demand-gen/web/website-buyer-fit-audit.md#checklist |
Metrics
| Metric | Value | Previous | Change | Period | Dimensions |
|---|---|---|---|---|---|
| Buyer-fit score web.buyer_fit_score | 68.0% | – | – | 2026-11-10 – 2026-11-10 | |
| Buyer-fit section score web.section_score | 83.3% | – | – | 2026-11-10 – 2026-11-10 | section: S1 |
| Buyer-fit section score web.section_score | 62.5% | – | – | 2026-11-10 – 2026-11-10 | section: S2 |
| Buyer-fit section score web.section_score | 75.0% | – | – | 2026-11-10 – 2026-11-10 | section: S3 |
| Buyer-fit section score web.section_score | 80.0% | – | – | 2026-11-10 – 2026-11-10 | section: S4 |
| Buyer-fit section score web.section_score | 25.0% | – | – | 2026-11-10 – 2026-11-10 | section: S5 |
| Buyer-fit section score web.section_score | 50.0% | – | – | 2026-11-10 – 2026-11-10 | section: S6 |
| Buyer-fit section score web.section_score | 100.0% | – | – | 2026-11-10 – 2026-11-10 | section: S7 |
| Buyer-fit section score web.section_score | 0.0% | – | – | 2026-11-10 – 2026-11-10 | section: S8 |
| Objections answered on site web.objection_coverage | 60.0% | – | – | 2026-11-10 – 2026-11-10 |
Folder: reports/publish/boldsign/website-buyer-fit-audit/20261110-0806_website-buyer-fit-audit_boldsign_bec1