The owner is the integration

Saturday, 9:15 in the morning. Anita has not yet finished her first cup of chai and her phone already holds four questions.

The laminate vendor wants to know if he can collect his payment for the Gachibowli project. Her designer asks whether the client approved the lighter oak or the walnut for the bedroom wall. Her salesperson wants to send the Kondapur villa quote at a slightly lower rate, because the client is comparing. And the site engineer at Jubilee Hills has sent a voice note: the tiles for the guest toilet are short by two boxes.

Each question has a simple answer. The trouble is that only Anita has it.

She remembers that the vendor delivered short last time, so the payment should wait until someone counts. She remembers the Gachibowli client said “lighter oak” on a call three weeks ago, which is written down nowhere. She knows the margin on the villa quote, which nobody else in the firm can see. And she knows the tile order was placed from an older drawing, before the client changed the toilet layout.

Anita runs eleven projects with a team of eighteen. Her firm has a quote template, a drawing folder on Google Drive, a WhatsApp group for each site and an accountant who comes in twice a week. It has systems. What it does not have is anything that connects them, except Anita.

The cable between the machines

In software, the piece that lets two systems talk to each other is called an integration. The sales system tells the accounts system that a deal closed. The design system tells the site system that a drawing changed.

In most interior firms, the owner is the integration. Not by choice. It just happened, one project at a time.

Think about the links an interior project depends on. The approved quote should become the budget. The budget should become the buying list. A drawing revision should reach site before the carpenter cuts. A quality check on site should be what makes a vendor payment due. A finished stage should trigger the client's next instalment.

Each of these is a handover from one part of the firm to another. In a firm where each part lives in its own tool, every one of those handovers passes through a person. Usually the same person.

Your firm is not limited by talent or demand. It is limited by how many connections one person can hold in their head.

At three projects, it feels like control

With three projects, being the integration works beautifully. The owner visits every site twice a week. She is in every client meeting. She signs every payment. She knows every drawing because she drew half of them.

This stage feels like control, and in a way it is. Nothing slips because one person sees everything. Clients love it, because they are dealing with the founder directly. It is also where most firms build their reputation.

The danger is that this stage teaches the wrong lesson: that the way to keep quality high is for the owner to touch everything.

At eight projects, the links start dropping

Somewhere around eight projects, the owner can no longer be in every room. She hires a project manager, then a second designer. Things seem fine for a while.

Then the small breaks begin. A revision is made but nobody tells site, so a wardrobe gets built with hinged shutters after the client asked for sliding. A vendor is paid in full before anyone checked that the work was finished. A quote goes out with last year's rate for hardware. A client is promised a date by sales that design has never heard of.

None of these is a disaster on its own. Together, they are the sound of links dropping. The owner's phone gets louder. Her day starts at 7 AM with site questions and ends at 11 PM with client calls. The new project manager is capable, but still has to ask her about anything that crosses from one area to another, which is most things.

At fifteen projects, the owner is the bottleneck

By fifteen projects, the firm is moving at the speed of the owner's replies. Payments wait for her. Approvals wait for her. Purchase decisions wait for her. Her team is not lazy; they simply cannot act without information that lives only in her head and her phone.

Five hours a day of answering, connecting and relaying. That leaves very little for the work only an owner can do: winning the next project, hiring well, setting design standards, and thinking about where the firm is going.

And then the owner goes to a family wedding for four days. Three sites stall. A vendor dispute escalates. A client who could not reach her rings the designer, who promises something that cannot be done. The owner comes back to find that the firm cannot run for four days without her. That is the real ceiling.

Building one record

The fix is not to hire someone to be a second integration. That just moves the bottleneck. The fix is to put the links into the work itself, so that information travels between sales, design, site and money without passing through a person's memory.

Whether you use software or not, the principles are the same.

1. One project record from the moment of yes. When a client signs, the approved quote becomes the single source for everything after: the rooms, the budget, the buying list and the site plan. Nobody re-types it into another sheet.
2. Write the links down as rules. A drawing revision always carries a note on what changed, and that note always goes to site. A vendor payment becomes due only after the work is checked. A quote below your margin needs approval before it goes. Rules replace memory.
3. Decide who sees what. Site engineers do not need to see money. Salespeople do not need to see cost. Clients never see either. Clear lines let you hand over work without handing over everything.
4. Give the owner a screen, not a phone. Every project on one view, with which ones are on track, at risk or critical, and why. The owner should look at exceptions, not answer every question.
5. Put decisions where the evidence is. When a payment is approved, the approver should see the proof of work right there. When a client approves a drawing, it should be recorded against that drawing, not in a chat.

Start with the link that hurts most. For many firms, that is drawings reaching site, or payments going out before work is checked. Fix one, let the team get used to it, then fix the next.

What the owner gets back

When the links live in the work, the Saturday morning changes. The vendor's payment is either due because the work passed a check, or it is not. The oak decision is recorded against the drawing. The villa quote is flagged for approval because it is under margin, and Anita sees exactly why. The tile order came from the current drawing, because the revision note went to site.

Anita still makes the decisions only an owner should make. She just stops being the cable.

How Pakka handles it

Pakka is built as four desks that hand work to each other. When a quote is won on the Sales Desk, one click creates the project with its rooms and BOQ. The approved lines become the project budget, and the quote's payment plan becomes the client's instalment schedule on the Money Desk.

On the Design Desk, every revision carries a note that goes to site, and pushing the approved drawings to production creates the site phases on the Ops Desk. A QC pass on site is what makes a vendor payment eligible, and a named person approves every release. The Command Center shows every project and every risk across the desks you use, so the owner sees the firm at a glance.