Custom e-signing software
Appfront builds custom software that embeds signing in your own process. The document is generated from your own data, sent to the right signatories in the right order, the status is visible in your system and the signed document automatically returns to the file. Get in touch.
What exactly do we build?
You buy the signature itself. There are specialist trust service providers that carry out the signing, verify identity and provide proof that a document has not been altered. That is a regulated market and not something to build yourself.
What is usually missing is everything around it. Generating the right document from your own data, determining who needs to sign and in what order, reminding anyone who leaves it lying around, making the status visible in the system where your people work, and putting the signed document back in the right file. That is the work that stays manual.
Appfront builds that layer as custom software on top of the service you choose. If you already use an existing provider, we build only the integration — we have separate pages for that, such as DocuSign or ValidSign.
The document from your own data
Not a manually assembled file but a document generated from what is in your system, so that no outdated data ends up in it.
The right route
Who signs, in what order, and who only needs to read along. With two parties that's straightforward; with a chain that includes internal approval, it's exactly where things go wrong.
Status where you work
See who hasn't signed yet without logging in to an external service, with reminders that go out automatically.
Build it yourself or integrate? Where we draw the line
Two different questions that often get mixed up. The answer determines the scope.
The process around it
Building the document, setting the route, tracking statuses, sending reminders, archiving and linking to your records. The signature itself comes from a trust service.
Connect your existing service
If you already work with a provider and just want to connect it to your system, see our integrations, for example SignRequest or Evidos.
Our development process for your signing flow
The level of signing you need determines which service you choose, and therefore what there is to build. We put that question first.
We map out which documents need to be signed, who signs, what level of assurance applies and what you need to be able to prove afterwards. We also look at which data needs to populate the document and where the signed document needs to go.
We design the document assembly, the signing route with its roles, the status tracking and the integrations with the trust service and with your records or administration.
We build in short iterations with automated tests, structured logging and monitoring. You see working versions along the way and steer based on what your team actually needs in practice, rather than on a specification written months ago.
A controlled go-live with validation and a safety net, followed by ongoing maintenance, monitoring and further development as your document flow or legal framework changes.
What custom signing software delivers in practice
What you need differs per document flow. These are the components that come up most often.
Assembling documents
Templates populated with data from your system, with the right attachments and terms, so nothing is pasted in by hand.
Signing routes
Multiple signers in sequence or in parallel, with internal approval beforehand and the option to let someone only read along.
Status and reminders
Visibility into what is outstanding and for how long, with automatic reminders and escalation when a document gets stuck.
Evidence and archiving
The signed document and its evidence file stored automatically in the right record or folder, so nobody has to transfer it.
Connection to the trust service
Integration with the provider you choose, including the level of signing that differs per document type.
Signing in your own environment
The signer stays in your branding and your portal instead of being clicked through to an environment they don't recognise.
Typical use cases in practice
Signing becomes a software question as soon as the volume or the route gets complicated.
Organisations with many similar agreements
Rentals, subscriptions, memberships or terms of delivery, where the process is always the same and the volume makes doing it manually impossible.
HR and onboarding
Employment contracts, declarations and amendments that need to be signed by multiple parties and should end up in the personnel file.
Healthcare and education
Consent forms and agreements with clients or parents, where recording who gave consent, when and for what is a requirement.
Portals with external parties
Environments in which suppliers, dealers or applicants sign documents as part of a larger process.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology we use
The signing itself runs through a regulated provider; we build the layer on top. The exact choice depends on your processes, the systems to be integrated and your hosting preferences. We deliberately choose a stack that your own team can manage and develop further, with no dependence on per-user licences.
Why Appfront for your signing flow?
Appfront builds custom software for a wide range of organisations in the Netherlands. When it comes to signing, we are clear upfront about who does what: the signature and the evidence come from a regulated service, and we build the process around it. That avoids a conversation halfway through about what is and isn't allowed.
We start with the question of what you need to be able to prove afterwards. That determines which level of signature you need, and that in turn determines which providers are eligible. Reversing that order gives you a system that later turns out not to comply.
On every project we write clear documentation and make sure your own team, or a future supplier, can understand and manage the system. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance. You own the solution and pay no per-user licence.
Also take a look at our broader services around custom software, contract management and legal workflow automation. Not sure about the right approach? Get in touch.
Security and evidence in your signing flow
Documents that get signed almost always contain personal data and sometimes sensitive information. Appfront builds in line with OWASP ASVS and with the GDPR as a starting point, with access per case file and an audit trail of who viewed or sent which document.
We store the trust service's evidence file together with the signed document, in a way that can't be altered. Without that evidence, a signature is hard to prove after the fact, and that is exactly when you need it. We set retention periods per document type.
More about our approach to security: information security policy and CVD policy.
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access following least privilege
- Audit trail of views and changes
- Secrets in a secure vault, not in code
- Documented data flows for your processing register
- Evidence file stored immutably alongside the signed document
Frequently asked questions about digital signing software
Answers to the questions we get asked most often.
No. The signing and the accompanying evidence come from a specialised trust service provider; this is a regulated market. We build the process around it and integrate with the provider you choose. That is precisely the layer where most manual work remains in practice.
That depends on what you are signing and what you need to be able to prove afterwards. For many ordinary agreements a lighter form is enough; for documents with a heavier burden of proof or a statutory formal requirement, you need a stronger variant, with identification beforehand. You make that choice with a lawyer; we make sure the system can handle both.
Yes, with most providers the signing can be embedded in your own portal and house style. That reduces drop-off, especially among consumers who are put off by being redirected to an unfamiliar environment. What exactly is possible differs per provider.
That is one of the most important things to agree on upfront. The system sends reminders according to your schedule, escalates after a set period and can withdraw the request. Without that, a document quietly stays open and nobody notices until someone asks about it.
Automatically in the case file it belongs to, together with the trust service's evidence file. That last part is often forgotten: without that evidence file, you have a PDF with an image on it and no demonstrable signature.
Yes, sequentially, in parallel or a mix of both, with internal approval as the first step. For chains with a fixed order, that is the core of the system: only once party A has signed does it go to B, and nobody has to forward it manually.
Yes. We can add signing to an existing document flow, for example from your contract management or your ERP, without you having to replace those systems. The signing layer sits alongside them rather than around them.
If you sign a handful of documents a month, a provider's portal is fine and certainly cheaper. Custom software pays off once volume grows, once the route is complicated, or once you want the document to come from your own data and the signed document to end up in the right place automatically.
Ready to build your signing flow?
Tell us which documents get signed, who signs and where the signed document needs to go — we're happy to think along on scope, integrations and the first version. A no-obligation first conversation gives you a clear picture of the possibilities and whether custom software pays off in your situation.