SignTheDoc raises Series B to build the future of agreements

Today we are announcing a $40M Series B. It is a genuinely good moment for the company, and the most useful thing we can do with a funding announcement is be specific about what it changes for the people who use SignTheDoc.

How we got here

In 2021, Jordan and I waited nine days for a single contract to come back signed. Nine days, for a two-page agreement both parties had already verbally agreed to. The delay was entirely mechanical — printers, scanners, a document sitting in an inbox over a weekend.

We built the first version of SignTheDoc over the following four months. Five years later there are 40,000 teams on the platform and twelve million documents have been signed through it.

What the money is for

• Engineering — roughly half. Deeper workflow capabilities, a better mobile experience, and continued investment in the API.
• Security and compliance — additional certifications, more regions for data residency, and growing the security team.
• Support — more people, more coverage hours, and better documentation.
• International — localisation and compliance work for markets we currently serve imperfectly.

What is not changing

The free plan stays free, with three documents a month and no expiry. It is not a trial and it is not going to quietly become one. A meaningful number of freelancers and small nonprofits run entirely on it, and that is a good outcome.

We are not adding per-signature fees. We have watched competitors do this and it makes the product worse — people start rationing signatures, which is the opposite of the point.

What we are building next

Three areas over the next eighteen months. Deeper workflows — conditional routing was the first step, and there is considerably more to do for teams with genuinely complex approval processes. Better integrations — the API is solid but the pre-built integrations lag what people ask for. And more regions — data residency in more jurisdictions, and proper support for qualified signatures in Europe.

What we learned raising it

Two things worth passing on to anyone doing this. The first is that the diligence process was substantially about our security posture rather than our growth numbers. Investors asked to see our SOC 2 report, our incident history, and our subprocessor list before they asked about retention. Five years ago that would not have happened.

The second is that our public post-mortems came up repeatedly, and positively. We had assumed publishing detailed incident reports was a reputational cost we accepted for the sake of honesty. It turned out to read as operational maturity. That was not the plan, but we will take it.

On growing without getting worse

The failure mode for a company at this stage is well documented. Headcount grows, the product accumulates features nobody asked for, support response times slide, and the thing that made people choose you quietly stops being true.

We do not have a clever way to avoid that. What we have is a set of numbers we watch and have committed to publishing internally every month: median time to first support response, median document completion time across the platform, and the number of clicks required to send a document from a template. If any of those get worse for two consecutive quarters, that is the priority regardless of what else is planned.

The last one matters more than it sounds. Feature growth almost always shows up as interface growth, and interface growth shows up as more clicks for the person who just wants to send a contract. Measuring it makes the tradeoff visible at the point the decision is made.

Thank you

To the teams who have trusted us with their most important agreements: thank you. Particularly to the ones who filed detailed bug reports in the early days when the product deserved them.

And to the people who told us plainly when something was bad — the broker who explained exactly why our mobile flow did not work at an open house, the counsel who sent three pages on what our audit certificate was missing — a disproportionate amount of the product came from those conversations.

We are hiring across engineering, design, and go-to-market. If any of the above sounds like something you would like to work on, we would like to hear from you. Roles and details are on our careers page, and the open application is genuinely read.