Your Architecture Project Descriptions Are Describing. They Should Be Persuading.

Pull up your firm’s portfolio page and read a project description out loud. If it sounds like “a 3,200-square-foot residence featuring reclaimed white oak flooring and a cantilevered steel staircase,” you’ve written a spec sheet. It’s accurate. It’s also doing almost nothing to convince the person reading it that they should hire you for their project. Don’t bury the best part of the story under a pile of square footage, like a load-bearing wall nobody’s allowed to talk about.

Describing versus persuading

Describing tells someone what exists. Persuading tells someone why it matters, and specifically, why the firm behind it is the one to trust with a similar problem.

Here’s the same project, described and then persuaded.

Describing: “This 3,200-square-foot residence features an open-concept living area, reclaimed white oak flooring, and a cantilevered steel staircase as the home’s central architectural feature.”

Persuading: “The clients had a long wish list and a shorter lot than they’d hoped for. Every version of the floor plan sacrificed either the open living area they wanted or the buildable footprint for the staircase. We solved it by cantilevering the stair off the second floor, which freed up the entire ground level for the open-concept space they’d been told wasn’t possible on a lot this size.”

Same project, probably the same photos. One of these gives a prospective client evaluating your firm a specific reason to believe you can solve a problem like theirs, because you just showed them you solved one.

Why most firms default to describing

It’s safer and it’s faster. Materials and dimensions are factual and easy to write without thinking too hard about the story. The actual decision-making behind a project, the tension between what the client wanted and what the site or budget allowed, requires someone on the team to remember the messy middle of the project, not just admire the finished result. That takes real effort to write, and it’s exactly the part that persuades.

It’s also the part competitors can’t copy. Any firm can post a beautiful finished photo. Only your firm can describe the actual constraint you solved on that actual project, in your own words. That specificity is the entire competitive advantage a written project description can offer, and most firms leave it sitting on the table, unused, like a decorative pillow.

The three-question framework

For every project description, answer three questions before you write a word. What did the client actually want, in their own words, before the design process started? What got in the way, whether that was budget, the site, a code requirement, or a heated disagreement about what would actually work? And what did your firm do to solve it, specifically enough that a reader understands the decision, not just the outcome?

Answer those three honestly and you have a persuading description. Skip them and you have a caption for a photo that could belong to any firm with a good photographer and a nice drone.

This matters more now, not less

Prospective clients researching architecture firms are increasingly asking AI tools to recommend one, and those tools favor content that demonstrates real expertise and a clear point of view over generic descriptions. A portfolio full of spec-sheet descriptions gives an AI tool (and a human reader) nothing to cite or remember. A portfolio full of specific, persuading project stories gives both something to work with.

If you want help turning your existing portfolio into content that actually makes the case for hiring your firm, that’s exactly the kind of project we like.

FAQs

Q: How long should an architecture project description be? Long enough to answer what the client wanted, what got in the way, and how your firm solved it, often 150 to 300 words. Length matters less than whether it tells an actual story instead of listing specs.

Q: Should I remove the technical details like square footage and materials? No, keep them. They matter to some readers and they support search visibility. Add the story around them instead of replacing them. The persuasive version includes the facts and the reasoning behind the decisions.

Q: What if the project didn’t have a dramatic story or constraint? Most projects have some version of a decision point, even a quiet one: a budget tradeoff, a site limitation, a client preference that shaped the design. Look for the smallest real decision and describe it specifically rather than manufacturing drama that isn’t there.

Q: Does this apply to interior designers and design-build firms too? Yes. The same describing-versus-persuading gap shows up across architecture, interior design, and design-build portfolios. Any firm whose work is visual and whose decision-making process is invisible to a prospective client benefits from writing the story behind the photos.