Ninety seconds to verify. Three days to sign — Verified in ninety seconds, then three days for a stamped agreement — Signzy closes the step that stays manual after everything else in the journey is digital.
Buy through TechBag
Same software. Better outcome — at a lower cost.
How it’s rated
Full scoreboard ↓Quick answer
This page covers Digital Contracting — stamping and signature. The rest of the marketplace:
Most product pages skip this. We start here — so you buy a capability, not a buzzword.
Stamp, sign and execute, inside the same journey — Contract 360 for the document lifecycle, eStamping for state-correct duty, and Aadhaar eSign for a legally valid signature.
What consolidation actually replaces, dimension by dimension.
| Dimension | A scanned signature on a PDF | Digital Contracting (Signzy) |
|---|---|---|
| The last step | Three days, manual | Minutes, in the same journey |
| Stamp duty | Legal review per state | Computed for the state and instrument |
| The signature | A scanned image on a PDF | Aadhaar eSign, valid under the IT Act |
| Multi-party | Email chains and reminders | Sequenced routing with status |
| If disputed | Prove who signed, somehow | An execution record with the duty paid |
| What it is NOT | — | Not your counsel — it executes, not drafts |
It EXECUTES agreements; your counsel drafts them and characterises each instrument. An instrument categorised wrongly gets stamped correctly for the wrong category, which protects you no better than not stamping it.
Vendors love diagrams; buyers need to know what they’re actually operating. Here’s the whole platform, demystified.
Indian stamp duty is set by each state, with its own rates, instruments and procedures. Paying the wrong amount or under the wrong state’s rules affects enforceability.
An electronic signature backed by Aadhaar and valid under the IT Act: the signatory authenticates by OTP against their Aadhaar record, with an audit trail.
Templates, generation, routing for signature and storage of the executed agreement — why the step often takes days though signing takes seconds.
Who signed, when, how they were authenticated and what duty was paid. This is the record in a dispute, and why a scanned signature on a PDF is weaker.
One flow from template to eStamp to Aadhaar eSign — duty paid under the right state and the audit trail kept.
Signzy Digital Contracting stamps, signs and executes — state-correct duty and the rest of the Signzy portfolio.
Duty computed and paid by the relevant state’s rates and instrument type — the part that decides enforceability.
OTP authentication against the signatory’s Aadhaar record, with an audit trail. Valid under the IT Act, not merely convenient.
Generating, routing for signature and storing the executed document — the lifecycle work that makes the step take days.
Sequences signatures across parties with reminders and status, where a guarantor or co-applicant breaks manual processes.
Who signed, when, authenticated how, and what duty was paid. If an agreement is ever challenged, this record is the position you argue from.
Contracting shares the marketplace with onboarding, so the signer is already identity-verified, not re-authenticated.
Here’s what genuinely sets it apart — and exactly where it stops.
Teams digitise verification into a ninety-second journey, then customers wait three days for a stamped, signed agreement from an unmodernised process. The journey is only as fast as its slowest step, so scope eStamping and eSign alongside verification, not as a phase two that often goes unfunded.
Stamp duty is set by each state — its own rates, instrument categories and payment procedures — and the applicable state depends on where the instrument is executed. An insufficiently stamped agreement can be inadmissible as evidence. Ask which states are covered and how rate changes, even mid-flow, are tracked.
A scanned signature on an emailed PDF is weak evidence: proving who applied it, when and why is hard. Aadhaar eSign authenticates the signatory by OTP against Aadhaar, valid under the IT Act, with an audit trail. For loans, guarantees and anything you may enforce, that difference shows only in a dispute.
Two boundaries. The platform executes documents but doesn’t draft them or classify unusual instruments; template design and legal characterisation stay with your counsel. And state coverage must be checked: which states for eStamping, how rate changes are tracked, and the fallback when a state system is down.
Contracting is funded last and felt first. A phase two that never gets funded leaves a fast verification feeding a three-day wait.
Which agreement types, executed where. Duty depends on both, and the answer determines what coverage you actually need.
The platform stamps correctly for the category you declare. An instrument characterised wrongly gets stamped correctly for the wrong thing.
Which states, how rate changes are tracked, and what happens when a state portal is unavailable — that outage becomes your customer's delay.
Verified customer straight to executed agreement, without re-authenticating a person you already verified minutes earlier.
Who signed, when, authenticated how, duty paid. It is the position you argue from if an agreement is ever challenged.
Modelled on Gartner Peer Insights structure. *Counts and breakdowns are illustrative pending verified review collection.
“We left contracting for phase two, which took a year, so customers experienced our fast onboarding as a three-day wait.”
“eStamping across states was the reason we bought. Doing it correctly per state was consuming legal review time we could not keep spending.”
“Ask about state coverage and what happens when a state portal is down, because that outage becomes your customer’s delay.”
“Aadhaar eSign changed our recovery position more than our speed. A properly executed agreement is a different conversation when something goes wrong.”
Analyst firms bury this view behind paywalls, and review-site grids score satisfaction, not fit for your estate. So here’s TechBag’s synthesis of the digital contracting market — tap any vendor to see why it sits where it does.
Execution strength vs product vision — the classic market map, minus the paywall.
eStamping plus Aadhaar eSign, India-native.
The grid nobody publishes — how well it joins the wider journey vs fit with Indian stamping and signature law.
State-aware duty on one contract.
Positions are TechBag’s illustrative synthesis of public review-platform data and vendor documentation — not a reproduction of any analyst graphic. Verify before relying on it.
Against a global eSign vendor, manual stamp and sign, and a scanned PDF signature — on Indian duty, legal standing and speed.
| Dimension | Signzy Contracting | A global eSign vendor | Manual stamp and sign | Scanned PDF signature |
|---|---|---|---|---|
| India eStamping | State-aware | Usually not | Correct, slowly | Skipped |
| Aadhaar eSign | Native | Sometimes | Wet signature | No |
| Evidentiary position | Strong | Strong | Strong | Weak |
| Speed to executed | Minutes | Minutes | Days | Minutes |
| Identity already verified | Same contract | Separate | In person | No |
| Published pricing | Quote-only | Often published | Staff + duty | Free |
Honest fit signals — because the fastest way to lose your trust is to pretend one product wins every scenario.
Drag the sliders (agreements executed monthly; cost of a day's delay). Estimates model the wait between verification and execution, plus legal review time spent on per-state stamp duty. Illustrative.
Loaded cost = salary + overheads per productive hour. Illustrative only — your TechBag quote models your actual environment and modules.
Quote-only — Signzy publishes no price. TechBag scopes the billing unit and confirms the stamp duty is passed through as its own line, then quotes in INR with GST.
Best when agreements still take days
Best for a broader rollout
Best across the journey
Whatever the list prices above, TechBag negotiates a significantly better deal — with GST-compliant INR invoicing and local support. Ask us for your discounted quote.
Tell us your requirements and current tools — we’ll model it against what you spend today.
Take this into your next vendor call — including ours.
Is contracting scoped alongside verification, or parked in a phase two that may never be funded?
Which agreement types do you execute, and in which states? Duty depends on both.
Has counsel confirmed how each instrument is categorised? Correct stamping of a wrong category is still wrong.
Which states are supported for eStamping, and how are rate changes tracked when a state revises them?
What happens when a state portal is unavailable? That outage becomes your customer's delay.
Are agreements you may need to enforce currently signed as scanned images? That is a weaker position than it feels.
Do any agreements need a guarantor or co-applicant? That is where manual routing usually collapses.
Is billing per document, per signature or per envelope, and is the duty itself passed through separately?
Scope this alongside verification rather than as a phase two — phase two often does not get funded — or let a TechBag advisor confirm state coverage and the fallback when a portal is down.
Stats, ratings, review counts and pricing are illustrative and sourced from public materials; verify before purchase.