Krishna Dey Concept · Hackathon concept that shipped
ClickWrap
ClickWrap captures recorded acceptance of terms in-product — a checkbox, link, or agreement viewer on a website, app, or signup flow — without sending the agreement through a full negotiation and e-sign ceremony. We explored that product shape as a 2023 hackathon with Sanket Mishra and Punit Batra; another team later shipped it. The shipped product has had more than $1M in revenue impact.
Hackathon contributor
Hackathon concept later built by another team.
Third prize, 2023 internal hackathon. Shipped-product revenue impact: more than $1M.
Built with Sanket Mishra and Punit Batra during SpotDraft's 2023 internal hackathon.
Challenge
Online agreements needed a lower-friction path than a full contract workflow: checkout, account creation, beta enrolment, and gated features where the user clicks to agree and legal still gets an auditable record.
Approach
We explored ClickWrap as a hackathon build — then called Clickthrough — focusing on the user journey, operational simplicity, and how an embedded consent surface could sit in SpotDraft's broader workflow ecosystem.
Outcome
The project won third prize internally and validated the product direction. A different team later built the production ClickWrap surface, with web and mobile SDKs. Revenue impact of the shipped product is more than $1M.
What it taught
Good hackathon projects do not need to become your long-term ownership area to matter; sometimes their value is proving demand and clarifying product direction early.
More projects
All projectsAn Amazon EFN chapter focused on internal fulfillment systems, requirements engineering, data pipelines, marketplace-launch automation, and high-scale inventory services where correctness and latency both mattered.
My Google Summer of Code 2019 project with Chapel Language focused on the Unit Testing Framework for Chapel, which gave me an early grounding in systems-level tooling and test infrastructure.
A product-systems arc that started with self-serve questionnaire setup for template workflows, was extended to third-party paper on the same foundation, and then evolved into the current Workflow Manager.