About the client
The client delivers construction services across multi-stage projects with heavy documentation, demanding compliance requirements, close financial oversight and recurring internal and external audits. Its teams worked across spreadsheets, email threads and legacy tools. To scale, the client set out to replace them with one purpose-built platform, and engaged FiftyFive Technologies as its software development partner.
One system flexible enough for every project type
- Different workflows. Support several project journeys, each with its own workflows and dependencies.
- Document versioning. Handle complex document formats and versioning, with task data linked across records.
- Compliance audits. Run internal and external approval workflows that satisfy compliance audits.
- Cashflow monitoring. Give real-time cashflow monitoring alongside detailed financial reporting.
- Outside stakeholders. Share, sign and verify documents securely across teams and outside stakeholders.
- Future integrations. Leave room for future integrations and partner onboarding.
What FiftyFive built
FiftyFive architected, built and deployed the platform end to end and continues to develop it. The scope covers: a centralised SaaS platform on a modular architecture; project journey templates that adapt to different project types; a form and document builder whose inputs link across tasks and compliance checks; real-time cashflow analysis and reporting modules; audit and risk management with layered approvals and digital signing; role-based access control and JWT authentication; dashboards and document-builder interfaces; containerised deployment on AWS.
How the solution works
Project journeys and documents
- Each project starts from a journey template matched to its type, which sets the stages, tasks and approvals it needs.
- Forms and documents created in the builder link their inputs to tasks and compliance checks, so a change in one record is reflected wherever it is used, and versions are kept.
Approvals, audit and signing
- Submissions move through layered internal and external approval workflows.
- Audit and risk management records are kept as work happens, and documents are signed digitally, so records are audit-ready without a separate collation step.
Finance
- Cashflow analysis and reporting modules give the client continuous financial oversight alongside project progress.
Security and deployment
- Role-based access control governs what each user can see and do, with JWT authentication across the platform.
- The modular services run in Docker containers on AWS.
Technology stack
What the solution enabled
Business transformation
Faster approval cycles
Fewer compliance errors
Saved per audit cycle
40% faster approval cycles
Template-driven, layered approvals replaced manual back-and-forth between submission and sign-off.
35% fewer compliance errors
Linked document data, versioning and built-in compliance checks reduced manual mistakes.
More than 25 hours saved per audit cycle
Continuously audit-ready records and digital signing removed the pre-audit document scramble.
Cashflow oversight
Real-time cashflow reporting, with continuous financial oversight.
FiftyFive Technologies architected, built and deployed a SaaS platform for a European mid-sized construction services company that ran projects, compliance, documents and cashflow across spreadsheets, email and legacy tools. The modular platform brings configurable project journeys, a linked form and document builder, layered approval workflows with digital signing, real-time cashflow reporting and role-based access into one system on AWS and Docker. Since launch, approval cycles are 40% faster, compliance errors are down 35% and each audit cycle saves more than 25 hours.
Technical questions
How are approval workflows run?
Submissions move through layered internal and external approval workflows. Audit and risk management records are kept as work happens, and documents are signed digitally, so records are audit-ready without a separate collation step.
How do forms and documents link to tasks?
Forms and documents created in the builder link their inputs to tasks and compliance checks, so a change in one record is reflected wherever it is used, and versions are kept.