Most teams don’t lose time because they’re disorganised. They lose it because the software makes them work around it. Files end up in three places, nobody’s sure which version is current, an approval sits in someone’s inbox for a week, and someone always has access they shouldn’t. If you’re running document handling on shared drives, email threads or a generic tool that almost fits, you know the drill.
That usually holds together until something forces the issue: an auditor asks for an approval trail you can’t produce, growth into several sites or departments, a regulatory deadline, an ERP or CRM migration that documents now need to plug into, or a move to remote work that paper sign-offs can’t survive.
I build document management systems around how documents move through your business: who raises them, who signs them off, where they get stuck and what they need to connect to. Then the software follows that process, instead of you changing the process to suit a product.
Where off-the-shelf document management falls down
Off-the-shelf isn’t always the wrong answer. If you mostly need somewhere central to store and share office files, with no complicated approvals and no sector-specific rules, SharePoint or Google Workspace will usually do the job. The trouble starts when your needs are more specific than the product allows.
The usual complaints:
- The software dictates the workflow. Fixed approval templates rarely match real conditional routing, such as “invoices over £10k need two sign-offs” or “this document type skips legal”, so people adapt to the tool or go back to email.
- Per-user pricing scales the wrong way. A subscription that looks manageable at ten people is painful at a hundred, adding approvers in a new department makes it worse, and you never own anything at the end.
- Industry rules don’t get met. Standard platforms struggle with the audit trails, metadata models and retention schedules that CQC, Ofsted or the FCA expect.
- Integrations are patchy or brittle. Connectors to accounting, CRM and operational systems break when vendors update their APIs, and older in-house systems often aren’t supported at all.
- The headline price hides the rest. Implementation, data migration, training, API access on higher tiers and per-document overage fees sit on top of the subscription quote.
The result is staff time lost hunting for the right document, manual workarounds to cover the gaps, and compliance steps that happen outside the system, which is exactly where audit gaps appear.
What you get
- Built around your process. I map how documents move through your business first, from creation to approval, filing and disposal, then build software that supports it.
- A data model that fits your work. Documents don’t always live in tidy folders. The system can be structured around the entities you work with, such as matters, projects, clients, properties or batches, with metadata, document types and retention rules to match.
- Approval workflows that match reality. Your routes, authority limits and edge cases are part of the system (more on this below).
- One-time cost. You own the system outright, source code included, with no per-seat subscription.
- Direct integration. Connections to the business systems you already use, so data isn’t re-keyed by hand and your documents aren’t held hostage by a vendor.
- UK compliance from the start. Encryption, audit trails, retention and data residency are designed in, with UK data protection law and your industry’s standards in mind.
- Support from the person who built it. I handle the rollout and stay on for changes afterwards.
Approval workflows inside the document system
Most document management buyers have an approval problem as well as a storage problem. Building the approval workflow into the DMS means the document, its versions, its sign-offs and its retention all live in one record, instead of a file in one place and the approval in an email thread.
Before writing code, I map your approval routes, your authority limits and the cases that break templated tools: the approver who’s on leave, the contract that needs two signatures, the value threshold that escalates to the finance director. That gives you:
- Conditional routing by value, document type, department or your own rules, so the right approvers are involved without anyone deciding manually.
- Parallel and sequential steps, including “three of five approvers” rules for higher-risk decisions.
- Escalation and delegation. A step that misses its deadline escalates, and an absent approver’s work goes to a named backup, so nothing stalls in one inbox.
- An approver inbox showing what’s pending, with approve, reject or request changes available from a phone and the full document in view. This matters for people who sign off on site, such as construction change orders or supplier certificates.
- An audit record of each decision with the approver, timestamp and the exact document version they reviewed.
- Downstream updates. Approved status posts back to your accounting system or CRM, and an approved invoice can flow straight to payment.
- Cycle-time reporting showing where approvals wait, by approver and by step.
If your approvals are simple, with standard document types, one to three signatories and a small team, an off-the-shelf approval tool is probably the cheaper answer. A build makes sense when routing is complex, the number of approvers makes per-seat pricing hurt, your document types are unusual (engineering change requests, clinical protocols, change orders), or the approval step has to read and write data in a legacy ERP.
Features I build in
Not every feature goes into every system. I start with a focused core and add the rest where it earns its place.
The core, in almost every build:
- Central document repository. Secure cloud or on-premises storage, organised by folder hierarchy or metadata, whichever suits your documents.
- Search that works. Full-text search across document content plus metadata, with filters by type, date, status and creator.
- Version control. Clear history, restore to a previous version, and check-in/check-out so two people can’t overwrite each other.
- Role-based access. Permissions by role, department and document type, so people see only the files and functions they should.
- Audit trails. An immutable, timestamped record of who viewed, changed, approved, exported or deleted what, the kind of log a regulator or auditor will accept.
- Retention policies. Rules per document type for archiving and secure disposal, with legal holds where deletion needs to be blocked.
Where the work justifies it, I add:
- Approval workflows as described above.
- OCR and document capture. Scanned paper and image PDFs turned into searchable text, with data extracted from invoices and forms.
- Electronic signatures, built in or through DocuSign or Adobe Acrobat Sign.
- Templates for standard forms and contracts, with fields filled from your existing data.
- System integration with Xero, QuickBooks or Sage, Microsoft 365 or Google Workspace, your CRM, and SSO via SAML or OIDC.
- Email capture. Relevant emails pulled in as documents and routed by sender or subject.
- Mobile access for staff in the field.
- Reporting and compliance dashboards. Workflow bottlenecks, approval cycle times, storage use and documents due for disposal.
How the build works
I phase the work so you get a usable system early. The most common reason document projects overrun is trying to re-engineer every process at once.
- First Gear. I go through your current document processes, pain points, compliance obligations and integrations, build a working prototype of one core workflow with your own documents, and scope the first release and what follows it at a fixed price.
- Phase one build. Either the storage core (repository, search, version control, access, audit trails and retention) or one approval workflow end to end, usually invoice approval, goes live within a month.
- Migration. I inventory your existing documents, weed out duplicates and dead files, agree a metadata standard, then migrate in batches and validate, running the old system in parallel where it helps.
- Pilot and rollout. One department, usually finance, uses it live first. Once cycle times and feedback look right, it widens to other departments and document types, with training for submitters, approvers and administrators.
- Later phases. Further workflows, OCR, integrations and reporting are added once the core is adopted. Approval rules usually need tuning once real usage data comes in, so that’s planned for.
Each later phase has its own fixed price and go-live date in the build plan.
What it costs
Per-user SaaS is easy to forecast and fine at small scale. It becomes the expensive option as headcount and approver numbers grow, because the bill never stops and the published price rarely includes implementation, migration, training or integration.
A custom build is a larger one-off cost with no per-seat fee afterwards. Most builds cost £2k–£10k and go live within a month, with the price fixed at the end of First Gear.
- No recurring per-user fees, so adding approvers or a department adds no licence cost.
- Time recovered from searching, re-keying and chasing sign-offs.
- You can change and extend the system without waiting on a vendor’s roadmap.
- You own it outright, source code and data in standard formats, so you’re never locked in.
Where this applies
Document management means something different in every sector, which is why the off-the-shelf fit is often loose:
- Legal and professional services: matter-centric structure, retention tied to case closure, privileged-access controls, and contract review routed across client, legal, finance and procurement with e-signature.
- Finance and accounting: supplier documents matched to invoices in Xero or QuickBooks, receipt OCR and coding, invoice and expense sign-off with segregation of duties, and retention aligned to HMRC’s six-year rule.
- Financial services: credit and loan approvals with risk escalation, and regulatory filings with board sign-off and an audit trail the FCA will accept.
- Healthcare and medical practices: patient consent tracking, clinical incident reports routed to a manager then compliance, referral documents, and links into practice systems such as EMIS.
- Social care: care plans, medication logs and safeguarding records, with care workers seeing only what they need and managers seeing the full audit trail for CQC.
- Education: pupil files kept until age 25, staff DBS documentation, safeguarding logs and evidence compiled for Ofsted.
- Manufacturing and engineering: revision control for drawings and CAD files, engineering change orders through engineering, production and quality, supplier certifications and ISO 9001 process evidence.
- Construction and property: change orders through project manager, architect and client, tenancy agreements and maintenance records linked to the property, and deposit-protection compliance.
- Insurance: claims workflow, policy document linking, and AML/KYC files held against the right record.
If your sector isn’t listed, the approach is the same: I build to your documents, your approval routes and your regulator.
Common Questions About Custom Document Management Systems with Approval Workflows
When does custom document management make more sense than SaaS? ›
If you need general office storage and basic sharing, SharePoint or Google Workspace is usually enough, and I'll say so. Custom pays off when you have multi-stage approval chains that don't fit fixed templates, sector rules such as CQC, Ofsted or FCA record-keeping, integrations with older accounting or operational systems, or a per-user SaaS bill that climbs steeply as your team grows.
How does the cost compare to a per-user subscription? ›
DMS and approval tools are usually priced per user per month, with implementation, migration and integration fees on top that are easy to overlook. A custom build is a larger upfront cost with no per-seat fee afterwards, so the more users and the longer you run it, the more ownership favours you. Most of my builds cost £2k–£10k, with the price fixed at the end of First Gear, so you can compare against a real figure.
What's the typical development timeline? ›
A focused first release, covering storage, search, version control, access control and audit trails, or one approval workflow end to end, usually goes live within a month. Further workflows, OCR and integrations follow as later phases, each with its own fixed price and about a month of work.
Can the system handle complex approval routing, not just a single chain? ›
Yes, and that's usually the reason to build rather than buy. I can route on document value, type, department or your own rules, run parallel and sequential steps, escalate when a deadline is missed, reassign automatically when an approver is on leave, and require, say, three of five approvers for higher-risk decisions.
Can you integrate with our existing systems? ›
Yes. Common connections include Xero, QuickBooks and Sage for matching documents to invoices and posting approved status back, Microsoft 365, SharePoint and Google Workspace, CRMs such as Salesforce or HubSpot, DocuSign or Adobe Acrobat Sign for e-signatures, and SSO via SAML or OIDC. Older or in-house systems can be reached through APIs, direct database access or file exchange where no connector exists.
How do you handle our existing documents and migration? ›
I inventory your existing files, identify duplicates and obsolete material, agree a metadata and naming standard, then migrate in batches and validate the results. Where it helps, the old system runs in parallel for a period so you can confirm nothing is missing before switching over.
What about data security and compliance? ›
Systems are built for UK GDPR: encryption at rest and in transit, role-based access, immutable audit logs, UK or adequacy-decision hosting, and tooling for subject access requests, erasure and retention. I can also build to sector retention rules, such as six years for tax records and longer for healthcare and legal matters, and shape audit trails to what your regulator expects.
