Paperform

Planning and scoping (1–5 days)

Define objectives: What forms are needed (lead capture, surveys, payments, bookings, quizzes), target audience, and required fields.

Data and workflow mapping: Where form submissions go (CRM, email, spreadsheet, Zapier), and how data should be routed.

Compliance considerations: Privacy (GDPR/CCPA) and payment requirements if collecting payments.

Set up and configuration (0–5 days)

Account provisioning: Create user accounts, teams, and permission levels.

Form creation: Build initial forms using templates or from scratch.

Branding and customization: Add logos, color schemes, fonts, and custom CSS if needed.

Integrations: Connect with apps (CRMs like HubSpot, CRM/marketing stacks, email tools, payment gateways like Stripe/PayPal, automation platforms like Zapier).

Payment setup: If accepting payments, configure products, pricing, tax, refunds, and webhooks.

Notifications and workflows: Set up autoresponders, internal notifications, conditional logic, and multi-step forms.

Testing and quality assurance (2–7 days)

Form testing: End-to-end tests for submissions, payments, and data routing.

Edge cases: Conditional logic, required fields, validations, and offline/embedded form behavior.

Security checks: Validate data handling, encryption, and access controls.

Deployment and go-live (0–3 days)

Publish forms: Deploy on websites, landing pages, or share links.

Monitoring: Ensure analytics, form submissions, and integrations are functioning in production.

Training and handover (1–3 days)

Team training: How to create/edit forms, manage submissions, and use automations.

Documentation: Quick-start guides or internal wiki for your team.

Typical total time

For small to mid-size deployments (a handful of forms with standard integrations): 1–2 weeks from planning to go-live.

For larger or more complex setups (multi-brand forms, extensive automations, custom CSS/branding, or enterprise requirements): 2–6+ weeks depending on complexity and stakeholder availability.

Form-level customization

Branding: logos, colors, fonts, background images.

Form fields: a wide range of field types (text, email, number, date, file uploads, rating, multiple choice, dropdown, file attachments).

Logic and validations: conditional logic, skip logic, validation rules, required fields.

Design: custom CSS (in Pro/Business/Enterprise plans) to tailor layout, spacing, and responsive behavior.

Styling options: custom themes and templates; ability to clone/duplicate forms.

Payment and commerce customization

Payment gateways: Stripe, PayPal (and sometimes others via integrations).

Pricing models: one-time payments, subscriptions, product options, discounts, taxes, coupons

Order flows: multi-step checkout, order summaries, invoice generation.

Integrations and automation

Native integrations: email marketing, CRMs, payment processors, analytics.

Automation platforms: Zapier, Integromat/Make for broader workflows.

Webhooks: for real-time data delivery to custom systems.

Data routing: route submissions to Google Sheets, Airtable, CRM contacts, or support systems.

Data handling and security

Access controls: user roles (admin, editor, viewer), team permissions.

Data retention and export: export formats (CSV, Excel, JSON), backup considerations.

Compliance: GDPR/CCPA readiness, data residency options via enterprise offerings.

Subscription plans (typical structure)

Monthly vs annual: Annual plans often offer discounts.

Plan tiers commonly include:

• Basic/Standard: core form builder, limited submissions, basic branding.

• Pro/Business: higher submission limits, more integrations, conditional logic, custom branding, basic payments.

• Enterprise/Custom: extensive admin controls, SSO, higher data limits, priority support, custom SLAs.

Common features across tiers:

Form creation and hosting

Submissions and storage limits

Basic integrations (email, basic CRM)

Standard payment collection (Stripe/PayPal) on higher tiers

Customer support via email; phone support typically at higher tiers

Typical price ranges (as of 2024–2025, approximate; verify current pricing)

Standard/Basic: often 12–25permonth(billedmonthly)oraround12–25permonth(billedmonthly)oraround10–15 per month when billed annually

Pro/Business: roughly 25–60permonth(billedmonthly)or25–60permonth(billedmonthly)or20–45 per month annually

Enterprise/Custom: pricing varies widely; often $100–$500+ per user per month or negotiated per-project; may include dedicated success manager, custom onboarding, and advanced security

Setup fees

Paperform generally does not charge a separate, mandatory setup fee for standard onboarding.

Some enterprise engagements or custom integrations may involve professional services fees for initial configuration, data migration, or custom development. These are typically quoted per project and can range from a few hundred to several thousand dollars depending on scope.

Maintenance and ongoing costs

Ongoing subscription is the primary ongoing cost.

Additional costs may include:

• Premium add-ons or higher submission allowances

• Increased workflow run limits or API usage in higher tiers

• Extra seats/users beyond included team members

• Third-party integration costs (e.g., subscription fees for connected apps, if applicable)

Support charges

Standard support is usually included with the plan (email or ticket-based).

Priority or enterprise-level support may incur higher-tier pricing or be included with Enterprise plans.

Some partners or onboarding vendors may offer paid support packages for dedicated onboarding, custom training, or 24/7 support.

Self-service resources:

• Knowledge base articles, product docs, and step-by-step guides.

• Tutorial videos and walkthroughs for common use cases (form creation, payments, automations, embed options).

Getting-started guides: Quick-start templates and onboarding checklists to accelerate initial form builds and integrations.

Product tours and in-app help: Guided tours within the platform to surface key features and best practices.

