Ramp vs Brex for a Studio's Phase-by-Phase Project Costs

A project number alone isn't specific enough for a studio, since a sample order made during schematic design and a rendering seat used during design development both belong to the same project but represent very different phases of billable work. A rendering seat purchased during design development, for instance, is a very different cost signal than the same seat still active during construction administration, when the studio should barely need it. Tagging spend to the phase, not just the project, is what lets a principal see whether a specific phase is running over its fee before the whole project closes out.

Most studios that only tag to the project level discover the phase-level overrun after it's too late to adjust the next phase's scope or fee to account for it.

Rendering, BIM, and visualization software seats are usually purchased by whoever is actively working on a deliverable and needs the tool that week, which means approval often happens informally, if at all. A studio that requires a project lead's sign-off before a new seat gets added avoids the slow accumulation of seats nobody remembers assigning, which is where a surprising share of software overspend actually comes from.

The goal isn't to slow designers down, it's to make sure a seat that gets added for one deliverable gets removed once that deliverable ships, rather than renewing quietly for years.

A simple rule, one seat per active deliverable, reviewed when that deliverable ships, catches most of the drift without requiring anyone to audit software spend on a fixed schedule.

A sample order that gets rejected during design development is still a real cost, and coding it to the phase it was ordered in, rather than dropping it from tracking because it didn't make the final selection, gives a principal an honest view of what a phase actually cost to run. A pattern of expensive samples that never make the cut is worth catching early, since it usually points to a design process issue rather than bad luck. Over a handful of projects, that data starts to show whether a particular material vendor or spec approach tends to generate more rejected samples than others, which is worth knowing before the next proposal goes out.

Treating rejected samples as invisible spend just because they didn't ship is the same mistake as ignoring a search that didn't result in a placement: the cost still happened.

Ramp's speed in issuing project- or phase-labeled virtual cards fits a studio taking on new commissions regularly, since a new project's spend controls can be set up the same day a contract is signed rather than after weeks of onboarding. Its automated receipt matching also reduces the manual work of tying plot prints and sample orders back to the right phase.

A studio with multiple offices, or one that carries significant equipment purchases alongside routine project spend, has more reason to check with Brex directly on how it handles a multi-office structure and what limit that kind of spend can actually support. The tradeoff, as with most comparisons in this space, is a fuller application up front: a platform built for multi-office accounts generally wants a clearer financial picture before it opens up that structure. That's less of an issue for an established studio than for one just building its first formal spend process.

The real cost shows up at the next fee negotiation, when a studio underbids a phase because it never had accurate data on what the same phase cost on a comparable past project. It's the same problem an engineering firm faces without project-level cost data: pricing decisions get made without the evidence that would actually justify them.

Studios that track spend by phase build a genuine internal benchmark over time; studios that don't are pricing every new project on instinct instead of their own history.

Build phase-level tracking around these habits:

• Tag spend to the project phase, not just the project number, so a principal can see whether schematic design or construction administration is over its fee.
• Require a project lead's sign-off before any new rendering, BIM or visualization seat is added, and name who removes it once the deliverable ships.
• Code rejected sample orders to the phase where they were ordered, so the phase's true cost stays visible.
• Compare phase costs across comparable past projects before pricing the next fee proposal, instead of bidding on instinct.