Sales Calls & Pricing That Works

Understanding Consultative Discovery Calls

A strong sales call for an architecture or engineering firm is not a portfolio show-and-tell. It is a working session to understand the client's project, risks, constraints, and definition of success. Think of the call as an early site investigation. Before an engineer recommends a foundation or an architect develops a concept, they gather facts. Sales should work the same way.

Start by asking why the project matters now. Is the owner facing a lease deadline, a failed building inspection, a capacity problem, a new funding award, or a growing client base? Ask what has already been tried, who will approve the work, and what could delay the project. For an engineering client, this may uncover a stormwater permit risk or an outdated utility survey. For a commercial design client, it may reveal that the real issue is not floor area but a move-in date tied to a new lease.

Do not rush to explain every service your firm offers. First understand the project well enough to decide whether your firm is a good fit. A useful discovery call should identify the project type, location, estimated construction value, schedule, decision makers, procurement method, required disciplines, and known risks.

Pricing Psychology

Clients rarely judge a fee in isolation. They compare it with the value of the project and the cost of mistakes. A $35,000 feasibility and concept package may feel high if the client sees only drawings. It looks different when the work can prevent a $400,000 purchase of the wrong property, avoid a failed entitlement strategy, or help the owner secure financing.

Explain what the fee protects or enables. An early survey, code review, and site feasibility study may reduce the chance of redesign, permit rejection, or an expensive change order later. A properly scoped engineering design may help a developer meet a funding deadline and begin construction during the right season.

Price the work according to scope, responsibility, and risk. Do not discount simply because a prospect says another firm is cheaper. First confirm whether the proposals include the same deliverables, site visits, coordination, calculations, permit responses, and construction-phase services. If the scope is different, the prices are not truly comparable.

Real-World Example

Suppose a manufacturing company wants to add a 40,000-square-foot production area. The owner asks for a quick fee to prepare drawings. Instead of immediately quoting a low design number, the principal asks about the production schedule, equipment loads, utility capacity, environmental requirements, permitting path, and planned construction budget.

The discussion reveals that the existing electrical service may not support the new equipment and that the company must be operational before a major customer audit in nine months. The firm proposes a paid feasibility phase covering utility review, code analysis, site constraints, and a preliminary plan for $28,000. The firm then offers a separate design agreement after the risks are understood. The fee is easier to accept because it is connected to avoiding delay and protecting a major customer relationship.

Key Concepts

- Diagnosis Over Pitching: Ask enough questions to understand the building, infrastructure, business, and decision process before describing your services.
- Cost of Inaction: Show what delay, weak documentation, permit problems, or poor coordination could cost the owner.
- Silence is Golden: State the fee and scope clearly, then stop talking. Give the client time to consider the investment.
- Scope Before Discount: Resolve differences in deliverables before discussing price reductions.

Building Trust

Trust grows when your questions show practical experience. A developer trusts a firm that asks about entitlements, pro forma timing, and lender requirements. A public agency trusts a firm that understands procurement rules, public meetings, and grant deadlines. An industrial owner trusts a team that asks about shutdowns, safety, and process continuity.

Do not promise outcomes you cannot control. Instead, explain your process, assumptions, exclusions, and decision points. Send a short recap after the call with the client's goals, known risks, next steps, and information needed. This proves that you listened and creates a clean record for the next conversation.

Conclusion

A productive sales call is an early act of professional service. Diagnose the client's situation, connect your work to financial and project consequences, price the defined scope with confidence, and let the client make an informed decision. Firms that sell this way win better-fit projects, protect margins, and start client relationships with fewer surprises.