Client management software for architects: seven problems it should solve
What client management means in an architecture studio, as opposed to a sales CRM: seven problems that appear past three people, what to ask any tool about each, what AtelierLab will not do, and a ten-minute test to run before you migrate anything.
- Client management for an architecture practice is the live relationship after the appointment: the drawings issued, the fee owed, the conversation, and who is allowed to see what. It is not the same job as a sales CRM.
- Seven problems show up in almost every studio past three people: no agreed current drawing, fees chased rather than collected, one client's details beside another's, consultants over-shared, a scattered conversation, unpriced revisions, and client files that leave with the person who held them.
- A tool earns its place by closing those seven, not by adding a dashboard. It should also say what it does not do.
- If you issue every drawing yourself and run two or three projects, a folder and a spreadsheet are still the right answer.
Ask the principal of a six-person architecture firm what "client management" means and you get a list of small, specific irritations. Which revision did the Mehras actually receive? Who told the Kapoors the lift shaft had moved? Why is the stage-three invoice still open when the drawings went out in March?
None of that is a software problem until the studio is big enough that no single person holds all of it in their head. This guide is for that moment: what client management software for architects is supposed to do, the seven problems it should solve, what it will not solve however it is sold, and a ten-minute way to test any tool, including ours, before you commit.
What client management means in an architecture studio
Search for "CRM for architects" and you mostly find sales tools: a pipeline of enquiries, a stage called "proposal sent", a reminder to follow up. That is a real job, and for a studio that lives on referrals it is a small one.
The job that costs a practice money comes after the appointment letter is signed. It has four parts, and every architecture studio already does all four, usually by hand:
- The drawings. What was issued to this client, at which revision, on which date, and what is current today.
- The fee. What is owed at this stage, whether it has been invoiced, whether it has been paid.
- The conversation. Approvals, questions, the instruction that changed the scope, in a place both sides can find again.
- The access. Who may see this project: the client, the structural consultant, the contractor, a new associate. For how long.
Client management software for an architecture firm is the system that holds those four things per client. A generic project management tool holds tasks. A sales CRM holds prospects. Neither has a concept of a drawing going out at a revision against a fee, which is why studios keep bolting custom fields onto them.
Seven problems it should solve
These are in the order they tend to hurt. Each has the symptom, the cost, and what to look for in a tool. Where AtelierLab has a specific answer, it is named, and linked to the page that describes the mechanism.
1. Nobody can say which drawing is current
The symptom is a client asking you to resend the latest plan for the third time because the folder holds five files with near-identical names. The cost is not the resend. It is the contractor who prices from the March plan because that was the one in his WhatsApp.
Look for versioned replacement: uploading a new sheet adds a revision rather than overwriting, the superseded ones stay on the record behind it, and the client opens one place and sees the live set. AtelierLab's document sets work this way. The habits that sit under it, numbering and a register, are in the drawing issue register guide and cost nothing.
2. Fees are chased instead of collected
The drawings go out because holding them back feels rude, and the stage invoice then ages for six weeks. This is the single most expensive habit in small-studio practice, and it is a process failure rather than a character flaw: the invoice and the deliverable live in different places, so nothing connects them.
Look for a tool that joins the invoice to the issue. In AtelierLab you attach the stage invoice to a document or a whole set; it stays locked until the payment is confirmed, then unlocks on its own. That is payment-gated issue, and the full collection workflow is in how architects collect fees online in India.
3. One client's details sit beside another's
A shared drive organised by project name is one mis-click from showing the Sharmas the Guptas' floor plan. Most studios have never had this go wrong and are one careless share away from it. The more serious version is a client portal that merely filters the screen: the data is still reachable.
Ask whether separation between clients is enforced below the interface. AtelierLab gives each client a private workspace with isolation enforced in the database, so one client cannot query another's records. Ask any vendor the same thing and note how precise the answer is.
4. Consultants and contractors get more access than they need
A Drive link sent to the structural consultant in March is still live in November. A contractor who needed one package has the whole project. The usual fix, a login for everyone, creates a password nobody remembers and a person nobody removes.
Look for expiring, revocable links that do not require an account, so access ends when the package does. Share links do this, and the payment gate still applies to them. The sharing protocol article covers what each recipient should receive at each stage.
5. The conversation is scattered across WhatsApp, email and calls
The instruction that changed the scope was a voice note. The approval was a thumbs-up emoji. Three weeks later nobody can show the sequence. WhatsApp is how Indian clients actually talk, and no tool will move them off it entirely, so the aim is narrower: decisions that affect scope or fee should live beside the drawings they concern.
Client chat is a message thread inside each client's workspace, switchable on or off per client. Use it for the decisions that matter and leave WhatsApp for "running ten minutes late". The point is a record, not a replacement.
6. Revisions go unpriced
Revision five arrives as one reasonable request after four others that were absorbed. Software cannot decide what your fee includes; that is a clause in the appointment letter and a number in a log. What software can do is make a round countable: when every issue is a numbered revision with a date, "this is the fourth set since approval" is a fact rather than an impression.
The pricing side lives in the scope creep guide, with a free variation log that works in a spreadsheet today. Treat a tool as support for that discipline, not a substitute for it.
7. A client's file leaves with the person who held it
The associate who ran the Verma house has left. Their emails, their downloads folder and their phone had the whole story. Whoever inherits the project reconstructs it from the client's memory, which is an awkward place to start a relationship.
If drawings, invoices and the thread live in a client's workspace rather than in someone's inbox, handover is a matter of opening the file. The audit log adds the record of what was issued, unlocked and downloaded, which is the part that is normally lost first.
| Problem | What to ask a tool | AtelierLab's answer |
|---|---|---|
| No agreed current drawing | Does a new upload add a revision or overwrite? | Versioned sets; superseded revisions kept |
| Fees chased | Can a file stay locked until an invoice is paid? | Invoice attached to a set; unlocks on verified payment |
| Client data mixed | Is separation enforced below the screen? | Per-client workspace, isolated in the database |
| Consultants over-shared | Can links expire and be revoked, with no account? | Expiring, revocable share links |
| Scattered conversation | Is there a thread next to the drawings? | Per-client chat, on or off per client |
| Unpriced revisions | Is each issue a dated, numbered revision? | Yes; the pricing clause is still yours to write |
| File leaves with the person | Does the record live with the client, not the inbox? | Workspace plus audit log of issue, unlock, download |
A tool that answers all seven well is rare. One that answers the two you hurt on, and says no to the rest, is better than a long feature list.
What it will not do
Be suspicious of any studio software that claims to do everything. AtelierLab is deliberately narrow, and the edges are worth stating:
- It is not a lead pipeline. It starts when the client is appointed.
- It has no timesheets or resourcing. In a five-person Indian practice that is a problem you rarely have yet. If you bill by the hour, you need something else beside it.
- It is not CAD or BIM. It holds the files you produce and does not convert them into a proprietary format.
- It is not your accounts. Keep Tally or Zoho for the books. This is the layer above, where the client, the set and the invoice meet; see what practice management means for an Indian studio.
- It is not site management. Snag lists and daily progress reports are another category.
A ten-minute test for any tool
Before you migrate anything, run this on a free trial, a demo account, or a demo call. It takes ten minutes and tells you more than a feature matrix.
Create a client and invite them
Time it. If it takes longer than a few minutes, you will skip it for the fourth client, and a system used inconsistently is worse than none.
Upload a drawing, then replace it
Does the old one survive behind the new one, and can the client still tell which is live?
Try to see another client's file
As the first client, hunt for any path to the second. Then ask where the separation is enforced.
Attach an invoice and try to open the file unpaid
The file should stay shut. Then ask who confirms the payment and what happens on a refund.
Ask where the money goes and what happens if you leave
Your own account or a platform wallet? Can you take your records out in the formats you put them in?
Rolling it out in a studio of three to fifteen
Most tools fail at adoption, not at features. A rollout that works is small and has an owner.
Name one person who owns it
Usually the partner who feels the fee problem most. A tool nobody owns drifts into being optional.
Start with the next project, not the live ones
Do not migrate a job mid-stage. Every client who is appointed after the switch begins in the workspace; older jobs finish where they are.
Tell the client in the appointment letter
One sentence: drawings are issued through your private workspace, and each stage's drawings are released on payment of that stage's fee. The payment stages guide has the wording.
Set a cutover date for issuing
After it, nothing leaves by email attachment. A soft transition means running two systems forever.
Do you need it yet
Not every studio does. If you are one or two people with a handful of live projects and you issue every drawing yourself, the whole system fits in your head, and software would solve a coordination problem you do not have. The honest threshold is the point at which "which is the latest?" stops being something you know and becomes something you check. That usually arrives around three people or six concurrent projects, or when unpaid stage fees become a weekly chore.
The full comparison of the options, including staying exactly where you are, is in Drive, WhatsApp or a client portal.
If these seven read like your studio
AtelierLab is in early access and onboarding our first studios personally. Set up in minutes, drawings released on payment, fees settling into your own Razorpay account. Tell us how many people issue drawings and how many projects are live, and we will say honestly whether it fits yet.
Questions, answered
The questions architects ask most about this, in plain language.
Ask us anythingSoftware that holds the live relationship with each client after appointment: the drawings issued to them and which revision is current, the fee owed and whether it has been paid, the conversation around the work, and who is allowed to see the project. It differs from a sales CRM, which tracks prospects, and from a general project tool, which tracks tasks.
Partly. A CRM manages enquiries and follow-ups before the appointment; client management software manages the project relationship after it. Many studios need both and use two simple tools. AtelierLab covers the second half only and does not run an enquiry pipeline.
Project management tools are built around tasks, owners and deadlines. Architecture practice is organised around a set of drawings that goes out at a revision against a fee, so the useful objects are the client, the issue and the invoice. You can bend a task board into that shape, but you will maintain the bend indefinitely, and it still cannot keep a file locked until an invoice is paid.
They sign in to their workspace with credentials you issue, in a browser, with nothing to install, and pay through Razorpay's hosted checkout with no account on their side. A consultant who needs a single package does not need a login at all: send an expiring link.
AtelierLab is in early access and onboarding by invitation, so there is no public price to quote. The honest comparison is against what the current arrangement costs: the hours spent reconstructing what was issued, and the stage fees that arrive late because drawings went out ahead of them.
The product is built around the studio and its clients. If you run a multi-partner practice with an unusual structure, tell us how work is divided when you enquire and we will answer for your set-up rather than guess. It is available in India only for now, because payments run through Razorpay in rupees.