Industry Insights

Where Software Subscriptions Quietly Eat Your Practice's Margin.

By Adam Morgan12 November 20269 min read
Where Software Subscriptions Quietly Eat Your Practice's Margin

A practice's software bill rarely appears on a fee proposal, yet it quietly erodes margin month after month. Here is how to find the leak and close it.

The Margin You Never Quoted For

Article illustration Fee proposals are built on hours. Principal, associate, Part II, visualiser: each gets a rate, each gets a number of days, and the total becomes the fee. Software almost never appears as a line. It sits underneath as overhead, paid monthly, and it comes straight out of profit whether the job runs well or badly. That would not matter if the bill were small. It usually is not. A five-person practice with a tool each for CAD, modelling, rendering, retouching, layout and a website can be paying for six or seven separate subscriptions before anyone bills an hour. Every one of them is priced per seat or per account, and none of them care whether the fee on the current job is £4,000 or £40,000. The arithmetic is simple enough to do on the back of a drawing: seats multiplied by monthly cost multiplied by twelve. Here is what that looks like at the two ends of the market.
ScenarioSeatsMonthly per seatAnnual cost
Consolidated platform, annual billing5£19£1,140
Consolidated platform, monthly billing5£29£1,740
Revit alone (public 2026 listings, roughly $3,005 to $3,045 per user a year)5about $250 equivalentabout $15,025 to $15,225
The Revit figures come from public 2026 comparison listings and are directional only. Check current UK VAT-inclusive pricing, and check whether you are on a full subscription, a limited tier or a promotional rate, before you quote your own numbers. The point survives the caveats: one BIM seat priced at that level is more than some small planning-stage commissions earn in profit, and it is a cost before rendering, image editing, publishing, storage or collaboration tools are added. Now set that against a real job. Take a modest householder or small change-of-use planning commission. After staff time, insurance and the practice's own overhead, the net profit on it is often a few thousand pounds. A software stack running into five figures a year means several such commissions exist largely to pay for the tools that delivered them. That is the margin you never quoted for.

Software scales by seat. The fee does not. Every extra person you hire adds a full set of subscriptions to a cost base the fee was never built to carry.

The invoice is only the visible part. Each additional tool adds file conversion, licence administration, onboarding for new starters and the quiet hour lost when someone cannot remember which package holds the latest drawing. None of that time is billable. All of it is paid for.

Audit the Stack Like You Audit a Fee Bid

You already know how to scrutinise a fee. You check every line, ask what stage it covers, and question anything that looks padded. Apply the same discipline to the tools. Start with a one-page register. One row per tool, with these columns:
  • Tool and named seat holder. Who actually holds the licence, not who it was bought for.
  • Annualised price. Convert monthly and quarterly billing to a yearly figure so they compare fairly.
  • Billing currency and renewal price. Introductory pricing and renewal pricing are often different.
  • What it includes. Credits, storage, commercial-use terms, file formats, maximum output size.
  • Project stage in use. Concept, planning, tender or construction. Be honest about which stage it genuinely serves.
Once the register exists, three patterns tend to jump out. ### Seats used for one task a month A rendering licence kept alive for a single competition entry is the classic case. It was bought for a deadline, it earned its keep for three weeks, and it has been billing every month since. Flag any seat that is opened less than once a month and ask whether a short-term arrangement would do the same job. ### Daily tools versus crunch-point tools Separate what the studio opens every morning from what it opens only at submission week. The daily tools justify their cost by volume. The crunch-point tools are where overlap hides, because nobody reviews them between deadlines and the renewal date arrives unnoticed. ### Duplicated function This is where the quiet savings sit. Two tools that both retouch images. Two that both lay out a Design and Access Statement. A presentation package and a layout package that overlap on every A3 sheet. A cloud storage plan inside a tool that duplicates the practice's main server. Mark every pair that does the same job at the same project stage, then decide which one stays. Article illustration A discipline-by-discipline view helps here, because the same overlap appears wherever people work across several tools. Film and VFX teams pay separately for rendering, compositing and editorial. Product designers move between CAD, visualisation and presentation. Landscape practices combine terrain, planting and imagery. Interior studios coordinate material libraries, renders and client boards. Educators manage student licences across drawing, modelling and publishing. None of these is a quantified market finding. Treat them as audit categories: the same question of what overlaps applies in each, and architecture is no exception. If AI generation tools sit in the stack, give them their own rows. They behave differently from conventional software, because they add a volatile layer on top of the fixed subscriptions.

The Hidden Costs Between the Tools

The register captures what you pay. It does not capture what happens in the gaps between tools, and that is where the larger, less visible cost lives. ### Handoffs are paid for in hours Round-tripping a model between a drawing package, a renderer and a layout tool costs time on every hop. Export, check the geometry, fix what the exchange format broke, import, re-apply the materials. Time is the thing a practice actually sells, so every hop is margin leaving through the door. ### Version drift is rework The second cost is subtler. A client sheet built from last week's export is already out of date when the principal moves a window. Somebody notices at the pin-up or, worse, after issue, and the sheet is rebuilt. That rework was never in the fee. It was caused by the gap between two tools, not by anything the designer did. ### Count the handoffs on one planning submission Walk through a typical planning submission and count them.
  1. The plan and model are drawn in a CAD or BIM package. Handoff one: export to a renderer.
  2. Views are generated. Handoff two: export images to an editing package.
  3. The renders are retouched for context, planting and light. Handoff three: placed into a layout tool.
  4. The Design and Access Statement sheets are assembled around them. Handoff four: drawings re-exported from the CAD package to sit beside the views.
  5. Everything is exported as a PDF. Handoff five: check scale, fonts and page size before it goes to the planning portal.
