NewSign anything, sealed. Fill and sign any PDF in place, scans included, with every signed copy sealed.See what shipped
Book a demo
ProductPipeline & outreachQuotes & pricingE-signatureFill & sign any PDFOnboarding & complianceBilling & usageCollections & paymentsRevenue recognitionAI & agentsIntegrations
SolutionsFoundersSales teamsFinance teamsOperations & complianceQuote to cashUsage-based billingForms from banks & partnersSaaSFintech & paymentsAI companies
DevelopersOverviewMCP serverWebhooks
ResourcesGuidesPricing calculatorSecurityWhat’s newGlossaryFAQ
CompanyAboutPrinciplesContactBrand
PricingBook a demo
Principles

The rules every feature has to follow.

Qasha handles agreements, signatures and money, where a small mistake costs trust. These eight rules decide how it behaves, and each one shows up in the product today.

  1. 01

    Evidence, not promises

    Anything Qasha says happened, it can show. A signature carries its proof, a figure leads back to its source, and a signed copy shows any change made to it.

    • Every signed copy is sealed with a trusted RFC 3161 timestamp.
    • Signers receive a certificate of completion.
    • Each figure in the ledger leads back to the agreement and invoice behind it.
  2. 02

    People decide

    Software drafts, checks and reminds. Commitments to customers, such as prices, approvals and what gets sent, stay with people.

    • Assistant drafts are reviewed and sent by a person.
    • When an approval policy applies, nothing is sent until that exact version is approved.
    • Automatic acknowledgements only use a template you approve, within limits you set.
  3. 03

    One record

    What was said, agreed, billed and paid belongs to one record of the customer, not to five tools that disagree.

    • Invoices are priced from the terms the customer accepted.
    • The conversation, the agreement and the invoices sit on the same customer.
    • Customers see their invoices, usage and signed agreements in one portal.
  4. 04

    Nothing changes behind your back

    What was agreed, sent or closed stays as it was. Corrections are new entries with a reason, never quiet edits.

    • Accepted terms are kept as signed; catalog changes never rewrite them.
    • Invoices are corrected with credit notes.
    • A closed period keeps its figures; corrections are recorded reversals.
  5. 05

    Personal by default

    Mailboxes, AI models and app connections belong to the person who authorized them, and documents to the people allowed to see them.

    • Each person sends from their own mailbox.
    • Each person can connect their own AI model.
    • A personal token acts with exactly its maker’s access.
  6. 06

    Your working stays yours

    Customers and signers see what they need to act. Your team keeps the evidence, the notes and the reasons.

    • The audit trail, with IP addresses and devices, stays with your team.
    • Restricted passages reach only the people allowed to read them; others receive a copy with them barred.
    • Signers never need an account.
  7. 07

    Say what syncs, and what didn’t

    Every connection shows exactly what it does. When something fails, you see it, with the reason, instead of finding out from a customer.

    • Each integration lists what it supports.
    • Every event sent to a connected system is kept, with how it went.
    • A failed delivery shows its last error and can be sent again by hand.
  8. 08

    When unsure, stop

    If Qasha can’t be certain an action didn’t happen, it doesn’t try again on its own. It holds the case for a person to look at.

    • A payment whose outcome is uncertain is held for review, never retried.
    • A payment counts once its settlement is confirmed.
    • Credit is granted once and only once.

Bring the whole deal into one place.

We’ll walk through your process, from first email to recurring invoice, and show you where Qasha fits.

Book a demo See pricing