# Introducing e-signatures: from pilot to rollout > You can introduce e-signatures without an IT project. Why a pilot in one department is the best start and how the rollout succeeds: five steps. Source: https://smartdocs.de/en/blog/introduce-e-signatures-in-your-company/ --- When mid-sized companies start thinking about electronic signatures, a project quickly takes shape: a requirements catalog, a vendor comparison, IT coordination, a training plan. Months later, not a single contract has been signed digitally. Yet the e-signature is one of the few digitization topics that you can start small and roll out big, without anyone having to install anything at the beginning. ## Why the big solution is the wrong start In a company, paper processes are spread across many shoulders: HR waits for signed employment contracts, sales prints quotes, purchasing files supplier contracts. If you want to switch all of that over at once, you have to convince everyone at once, and that is exactly where rollouts fail. The better approach turns the logic around: one department starts, collects results, and the numbers convince the rest. This works particularly well with e-signatures because the other party needs nothing: signers receive a link by email and [sign in the browser](/en/features/), with no account and no app. ## Step 1: Pick the use case with the most paper Look for the document that is printed, sent and scanned back most often. In many companies, that is the employment contract; elsewhere, it is the quote or the NDA. Two criteria make a good pilot case: high frequency (the effect becomes visible quickly) and a measurable pain point, such as the time between sending a contract and getting it back. While you are at it, quickly check the right [signature level](/en/signature-levels/): for contracts with no form requirement, the simple signature is sufficient; sensitive contracts get the advanced level with an SMS code; and only where the law requires the statutory written form do you need the qualified signature (QES), for example for fixed-term employment contracts. ## Step 2: Start the pilot without budget approval The pilot needs no budget and no IT: a free plan with a handful of signature requests per month is enough to test the process with real contracts. What matters is that the pilot handles real requests, not test documents. Only real returns show how much time the digital route saves and where the process gets stuck. Before you start, define two numbers you want to measure: the turnaround time (from sending to the last signature) and the return rate without reminders. The request status delivers both automatically. ## Step 3: Set up templates and responsibilities Once the first requests have gone through, structure pays off: recurring contracts become templates with fixed field positions, so a new request starts in seconds. Roles and permissions control who may change templates and who only sends. If the standard contract changes, versioning ensures that ongoing requests keep their version. ## Step 4: Involve data protection and the works council early The most common delay in a rollout is not technical but organizational: the data protection officer was asked too late. Involve them during the pilot and present the documents they will ask for anyway: the data processing agreement (DPA), documentation of technical and organizational measures (TOMs) and information on where the data is stored. At SmartDocs, the answer is short: exclusively in [German data centers](/en/security/), with no transfer to third countries. You can also win over the works council with a clear argument: the audit trail logs the events of the individual signature request, not the work performance of employees. ## Step 5: Roll out department by department and measure The rollout follows the pattern of the pilot: each additional department joins with its own templates and matching roles, and locations that need to stay completely separate become their own organization. The pilot department supplies the arguments, too, because nothing convinces purchasing faster than the HR colleague who cut her turnaround time from two weeks to two days. If you want to send contracts automatically from your existing systems, connect the [REST API](/en/developers/), but that is an expansion step, not a prerequisite. ## Objections from practice, answered briefly **"Our contract partners will not go along with it."** The other party needs neither an account nor software, just the link from the email. Anyone without an email address signs in person on the tablet. **"We have no IT capacity."** You do not need any to get started: SmartDocs runs in the browser, and there is nothing to install and nothing to operate. **"What if we want to switch again?"** Signed documents, completion certificates and audit trails can be exported at any time. Completed signatures remain valid because the evidence documents are in your hands. ## Conclusion Introducing e-signatures is not an IT project but a series of small, measurable steps: one use case, a free pilot, clean templates, compliance clarified early and a department-by-department rollout. To see how SmartDocs supports companies with multiple departments and locations, visit our page [For mid-sized businesses](/en/mid-sized-businesses/). The first step costs nothing: the [Free plan](/en/pricing/) stays free permanently.