Questions we actually get.

The moment your client hits approve, GuildSeal hashes the entire job record — scope, photos, timestamp, both parties' identifiers — and writes that hash to the Polygon blockchain. You get a transaction ID. That ID links to a public record that proves the hash existed at that exact moment. Nobody can alter the underlying record without the hash changing, and nobody can change the hash on-chain. That's the permanence. That's the product.

That's a different problem — and honestly, a harder one. GuildSeal protects you when a client approves and then disputes later. If someone refuses to engage with the sign-off process entirely, you're dealing with a bad-faith client, not a documentation problem. What GuildSeal does do: the initial scope sign-off at job start creates a record that the client agreed to the work before you touched anything. That's useful in collections, small claims, or licensing board disputes even without the completion sign-off.

No. Your client gets a text with a link. They open it, review the scope or photos, type their name, and hit approve. No app, no account, no friction. This was a deliberate call — if the client has to create an account, half of them won't bother, and your protection disappears with them. The entire client flow is designed to take under two minutes on a phone.

Under the ESIGN Act and UETA, yes — an electronic signature, including a typed name with clear intent to approve, is legally binding in all 50 US states. What makes GuildSeal's record stronger than a standard e-sign tool is the blockchain anchoring: the timestamp, the content of what was approved, and the identity data are all baked into an immutable hash. You're not just proving someone clicked a button — you're proving exactly what they saw and approved, and when. That's harder to dispute than a PDF with a typed name and no record of the document content at signing time.

The blockchain record survives us. Every transaction ID we give you points to an entry on the Polygon public ledger — a decentralized network that no single company controls, including us. If GuildSeal ceased to exist tomorrow, the hash and timestamp would still be there, publicly verifiable by anyone. What you'd lose is the hosted verification page and the photos we store. This is why we recommend downloading your job records and keeping local copies of completion photos for any job that might matter in court. The blockchain is the proof. We're the interface.

An email with photos proves you sent photos. It does not prove the client saw them, reviewed them, and approved the work as complete. Clients dispute emails constantly — they claim they didn't see it, misunderstood it, that the photos showed something different. GuildSeal's record captures explicit client approval of specific content at a specific moment, timestamped and signed. The difference in a dispute is the difference between "I sent them photos" and "they reviewed these exact photos on this date and typed their name to confirm the job was done." One ends arguments. The other starts them.

Yes. The record structure works for any job where there's a defined scope, a client, and a completion point. Residential work is the most common use case because disputes there tend to be personal and contentious. But light commercial — retail buildouts, office renovations, multi-unit property work — is fully supported. Where GuildSeal isn't the right tool is large commercial projects with GCs, subcontractors, lien waivers, and formal AIA contract structures. That's a different product category entirely. If you're a solo operator or small crew doing work under $500K, you're the target.

Three complete jobs, no card required. Each job gets the full treatment: scope sign-off, completion photos, client sign-off, blockchain anchoring, and a permanent verification link. Not a watered-down version of the product — the real thing, three times. The reason we do it this way is simple: the value of GuildSeal is clearest when you actually use it on a real job with a real client. Three jobs is usually enough to either get burned by a dispute and understand exactly why you need this, or to sign off a job without any drama and realize you just changed how you do business.