Lean Planning, CPM and Work Tracking all in one place.
// quick_answer
Smartapp implementation for a large general contractor takes 2–3 days for a single pilot project and 60–90 days for full company-wide deployment. The phased approach — pilot first, then portfolio rollout — is standard for enterprise GCs. A dedicated Smartapp implementation manager handles ERP integration configuration, cost code mapping, and company template setup. Your IT team reviews and approves rather than builds. After initial rollout, each new project deploys in days because it inherits your standardised templates and live ERP connection automatically.
[
SECTION_01
The full implementation schedule
From contract signature to full portfolio deployment — every workstream, every milestone, plotted against a 90-day horizon.
Pilot project
ERP integration
Template config
Parallel run
Portfolio rollout
Legacy retired
W1
W2
W3
W4 ✦
W5
W6 ✦
W7
W8
W9
W10 ✦
W11
W12
W13 ✦
✦ = milestone gate · W4: ERP integration live in sandbox · W6: pilot validated, rollout begins · W10: 80% of portfolio live · W13: legacy tools retired
[
SECTION_02
Phase-by-phase breakdown
Five phases, each with a clear owner, clear deliverables, and a clear exit criterion before the next phase begins.
PHASE_01
Pre-implementation: scoping & configuration planning
Days 1–5
›Smartapp implementation manager conducts discovery session with your operations lead, IT director, and finance team (2–3 hours total)
›ERP structure reviewed — WBS hierarchy, cost codes, chart of accounts, and integration touchpoints documented
›Cost code mapping document produced — maps Smartapp categories to your ERP's financial structure. This is the single most important configuration artefact in the whole deployment
›Project type matrix defined — which template configurations apply to which project types (commercial, data center, heavy civil, O&M)
›Pilot project identified — recommended: a mid-size active project with an experienced superintendent and a PM comfortable with new tools
EXIT CRITERION: Cost code mapping reviewed and approved by finance lead. Pilot project confirmed.
PHASE_02
Pilot project deployment
Days 1–3
›Drawing library imported from your existing document management system or file server — latest revision of each sheet published to 
Smartapp FIELD™
Smartapp FIELD™›Project team onboarded on Smartapp FIELD™ mobile app. Average onboarding time: 83% faster than tools previously used by the same GC
Smartapp FIELD™ mobile app. Average onboarding time: 83% faster than tools previously used by the same GC›Daily report template configured for this project type. RFI workflow set up — responsibility matrix, SLA thresholds, escalation rules
›PLANNER configured — CPM schedule imported (from Primavera P6, MS Project, or Asta), six-week pull planning window activated
›First daily reports submitted. First RFIs raised. Implementation manager on call for the first 72 hours
EXIT CRITERION: Field team completing daily reports and submitting RFIs in Smartapp without assistance. Drawing access confirmed across all devices including offline.
PHASE_03
ERP integration & template standardisation
Weeks 1–4
›SAP, Oracle, or other ERP connector deployed into sandbox environment. Cost code mapping applied. Synthetic transactions posted and verified in ERP
›Pilot project runs with ERP integration active — field cost postings from daily reports flow into ERP automatically. Finance team verifies postings against manual process in parallel
›Company-wide templates built in AppStudio — standardised daily report formats, RFI workflows, safety checklists, financial controls. Templates derived from pilot configuration and extended across project types
›ORG Central portfolio dashboard configured for VP/CIO role — filter views, alert thresholds, KPI selections approved by executive stakeholders
EXIT CRITERION: ERP integration validated by finance team over 2-week parallel run. Company templates approved by operations lead.
PHASE_04
Portfolio rollout
Weeks 6–13
›Active projects onboarded in waves — recommended: 8–12 projects per week for large portfolios, prioritised by project phase (early-stage projects first, then mid-stage, then near-completion)
›Each project inherits company templates automatically — drawing library imported, ERP connection live, field team onboarded. Each project: 1–2 days of setup time
›Subcontractors invited to Smartapp for their scope — no seat charge, no IT setup required on their side
›Hardware activated where applicable — Jobsite BADGE, ACCESS, BOARDS, and RTLS configured per project site requirements
›Weekly rollout review with implementation manager — adoption metrics, field feedback, configuration adjustments, escalations resolved
EXIT CRITERION: 80% of active project portfolio live on Smartapp with ERP integration active. Field team daily report completion rate above 90%.
PHASE_05
Legacy retirement & steady state
Weeks 10–13
›Legacy tool contracts identified for non-renewal — typically 5–7 point solutions (Procore, Primavera, safety app, finance module, daily reporting app, drawing management, middleware)
›Historical data archived from legacy tools before decommissioning — RFI logs, submittal registers, drawing revision history exported and stored
›Manual ERP processes retired — Friday spreadsheet export discontinued, finance team trained on live Smartapp/ERP dashboard
›Handover to Smartapp Customer Success Manager — ongoing QBR cadence, product updates, and expansion planning for new project types
EXIT CRITERION: All legacy tools retired or on non-renewal notice. 100% of portfolio live. ERP receiving live field data with no manual export process remaining.
[
SECTION_03
ERP integration: what affects the timeline
The ERP integration is typically the longest single workstream. Here's what drives the timeline — and what Smartapp does to compress it.
For SAP (Smartapp's official certified integration), the timeline is 2–3 weeks from kickoff to sandbox validation. For Oracle (bidirectional connector), 2–4 weeks. For other ERPs via open API, 1–3 weeks depending on the ERP's API maturity and your IT team's availability for review.
The single biggest variable isn't technical — it's the cost code mapping review. Smartapp's integration team builds the mapping document in 2–3 days. But the review cycle — getting sign-off from finance, IT, and operations on how Smartapp's cost categories map to your ERP's WBS structure — can take 1–2 weeks if stakeholders aren't aligned and available. GCs that move fastest on implementation pre-assign a finance lead as the mapping review owner before Day 1.
// implementation_accelerator
The two factors that most accelerate Smartapp implementation: (1) a dedicated finance lead who owns the cost code mapping review — not a committee — and (2) choosing the pilot project before the implementation kickoff call. GCs that have both ready on Day 1 consistently reach full portfolio rollout in 60 days or fewer.
"We had Smartapp live on our first project in 48 hours. The ERP integration took three weeks — but that was mostly waiting for our SAP team to schedule the sandbox session, not anything on Smartapp's side."
— SVP & CIO, Gilbane Building Company
[
SECTION_04
Implementation timeline compared
How Smartapp's implementation compares to the other platforms large GCs typically evaluate.
| Milestone | Smartapp | Procore | Autodesk CC |
|---|---|---|---|
| Speed | |||
| Pilot project live | 2–3 days | 1–2 weeks | 2–3 weeks |
| Company-wide rollout | 60–90 days | 3–6 months | 4–8 months |
| New projects after initial rollout | Days (template inheritance) | 1–2 weeks | 1–3 weeks |
| Resources required | |||
| IT team involvement | Review & approve only | Active configuration | Active configuration |
| Development / custom code | None — no-code AppStudio | Often required | Often required |
| Implementation managed by | Smartapp team | SI partner often needed | SI partner often needed |
| ERP integration | |||
| SAP integration timeline | 2–3 weeks (certified native) | 6–12 weeks (3rd party) | 6–12 weeks (3rd party) |
| ERP integration owner | Smartapp integration team | 3rd party connector vendor | 3rd party connector vendor |
| Ongoing ERP maintenance | Managed by Smartapp | 3rd party dependency | 3rd party dependency |
The speed difference comes primarily from two structural advantages: Smartapp's no-code AppStudio (which eliminates the configuration backlog that slows enterprise software rollouts) and the certified SAP integration (which removes the 3rd-party connector procurement and setup cycle). Implementation partners — the system integrators that Procore and Autodesk deployments commonly require — are not needed for Smartapp.
[
SECTION_05
Implementation risks — and how to avoid them
The most common reasons enterprise GC implementations run long — and what Smartapp's team does to prevent each one.
// risk
Cost code mapping delays
Finance and IT stakeholders aren't aligned on how Smartapp categories map to ERP structure. Review cycles span multiple teams without a clear owner.
// mitigation
Assign a single finance lead as mapping review owner before Day 1. Smartapp produces the mapping document in 2 days — the review should take one working day with a single decision-maker.
// risk
Over-customising before going live
Teams spend weeks customising templates and workflows before anyone has used the platform — adding friction and delaying field adoption without meaningful benefit.
// mitigation
Go live with Smartapp's default configuration on the pilot. Measure what the field actually needs after 2–3 weeks of real use, then customise based on evidence rather than assumption.
// risk
Pilot project chosen poorly
Pilot selected is either near completion (too little to learn from) or the most complex project in the portfolio (too risky for a first deployment). Both scenarios reduce the pilot's value.
// mitigation
Ideal pilot: a mid-phase project (25–60% complete), mid-complexity, with a superintendent who is comfortable with technology and a PM with strong organisational skills. Early-stage projects are acceptable alternatives.
// risk
SAP / ERP team availability
The ERP team can't schedule sandbox access or approve integration settings promptly — creating a 2–4 week gap in the implementation that's completely outside Smartapp's control.
// mitigation
Schedule ERP team availability and sandbox access as the very first item on the implementation kickoff call — before anything else is agreed. Smartapp can start pilot deployment and template configuration while ERP runs in parallel.
// risk
Field adoption resistance
Superintendents and field workers resist the new platform, continue using legacy tools informally, and the rollout stalls with partial adoption — leaving the company paying for two systems.
// mitigation
Make the superintendent's life measurably easier in the first week — daily reports submitted faster, RFI responses on their device, drawings always current. Smartapp's 83% faster onboarding stat is real; the adoption case makes itself if the rollout starts with the right project and the right super.
// risk
Scope creep during rollout
Mid-rollout, additional feature requests, integrations, and customisations accumulate — extending the timeline without a clear owner and exit criterion for the rollout phase.
// mitigation
Enforce a clear rollout scope: get all active projects live on standard configuration first. Log enhancement requests in a backlog for Phase 2, addressed after legacy tools are retired. The rollout phase has one job: get everything live.
[
SECTION_06
Frequently asked questions
Does Smartapp implementation require a system integrator or implementation partner?
No. Smartapp's implementation team handles the full deployment — ERP integration, template configuration, field team onboarding, and drawing library migration. System integrators and implementation partners are not required because Smartapp's no-code AppStudio eliminates the configuration work that typically requires a specialist. For GCs with complex SAP environments or custom ERP configurations, Smartapp's integration team works directly with your IT team rather than routing through a third party.
What happens to data from Procore, Primavera, or other tools being replaced?
Smartapp's implementation team supports migration of core data from existing tools: drawing libraries and revision history, RFI logs, submittal registers, and schedule files (from Primavera P6, MS Project, or Asta). Historical financial data stays in your ERP — the integration connects Smartapp to the live ERP, so pre-existing project financials remain in their original system. For compliance and audit purposes, legacy tools are typically archived rather than deleted.
Can Smartapp be implemented mid-project — not just at project start?
Yes, and this is common for large GCs who begin deploying Smartapp while projects are already active. The drawing library import handles mid-project drawing sets automatically — the platform publishes the current revision of each sheet without requiring a fresh set. RFI logs can be imported from prior tools so historical context is preserved. Financially, the ERP integration can be configured to start from a defined cutover date, with pre-cutover actuals remaining in the original system.
How is the Smartapp implementation team structured for an enterprise deployment?
Each enterprise deployment is assigned a dedicated Implementation Manager who owns the end-to-end rollout — from kickoff through legacy tool retirement. The Implementation Manager is supported by Smartapp's integration team (for ERP configuration), a field adoption specialist (for superintendent and field worker onboarding), and a solutions architect (for complex AppStudio configurations). After rollout is complete, the account transitions to a dedicated Customer Success Manager for ongoing support, QBRs, and expansion planning.
What is the minimum viable deployment — if we want to start with just one module?
Smartapp PLANNER™ (CPM and lean scheduling) and Smartapp FIELD™ (drawing management, RFIs, daily reports, safety) can each be deployed independently as a starting point. The most common entry point for large GCs is FIELD — which goes live fastest and delivers visible productivity improvements within days. PLANNER and FINANCE are typically activated in weeks 2–4 of the pilot. The full Smartapp ONE platform (all modules plus hardware) is activated during the portfolio rollout phase.
What does implementation support cost for an enterprise GC?
Implementation support — including the dedicated Implementation Manager, ERP integration configuration, template setup, and field onboarding — is included in the Smartapp ONE enterprise contract for large GC deployments. There is no separate implementation fee for standard deployments. For GCs with unusually complex ERP environments or custom configurations requiring extended integration work, a scoped additional services engagement may be proposed — this is agreed and priced before implementation begins, not after.
Plan your implementation
Request a demo and we'll scope your specific deployment — ERP, project types, team structure, and a realistic 60-day plan.
Last updated · May 2026 · Smartapp resources
