An architect can manage a design team and still be unprepared for a client-side development role. The owner is deciding whether to buy a site, how to finance the project, which risks to carry, when to seek approval and what the asset must do after construction. Your architecture experience can be valuable, especially in design quality and consultant coordination, but a development manager is judged against a wider chain of decisions. To make the transition, show where you have already influenced that chain and where you need to learn the owner’s economics.
The Urban Land Institute’s introduction to the development process maps stages from idea and feasibility through construction and asset management. The AIA’s accounts of architects moving toward development show why some practitioners seek more influence upstream. This article is a career translation guide, distinct from becoming an architectural project manager inside a design firm.
Learn the owner’s question at each stage
In concept design, an architect may ask what form best serves the brief. A development manager may first ask whether the site, programme, funding and approvals can support a viable project at all. During design, they may ask whether an option protects value, schedule and operating needs. During construction, they may weigh changes against contingency and commitments to tenants or funders. After handover, the asset still has to operate.
Build a stage map for one project you know. Note the owner’s decision, the information supplied by architects and consultants, and the risk that remained. Perhaps your planning options affected unit count or a façade decision affected operating cost. You may not have seen the full financial model. State what you observed and what you would need to learn to make the owner-side call.
Do not claim that “architects already manage everything” because you coordinated design deliverables. A developer may manage land, capital, entitlement, market, leasing and asset questions beyond the architect’s scope. Respecting that gap makes your transition more credible.
Translate one project without changing the facts
Choose a project where you helped a client decide among options. Tell the story in owner-side terms: the decision to be made, constraints, options, information you supplied, who decided and what followed. For example, “I compared two massing options that changed usable floor area and approval risk; I prepared the planning and access evidence for the client’s decision.” Do not say you chose the investment strategy if you did not.
Include a small decision table rather than only final images. Columns can be option, design effect, approval or cost question, owner decision and unresolved risk. If financial figures are confidential or unknown, do not invent them. You can state that the cost consultant evaluated the effect. A client-side employer wants to know whether you can organise the information needed for a decision.
If your best evidence is a project that was cancelled, it may still be useful. Explain what was learned during feasibility and why the client chose not to proceed, if you are permitted to share it. Avoid presenting cancellation as failure when the decision protected resources. A development manager must sometimes stop a weak project.
Build financial literacy at the right level
You do not need to become an investment analyst overnight, but you should understand basic terms in the roles you target: development cost, contingency, revenue or rent assumptions, financing conditions and time value. Read a current development primer and ask a professional to walk through a simplified pro forma. Then test how one architectural decision changes the model’s inputs. Use a hypothetical example if real data is confidential.
Be clear about uncertainty. Increasing net lettable area might raise projected revenue while making approval or construction harder. A cheaper material may increase operating cost. A fast programme can reduce carrying cost but introduce delivery risk. The owner-side role is to compare these effects with specialists, not to assume one design metric dominates.
In an interview, say which financial decisions you have seen and which you have not. “I have presented design options alongside cost advice, but I have not owned a land-acquisition model” is a useful boundary. Ask whether the role includes training or a finance partner who can help you build that skill.
Show stakeholder and approval work
Architects often coordinate planners, engineers, clients and authorities. Translate that into owner-side evidence: how did you identify a decision maker, prepare an approval, manage conflicting requirements or keep a programme moving? Provide a specific example with dates or stages if you can verify them. Do not imply you controlled an authority’s decision.
Development managers may work with lenders, investors, tenants, community groups and operators as well. If you have not dealt with them, identify the parallel skill and learning gap. A public-sector architecture project with multiple users may show stakeholder mapping, but not lender negotiations. Show the method without erasing the difference.
Ask the prospective employer which stakeholder relationships the new hire will own in the first year. A junior client-side role may focus on reporting and consultant coordination; a senior role may require independent approvals and commercial judgement. Choose the level that matches your actual authority to date.
Change the CV’s verbs
An architecture CV may say “designed a 150-unit scheme.” A development-oriented version can say, if true, “prepared three planning options for a 150-unit scheme, showing area and access implications for the client’s feasibility decision.” The second statement connects your design work to a decision. Keep the architecture skill visible; it is part of your advantage.
Use outcomes you can defend: an approved brief, a resolved programme conflict, a planning submission made, a tender package coordinated or an option rejected after evidence review. Be cautious with “saved £X” or “increased return” unless you saw the actual calculation and are allowed to disclose it. Quantification is useful only when trustworthy.
Put a short transition summary at the top: “Architect with seven years in housing feasibility and delivery, moving toward client-side development management with strengths in option appraisal and consultant coordination.” Adapt it to the role. A list of software tools is less important than evidence that you can help the owner make a decision.
Ask what the job is really responsible for
Test one owner-side trade-off
Imagine that a design change adds attractive shared space but reduces lettable area and delays an approval. Do not answer “approve” or “reject” from instinct. Ask what the shared space is intended to achieve, how the change affects residents or tenants, who has cost and revenue estimates, and whether the approval timeline can absorb it. Then frame the decision the owner must make with the information still missing. In a development interview, this demonstrates that you can respect design quality while understanding the investment and operating consequences. It also shows the difference between presenting an option and owning the commercial decision.
Use the same method with a real project if you have permission to discuss it. State which facts you supplied as architect and which decisions remained with the client. A precise boundary helps the employer see your potential without mistaking adjacent experience for direct development authority.
Does the development manager own a site from acquisition to handover or support a senior director on several assets? Who controls the budget? Who signs consultant appointments? What is the relationship with the internal design team or external architects? How is success measured: approval, programme, financial return, resident outcome or a mix? The answers define whether your experience fits.
Also ask about working hours and risk. Client-side roles can offer more influence but can carry deadline, finance and stakeholder pressures. Do not assume the move automatically improves pay or balance. Compare the written offer and daily responsibilities with your current role.
A 90-day learning plan
When speaking with a developer, ask for an example of an architectural recommendation they rejected despite liking the design. What constraint controlled the decision? How did the architect respond? That story will teach you more about owner-side work than a generic description of “commercial awareness.” It may reveal a financing deadline, operating requirement or approval risk that was invisible to the design team. Practise restating the owner’s concern before proposing a different solution; the skill is to keep the design conversation connected to the decision the client actually faces.
Choose one development stage you know poorly, such as acquisition or asset management. Read an authoritative primer, interview a practitioner and make a hypothetical decision sheet linking site facts to design, programme and finance questions. Then prepare two real project stories with owner decisions and your exact contribution. Apply to roles that can use your architecture strengths while you build the missing commercial skill.
The transition works when an employer can see how you think beyond the drawing set. Show the owner decision you helped inform, the risk you made visible and the financial or operational question you are ready to learn next.
Browse current architecture jobs on Jobs.archi and compare your next step with our guide to architecture burnout and career choices.
The post From Architect to Client-Side Development Manager: Translate Your Decisions first appeared on jobs.archi.