How to Qualify Public and Private AEC Opportunities: A Zoho CRM Walk-Through

Opportunity qualification is the shared process of deciding whether a potential project fits the firm’s services, geography, capacity, relationships, and timing. It matters because public and private opportunities can look attractive while requiring different evidence and different decisions. A source link alone is not a qualification record.

The moment: two opportunities and one review meeting

This is an illustrative scenario. A 14-person architecture and engineering practice works across civic renovations, housing, and light industrial projects. On the same morning, a city posts a library RFP and a private developer asks for a fee proposal. The principal sees the RFP. A project manager knows the developer. The marketing coordinator has the deadline and location.

The team meets without a common record. One person asks whether the practice has the right service fit. Another asks whether the deadline conflicts with a current submission. Nobody can explain why the private lead should be treated differently from the public RFP. The failure this workflow prevents is investing proposal time before the practice has recorded its reasons.

How Zoho CRM handles it

Zoho CRM has lead and deal management, custom fields and modules, workflow rules, tasks, integrations, APIs, and reporting. Start with the vendor’s official CRM overview at Zoho CRM.

1. Create or import the opportunity. Create a lead or deal for each source. Record the client, source, location, service fit, deadline, estimated value, relationship owner, and procurement path. Keep the public notice and private request distinct even when they come from the same contact. Zoho’s CRM model supports records for leads, accounts, contacts, and deals. A sample deal record is Deal Name: Central Library Renovation; Lead Source: Government website; Stage: Qualification; Closing Date: 2026-09-15; Amount: 0. Import only cleaned records so duplicate clients do not create duplicate reviews.

2. Apply qualification fields. Use custom fields or a custom module for the questions the firm actually asks. A simple form can include service fit, sector experience, geographic fit, available team, relationship strength, delivery risk, deadline clarity, and decision. Use defined values such as Strong fit, Needs review, and Do not pursue. For example, add the custom field Service Fit and set it to Strong fit when the opportunity matches the practice’s services. Zoho supports custom modules and fields as configuration options.

3. Assign tasks through workflow rules. When a new opportunity arrives, assign a review task to a named person. Route a public RFP to the marketing coordinator for eligibility and submission requirements. Route a private lead to the principal for relationship context. Set a workflow criterion such as Lead Source is Government website, then create the task Verify eligibility and submission requirements for the marketing coordinator. Zoho workflow rules can respond to record conditions and take configured actions. Keep the rule visible and test it with sample records before relying on it.

4. Review scores and reports. Use a score only when the firm can explain the inputs. Review records by decision, owner, sector, deadline, and source. Build a report with columns Deal Name, Stage, Closing Date, Lead Source, and Owner, then filter it to Stage is Qualification. Zoho CRM has reports and dashboards for reviewing CRM data. The report should expose missing answers and competing deadlines. It should not turn a subjective decision into a false certainty.

Learn more about Zoho CRM →

The trick to using it well

The non-obvious discipline is separating qualification evidence from the decision. Store the facts first. Store the reason for the decision second. “Private housing lead” is not a reason. “Our housing team has relevant experience, the location fits, and the requested fee date conflicts with an existing submission” is useful context.

Define a minimum record before a review can close. Require a source, client, location, service fit, deadline, owner, and decision. Do not make every field mandatory at intake if the source does not provide it. Instead, create a task for the person who can verify it. A workflow that creates a confident-looking record from incomplete data creates faster confusion.

For public opportunities, keep eligibility and procurement questions explicit. For private opportunities, record relationship context and the next conversation. The same CRM can hold both, but the practice should not use one identical checklist for both.

What it delivers

For the illustrative practice, the workflow produces a qualified opportunity record. The library RFP has its source, location, service fit, deadline, owner, and eligibility questions. The private developer lead has its relationship, scope, expected timing, and next conversation.

It produces an owner and next task. The marketing coordinator can verify the RFP requirements. The principal can confirm the private client’s expectations. A review does not end with “we should look at this.” It ends with a named action or a documented decision.

It also produces a pipeline report. The practice can see which opportunities need information, which are qualified, and which were declined. The reasons become useful practice knowledge when they are written consistently.

Where it fits, and where it doesn’t

Zoho CRM fits a practice that needs configurable records, qualification fields, workflow rules, tasks, reports, and connected systems. The ToolSpec identifies Zoho Flow, Google Workspace, Microsoft 365, REST APIs, and webhooks as surrounding integration options.

The limitation is that scoring criteria and source validation remain firm responsibilities. Configured automation can amplify incorrect or duplicate intake data. Zoho does not determine whether the library procurement is eligible, whether the firm has capacity, whether a relationship is strategically important, or whether the developer’s request is complete. The architect still decides whether to pursue the opportunity. The review should include an explicit way to pause an opportunity. A missing document or unclear deadline is different from a rejection. Record that difference so the owner knows whether to investigate, wait, or close the record.

Keep the solicitation and request documents in the appropriate repository. Link to them where the practice’s permissions allow. Protect contact and project information with roles and profiles. API features and quotas vary by edition, so verify the current plan before designing a connected intake. Monitor failed automations and review changes to qualification rules.

The takeaway

The useful Zoho CRM pattern is to record facts, apply a transparent qualification method, assign the missing-information task, and review the decision. For a 14-person practice, that makes a public RFP and a private lead comparable without pretending they are identical. Zoho supplies configurable CRM mechanics; the firm supplies criteria and source checks.

Common questions

Should public and private opportunities use the same fields?

Use shared basics such as client, source, location, service fit, deadline, owner, and decision. Add path-specific questions for procurement eligibility or relationship context.

Is a score required?

No. A short evidence checklist may be better than a score. Use a score only when people can explain how its inputs produce the result.

Can a workflow check an RFP?

It can assign a validation task or flag missing fields. The task should point to the solicitation and the eligibility questions the reviewer must answer.

How should a declined opportunity be recorded?

Close it with a clear reason, such as capacity, service mismatch, geography, deadline, or procurement constraint. Avoid a generic “not a fit” value when the team needs to learn from the decision.

Can the CRM import opportunity data?

The record supports imports and connected intake patterns. Clean duplicates, map fields, secure credentials, and test the result before making an imported source part of the review process.

Who owns qualification?

The firm should name an owner for the record and separate reviewers when independence or procurement rules require it. Automation can route the work to those people.

Disclosure: DataDrivenAEC may earn a commission if you subscribe through links in this walk-through. Product behaviour is described from Zoho Corporation’s documentation; the scenario is illustrative.