Good questions, straight answers.

Qasha is the connected revenue workspace: pipeline and outreach, quotes, agreements and e-signatures, onboarding, billing, collections and revenue, kept in one record of every customer.

Teams who sell, onboard and bill business customers: founders, sales, operations and compliance, and finance.

Team is $353 a month for up to 5 users, Business is $753 a month for up to 15 users, and Enterprise is priced for your team. Every plan includes every feature.

This website is. The Qasha app is in English today, including the signing page and the emails and PDFs Qasha creates. Your own documents, quotes and agreements can be in any language.

No. This site sets no cookies for analytics, advertising or tracking. The only cookie it can set remembers the language you choose.

No. A mailbox connection belongs to the person who authorized it. Colleagues share the conversation in Qasha, not your credentials.

The reply is captured and sorted, and the follow-up sequence for that conversation stops. If the inbox could not be checked, the next step waits instead of assuming nobody replied.

No. Automatic acknowledgements use a fixed template you approve, for reply types you choose, within limits you set. Pricing and tailored answers stay with your people.

Yes. Fixed and usage charges, tiers, volume rates, percentages, minimums, caps, trials and setup fees can be combined in one set of terms.

Nothing changes for them. The accepted terms are kept as they were signed, and catalog edits never rewrite an earlier agreement.

Yes. When a policy applies, the document cannot be issued until it is approved, and the approval is for that exact version.

In most countries, for most agreements, yes. Qasha confirms each signer with a code sent to their email, records when and how they signed, and seals the signed copy so any later change shows. Some documents and some institutions still require wet ink or a qualified digital signature, so check what applies to yours.

No. Each signer receives a secure link and confirms who they are with a one-time code sent to their email.

The signed copy and a certificate of completion naming who signed and when. The audit trail with IP addresses and devices is kept for your team and never sent to them.

Qasha straightens it, reads its words and finds what it can, then asks you to check that page closely. You can always place or adjust fields by hand.

The signed copy is the bank’s own form, page for page, with the fields filled in and the signatures in place, sealed so any change shows. Some institutions still insist on wet ink; it is worth checking theirs.

Yes. Fill in your part yourself, and only the fields you assign go to the signers.

No. Qasha coordinates the compliance work and shows what evidence is still missing. Checking it and approving the customer stay with your reviewer.

The colleagues involved in it. A case is not visible to the whole workspace by default.

Yes. Fixed and usage charges, credits and adjustments can appear on the same invoice for the same service period.

Their accepted terms are kept as signed. Catalog changes never allocate credit or change an earlier agreement automatically.

Yes. Their billing portal shows this period’s usage and where the next invoice is heading.

Only under a reminder policy your team has reviewed, and each attempt’s status is visible.

Card payments run through Stripe today, from the invoice and the billing portal.

No. Qasha keeps the operating record of what was agreed, billed, paid and recognized, and connects to QuickBooks Online and Xero for your general ledger.

Not silently. A closed period keeps its figures; corrections are made with a recorded reversal.

No. Drafts are reviewed and sent by a person. Automatic acknowledgements only use a fixed template you approve, within limits you set.

Claude, Gemini or another model with a compatible interface. A workspace can set a default, and each person can connect their own.