Making Your Business Run Without You

Understanding the Franchise Rule

The Franchise Rule is about making your architecture or engineering firm run the same way every time, even when you are not in the office. Think of a firm where the principal is not the one redlining every drawing, chasing every permit comment, or answering every contractor question. The work still moves because the process is built into the firm.

In this industry, clients do not buy just design talent. They buy predictability. A school district wants the same response time on a renovation as it got on the first project. A developer wants permit sets that follow a standard path. A GC wants RFIs answered before the job slows down. If your firm depends on one star designer or one rainmaker engineer, you do not have a business yet. You have a pile of heroics.

The Importance of Systems

A firm that runs like a franchise has repeatable systems for proposals, kickoff, schematic design, code review, QA/QC, consultant coordination, and client communication. These systems make sure every project follows the same steps, no matter who is running it.

For example, if your team is doing tenant improvement work, there should be a standard process for site verification, base plan setup, consultant scope checks, and permit submission. If the process lives only in someone’s head, errors creep in. One PM uses one naming system, another uses a different one, and suddenly the drawing set is a mess before it even reaches QA.

Building a Self-Sufficient Firm

To make the firm self-sufficient, start by finding where you are the choke point. Maybe every consultant email goes through you. Maybe only you know how to negotiate scope creep with a client. Maybe only you can review fee proposals or decide if a change order should be issued. That is not leadership. That is a bottleneck.

Build simple rules people can follow. Create a checklist for responding to contractor submittals. Build a decision tree for common client requests like moving a wall, adding a rooftop unit, or changing a structural bay after schematic design. Set clear thresholds for when a project manager can decide alone and when it needs principal review.

Real-World Scenario

Consider a small civil engineering firm that handles stormwater design for private sites. The owner personally reviews every hydrology report and every grading plan before it goes out. When that owner is buried in meetings or at a site walk, submittals stall, clients wait, and the staff sits idle. After building a standard review checklist, defining acceptance criteria for each phase, and training a senior engineer to sign off on routine work, the firm keeps projects moving even when the owner is away.

The Role of Documentation

Documentation is how you turn firm knowledge into an asset. That means written QA/QC checklists, standard drawing sheet indexes, permit submission guides, consultant coordination steps, and sample emails for difficult client or contractor conversations.

In an architecture or engineering firm, documentation should be easy to find and use. Store it in your project management system, not buried in a random folder on one person’s desktop. If a new project architect can onboard and run a standard permit set without asking five people for help, your documentation is working.

The Benefits of a Franchise Model

When your firm runs on systems, projects move faster, fewer mistakes slip through, and your people make better decisions without waiting on you. It also lowers risk. A firm that can survive a vacation, a sick leave, or a busy bid week is a stronger firm.

Just as important, systems help you grow without lowering quality. You can add more projects, more staff, and more clients without the whole thing breaking every time workload spikes.

Conclusion

The Franchise Rule is about building an architecture or engineering firm that does not depend on the owner to keep the wheels turning. When your proposals, project delivery, QA/QC, and client communication all have a standard method, the firm gets steadier and more valuable.

The goal is not to remove judgment. The goal is to stop relying on memory and heroics. In this business, good systems protect quality, protect profit, and protect your time.

Example Scenario

Imagine an architecture firm where only the principal knows how to handle permit responses with the city. By creating a permit response playbook, including standard comment response language, consultant coordination steps, and approval authority levels, the firm can keep projects moving even when the principal is in client meetings or out on vacation.