An Engineering Firm's Client Worksheet, Before Gainsight or ChurnZero

Both platforms build health scores from application usage: logins, in-app actions, support tickets. An engineering firm's deliverables are stamped drawings, reports, and site inspections, none of which produce that kind of event stream unless you've built a client-facing project portal that owners or general contractors log into regularly. Most firms haven't, which means there's no usage data for either platform to score against.

Set up a simple tracker with one row per client and these columns: date of the last completed project and whether a new one is in the pipeline, whether the primary contact (owner, developer, or general contractor) has changed, whether the last invoice cycle ran on time without dispute, whether any change orders or scope disagreements are still unresolved, and a one-line note from the project lead on how the relationship feels right now. Nothing here requires software beyond a spreadsheet or your project-management tool's custom fields.

Each client row carries these fields:

• The date of the last completed project, and whether a new one is already in the pipeline.
• Whether the primary contact, such as the owner, developer, or general contractor, has changed.
• Whether the last invoice cycle ran on time without dispute.
• Whether any change orders or scope disagreements are still unresolved.
• A one-line note summarizing the most recent contact with the client.

Take a client with an active structural assessment project. If the general contractor's project manager changed mid-project, that's a flag in the contact column, worth a deliberate check-in rather than assuming continuity. If a change order from three months ago is still unresolved, that's a flag in the scope column, and it's usually the kind of thing that quietly sours a relationship long before the client says so directly. Two flags on one client, especially a contact change and an unresolved scope issue together, is the pattern worth a principal-level call before the project wraps.

The worksheet only works if someone reviews it on a schedule, ideally at a monthly principal or project-lead meeting, not just when a client relationship is already visibly strained. Firms that build this into an existing meeting rather than creating a new standalone task are far more likely to keep it current past the first few months.

If your firm builds a genuine client portal, for project status, document sharing, or inspection scheduling, and general contractors or owners log in regularly enough to generate a real usage pattern, that specific offering becomes worth evaluating against either platform. Keep the evaluation scoped to that portal rather than extending it to client relationships generally, since the worksheet above will keep outperforming a usage-based score for everything outside it. Routing the worksheet's flags into Salesforce, if that's where your business-development pipeline lives, keeps retention next to the rest of your client data instead of in a separate file. See Gainsight vs ChurnZero vs Salesforce for more on how the platforms compare against a CRM directly.

A frequent gap is marking the scope column resolved the moment a change order gets signed, rather than once the underlying disagreement about who caused the extra cost is actually settled. A client who signed the change order under pressure to keep the schedule moving may still feel the firm mishandled the original scope, and that unresolved feeling is what shows up months later as a client who doesn't call for the next project. Track the worksheet entry as open until the relationship itself feels resolved, not just the paperwork.

The same pattern applies to contact changes. Updating the worksheet to note a new project manager on the client side isn't the same as having actually rebuilt rapport with that person. Treat a contact change as an open item until the project lead has had a real conversation with the new contact, not just an introductory email.

Firms that get this right usually build a short standing rule into the worksheet itself: no entry moves from open to closed without a one-line explanation of what actually resolved it. That small habit is what keeps the worksheet honest instead of turning into a checklist people mark done to clear a task, and it takes a project lead a couple of minutes at each monthly review to maintain.