Working ON Your Business & Setting Your Vision

Introduction

You may have built a respected architecture or engineering firm with steady projects, strong relationships, and healthy cash flow. Yet if every design decision, client concern, fee change, and technical question still comes to you, you do not truly own a firm—you own a demanding production job. Growth becomes limited by your calendar. Your team waits for approval, projects slow down, and you cannot spend enough time on strategy, recruiting, major pursuits, or ownership planning.

To scale an architecture or engineering firm, you must move from working IN the firm to working ON the firm. Working IN means producing drawings, reviewing calculations, attending every coordination meeting, answering every RFI, or personally fixing every proposal. Working ON means building the delivery system, developing project leaders, setting the firm's market direction, and creating standards that allow good decisions without your constant presence.

The Shift: From Operator to Owner

Working IN the firm means you are still the primary project technician. You may be the only person who can approve a structural detail, lead a client presentation, resolve a construction issue, or price a scope change. Your technical skill may have built the firm, but it can also become the firm's largest constraint.

Working ON the firm means creating a reliable professional-services machine. This includes defining who can make project decisions, writing project start-up and closeout procedures, training project managers, setting review standards, and building a predictable business-development process. You are not abandoning technical quality. You are making quality repeatable through people, checklists, peer review, and clear authority.

Start by identifying work that truly requires the principal's judgment. A complex zoning strategy, high-risk structural decision, or sensitive client negotiation may belong with you. Routine drawing reviews, meeting agendas, submittal tracking, invoice follow-up, and standard code checks should usually have an assigned owner and a documented process. The goal is not to remove all owner involvement. The goal is to reserve it for the decisions that create the most value.

Defining Your Vision and Core Values

When a principal steps back from daily project work, the team needs clear direction. Otherwise, staff may make different assumptions about design quality, client service, schedule control, profitability, or risk. A useful vision describes the type of firm you are building and the clients you intend to serve. For example: “Within five years, we will be the most trusted 25-person building-systems firm for healthcare renovations across the region.”

Core values should guide real project decisions, not sit on a wall. If a value is “Clear Advice Before Pretty Drawings,” the team knows to raise a code or budget issue early, even when the news is uncomfortable. If a value is “Promise Only What We Can Staff,” project managers know they must check workload before accepting an aggressive deadline. If a value is “One Complete Review,” staff understand that drawings must pass an internal coordination check before going to the client.

Turn each value into observable behavior. Define what it means during project kickoff, design review, client communication, fee negotiation, and construction administration. Then use those standards in hiring, reviews, promotions, and project debriefs. A value that never affects a staffing or project decision is only a slogan.

Real-World Example

Consider the principal of a 14-person civil engineering firm who still reviews every grading plan, attends every client meeting, and handles every contractor question. The firm has good work but cannot accept larger municipal programs because the principal is overloaded. The owner chooses three operating values: “Document the Decision,” “Raise Risk Early,” and “Design for Constructability.”

The firm creates a project kickoff checklist, a standard design-review log, and an escalation rule for budget, schedule, and liability risks. A senior project manager becomes the first reviewer for routine plans, while the principal stays involved in major scope decisions and key client relationships. After 90 days, the principal has moved 20 hours per week away from production and now spends that time recruiting, meeting public-works clients, and improving the firm's project-selection process.