Illustrative engagement
From WhatsApp approvals to one project record.
An illustrative engagement for a contractor or developer running projects through spreadsheets, WhatsApp, email and a generic ERP that doesn’t understand BOQs, inspections, drawings or submittals.
Illustrative: how we would scope this, not a completed client project.
The situation
Where it breaks today.
Common patterns we plan for, not a description of a specific client.
Approvals in chat
Inspection results live in WhatsApp threads, so the decision never reaches the project record.
Progress rebuilt from photos
The QS rebuilds progress from photos and spreadsheets before every payment application.
An ERP that can’t see the BOQ
The ERP can’t see which BOQ line a payment certifies, so site and finance argue over the same number.
What we’d build first · illustrative
One live project first, then the money.
A possible first scope. The real one is agreed with your team after discovery.
ArkanCS on one live project
Inspections and submittals for a single project, with approvals routed by role.
Certified quantities in ArkanERP
Release two connects approved quantities to payment progress, procurement and project accounting.
ArkanPM only where it applies
Property operations join only if handed-over assets need to be run.
Custom modules for the gaps
Where a workflow is specific to the business, we build it around the same records.
Decisions we’d make early
Model the approval, not just the status.
The expensive-to-change decisions come first, so later changes stay cheap.
Model each approval as an event
Record each approval against a document, by an actor holding a role, rather than as a status column.
Trade-offSlower to set up than a status column, but delegation and audit become rules, not rebuilds.
Start with one project, not the portfolio
Prove the routing and roles on a live project before rolling out further.
Trade-offOther projects wait for the second wave, but the rules they inherit have been tested.
Give each record one owner
ArkanERP owns certified quantities and payments; ArkanCS owns the site evidence behind them.
Trade-offTwo systems to connect, but nobody argues about which number is right.
How we’d judge it
A connected operational platform where site, office, finance, and management teams work from one source of truth.
Success is defined with your team before development begins.
Routing
An inspection reaches the right reviewer.
Reconciliation
Approved quantities reconcile with payment progress.
Access
Each role sees only the projects it can access.
What stays with you
Your modules, our products, your choice of host.
Custom modules and their source code are yours under the engagement agreement. ArkanCS, ArkanERP and ArkanPM remain Digital Cubic products. Hosting on Vloud is optional; we can deploy to your own cloud account instead.
- Construction management
ArkanCS
Construction management for field-to-office workflows: inspections, submittals, drawings, scheduling, and execution control.
Explore - ERP for project-driven companies
ArkanERP
ERP tailored for construction and project-driven companies: finance, procurement, HR, and project accounting workflows.
Explore - Property management
ArkanPM
Property management platform for owners, operators, leasing, maintenance, tenant services, and asset operations.
Explore - Service
Web Application Development
Web platforms and portals designed around real users, business workflows, and long-term maintainability.
Explore - Cloud deployment, hosting, and operations
Vloud
Cloud deployment, hosting and operations platform, offered as SaaS. It runs our own products and hosts client systems.
Explore - AI-assisted debugging and monitoring
ErrorLens
AI-assisted debugging, monitoring and issue visibility, offered as SaaS, to improve system reliability and engineering response.
Explore
Who owns the code?
You do, for the custom work we build for you. It is set out in the engagement agreement. Our own products stay ours.
Is our data ours?
Yes: your data belongs to you.
Will you sign an NDA?
If you need one, yes.
How do we start?
With a free 30-minute discovery call about the workflow, then a short discovery that turns it into an architecture and a phased plan.
How long will it take?
It depends on scope. We confirm scope, timeline and price in a written proposal after discovery.
Where is it hosted?
We can host in-region when data residency matters, or deploy to your own cloud account instead.
Start a conversation
Working through a similar challenge?.
Free 30-minute discovery call. Bring the workflow; we’ll tell you whether it’s a product fit, a custom build or neither, and what a first release could include.