Krishna Dey Shipped · Hackathon to shipped product
Legal Intake
Structured legal-request intake, first explored as a 2024 internal hackathon project with Sanket Mishra and Punit Batra, then built out through 2025 as a cross-functional squad I led, and shipped to production in January 2026 as the 'front desk of Legal' inside SpotDraft.
Engineering Manager and cross-functional squad lead
Shipped January 2026.
Third prize, 2024 internal hackathon. Surpassed SpotDraft's internal target of more than $1M in revenue impact for this financial year.
Hackathon concept built with Sanket Mishra and Punit Batra during SpotDraft's 2024 internal hackathon; production program delivered with a cross-functional engineering, QA, and product squad through 2025-2026.
Challenge
Legal requests often arrive through fragmented channels — conversations, forms, email, messaging tools — and become difficult to track: who owns it, what tasks it produced, what changed, and whether it became a contract at all.
Approach
After the hackathon validated the idea, I led the engineering program: wrote the architecture connecting Legal Intake to Workflow Manager, the task system, and polymorphic metadata/comments/attachments so intake could reuse existing platform primitives instead of a parallel system. I split delivery into four workstreams (workflow setup, request creation, detailed intake/task view, listing and routing) with explicit frontend/backend/QA ownership, ran a spec-first process, and built a capacity model that tracked each engineer's velocity, availability, and committed load against sprint assignments so at-risk work surfaced before deadlines slipped.
Outcome
The first production version shipped in January 2026 via a coordinated, feature-flagged release. Legal Intake gives teams a standardized way to capture, route, and track inbound legal requests, with later work extending it to Slack and email intake and AI-assisted classification. It has already surpassed SpotDraft's internal target of more than $1M in revenue impact for this financial year.
What it taught
Reusing existing platform primitives (workflow configuration, task model, polymorphic metadata) instead of building a parallel intake system kept the surface coherent. Capacity-aware planning surfaces schedule risk before it becomes a missed date, and shipping to production is not the same milestone as being ready for full customer enablement.
More projects
All projectsA configurable reverse-sync system for pushing contract and workflow data back into Salesforce, shaped to be extensible across triggers, conditions, object mappings, and future automation use cases.
Native integration and platform work spanning CRM, procurement, and collaboration systems, with emphasis on reusable primitives, metadata-aware design, and integration surfaces that stay coherent as the catalog expands.
Replaced SpotDraft's fixed two-party contract assumption with configurable party roles, so contract creation, questionnaires, and publishing could support more than one organization or individual on either side of an agreement.