Five handoffs for one submission, each with its own chance of a broken link, a flattened layer or a font that did not travel. Multiply that across a practice running several live applications and the unbilled time becomes a real number.

Every handoff is a place where hours leak and versions drift. Count them per submission before you decide the stack is fine.

Article illustration Where one platform holds the steps together, the handoffs shrink without anyone changing how they design. In ArchAdemia Tools, Linea holds the plan and the model as one building, Retouch handles the render in the same workspace, and Layout carries the Design and Access Statement and the crit board. A perspective view can go from Linea straight to the rendering studio, and the retouched image drops into a Layout sheet without a round trip through three separate exports. The designer still designs the way they always have. The gaps between the tools are what get smaller.

Consolidating Without Losing Capability

Consolidation only pays if the replacement does the job. A cheaper tool that cannot read a consultant's file costs more than the one it replaced. So test any candidate on a live project, not a demo file. ### Keep working with consultants' CAD and BIM The first test is exchange. Linea imports DWG, DXF and IFC, and exports DWG, DXF and IFC4, so existing work moves in and out of consultants' CAD and BIM tools without a wholesale switch. It also reads native IFC files from Revit and ArchiCAD. The import dialog draws the file before it lands, and a practice CAD file that holds twenty-odd drawings in one model space can be cropped to the single plan you want with a click. Check these against your own consultant files, not against a sample, because exchange behaviour is the thing most likely to differ between practices. ### Drawing issue and presentation under one roof Vector takes a CAD or PDF export and turns it into editable linework: drop in a vector-ready PDF, a DWG or a DXF, and it lands as real, editable geometry at true real-world scale, with the layers restored. Layout exports vector multi-page PDFs at true sheet size, with optional bleed and crop marks. Between the two, drawing issue sheets and presentation sheets can sit in one place rather than passing through a separate drawing package and a separate publishing package. ### The plan, the price and the trial ArchAdemia Tools is a single plan: £19 a month billed yearly (£228 a year), or £29 a month billed monthly, all in. It starts with a 7-day free trial that needs no card, which means a practice can run a real submission through it before cancelling anything it already pays for. Do exactly that. Choose a live or recently issued planning application, rebuild the views and sheets, and see where the friction really is. ### What the credits cover Credits cover AI actions only. Drawing, modelling and manual layout work cost none, so the monthly bill does not scale with every hour of drafting. This matters because it separates the fixed cost of the platform from the variable cost of generation, and it is the right way to reason about any tool that sells credits. That reasoning applies to AI generation tools generally, and it is worth doing before you commit to any of them. Published credit-based plans can look inexpensive until you work out what iteration costs. Higgsfield's listed plans, for example, run at $15 a month for Starter (200 credits), $49 for Plus (1,000) and $129 for Ultra (3,000), and its own material lists 35-plus models. That is vendor marketing, not independent validation, and unused credits, model restrictions and commercial-use terms can make an apparent monthly price misleading. Per-use pricing is easier to read. Runway's developer pricing page lists Seedance 2.5 at $0.20 per second at 480p, $0.30 at 720p, $0.68 at 1080p and $1.10 at 4K, with an 80-credit, $0.80 minimum generation. These are platform-listed rates, not independent measurements of quality, render time or success rate. Even so, the arithmetic is instructive. A ten-second 1080p clip at the listed rate costs $6.80 before failed attempts, reference inputs or subscription fees. Ten attempts cost $68. For a competition animation or a client fly-through, iteration is the real cost, not the one clip that finally works.

When you price any generation tool, budget for the attempts, not the finished output. Iteration is where the money goes.

Pricing Software Into Your Fees From Now On

The audit is a one-off. The habit is what protects margin. ### Treat the tool bill as an overhead and allocate it Allocate the software cost to each project, so the true cost of a competition entry or a planning application is visible. If a competition run needs a rendering seat for three weeks, that seat belongs on the competition's cost, not buried in general overhead where it quietly depresses every other job. Honest allocation changes which commissions look profitable. ### Predictability protects fixed-fee work On fixed-fee work, scope creeps and hours stretch. The fee does not move. A smaller, more predictable subscription line means one fewer variable eating the margin when the job overruns. A flat per-seat plan is easier to forecast than a stack of separate subscriptions with different renewal dates and different price changes. ### Review it on a schedule Put the register review in the same diary slot as the annual fee-rate review. Software is then never the thing nobody looks at. Re-check renewal prices, seat counts and which tools each project stage genuinely used. Before the review, collect the evidence for each tool: named seat, annualised price, billing currency, renewal price, credits, commercial rights, file formats, maximum output and actual project stage. For any interoperability claim, including the ones above, verify against the vendor's current documentation and your own consultant files rather than taking a summary on trust.

You cannot control what a client will pay, but you can control what it costs to deliver, and the software stack is the easiest cost to cut without touching the quality of the work.

Start with the register this week. List every tool, every seat and every renewal date, then mark the duplicates and the single-task licences. Whatever you cut goes straight back into profit on every commission that follows.

Keep reading.

Try ArchAdemia Tools for yourself

Draw it, model it, render it, publish it. One place, built for architects and small practices. From £19 a month, all in.

See what it does