Community and resources: Access to community forums or user groups (if offered by Paperform or via partners).

Email/ticket support: Standard support to answer questions and resolve issues.

Priority/enterprise support: Higher-tier plans often include faster response times, SLA-backed support, and potentially dedicated success contacts.

Phone support: Often reserved for higher-tier or enterprise customers; availability varies by region and contract.

Onboarding support packages: Some customers may purchase or be allocated a structured onboarding plan with a success manager, especially in Enterprise or with partners.

Role-based access control (RBAC): Admins assign roles (admin, editor, viewer) to limit what users can see and do.

Team and user provisioning: Centralized management of users, invitations, and permissions.

Single sign-on (SSO): Enterprise plans may offer SSO (SAML) for integrating with your IdP.

Data in transit: TLS/SSL encryption for data moving between users, Paperform servers, and connected services.

Data at rest: Encryption of stored form submissions and assets on Paperform’s storage.

Secure data processing: Practices around how submissions are handled, stored, and transmitted to connected apps (e.g., CRMs, spreadsheets, payment gateways).

GDPR/CCPA readiness: Templates and features to support data subject requests, consent capture, and data processing agreements.

Data residency options: Enterprise offerings may include choices for data storage location in certain regions.

Auditability: Logs of user actions and form submission events for monitoring and compliance.

Regular product updates: Paperform typically rolls out feature enhancements, fixes, and incremental improvements on a scheduled cadence (monthly or quarterly in many SaaS products), with additional hotfixes as needed.

Major releases: When significant features or architectural changes are introduced, there may be a broader release cycle and updated documentation.

In-app notifications: Alerts within the product about new features or changes.

Release notes: Public or partner-facing changelogs detailing what’s new, what’s fixed, and any impact to workflows.

Impact guidance: Documentation on any required changes (for example, if a field type changes, or a new integration requires reconfiguration).

Backward compatibility notices: Warnings if updates affect existing forms, workflows, or integrations.

Migration paths: Guidance or tools to help users transition to new features or API changes.

Beta/early access programs: Optional programs for customers to try new features before general release.

Customer ownership of data: Submissions, responses, form constructs, and related data are generally owned by the customer. Paperform acts as a data processor, hosting data on behalf of the customer.

Permissible use: Paperform’s terms typically grant the service to process data strictly to provide the platform functionalities (form building, submissions, integrations, payments) and to operate and improve the service in accordance with your contract and privacy commitments

Data processing agreements (DPA): For organizations handling personal data, a DPA is typically available or required, outlining roles, subprocessors, data security, breach notification, and data handling obligations in line with GDPR/CCPA and other regulations.

Access and export: Customers usually can export submissions and form data in standard formats (CSV, Excel, JSON) from the dashboard. This enables migration to other systems or backups.

Data exports by form or bulk: Options often exist to export individual form submissions or bulk exports across forms.

APIs and webhooks: If you have ongoing needs, Paperform’s API and webhooks typically allow real-time or scheduled data extraction to your systems, supporting portability via developer-built integrations.

Data deletion and retention controls: You should be able to delete individual submissions or purge data according to retention policies. Retention settings and data destruction windows are commonly configurable.

Seat/user scaling: Plans typically include a base number of team members with the option to add more seats/users at published per-seat prices.

Usage-based scaling: Submissions, form views, or API calls may have tiered limits; higher tiers unlock greater quotas.

Plans and tier changes: Upgrading is straightforward (pro-rated adjustments). Downgrading may be restricted to certain times (e.g., at renewal) or may require review due to data/usage limits.

Data and feature access during scaling: When moving between tiers, access to features (e.g., advanced analytics, admin controls, SSO) changes according to the new plan.

Professional services for migration: For complex migrations or large-scale deployments, onboarding or migration assistance may be offered as a paid service

Term length: Monthly vs annual commitments; annual plans typically offer discounts but reduce flexibility.

Upgrade/downgrade windows: Some contracts restrict mid-term changes or require adjustment at renewal date.

Renewal cadence: Typically monthly or annual renewals; annual terms often renew automatically unless canceled.

Price changes at renewal: If price adjustments apply, you should receive prior notice before renewal and have an opportunity to accept the new terms or switch plans.

Renewal notices: Many contracts include a mandated notice period for non-renewal (e.g., 30–60 days prior to end of term).

Cancellation during term: Terms vary; some plans allow cancellation at any time with prorated refunds for unused time, while others may not offer refunds for partial periods.

Data portage after cancellation: Post-cancellation, customers typically retain access to data for a defined grace period to export data, after which data is archived or deleted per policy.

Deactivation vs termination: Cancellation usually leads to deactivation of accounts and removal of access at end of term.

Renewal cadence: Typically monthly or annual renewals; annual terms often renew automatically unless canceled.

Price changes at renewal: If price adjustments apply, you should receive prior notice before renewal and have an opportunity to accept the new terms or switch plans.

Renewal notices: Many contracts include a mandated notice period for non-renewal (e.g., 30–60 days prior to end of term).

Cancellation during term: Terms vary; some plans allow cancellation at any time with prorated refunds for unused time, while others may not offer refunds for partial periods.

Data portage after cancellation: Post-cancellation, customers typically retain access to data for a defined grace period to export data, after which data is archived or deleted per policy.

Deactivation vs termination: Cancellation usually leads to deactivation of accounts and removal of access at end of term.