For contractors whose Salesforce project left estimators, project managers and business development working from separate spreadsheets again, we stabilize the org and finish what was promised.
A construction rescue usually centers on the gap between winning work and building it. Failed orgs often track bids well enough but lose the thread when a project is awarded, so project managers never see what business development promised and the ERP holds the only reliable job data. We assess the bid pipeline, the project object design and the connection to job costing, fix the handoff first, and then decide what else to keep. Estimators, preconstruction and operations each get a working piece back, not a general promise of improvement.
Construction breaks standard sales assumptions. One building project attracts several general contractors bidding at once, so a subcontractor may pursue the same job through multiple customers, and a naive build creates a duplicate opportunity for every bidder. Revenue is recognized over the life of a project, not at signature, which leaves forecasting built on closed-won amounts looking wrong. Field supervisors work on job sites with gloves, dust and patchy signal, so they reject anything that feels like office software. Many stalled construction projects were designed by people who had not seen that reality, and a rescue has to correct those assumptions before adding anything new.
We review how projects, bidders and bids relate. Where the original build created a separate opportunity for each general contractor, we introduce a shared project record with linked bids, merge the duplicates and preserve which contractor each bid went to. Win rates and pipeline reports then describe real jobs instead of inflated counts. Estimators also get a cleaner view of which contractors they bid through most often and how those relationships convert.
When a bid is won, scope, contacts, schedule assumptions and exclusions should carry into a project record that operations owns. We rebuild that transition, add a short checklist for preconstruction, and make sure project managers can see the original estimate notes without asking business development for a forwarded email. Accounting sees the same awarded record, so job setup in the ERP starts from agreed information rather than a phone call.
Superintendents and foremen abandoned many construction orgs because the mobile experience asked for office-style data entry. We cut field forms to daily essentials such as site issues, photos and customer contacts, check how they behave on site, and move everything else back to the office where it belongs. Photos and notes attach to the project and account automatically. Office staff then pick up follow-ups the same day instead of waiting for a weekly meeting.
Leadership wants backlog, pipeline by market sector and expected revenue by quarter. Failed builds often reported only on closed opportunities. We rebuild reports and dashboards around awarded but unbilled work, using job cost data from the ERP, so executives stop exporting to spreadsheets to answer basic questions. Reports are grouped by market sector, region and project type, matching how leadership already discusses the business.
Recovery starts with interviews across business development, estimating, operations and accounting, followed by a review of the org and its data. We stabilize whatever blocks bidding immediately, since a missed bid deadline costs more than any configuration flaw. Data model changes are staged in a sandbox and tested against real projects from the past pipeline before release. Accounting joins every integration decision, because job cost numbers are what ownership trusts. Releases are small and announced in advance, and each one is paired with short training for the group it affects.
Awarded jobs create or match projects in the ERP, and cost, billing and change order totals return to Salesforce for backlog reporting.
Estimate totals, versions and key assumptions attach to the bid record, so nobody retypes numbers or loses track of which version the customer saw.
Schedules, submittals and daily logs stay in the project tool; Salesforce references status and key dates so account teams know where each job stands.
Model the relationship between a building project and the contractors bidding it before cleaning anything. Getting this wrong again recreates the duplicate problem and makes win-rate reporting meaningless for another cycle. Decide how owners, architects and general contractors appear as related parties on each project.
Backlog and revenue figures shown in Salesforce must match what the finance team reports. Agree the source of each number with accounting early, or executives will keep one spreadsheet as the real answer. Document the definitions for backlog, awarded value and expected revenue inside the reports themselves.
Test mobile changes on site, not only at a desk. Glare, gloves and signal gaps expose problems that office testing misses, and field crews judge the whole system by that first experience. Bring a superintendent into testing and let their feedback decide what stays on the mobile layout.
Client names are anonymized.
The most common cause is one opportunity per bidding general contractor on the same building project, so a single job appears several times. Estimated values stack up and win rates fall. Fixing it means linking bids to one shared project and adjusting reports, which we can do without losing the history of who you bid through.
It should not. Payroll, retainage, cost codes and pay applications are jobs for the contractor's accounting platform. Salesforce handles relationships, pursuits and customer-facing activity, then reads cost and billing results back for reporting. Many failed projects tried to duplicate ERP functions, and part of a rescue is removing that overlap. Keeping each system in its lane makes the integration simpler to support.
Ask what they would record on a phone at the end of a shift and build only that. Most rescues remove fields, simplify navigation and pre-fill job context so entries take seconds. We also check whether field staff even need full licenses, since some tasks suit simpler forms or the project tool. Adoption returns when the app saves them a phone call.
We freeze changes to bid records during busy bid periods, test every modification in a sandbox using recent real bids, and release in small steps with notice to estimators. If a change touches how bids are created, we walk the estimating team through it before release rather than after complaints arrive. Estimators also get a named contact for questions during each release.
One onshore team with 150 Salesforce certifications, a Salesforce Consulting Partner since 2017.
A monthly brief for the people who own Salesforce, AI and revenue technology
What changed in Salesforce and AI this month, and what to do about it.
One email a month. Written by the consultants who deliver the work, not by a marketing team, for the leaders who make the technology decisions.
Consultant analysis, not vendor recaps. One click to leave.