What clients should expect from a tech-enabled architect

Many architecture practices advertise technology as a service differentiator: CAD drawings, 3D renders, BIM, drone surveys. For a client evaluating architects, these terms can be hard to interpret. Does it matter whether the practice uses Revit or AutoCAD? Does a 3D render make the building better? Does a drone survey add value or just cost?

The answer depends on whether the technology is integrated into the process or just layered on top of it. A practice that produces 3D renders but runs the project on WhatsApp and a Google Sheet is not meaningfully more technology-enabled than one that sketches on paper but communicates clearly and manages decisions systematically.

The question clients should ask is not 'what software do you use?' but rather 'how does your technology make my project better managed, more accurately priced, and better documented?' This article explains what a genuinely tech-enabled practice delivers and what questions to ask when comparing.

In traditional practice, a site analysis begins with a site visit. The architect walks the plot, takes notes, reviews the title deed, identifies constraints, and spends a day or two compiling a site report. This is the right process, but it is slow, and it means the client cannot get a meaningful picture of their site's potential until the architect has been formally appointed and has made a physical visit.

A tech-enabled practice connects to GIS (Geographic Information Systems) data that provides parcel boundaries, zone classifications, setback requirements, topography, proximity to utilities, and environmental overlays from a digital query. This does not replace the site visit — physical observations about gradient, access, neighbour context, and ground conditions still require eyes on the ground. But it means the fundamental regulatory picture is available before the first meeting.

For clients, this matters because it compresses the decision cycle. Instead of waiting two weeks for a site report, the client can walk into the first meeting already knowing the zone, the permitted floor area, the required setbacks, and the rough cost range. The meeting is about confirming and refining, not discovering.

One of the most common client complaints about architects is that cost estimates are vague, inconsistent, and always low at the start and high at the end. This is a genuine problem in traditional practice: the early estimate is intuitive, based on the architect's memory of similar projects, with no documented assumptions.

A tech-enabled practice uses documented cost benchmarks derived from real project data: measured rates for different construction types, finish levels, building typologies, and locations. When the preliminary cost estimate says 'KES 65,000-80,000 per square metre for a mid-range residential building in Mombasa,' there is a documented source for that range, and the client can interrogate the assumptions.

This also means the estimate updates correctly as the project develops. If the client changes from two storeys to three, the system can update the preliminary cost estimate based on the changed floor area rather than starting from scratch. If the specification changes, the rate changes accordingly. The trajectory from preliminary estimate to contract sum is tracked and explained, not just jumped at the tender stage.

A major source of friction in traditional architecture practice is information fragmentation. The site analysis is in one folder, the design drawings are in another, the approval documents are in a third, the contractor correspondence is in an email thread, and the client is not sure what the latest version of anything is.

A tech-enabled practice maintains a single project record that connects all of these elements. Site data, design documents, approval submissions, cost plan, contractor correspondence, payment certificates, and variation orders all sit in the same structured file. The client can access their project status at any point without having to chase the architect.

This matters especially at transition points: when a consultant leaves and is replaced, when a contractor is changed, when a dispute arises and records need to be produced, or when the client wants to hand the project over to a property manager. In each case, the project record is the reference — not someone's inbox.

Email is the default communication channel for most architecture practices in Kenya. It is flexible and familiar, but it makes decisions hard to track, approvals easy to miss, and the project timeline difficult to see as a whole.

A tech-enabled practice uses structured communication: approvals are formal sign-offs with a date and a clear description of what was approved; instructions are numbered and referenced; payment certificates are issued through the system with a clear link to the contract items they cover; and the project dashboard gives the client a stage-by-stage view of progress.

Clients who have experienced both models consistently report that the structured approach reduces anxiety: instead of wondering whether the project is on track, the client can see where it is and what the next decision point is. This is particularly important for clients who are not physically present in Mombasa and are managing a project remotely.

There is a lot of noise around AI in construction and architecture. It is worth being specific about what AI means in the current practice context and what it does not mean.

At Architect Darani, AI-assisted analysis currently contributes to three areas. First, site feasibility: the system uses trained models to interpret zoning data, generate cost benchmarks from project comparables, and flag site constraints from GIS layers. This is not a replacement for the architect's judgment — it is a tool that the architect uses to work faster and with better-documented assumptions.

Second, document generation: standard reports — feasibility summaries, climate briefs, approval checklists — are generated from structured data rather than written from scratch each time. This reduces the time between site query and report delivery without reducing the quality of the output.

Third, content and communication: client summaries, proposal documents, and status updates are drafted from structured project data and reviewed by the consultant before being sent. This ensures accuracy while saving time on routine correspondence.

What AI does not do: it does not design buildings, does not make regulatory judgments, and does not replace professional indemnity. Every output from an AI-assisted system is reviewed and validated by a registered professional before it goes to the client or to a statutory body.

When evaluating architecture firms for a project, the technology question is worth asking directly. Specific questions that will reveal how integrated the technology actually is:

How will I know the status of my project without calling you? If the answer is 'you call me,' the project management is not systematised. If the answer is 'you have access to a project dashboard,' ask to see a sample.

Where do your cost estimates come from? If the answer is vague, the estimates are intuitive. If the answer references benchmark data and documented assumptions, the estimates are traceable.

How are design changes tracked? In a fragmented practice, changes get lost or misunderstood. In a structured practice, every instruction is numbered, dated, and linked to the relevant drawing revision.

Can I access my project documents directly? In a well-structured practice, the client has direct access to their project record — drawings, approvals, cost plan — without having to request each document separately.

Architect Darani is happy to walk any prospective client through the REDM system before a formal appointment. The project check is the best way to start: it shows how the technology works in practice, with your actual site data.