What We Evaluate in the First Conversation About Your Project
In the South Bay and Peninsula, including Saratoga, Los Gatos, Palo Alto, Campbell, Sunnyvale, Menlo Park, Atherton, Woodside, and the surrounding cities we work in, most residential projects start with the same set of questions. Can we add a second story. Can we open this wall. Can we stay within a budget. Can we control cost. Can we start construction quickly.
On the surface, these sound like design questions. In practice, they are not. They are early signals of structure, risk, and feasibility that determine how the entire project will behave later in design, permitting, and construction.
What matters in the first conversation is not producing answers. It is understanding whether the project is stable enough to design without forcing corrections later. We are effectively evaluating whether the project has been thought about clearly enough to design, or whether it is still at the stage where the homeowner's assumptions about what is possible have not yet been tested against what is actually there.
Second story additions: structure before form
When a second story is raised, the question is rarely about form. It is about whether the existing structure can support a fundamentally different load condition, and what that change triggers across foundation, framing, and code compliance.
In most residential homes, especially older construction, zoning is not the constraint. Structure is. A second story is not an extension of design. It is a redefinition of the building system.
In Cupertino, there is a second question that determines the entire project timeline: the ratio of second-floor area to first-floor area. If that ratio exceeds 66%, the project moves from the Two-Story Permit path into Residential Design Review, a process with a public hearing, design compatibility findings, and a schedule that runs four to six months longer. We establish that ratio in the first conversation, not after schematic design is underway. It is a design variable, not a ceiling. Every room placement decision that follows is shaped by it.
In Saratoga, we map remaining FAR against the program, identify tree canopy that may intersect with the proposed footprint, and establish whether the project falls inside or outside the Design Review triggers before any design direction is set. In Palo Alto, the first determination is which review track applies, ODS or Individual Review. Those are not interchangeable paths. The answer shapes how we sequence design from the start.
Wall removal: a structural investigation, not a layout decision
Removing walls is often framed as spatial improvement. In reality, it is a structural investigation.
Walls are frequently part of load paths that are not visible until the system is evaluated as a whole. Once those elements are removed, the question is no longer about openness. It is about what has to be introduced to maintain stability.
This is where many projects begin to expand in scope without it being visible at the start. A homeowner expecting a cosmetic reconfiguration discovers a beam, a post, or a foundation condition that changes the scope and the budget before design has formally begun.
Budget alignment: calibrating expectations, not confirming a number
Budget is usually treated as a fixed constraint. In early stages, it is not.
It reflects how defined the project is, not what the project can actually support. Two projects with identical budgets can behave completely differently depending on how much uncertainty exists in structure, permitting, and scope definition.
Until those elements are clarified, budget is not a control tool. It is an incomplete input. We had two clients in the same year, both in Saratoga, both with second-story addition projects, both with similar budgets. One came to us after already having conversations with a contractor who had given them a rough number. The other came with no prior conversations, just a clear sense of what they wanted. The first project took three design cycles to stabilize because the contractor's early number had shaped expectations that did not survive structural evaluation. The second moved from feasibility through permit submittal without a single massing revision. The budget on both projects was comparable. The definition at the start was not.
Cost is driven by uncertainty, not complexity
Cost is often assumed to be tied to size or design ambition. In residential work, it is driven by ambiguity.
When scope is unclear, or when decisions are deferred into construction, the project is effectively resolved multiple times by different parties under different assumptions. That is where cost drift originates. Control does not come from simplifying design. It comes from defining scope early enough that interpretation is no longer required later.
What we are not doing in the first conversation
We are not designing. We are not committing to a scope, a fee, or a schedule.
We are evaluating whether your project is a fit for the site, for the budget, and for our practice. That evaluation protects you as much as it protects us. A project that moves into design without that alignment produces drawings that have to be revised when constraints arrive. The first conversation is where we determine whether we can make those commitments honestly.
If the project is feasible and the scope is realistic, we move forward. If the site has constraints that change the program materially, we establish that before any design investment is made.
What we evaluate first
Every early conversation is centered around one question: how much of this project is already defined, and how much still needs to be resolved before design can safely begin.
Because residential architecture is not defined by ideas or drawings. It is defined by when constraints become fixed. If constraints are fixed too early, the project becomes reactive. If constraints are fully understood before design begins, the project becomes stable. That difference determines everything that follows.
The role of early architectural involvement
Our role at the beginning of a project is not to produce immediate design direction. It is to establish what is actually true about the project. What exists. What is structurally possible. What zoning allows. What can be built without creating conflict later in the process.
Only after that is understood does design begin. At that point, decisions are not speculative. They are grounded in a complete understanding of constraints. That is what allows the project to remain consistent through permitting, engineering, and construction.
The real takeaway
Our position is direct: the first conversation with a homeowner is not a design conversation. It is a diagnostic one. We are not evaluating what they want to build. We are evaluating whether the project is stable enough to design without creating problems that will cost more to fix later than they would have cost to prevent. Most architects will tell you what is possible. We think the more important question is what is actually true about the project right now, before anything is committed. That evaluation is not a preliminary step before the real work begins. It is the real work. And getting it right before design begins is what makes the rest of the process reliable. If you are in the early stages of a remodel, addition, or custom home in the South Bay or Peninsula, the most useful thing you can do is understand your project's constraints before you start designing inside them.
If you're thinking about a remodel or addition and want to understand what a proper feasibility evaluation actually looks like before design begins, our Feasibility and Starting Smart guide covers exactly that. Read the guide
For what architects actually do across the full design and permit process and how constraint definition shapes every phase, see What Architects Actually Do on Remodels and Additions.
For guidance on when to bring an architect in before purchase, before engaging a contractor, or at the start of design, see When to Bring an Architect Into a Home Purchase or Renovation Plan.