How Mookerjee Design Blueprinted Its Notion System

Client

Mookerjee Design

Industry

Interior Design

Team size

1 People

Delivery time

5 Days

Headline results

A CRM, not a project tracker

The obvious build for a design studio was the wrong build for this business.

Calls become intelligence

Every discovery call transcribed, scored, and mined for patterns instead of half-remembered.

Built for one founder's rhythm

Pillar-coded time-blocking designed around scattered ideation, not against it.

The challenge

Mookerjee Design started as a traditional hospitality creative direction and interior design studio, built on Claire Mookerjee’s 20+ years in design (Gehl Architects, Head of Design at Future Cities Catapult) and proven on her own demonstrator project. Borradill, two cabins above Loch Sunart, went from 30% to 72% occupancy with a 120% increase in weekly rates after her “Design for Return” methodology was applied.

The methodology worked. The operations behind selling it hadn’t caught up.

The business was reshaping mid-flight, and the day-to-day showed it:

  • A pivot in progress: splitting into three pillars: a packaged Audit, a fuller Method consulting offer, and the Atlantic Guild newsletter as both content brand and sales funnel
  • No real CRM: an estimated 95% of Claire’s time going into outreach and lead conversations, with nothing structured tracking them
  • Discovery calls going untracked: no systematic capture of recurring objections, questions, or qualification signals
  • Lead sources scattered everywhere: ~2,000 legacy subscribers in a Squarespace CSV, LinkedIn cold outreach, Instagram followers, events and speaking, plus a hypothetical pipeline of underperforming holiday-let owners still to identify

 

The pivot itself was the thing operations had to catch up to:

The business at the moment is going through this change where it's not about a workflow. It's about generating leads and conversations.

The solution: a CRM-first system for a business in transition

Deliberately not a design-studio project tracker. The system was scoped around the loop the business actually runs on: Lead Source → Capture → Qualify → Discovery Call → Proposal → Closed Project → Content → More Leads.

The lead engine

  • Contacts CRM: every lead in one database with Lead Source, Relationship Stage, and Priority
  • Stage flow: Cold → Warm → Call Booked → Proposal → Client
  • Every channel absorbed: website, LinkedIn, Instagram, newsletter, events, referrals, cold outreach
  • Properties database: the underperforming holiday-lets worth approaching

The intelligence layer

  • Discovery calls transcribed by Notion AI, logged with Key Themes and an Opportunity Score
  • Patterns across calls: common objections and qualification signals, queryable instead of remembered
  • Proposal drafting from actual call data, in Claire’s voice
  • Lightweight Projects, on purpose: minimal by design until real engagements demand more

Custom CRM database view

Content as a funnel

  • Content & Newsletter Pipeline for Atlantic Guild and LinkedIn
  • Linked to source material: calls, properties, and projects become case studies and newsletter issues
  • A closed loop: content generates leads, leads generate calls, calls generate content
  • Events & Speaking tracked as its own lead channel

Structure for a scattered mind

  • Gantt-style weekly planning, color-coded by pillar: Audit, Method, Atlantic Guild, General
  • Ideation windows separated from focused execution blocks
  • Designed around the founder’s rhythm, not imposed on it
  • Finances kept high-level to match the stage of the business

Integrations mapped to her actual stack

  • cal.com for scheduling with pre-call qualifying questions, feeding new CRM entries automatically
  • Beehiiv newsletter webhook to sync new subscribers and publishing status into Notion
  • Squarespace CSV import bringing ~2,000 legacy subscribers in as a segmented, taggable list
  • Claude AI, connected bidirectionally with Notion, to analyze call transcripts, draft proposals in her voice, and support legally scoped lead research
  • LinkedIn and Instagram flagged honestly as partially manual and AI-assisted rather than fully automatable, given each platform’s data restrictions

integration map schema

How it changes daily reality

  • Outreach stops being memory work. Every lead has a stage, a source, and a next step instead of living across three inboxes and a CSV.
  • A call produces three things. A follow-up, a proposal draft, and a content idea, all from the same transcript.
  • The newsletter feeds the pipeline. Atlantic Guild stops being a separate creative project and becomes the top of the funnel.
  • Tuesday has a purpose. Pillar-coded blocks separate the hours for having ideas from the hours for shipping them.

