HubSpot/Salesforce: When a deal is marked Closed Won, the CRM's work is done. To start the project, someone has to copy client data into the project management tool, re-enter project scope and deliverables, rebuild timeline and milestones, manually transfer estimated hours, set up time tracking, and create invoice schedules in accounting software. The same data, entered three times. The handoff is a gap where context gets lost and margin targets disappear.

.STUDIO: When a deal is marked Won, it becomes an active project in the same system. Client data flows forward automatically. Estimated hours from the sales estimate become the project baseline. Margin targets are visible from day one. The project team has full context because it's the same operational record, just moving from "sales" to "delivery" view. There's no handoff. There's no re-entry.

HubSpot/Salesforce: Opportunity value is a single field: "Deal Amount: £150,000." There's no structure for building that number from resource reality. Studios estimate in separate spreadsheets, then manually enter the final fee. The pricing logic and the opportunity record are disconnected.

.STUDIO: Inside every opportunity, studios build resource estimates: hours by role (Director of Design: 80h, Senior Designer: 290h, CAD Junior: 340h), hours by phase (Concept: 180h, Schematic: 280h, Detailed: 440h), expenses by category, hourly rates per role, and the list goes on to being infinitely customizable. The fee is derived automatically: total hours × rates = fee and margin. The proposal goes out knowing exactly what it costs to deliver and what margin the fee generates. Pricing connects to capacity reality before contracts are signed.

HubSpot/Salesforce: RFPs exist as opportunities with due dates in task lists. There's no structured RFP workflow. Studios manage RFP timelines in separate calendars or project tools — defeating the purpose of centralising BD operations.

.STUDIO: Each opportunity can have: submission deadline with countdown visibility, required documentation checklist (brief, technical approach, team CVs, project references, fee proposal, insurance certs), presentation date and preparation milestones, and RFP stage tracking (Received → Pursuit Approved → In Progress → Internal Review → Submitted → Presented → Decision). The RFP calendar is part of the CRM. Leadership sees all submission deadlines at a glance. Nothing gets missed.

HubSpot/Salesforce: Opportunities are marked Won or Lost. Lost deals disappear from the active pipeline. There's no systematic tracking of pursuit cost or patterns in which project types consistently fail.

.STUDIO: Time (including design competition hours) can be logged against opportunities not just active projects. When a deal is lost, the system calculates pursuit cost: hours logged × cost rate = total investment. Aggregate across all lost deals to reveal which project types waste BD and Design Team capacity. This enables strategic decisions: stop pursuing small hospitality projects where conversion rates are consistently low, reallocate effort to corporate and healthcare where they're higher. Generic CRMs don't track this at all.

HubSpot/Salesforce: Profitability is calculated after delivery, if at all. The CRM tracks revenue (fee), but not cost or margin. Studios discover whether a project was profitable weeks after invoicing.

.STUDIO: Every opportunity shows expected margin calculated from the resource estimate. A restaurant project with 13% margin (below the studio's 30% target) is visible before the contract is signed. Options: increase fee, reduce scope, or decline. What the studio does NOT do: win the deal and discover the margin problem mid-delivery.

Studios running on CRM for interior design studios with margin visibility make strategic pursuit decisions: only chase deals worth winning at target profitability.

HubSpot/Salesforce: These are sales tools. Project management happens elsewhere. Specifications happen elsewhere. Time tracking happens elsewhere. Invoicing happens elsewhere. The studio operates in fragments, with manual connections between each piece.

.STUDIO: Sales, project management, specifications, time tracking, and invoicing operate in one connected system. When a project moves from sales to concept design, it's the same record — just progressing through phases. When a designer logs time against a specification task, that time is visible against the project budget in real time. The system isn't a sales tool bolted onto operations. It's the operational infrastructure the entire studio runs on.

Programa: No profitability reporting. No real-time margin visibility. No time-to-cost tracking. No invoicing integration. Studios using Programa still run financials in QuickBooks, Xero, or spreadsheets. Leadership doesn't have a real-time view of whether projects are profitable until after delivery.

.STUDIO: Every project shows estimated hours vs actual hours logged, estimated cost vs actual cost, target margin vs current margin trajectory, budget remaining by phase, and resource utilisation by team member. Leadership sees financial reality in real time - not weeks after invoicing when profit leakage has already happened.

Programa: Basic pipeline tracking exists, but it's secondary to the tool's core focus. No resource-based estimating. No lost opportunity cost analysis. No sales performance metrics. No pursuit ROI visibility.

.STUDIO: Full sales operations: pipeline management, resource-based estimating, RFP tracking, lost opportunity cost, sales margin by deal, win rates by project type, pursuit ROI, weighted pipeline forecasting. The sales function gets the same operational depth that delivery gets.

Programa: Time tracking exists in various implementations, but it doesn't connect to project budgets, margin targets, or financial forecasting. It's activity tracking, not profitability management.

.STUDIO: Time tracking connects directly to project financials: time logged → cost calculated → margin updated in real time. Projects show hours used vs hours remaining by phase. If a project hits 80% of estimated hours at 60% completion, leadership sees it while there's still time to adjust.

Studios running on project management software for interior designers that connects time to margin report catching profit leakage 2–4 weeks earlier — when it can still be addressed.

Programa: Built for designers. Excellent for specifications, mood boards, and product selections. Not a studio director's operational control and financial visibility platform.

.STUDIO: Built for the entire studio: BD team (pipeline management, estimating, RFP tracking), design team (project management, specifications, product libraries), project managers (timeline, budget, team coordination), leadership (financial visibility, profitability, capacity planning), and finance (time-to-invoicing, margin tracking, revenue forecasting). Everyone works in the same system. Data flows between functions automatically.

Sales pipeline tracking

✅ Excellent

⚠️ Basic

✅ Design-specific

Resource-based estimating

❌ No

❌ No

✅ Native

RFP management

⚠️ Tasks only

⚠️ Basic

✅ Structured workflow

Lost opportunity cost

❌ No

❌ No

✅ Automatic calculation

Sales margin visibility

❌ No

❌ No

✅ Before deal closes

Sales → delivery handoff

❌ Manual re-entry

⚠️ Limited

✅ Automatic flow

Project management

❌ Separate tool needed

✅ Good

✅ Connected to sales

Specification management

❌ Separate tool needed

✅ Excellent

✅ Connected to projects

Time tracking

❌ Separate tool needed

⚠️ Activity tracking

✅ Connected to margin

Financial visibility

❌ Separate tool needed

❌ Limited

✅ Real-time profitability

Invoicing integration

❌ Separate tool needed

❌ Separate tool needed

✅ Connected to actuals