About
We built Pactthread because contract management should not require a spreadsheet, a paralegal, and a prayer
The blank-page problem was always the first bottleneck named. The routing problem was always the second. We built for both.
Robert Castellano, CEO
Origin
How Pactthread started
Robert Castellano spent eight years in legal operations roles at companies that were signing new customers and vendors faster than their contract infrastructure could keep up. The pattern repeated at every company: intake by email, drafts in Word attachments forwarded across three inboxes, approvals chased via Slack, obligations in a shared calendar with no owner and a column called "check this one".
In 2023, Robert left legal ops to build Pactthread. The first version was focused entirely on approval routing and obligation tracking, the two failure points that caused the most downstream damage. The drafting layer came next, because the blank-page problem was always the first friction point named by every legal-ops lead he spoke to during those eight years.
New York was the obvious home. It is where deals get papered at volume, where in-house legal teams are squeezed hardest between deal speed and process discipline, and where the gap between "close the contract" and "manage the obligation" shows up fastest on the P&L.
Pactthread is not built for the enterprise CLM market. We are not competing with the platforms that need a six-month implementation and a dedicated IT project. We built for the team managing 200-400 active contracts with a 3-5 person legal function and a spreadsheet that nobody trusts. That team is in every company between $15M and $150M in revenue. That is exactly who we are here for.
The Team
Three people who have lived the problem
Robert Castellano
CEO & Co-Founder
Eight years running legal operations at technology and services companies before co-founding Pactthread in 2023. Has personally managed contract backlogs, built approval matrices, and inherited obligation spreadsheets that were already wrong. Pactthread is the tool he kept wishing existed.
Dana Park
Head of Product
Spent five years as a contract manager at a professional services firm before moving to product. Knows what a 12-step approval matrix looks like from the inside. Designed Pactthread's approval routing logic and the clause library system from firsthand experience with both.
Eli Soto
Lead Engineer
Previously built document ingestion and metadata extraction pipelines at a legal-tech company. Leads Pactthread's obligation extraction engine and all third-party integrations. Knows that the hardest problem in CLM is not the AI, it is getting clean data in and out of the tools the team already uses.
What We Believe
Three things we will not compromise on
Contracts should move, not wait
Every day a contract sits in review is a day revenue, a vendor relationship, or a project deliverable is on hold. Approval delays are usually process failures, not bandwidth failures. We build for the process first.
AI suggestions that explain themselves
We do not ship a redline suggestion without a reason attached. Legal teams need to understand the "why" before they accept or reject. A rationale-free suggestion is noise that slows review down, not a tool that speeds it up. Every suggestion in Pactthread carries its reasoning.
CLM manages process, not judgment
Pactthread handles drafting, routing, tracking, and reminders. It does not make legal judgment calls, interpret contract law, or replace counsel review on non-standard deals. We are clear about that boundary because legal teams need to trust what the tool does and does not do.
See what we built
Walk through the platform in 30 minutes with a contract type your team handles. No slides, no sales deck. Just the product.
See the Platform