Contact

Contact sales

Plans, quotes and Enterprise, API or Dedicated pricing.

Start free Contact us

What happens after you send your message

The WQ3 team reviews your message and replies by email as soon as possible on business days.

We review it

Your request goes to the right team based on the topic you chose.

We get in touch

We reply by email or phone to understand your needs and agree the next step.

We propose a fit

A quote, a walkthrough session or an integration plan, depending on your request.

Helpful details to include

The kind of documents you sign, roughly how many users, the systems you want to connect, and any legal or security requirements your organisation has.

Map signing requirements to each participant

Start with participant roles rather than a plan label. WQ3 offers three levels: electronic signature, remote signing and token signing, and allows different levels for different signers in the same document. For a useful sales discussion, identify which participants can use an electronic signature and which must meet your organisation’s digital-certificate requirements.

Keep identity verification separate from that choice. eKYC is an account-verification add-on that can be required with any signing level, not a fourth level. This distinction helps frame your requirements when evaluating an agreement involving participants with different authority or evidence requirements.

Turn a walkthrough into a practical evaluation

Choose a representative workflow and define what a walkthrough should demonstrate. Useful checkpoints include how each participant receives their private invitation, what they can access, and what evidence remains when signing is complete. Use fictional names and non-sensitive wording rather than sending confidential agreements in an initial enquiry.

Evaluate the full document journey, not just the signing moment. WQ3 locks documents once sent, records actions, and provides an audit trail and completion certificate for completed documents. Ask how these controls relate to your internal review, record-keeping and handover steps, then assess them against your acceptance criteria.

Structure integration and deployment questions

For Enterprise, API or Dedicated discussions, separate the desired outcome from the proposed implementation. Describe where a signing request should originate, where your team needs to track progress, and where completed documents should go. This makes the workflow discussable without assuming a ready-made integration exists.

Distinguish essential requirements from preferences that can wait. Bring open questions about authentication, permissions, data responsibilities and deployment constraints for confirmation during scoping. Do not assume that a product label establishes support for a particular system, hosting arrangement or service commitment; ask for the proposed scope to identify what is included and what needs further review.

Give reviewers clear acceptance criteria

Prepare a shared evaluation checklist for procurement, legal, security and operational stakeholders. Legal reviewers can identify relevant agreement types and jurisdictions, while security reviewers can specify the evidence they need about access controls, document integrity and personal-data handling. WQ3’s compliance pages describe alignment with named laws, but legal suitability still depends on the requirements applicable to your use.

Include what a reviewer will need after signing. WQ3 provides a public verification page, a reference and QR code, and a document-fingerprint comparison to check authenticity without an account. Discuss how this evidence would support your organisation’s record-keeping, review and dispute-handling procedures rather than judging the purchase only on signing convenience.