Theindustrydoesn'thaveatoolingproblem.
Ithasafoundationaldataproblem.

Between the two of us, we've worked on and managed over 60 projects in architecture and interior design. We've sat in coordination meetings with owners, GCs, consultants, city officials, architects, designers, and vendors. We've heard the same frustration from every one of them.

Nobody is looking at the same drawing. The contractor is asking for a finish schedule that was sent three weeks ago. The engineer is referencing a set that's two revisions old. The vendor wants the spec confirmed for the third time. The consultant needs information that already exists in someone else's email thread. Every project, every week, the same loop.

You learn to live with it. You build spreadsheets, you label PDFs carefully, you copy the same eight people on every email. And it still falls apart.

We went through one of the most respected project management programs in the AEC industry hoping to find a better way. What we found was that the recommended solution was to stitch together the same disconnected systems everyone already used — just more disciplined about it. More naming conventions, tighter folder structures, stricter meeting cadences.

That was the moment it clicked.

The industry doesn't have a tooling problem.
It has a foundational data problem.

Every project follows roughly the same workflow. The same handoffs, the same approvals, the same questions. But the information needed to run those workflows is scattered across PDFs, emails, texts, and software that doesn't talk to each other. So every handoff is a translation. Every question is asked twice. And nothing — no general-purpose AI, no project management overlay — can fix that until the underlying data stops being scattered in the first place.

We're starting with solo interior designers and small firms — the people who feel the pain most acutely because there's no one else to absorb it. One person specifying products, tracking procurement across dozens of vendors, fielding client questions, sending invoices, chasing approvals. Currently doing it across a spreadsheet, a PM tool, an inbox, and a notes app.

Moodiri replaces that stack. Spaces, products, vendors, invoicing, approvals, and a branded client portal in one connected system. The designer stops re-entering the same information in four places. The client stops emailing for status updates because they can see everything themselves.

This is a real product solving a real problem today. It's also the foundation for everything that comes after.

Every specification, approval, vendor interaction, and payment that flows through Moodiri builds something the built environment has never had: structured project context that exists from day one and stays connected through every handoff.

Long term, that context unlocks a different way of working. A designer or architect enters an address and immediately sees zoning, permitting requirements, feasibility risks, required consultants, budgets, and procurement workflows. Every stakeholder inherits the information they need without endless calls or document searches. Decisions made in design carry forward into procurement, into permitting, into construction — without anyone having to translate them by hand.

The result isn't better project management software. It's the operational infrastructure that future tools, workflows, and AI systems for the built environment can finally build on top of.

Moodiri is built by Ali Fahmy and Alivia Mountford. We met working at the same firm and spent two years coordinating projects side by side — Ali as a project manager on the architecture side, Alivia running project management, interior design, furniture, and purchasing. We sat in the same coordination meetings, fielded the same repeat questions, and watched the same information get lost in the same handoffs, project after project.

Eventually we stopped accepting it as the cost of doing business. We're building Moodiri because the people doing this work deserve better than what they have.