MEP consultants · CRM
Keep every architect, project and proposal in one record the whole firm can read.
A CRM for an MEP consultant is a single record of the architects, developers, projects and proposals that make up your pipeline. GullySales works on setting up a simple system in a tool your firm already uses or one in common use in India, and on the habits of filling it in.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What CRM means
A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.
Last updated 14 Nov 2026.
For MEP consultants
Where it usually goes wrong, and what we would do.
“The pipeline lives in two partners' heads”
When a principal travels or leaves, nobody knows which proposals are open or who was promised a call. A shared record turns private memory into firm knowledge.
“A contact belongs to several projects”
One architect appears on several projects over the years, each with a different developer. A system that lists only companies loses this, so contacts, projects and proposals need to be linked.
“Fee proposals stall at the client's confirmation”
A proposal held until the client confirms the project is neither won nor lost. Without a status for this, such proposals vanish from view and are chased too early or never.
What we do
What we deliver for MEP consultants.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
A record built around projects
Each project holds the architect, developer, building type, stage, fee proposal and next step, linked to the people involved.
Result: One page shows everything about a project.
Stages that match how you win work
Stages such as concept discussion, fee requested, proposal sent, held by client, appointed and lost.
Result: Each proposal sits at a stage everyone understands.
A proposal register
Date sent, scope, fee basis, decision maker and the next call, for every proposal.
Result: You can list the proposals waiting on a decision.
Source and loss reasons
Where each lead came from and why a proposal was lost, recorded in plain words.
Result: Patterns across losses become visible.
A short training for the team
One session on what to enter and when, with a one-page guide.
Result: Engineers and principals know what is expected of them.
How the result is measured
- Enquiries logged in the CRM
- Data completeness
- Reports generated from CRM data
Recorded as a baseline before work starts, so every later report has an honest comparison.
Fields worth keeping
Fields that tie a person, a project and a proposal together.
- Project and building type
- Filled when the project is first noted. Lets you filter proposals by hospital, hotel or plant and see where wins and losses sit.
- Architect and developer
- Both linked to the project. Shows who recommended you across several buildings and who has not yet met anyone at the firm.
- Stage of design
- Concept, schematic or tender, updated by the principal. Shows which proposals can still be won and which are already decided.
- Fee proposal register
- Date sent, scope and revision, filled by whoever issues the proposal. Prevents two versions circulating to the same client.
- Who decides and who signs
- Two names, set after the first meeting. Tells you whom to follow up with, and why a proposal is held.
Who it is for
This is written for these MEP consultants.
- MEP design consultancies for commercial and residential buildings
- Hospital and healthcare MEP specialists
- Hotel and hospitality MEP consultants
- Industrial and factory MEP design firms
- HVAC design consultants
- Electrical design and power distribution consultants
- Plumbing, drainage and public health design consultants
- Green building and energy efficiency MEP consultants
Before you decide
When this may not be the right fit.
- The partners will not share proposals in one place, so a record would hold only what the junior staff enter.
- You have only a few active proposals, and a spreadsheet already covers them without anyone forgetting.
Before you decide
Agree the work. Know how to judge it.
CRM for MEP consultants: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.
Make the scope clear
Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.
Check the work in use
Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.
Know when to change course
If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.
These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.
Before we start
What to have ready before the work starts.
The records, access and decisions this work needs from MEP consultants. Anything missing is noted in the written scope, with who will supply it.
- The proposal files and spreadsheets in use
- Every spreadsheet, folder or email list where proposals are tracked today. We import from them so the record does not begin empty. If proposals live only in the partners' memories, the first task is a sitting to write them down, and the record opens later than planned.
- A partner who owns the record
- One partner must own the record and review it with the team at their usual meeting. Without an owner it falls behind and stages freeze, and within a short while the old spreadsheet is back in use. The owner need not do the entering, but must decide what a stage means.
- The contact list of architects and clients
- The names, firms and projects of the architects, developers and owners the firm deals with. A phone export or a spreadsheet is acceptable. Without it the record starts with empty contacts, and the first weeks are spent typing instead of seeing which relationships link to which projects. The architect who appears on four live proposals is then invisible as a single relationship, and nobody can tell which partner should ring.
- The firm's own stage names and loss reasons
- A note of how the partners describe the stages of a proposal and why they lose work, in their own words. We use that language. Without it, we invent stages and reasons that the team does not use, and the fields stay empty after the first week.
- A decision on who edits and who views
- Decide which staff can edit proposals and which can only read them, and what happens to a principal's contacts when that principal leaves. Without this, anyone can change a stage, and a departing partner's relationships go out of the door with them.
How it works
How the CRM work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Trace one project from enquiry to fee proposal
We follow a recent project through the firm: who took the first call, who asked for drawings, who drafted the scope, who signed the proposal and who chased the architect afterwards. You supply the emails or notes that show it. The trace shows which steps the record has to hold and where the knowledge sits in one partner's head and nowhere else in the firm.
- 2
Define stages that match how work is won
We write the stages in the firm's own words, such as watch list, first meeting, scope sent, proposal issued, held by client, appointed and lost. You approve the names. A stage that nobody can tell from the one before it is merged with it, so the record shows clearly where proposals stall and who is waiting on whom. The partners then see at a glance that three proposals sit at the same stage for the same reason, which a spreadsheet never showed them.
- 3
Build the record around the project
We set up the record so the project is the main entry and the contacts hang from it, since an architect belongs to several projects and a developer's technical head to more. A contact page lists every project the person appears in. You choose the tool, and we explain plainly what each option can and cannot do for a firm of this size.
- 4
Enter the proposal register from the files
We take the firm's proposals from files and spreadsheets and enter them with the building, client, architect, fee stage and last contact. You check each entry. Where two partners remember a proposal differently, the partner who owns the file decides, and we note the disagreement beside the entry so that nobody loses the history of what was said.
- 5
Add source and loss reasons to every entry
We add two fields: how the enquiry arrived and, if the proposal was lost, why. The loss reason is chosen from a short list and one line of text. The partners fill these in at the time of the decision. Without them the record cannot show where work comes from or which reasons recur.
- 6
Train the team and review the first entries
We sit with the engineers and partners for a short session on entering and updating a project, then review the first entries together and remove fields that nobody filled. Against the earlier spreadsheet, you see what the record now shows that the old one could not, such as proposals held for the same reason. No increase in appointments is promised.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales management. A target, a review routine and someone who owns the number.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3 · you are here
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
Do we need an expensive CRM?
Who should update the CRM?
What happens to the record when a principal leaves?
Should drawings be stored in the CRM?
Can the record hold drawings and calculations?
Who enters the data when the partners are busy?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
More for MEP consultants
Related work to consider.
Closest to this: leads and follow-up
Also for MEP consultants
Or start from the overview: sales and marketing for MEP consultants.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.