How we worked together

The most valuable outcome of the call was a correction. An earlier website-only analysis had scoped a traditional design-studio workflow; the conversation revealed the business needed a CRM and lead engine first, with design delivery deliberately deferred. The blueprint changed shape before a single database was built.

  • Initial analysis. A website-based read of the business which assumed the wrong workflow.
  • Discovery call. Surfacing the three-pillar pivot, the 95% outreach reality, and the founder’s own working style.
  • Blueprinting. Mapping eight databases, each to a specific gap named on the call, and explicitly leaving the project tracker thin.
  • Phasing. Sequencing the build so the CRM lands first and the speculative work lands last.

The client’s verdict on the experience:

I'd spent weeks trying to work out what my new business actually needed. One conversation, and David mapped it back to me more clearly than I could describe it myself.

The results

🗂️ A pipeline that holds itself

The first thing a CRM replaces isn’t a tool. It’s the mental ledger of who has been contacted, who is waiting, and who was quietly dropped.

I believe each team member saves between 2 to 3 hours when we use the Notion platform to streamline all our company info. No more jumping from several different platforms and notebooks.

With Lead Source, Relationship Stage, and Priority on every contact, the question stops being “where did this person come from?” and becomes “what’s the next move?”

🎙️ Calls that stop evaporating

When 95% of the work is conversations, the conversations are the asset. Transcription plus Key Themes and an Opportunity Score turn each call into something reusable rather than something remembered.

I didn't realize how much I was losing by not remembering my own calls. Now a discovery call turns into a follow-up, a proposal draft, and a newsletter idea without me having to hold all of that myself.

That’s the compounding piece: one hour on a call producing three outputs instead of one, and a body of evidence about which objections keep coming back.

📰 A funnel instead of a side project

Claire´s newsletter, Atlantic Guild, was already good content. What it wasn’t was connected to anything. Linking issues back to the calls, properties, and projects that inspired them closes the loop between marketing and delivery.

I went from feeling like I was drowning in outreach to feeling like outreach was finally working for me.

The shift is from chasing leads one at a time to running a channel that keeps producing them.

⏱️ A week with edges

The time-blocking layer exists for the problem Claire named herself fast ideation, scattered follow-through. Pillar-coded blocks give ideas a window and execution a boundary.

The three pillars used to live in three different tabs in my head. Now they live in one calendar, in three colors, and I actually know what Tuesday is for.

Taken together, that’s the test the whole system has to pass:

This is the first system I've used that doesn't ask me to be more organized. It just organizes me.

Key takeaways

Solo consultants almost always get sold the wrong system. The recognisable build for a designer is a project tracker, for a coach it’s a client roster, for a studio it’s a delivery pipeline, and all of them describe a business that already has clients. When 95% of the work is conversations, the system has to be a CRM first and a delivery tool eventually. Building the delivery layer early feels productive and quietly solves nothing.

  1. Build for the business the client is becoming, not the one they started with. Mookerjee Design looked like a design studio on paper; the system was scoped around the CRM-and-content startup Claire was actively turning it into.
  2. Treat AI as a working team member in the architecture, not a bolt-on feature. Claude and Notion AI were designed into the core loop, transcribing calls, spotting patterns, drafting proposals, because that’s how Claire already planned to work.
  3. Design the system around the founder’s own working style. Pillar-based time-blocking was scoped specifically to address a self-described scattered ideation pattern, not just business processes.
  4. Leave the obvious database deliberately thin. Building out a detailed project tracker before real engagements exist is effort spent on a workflow the client explicitly asked to avoid.
  5. Be honest about what can’t be automated. Flagging LinkedIn and Instagram intelligence as partially manual protected the plan from a promise the platforms won’t allow.

Spending most of your week on outreach with no system behind it?

If your leads live across a spreadsheet, your inbox, and your memory, let’s talk.

More Case Studies

Let's See If We're a Fit

No pitch deck. No obligation. 30 minutes to understand your business and tell you honestly what I think, including if I’m not the right fit.

Built for the businesses that build everything else.

Join Our Newsletter

No product pitches. No padding. One weekly read for serious operators.

© 2026 NotioStore. All Rights Reserved.