How Gaegane Group Mapped Its Notion System

Client

Gaegane Group

Industry

Architecture, Construction, Design

Team size

25 People

Delivery time

14 Days

Headline results

One structure, three businesses

Business → Project → Task validated as the right shape for a turnkey design-and-build firm.

A portal per client

One login showing sketches, invoices, and messages, instead of scattered email threads.

Proof, not memory

Version history, recorded meetings, and signed documents as a durable record of approvals.

The challenge

Gaegane Group is a turnkey firm (clients can choose design-and-build or build-only) spanning architecture, interior design, and construction under one roof. Construction already ran on dedicated project software. The design side, and the client experience wrapped around both, had no real system behind it.

The day-to-day was running on tools that weren’t built for the job:

  • Microsoft email and documents for project updates and file sharing
  • Dedicated construction software covering only the build side of the business
  • No connective tissue between design projects, construction projects, and the clients they belonged to
  • Informal, verbal sign-offs with a meeting note written afterward as “proof”
  • ChatGPT prototypes for proposals, disconnected from the firm’s own pricing and documents

The symptom that mattered most was relational:

A recent client "felt like he doesn't... know how the project was going" and couldn't easily share progress with his spouse, because everything lived in scattered emails rather than something visual.

Underneath that sat a quieter risk. Approvals happened in conversation: plans presented, verbal yes, note written from memory.

The solution: a multi-business hub with client-facing portals

The call was a live walkthrough of an existing multi-business Notion template, adapted on the spot to Gaegane Group’s turnkey structure rather than a single-service business.

The operating core

  • Business: one record per angle of the company (design, interiors, construction)
  • Projects: related to the business they belong to, so concurrent work stays sorted
  • Tasks: a single database filterable by business, project, date, priority, or status
  • No duplicated tracking: one company, one task list, many lenses

The client layer

  • Duplicable portals: one per client, so no client can ever see another’s information
  • Combined views: architecture, interiors, and construction in a single portal as phases progress
  • Message board: replacing email threads; clients get a notification and a direct link
  • Guest access: clients see their project without touching the workspace

Task database filtered and grouped by Business

Proof & protection

  • Version history: who changed what and when, even if a client later edits the record
  • Documents & Payments: contracts attached with sign-off tracked against the project
  • AI meeting notes: verbal approvals captured as a timestamped transcript, not a memory
  • Exports: PDF, CSV, HTML, or Markdown depending on whether it’s a legal record or a data handoff

The experience layer

  • Board, gallery, and chart views instead of tables, so nothing reads like a shared document
  • Property-level control over exactly how much detail a client sees
  • Embedded tools: Google Drive, Figma, Miro, Sketch, Loom, viewable without app access
  • AI grounded in the firm’s own files: pricing pages, SOPs, and compliance rules, read at the moment of asking

client portal page showing embedded views for architecture

How it changes daily reality

  • The update request disappears. The client stops asking how the project is going, because they can log in and see it and so can their spouse.
  • One project, not three. Design, interiors, and construction surface in a single portal, even though they’re separate businesses behind the scenes.
  • Approvals leave a trace. A design accepted on a given date is recorded by the system, not reconstructed from a follow-up note.
  • Proposals start from the firm’s own numbers. Notion AI reads the actual pricing page rather than relying on what it was told in a previous chat.

client proposal mockup

How we worked together

The discovery call started with a story about a client who didn’t know how his own project was going. Before touching a single database, we mapped the shape of the business: three service lines, one turnkey promise, construction already handled elsewhere, and a design side held together by email. The gap wasn’t in the tooling. It was in what the client on the other end could actually see.

Then came the part Odirile hadn’t planned to raise, and raised anyway. Approvals happened in conversation. A plan presented, a verbal yes, a note typed afterward. Half-joking about being sued three years later, he described a real exposure. That moment quietly changed what the rest of the call was about.

  • Discovery. Mapping the businesses, the tools already in place, the client-experience gap, and the legal exposure around approvals.
  • Live walkthrough. Demonstrating the multi-business core, duplicable portals, version history, embeds, and AI grounded in real documents.
  • Handover. In 14 days, Odirile got the working structure in his own workspace, the multi-business core and a duplicable client portal.
  • Straight into a live project. The first portal was pointed at a real client instead of a test page, so the system started earning its keep on actual work from day one.

The client’s verdict on the experience:

I came in thinking I'd get a sales pitch, you know: here's the package, here's the price. It wasn't that at all. David opened the actual thing and started changing it in front of me while I was talking. I'd say, but I've got three businesses, and instead of writing it down for later he just built it right there so I could see it. And he didn't push me. I told him I wanted to learn it properly first and he agreed with me, which honestly you don't expect from someone who's selling you something. That's when I knew I was dealing with the right person. I understood my own business better after that call than I did before it.

The results

🚪 A private portal per client, open 24/7

Each client gets their own duplicated portal reached by guest link: sketches, drawings, invoices, and project status in one login, with no access to anyone else’s work and no access to the firm’s internal workspace.

Clients stopped phoning me for updates. They just log in their portals.

🧩 Three service lines shown as one project

Design, interiors, and construction run as separate businesses in the operating core, but surface in the client’s portal as combined views so the client sees the single project they bought, not the org chart behind it.

Three different businesses on my side, one project on his side. That's the part I couldn't picture until I saw it running.

💬 A message board instead of an email thread

Project conversation lives on the portal’s message board. The client gets a notification with a direct link, and the discussion stays attached to the project instead of scattering across inboxes.

No more scrolling back through emails looking for what we agreed. It's all sitting on the project where it belongs.

🛡️ Approvals that leave a timestamp

Version history records who changed what and when, contracts sit in Documents & Payments with sign-off tracked against the project, and AI meeting notes capture verbal approvals as a timestamped transcript rather than a note written from memory.

I asked about proof once, half-joking about being sued three years from now. I stopped joking when a client changed his mind about a finish and I could show him the date he approved the original.

🧠 Proposals drawn from the firm’s own numbers

Notion AI reads the firm’s real pricing pages, SOPs, and compliance rules at the moment of asking, so a proposal starts from the business’s actual figures instead of whatever was explained in a previous chat.

Proposals come out of my own pricing now, not out of my head at eleven at night. I ask, it reads the actual page, and what comes back is our numbers.

Key takeaways

Turnkey firms carry a structural problem that single-service businesses don’t: the client buys one outcome, but the company runs several businesses to deliver it. Construction software handles the build. Design software handles the drawings. Nobody sells the layer that makes it feel like one project to the person paying for it. That layer is where the relationship lives.

  1. A turnkey business needs a turnkey structure. Separate businesses sharing one Task database, filterable by business or project, avoids duplicated tracking systems for what is really one company.
  2. Client experience is usually the real ask behind a tools request. The core frustration wasn’t a missing feature; it was a client in the dark. A visual portal solves a relationship problem, not just an organizational one.
  3. Encourage a learning period before scoping a build. Recommending a few weeks of exploration protects both the client and the eventual system from being shaped by guesswork.
  4. Design for evidence, not just workflow. In a regulated, dispute-prone industry, version history, recorded meetings, and exportable records directly answer a legal concern the client raised without being prompted.
  5. Ground the AI, don’t chat with it. Pointing Notion AI at the firm’s own pricing pages and compliance documents beats re-explaining the business in every conversation.

unning architecture, interiors, and construction as one turnkey business?

If your clients can’t see their own project without emailing you first, 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.