Published
Why Generic CRM Structures Fail Interior Design Workflows
HubSpot and Salesforce were built for SaaS sales teams running high-volume, short-cycle deals. Design studios run low-volume, long-cycle, relationship-driven work. The mismatch creates friction, not efficiency.
Author:
Alice Hart
Estimated reading time: 8 minutes
Your studio is growing. You need better pipeline visibility, more structured BD operations, and a system that doesn't rely on one person's inbox. Someone suggests HubSpot. It's the obvious choice: industry-standard CRM, used by thousands of companies, strong reputation.
You sign up. The onboarding starts. "What are your pipeline stages?" the system asks. You look at the defaults: Lead → Marketing Qualified Lead → Sales Qualified Lead → Opportunity → Proposal Sent → Closed Won.
None of these match how your studio actually works. You customise: Leads → RFP Received → RFP Submitted → Expected → Won. Better. But it still feels off.
Then you start using it. The system wants you to score leads. It prompts you to create email sequences. It asks about deal velocity and conversion funnels. It tracks page views and form submissions. None of this applies. Your studio doesn't get 200 leads per month. You get 15–30 high-value inquiries per year, each requiring deep relationship cultivation over 6–18 months. You get smaller ones too, but nowhere close to 200 per month.
Three months in, the team has stopped using HubSpot. Too much friction, too little value. You're back to the spreadsheet.
"We tried HubSpot but it doesn't fit how we work."
This is the story studios tell when they realise generic CRMs aren't built for them. Not because HubSpot is bad software - it's excellent at what it's designed to do. But what it's designed to do is run high-volume SaaS sales, not low-volume, relationship-driven design project sales.
The Problem: Generic CRMs Optimise for Volume, Not Relationships
HubSpot and Salesforce were built for a specific sales motion: high-volume, short-cycle, largely standardised B2B sales. A SaaS company gets 500 demo requests per month. Most are unqualified. The CRM helps filter signal from noise: lead scoring, automated nurture sequences, behaviour tracking, conversion funnel optimisation. The goal is moving volume through a repeatable process quickly.
Interior design studios operate in a fundamentally different sales environment:
Volume vs Relationship |
|---|
A SaaS company tracks hundreds of active opportunities. An interior design studio tracks 10–20. Each one is a complex, high-value, multi-month relationship and not a lead moving through a funnel. |
Short-cycle vs Long-cycle |
|---|
A typical SaaS sales cycle is 30–90 days. A design studio's sales cycle is 6–18 months. From first inquiry to signed contract, there might be site visits, stakeholder meetings, proposal iterations, budget revisions, RFP responses, and procurement reviews. The relationship develops slowly, with context accumulating over time. |
Standardised vs Bespoke |
|---|
SaaS products are standardised. Every prospect gets the same demo, the same trial, the same pricing tiers. Design projects are bespoke. Every opportunity requires custom estimating, unique resourcing, tailored proposals. There's no repeatable playbook - each deal is different. |
Transactional vs Relational |
|---|
SaaS sales end at the close. The product is delivered via software. Design sales are just beginning at the close - the project starts, requiring coordination between sales, delivery, specifications, and financials. |
Generic CRMs optimise for the first model. Studios operate in the second. The mismatch creates friction at every level.
What Breaks When Design Studios Use Generic CRMs
1. Pipeline Stages Don't Match Design Project Realities |
|---|
HubSpot's default stages assume a linear qualification funnel. But design studios don't move opportunities through Marketing Qualified → Sales Qualified → Opportunity. They move through:
You can customise HubSpot to match this, but you're fighting the tool's assumptions. The system's automation, reporting, and workflow logic are all built around qualification funnels, not project pursuit stages. Every customisation is a workaround. |
2. There's No Resource-Based Estimating |
|---|
Before a design studio proposal goes out, someone needs to answer: can we deliver this at the quoted fee, with the team we have available, at the margin we need? This requires building an estimate: hours by role (Director of Design, Senior Designer, CAD Junior, Visualizer, Technical Manager), by project phase (Concept Design, Schematic Design, Detailed Design, Tender, Construction Supervision), at defined rates. The fee is derived from the resource plan. Generic CRMs have no concept of this. They track opportunity value as a single number. There's no structure for building estimates from resource data, no connection to team capacity or utilisation, no way to see if the quoted fee is actually deliverable. Studios end up building estimates in separate spreadsheets, then manually entering the final fee into the CRM. The estimating logic and the opportunity record are disconnected — which is exactly the fragmentation problem CRMs are supposed to solve. |
3. The CRM Stops at the Close |
|---|
In HubSpot or Salesforce, a deal moves through stages and ends at Closed Won. The CRM's job is done. What happens next (project management, specifications, time tracking, invoicing) is someone else's problem. But for design studios, winning the deal is just the beginning. The project starts. The client record needs to flow into project management. The estimated hours need to become the baseline for time tracking. The fee needs to connect to invoicing. The scope needs to translate into deliverables and milestones. If the CRM stops at the close, this entire handoff is manual. Someone copies data from HubSpot into the project management tool, the specification system, the time tracker, and the invoicing platform. The same client information typed four times. Four opportunities for error and version drift. Studios running on CRM for interior design studios that connect sales to delivery don't re-enter data. The won opportunity becomes an active project in the same system — client details, estimated hours, team assignments, and financial parameters flow forward automatically. |
4. Relationship Context Gets Fragmented |
|---|
Design projects are relationship-intensive. A single opportunity might involve 8 meetings over 12 months, 15 email threads with different stakeholders, 3 site visits, 2 proposal iterations, 6 phone conversations with the decision-maker, and 4 presentations to internal teams. Generic CRMs can log this activity — but the structure is transactional, not narrative. You get a list of touchpoints, not the story of a relationship. When someone needs to pick up a client conversation mid-stream, they scroll through 30 logged activities trying to reconstruct context that should be immediately accessible. Project management software for interior designers treats relationship context as operational memory, not administrative logging. Every conversation, preference, constraint, and commitment is part of the permanent record — structured for continuity, not just compliance. |
5. RFP Management Doesn't Exist |
|---|
Design studios respond to formal RFPs — Requests for Proposals that come with submission deadlines, required documentation, presentation dates, and multi-stage evaluation processes. Managing RFPs requires tracking submission deadlines per opportunity, maintaining RFP documentation and requirements, coordinating proposal development across team members, scheduling presentations and follow-up milestones, and monitoring where each RFP is in the client's evaluation process. Generic CRMs have tasks and reminders, but no structured RFP workflow. Studios end up managing RFP timelines in separate calendars or project management tools — which defeats the purpose of centralising BD operations in a CRM. |
6. Reporting Doesn't Match What Studios Need |
|---|
HubSpot's reports optimise for funnel metrics: conversion rates by stage, lead source performance, deal velocity, email engagement, page views per lead. These metrics are useful for SaaS sales teams running volume through repeatable processes. Design studios need different visibility:
These reports are either impossible or require heavy customisation in generic CRMs. Studios end up exporting data into spreadsheets to get the answers leadership actually needs. |
The Customisation Trap
The obvious response is: "Just customise HubSpot to fit design workflows."
In theory, this works. HubSpot and Salesforce are highly customisable. You can create custom fields, custom pipeline stages, custom objects, custom reports. With enough consulting hours and technical expertise, you can bend these systems to approximate design studio workflows.
The problem is threefold:
Customisation is expensive. Heavy HubSpot customisation requires consultants charging £150–£200/hour. Getting the system configured to approximate design workflows costs £10,000–£20,000. That's before training, before data migration, before ongoing maintenance.
Customisation is fragile. Every customisation is a workaround fighting the tool's core logic. When HubSpot updates its platform — which happens regularly — custom configurations can break. Someone has to maintain the customisation layer, which requires ongoing technical expertise.
Customisation still doesn't connect sales to delivery. Even a heavily customised HubSpot still stops at the close. The handoff to project management, specifications, time tracking, and invoicing is still manual. Studios end up with an expensive, customised CRM — plus all the separate tools they already had. The fragmentation problem persists.
"We spent months customising HubSpot and it still doesn't connect to how we actually work."
What Purpose-Built Actually Means
Purpose-built doesn't mean "has more features for designers." It means the tool's core logic matches how design projects actually move through sales and delivery.
Pipeline stages reflect design project pursuit. Leads → RFP Received → RFP Submitted → Expected → Won/Lost is the default structure, not a customisation. Each stage has appropriate probability weighting and workflow logic built in.
Resource-based estimating is native. Opportunities include estimating tools: hours by role, by phase, at defined rates. The fee is derived from resource planning, not entered as a standalone number. Margin visibility exists before the proposal goes out.
RFP management is structured. Each opportunity can have submission deadlines, required documentation, presentation schedules, and evaluation milestones tracked within the opportunity record. The RFP calendar is part of the CRM, not a separate tool.
Sales connects to delivery. Won deals don't stop at the close. They become active projects in the same system. Client data, estimated hours, resource assignments, and financial parameters flow forward automatically. No re-entry. No handoff gap.
Reporting matches studio operations. Pipeline value by project type, lost opportunity cost, sales margin by deal, conversion rates by stage — these are default reports, not custom builds. Leadership gets the visibility they need without exporting to spreadsheets.
Studios using interior design management software report faster setup, better team adoption, and higher utilisation because the tool is designed around their workflow from the ground up — not customised to approximate it.
The Real Cost of Generic CRMs
The cost of using a generic CRM isn't just the subscription fee. It's:
Customisation expense — £10,000–£20,000 to configure the system for design workflows
Ongoing maintenance — technical expertise required to maintain custom configurations
Adoption friction — teams resist tools that don't fit their workflow, leading to low utilisation
Fragmented data — sales in one system, delivery in another, specs in a third, time tracking in a fourth
Manual handoffs — every won deal requires re-entry across multiple systems
Lost context — relationship history and project knowledge scattered across disconnected tools
Leadership blind spots — reporting that doesn't answer the questions studios actually need answered
The compounded effect: studios pay for enterprise CRM subscriptions, invest heavily in customisation, and still end up managing core operations in spreadsheets and parallel tools because the CRM doesn't actually run the business.
The Question That Reveals the Fit
If your CRM stopped working tomorrow, would your project delivery operations stop with it?
For studios using generic CRMs, the answer is no. Project work would continue uninterrupted because delivery happens in separate tools. The CRM is a sales tracking layer on top of operations, not the operational system itself.
For studios using purpose-built systems, the answer is yes. Sales, project management, specifications, time tracking, and invoicing all run in the same system. If it stopped, everything stops — because it's the operating system, not a sales tool.
That difference is what "purpose-built" means.
Stop Fighting Your Tools
Generic CRMs aren't bad software. They're excellent at what they're designed to do: run high-volume, short-cycle, standardised B2B sales. But design studios don't operate in that sales model. They run low-volume, long-cycle, relationship-driven, project-based work. The workflows are fundamentally different.
Studios that try to force-fit generic CRMs end up spending months on customisation, maintaining fragile workarounds, and still operating with fragmented data across disconnected tools. The CRM becomes another silo to manage, not the solution to fragmentation.
Purpose-built tools win when the workflow is specialised. And interior design studio operations are deeply specialised — not because designers are unique, but because the work itself (project-based, relationship-intensive, bridging sales and delivery) has structural requirements that generic tools weren't designed to meet.
If your studio has spent months trying to make a generic CRM work and it still doesn't fit, the problem isn't you. It's the tool. And tools can be changed.
See what purpose-built CRM looks like. Book a free 30-minute Sales Process Audit and we'll map exactly why generic tools create friction for your workflow — with no obligation to proceed.
