The Development
Playbook

Practice

Why I gravitated to finance from architecture

25 June 202613 min readBy Raphael Mwito
Editorial illustration / Practice

I did not gravitate toward finance because I became less interested in architecture. I moved toward it because architecture kept presenting questions that drawings alone could not answer.

01 / The questions behind the brief

Architecture showed me the building. It also showed me how much had already been decided.

My formal training was in architecture at the University of Nairobi. Architecture teaches you to look closely: to read a site, organise a programme, understand proportion, coordinate systems, and imagine how people might inhabit a place that does not yet exist. It is an education in possibility—but also in constraints.

The longer I looked at projects, the more I noticed that many of their most consequential architectural conditions had been established before the architect began to draw. The land had been acquired at a particular price. A return had been promised. A programme and area target had been adopted. Time, financing, approvals, procurement, and market expectations were already pressing on the brief.

These were not external commercial matters waiting politely outside architecture. They were inside the plan. They influenced the depth of a floorplate, the size of a unit, the generosity of circulation, the choice of structure, the amount of contingency, and the patience available for design.

I wanted to understand not only how a building takes form, but how the conditions for that form are created.

02 / Following the project upstream

Finance offered another way of seeing.

The transition began earlier than I understood at the time. In my first years of practice in Uganda and Rwanda, I worked on offices, serviced apartments, commercial projects, hospitality, and corporate interiors. The principal of the practice also introduced me to financial modelling and business-plan writing. For the first time, the drawing and the development argument were being discussed together.

That connection became more explicit when I moved into an in-house architect and project-management role at Spencon Development Company. I was not only coordinating consultants and developing concepts across land banks in Kenya, Uganda, and Tanzania. I was also researching markets, modelling proposed projects, and writing the initial business cases. The question was no longer simply, “What can we design here?” It was, “What project should this land become, and does its case hold?”

I began moving toward finance because I wanted a more complete language for those forces. Architecture could tell me whether a proposition was spatially coherent. Finance helped me ask whether its assumptions were economically coherent—and who carried the risk when they were not.

Studying toward the CFA charter was demanding precisely because it required a different discipline. It moved from physical relationships to cash flows, capital structures, valuation, uncertainty, and opportunity cost. Yet the underlying habit felt familiar: take a complicated system apart, understand how its pieces interact, and test whether the whole argument holds.

The spreadsheet was not the opposite of the drawing. Both were models. Both simplified reality. Both could clarify a decision or conceal a weak assumption. And both were only as useful as the judgment behind them.

The widening frame

What changed in how I saw a project.

01

Object

System

From the building itself to the land, approvals, capital, delivery, and operations around it.

02

Cost

Consequence

From asking what an element costs to asking what each decision does to risk, return, and long-term value.

03

Client brief

Investment thesis

From receiving the requirements to examining the assumptions that produced them.

04

Completion

Performance

From the finished building to occupancy, income, maintenance, adaptability, and lived experience.

03 / Crossing into investment

The decisive move was from developing projects to managing capital.

At STANLIB, I became Investment Manager for a substantial institutional property portfolio. The scale changed, but so did the point of view. I was helping pension and insurance capital enter the property asset class, originate investments, restructure portfolios, reposition income assets, and decide where land banks could create value.

That role made one lesson particularly clear: a property is never only a project. To an institution it is also an allocation of scarce capital, a stream of income, a concentration of risk, a governance process, and an obligation to beneficiaries who may never see the drawings.

I was also involved in the early work of establishing the Fahari Income REIT and analysing potential assets for it. Years later, returning as CEO of the listed REIT made the arc visible to me. I had moved from drawing buildings, to modelling developments, to allocating capital, and ultimately to being accountable for the strategy and performance of an income-producing real estate platform.

04 / The useful discomfort

Each discipline exposed the blind spots of the other.

Architecture can become absorbed by the object and understate the machinery required to realise it. Finance can reduce the project to variables and understate the physical and human consequences of those variables. Working between them creates a productive discomfort.

A high efficiency ratio may look compelling until the plan reveals what has been sacrificed to achieve it. A premium specification may appear excessive until it is connected to durability, leasing, maintenance, or the credibility of the product. A target return may look precise until one asks how much of it depends on optimistic pricing, compressed time, or risks transferred to somebody else.

I became interested in the space where one discipline interrupts the easy conclusions of another. That is often where the real development decision sits.

05 / Architecture was not left behind

The architectural instinct remained central.

Finance did not replace the way architecture taught me to think. It expanded the field in which that thinking could operate. I still begin with relationships: between a site and its city, a user and a room, a structure and its span, an asset and the systems that sustain it.

But I now also look for the capital relationship, the timing relationship, the operating relationship, and the distribution of risk. A building is not only designed through plans and sections. It is designed through acquisition terms, investment mandates, approval pathways, procurement choices, debt covenants, and decisions about what must be protected when pressure arrives.

Development advisory sharpened this integration further. At Mentor Management, Britam Properties, and later Property Geometrics, the work ranged from feasibility and investment strategy to professional-team assembly, design optimisation, funding, leasing, operations, and asset exits. Projects as different as retail centres, serviced apartments, corporate headquarters, affordable housing, and mixed-use developments kept reinforcing the same point: value is created across the whole chain, not inside one professional package.

This has made me less interested in disciplinary territory and more interested in project coherence. The question is not which profession owns the answer. The question is whether the land, market, design, capital, delivery plan, and long-term use tell the same story.

The work now

I work at the intersection because development itself happens at the intersection.

My work across real estate, investment, architecture, and applied AI follows the same impulse: connect information that is usually separated, make assumptions more legible, and improve the quality of the decision before it becomes expensive to change.

06 / Why this platform exists

The Development Playbook is an attempt to reconnect the project.

The platform grows directly from this journey. It is for architects who want to understand the commercial logic shaping their briefs; analysts who want to see what their assumptions produce in the physical world; developers trying to hold multiple disciplines together; and institutions making decisions that will outlive the original model.

I remain convinced that better development does not come from adding more isolated expertise. It comes from building stronger translations between forms of expertise—and from recognising that the quality of a project depends on decisions made long before the building becomes visible.

I did not move away from architecture. I followed its questions into the wider system that determines what gets built.