DesignFlow OS — Systemise the admin. Never the craft.
DesignFlow OS

You trained to design. To deliver. To exercise judgement.Not to spend your week on the admin anyone could do.

Somewhere along the way, the work became everything else. The chasing. The admin. The information scattered across folders, inboxes, and a dozen tools that never quite talk to each other — the hours that should go to your craft, going somewhere else entirely.

DesignFlow OS is built on a simple conviction: the work that needs your judgement should have all of it, and everything else should look after itself. Not by replacing you — by giving your practice a structure to hold its information, a system that runs when you step back, and intelligence woven through both, so the admin that never needed you simply stops landing on your desk.

Systemise the admin. Never the craft. The judgement stays yours. The design stays yours. What leaves is the work that anyone — or any well-built system — could have done, so the part that only you can do gets all of you.

One system, from how you name a folder
to how you close out a job.

Structure your information so it can be found and read. The intelligence works across your design stages — and connects to those folders and your inbox, handling approvals, procurement and the admin, feeding it back into your studio's system. The products connect because the work connects.

And the system is a loop, not a line. Issued drawings flow back automatically. On site, what you notice is captured and carried home. And when you advise a client on delivery, the same intelligence reads the project and tells you what matters. One connected system — because the work was always connected.

And if you’re the one holding it all together —

If your practice can’t run without you, you don’t have a practice. You have a job.

The most skilled person in the studio shouldn’t be the one the whole thing depends on. When everything lives in your head and your inbox, stepping away isn’t rest — it’s risk. A practice should hold together whether or not you’re in the room.

Each one stands alone.
Together they hold the whole practice.

Pearl Ume — architect, project manager, and founder of DesignFlow OS
Pearl Ume · Architect & Founder

I'm building this as someone who does the work — not just someone who builds software for it.

I trained as an architect, and I still am one. Over time the work expanded, and I moved into project management — but the two have never separated. Architecture taught me to hold complexity, to see how one decision ripples across brief, structure, programme and cost. Project management taught me to turn that complexity into decisions and movement. I sit in both worlds, and I always have.

That's also how I came to see the same problem everywhere I looked. Whether a studio is designing a building or a project manager is delivering one, the most skilled people spend a startling amount of their time on work that doesn't need their skill — assembling, chasing, copying, reconciling, keeping scattered information in their heads because nothing else was holding it.

DesignFlow OS is what I've built in response. One connected system for how design and construction practices actually work — from how you structure a folder to how you advise a client on site — with intelligence running through all of it, doing the work that never needed a professional, so the professional is free for the work that does.

I'm building it as someone who does this work, not just someone who builds software for it. That's the whole point.

P
Pearl Ume
Architect & project manager — with experience across design practice,
public-sector programmes, and complex project delivery

A practice that holds together
whether or not you're in the room.

Your information has a home, your studio keeps moving, and your attention goes to the work you actually trained for. The craft stays human. The judgement stays human. The rest runs itself.