In-house product delivery
Architecture, approved customisation and core implementation stay with the Spontaneous Enterprise team. You are not handed to an anonymous partner midway through configuration.
Implementation
ERP goes live when the organisation is ready — not when the installer leaves.
Shasvatm is delivered as a governed journey: discovery against live projects, configuration that mirrors your authority, masters you own, training that includes the site, signed scenarios, then a controlled rollout. Implementation is quoted separately from licence. Architecture and core delivery stay with our team.
Seven stages
Each with an exit criterion, not a vague milestone.
In-house delivery
Product team configures and stands up go-live.
Your operating model
Approvals and projects as they already work.
Controlled rollout
Hypercare, an issue register, then steady support.
How we work
Construction ERP fails in the gap between software and the way sites actually run. We close that gap on purpose.
Project-driven organisations do not fail implementations because they lack screens. They fail because indents, approvals, stock and RA bills were never forced onto one backbone with named owners. Shasvatm implementation is designed against that failure mode: live projects in discovery, authority encoded in the workflow engine, and a go-live that is allowed to be staged.
Standard product first
We configure the approval engine, masters and project structure before we discuss custom code. Change requests are estimated, approved and delivered against a man-day rate — they are not buried inside a vague implementation bucket.
Your data, your openings
You own master-data completeness. We provide the method, templates and validation. Historical migration, extra reports and third-party interfaces are scoped when they are real requirements, not assumed.
Remote-first, site-aware
Implementation is primarily remote so project and commercial teams can join from sites. On-site days are used when they change the outcome — and are charged separately when they are required.
The journey
Seven stages. One backbone. No silent handover.
Select a stage. Every step states what we do, what you do, and what must be true before we move on. Timelines depend on scope, masters, process decisions, integrations and whether your teams are available for validation and training.
Same journey for Community, B1 and Enterprise — the module set and company structure change with edition, the discipline does not.
Stage 01
Discover
We implement your operating model — not a generic template with your logo on it.
Business processes, project structure, existing systems, users and masters. The output is a shared picture of how work actually moves from site to head office.
Shasvatm owns
- Map project, procurement, stores, subcontract, billing and finance as they run today
- Record approval authority as it exists in the organisation, not as software would prefer it
- Identify existing systems, statutory touchpoints and integration boundaries
- Agree edition coverage, in-scope modules and what is explicitly out of this phase
You own
- Nominate a sponsor and process owners for project, commercial and finance
- Walk us through a live project, not a cleaned-up example
- Share current masters, sample documents and known pain points
Exit criterion
A written discovery note: in-scope processes, project structure, users, masters and open decisions.
At a glance
Discover through stabilise, without losing the thread.
01
Discover
Before configuration begins
02
Configure
Product, not custom code
03
Prepare
Data is the critical path
04
Train
Role-based, not classroom theatre
05
Validate
Your scenarios, your documents
06
Go live
Controlled rollout
07
Stabilise & improve
After the first billing cycle
Readiness
We will not pretend a go-live date is a substitute for organisational readiness.
The implementation fee assumes timely master data, availability of key users, standard product workflow, an agreed calendar and primarily remote support. That is not small print — it is how a construction ERP actually gets adopted.
A sponsor who can decide
Approvals, freeze dates and “good enough” masters need an owner inside your organisation. Implementation cannot substitute for that authority.
Process owners, not only IT
Procurement, stores, billing and finance must be in the room. Site users must see the mobile and store transactions they will live with.
A calendar you can keep
The quoted implementation assumes timely masters, agreed workshops and UAT attendance. Slippage on your side revises timeline and, where it consumes extra effort, cost.
Scope that matches the edition
Community, B1 and Enterprise do not implement the same module set. We will not configure budget control or production on an edition that does not include them.
Commercial clarity
Implementation is a defined piece of work. It is not an open cheque.
Licence, flat annual and subscription fees do not include implementation. Customisation is estimated after a written requirement, with a minimum billing block, and delivered only when commercially approved. Integrations, biometric or messaging gateways, and extra reports are scoped when they are required.
| In the implementation | Scoped separately |
|---|---|
| Configuration of in-scope modules for the selected edition | New paid modules and custom development unless approved as a change request |
| Standard product reports and the workflows agreed in discovery | Client-specific reports and BI dashboards beyond the product set |
| Guidance on masters, openings and user mapping | Unbounded legacy / historical data migration |
| Primarily remote implementation support | Travel, on-site days and premium on-site support unless quoted |
| Cutover support and a defined hypercare window | Statutory or accounting advisory; hardware, cloud and database licences on client-hosted deployments |
Cloud is the default conversation. Self-hosted remains a first-class option; on client infrastructure, you bear server, database and related licences, and we deliver and support the application. How commercials sit beside implementation →
What “ready” looks like
Live is a control decision, not a software event.
We look for signed scenarios on your documents, openings that finance will stand behind, super-users who have already transacted, and a freeze the sponsor will enforce. If those are missing, we recommend waiting — a delayed go-live is cheaper than a live system nobody uses.
- A project structure and BOQ / job setup that commercial teams recognise
- Approval paths that match how purchase orders and bills are actually signed
- Store and site users able to GRN, issue and indent without a parallel register
- The first operating cycle planned: who raises, who approves, who bills
- Hypercare named by severity, with one issue register
Start with discovery, not a go-live date.
A first conversation covers how your projects, approvals and billing actually run — and whether Community, B1 or Enterprise is the right edition to implement.