Because it shouldn't be hard
Senior architectural, project and BIM‑led support when projects start to feel stretched, unclear, or over‑complicated.
Because it shouldn't be hard
Senior architectural, project and BIM‑led support when projects start to feel stretched, unclear, or over‑complicated.
We work across project set‑up, delivery, and reset — helping teams bring structure, clarity, and calm to work that matters.
Helping teams start well — or take a step back and reset when things feel unclear.
This might include defining scope, roles and programme, or simply creating space to think clearly before moving forwardd.
Hands‑on support where needed — bringing experience, structure, and calm to keep projects moving..
We work alongside teams to reduce friction and support delivery.
Experienced, pragmatic input during periods of change, pressure, or uncertainty.
Sometimes what’s needed is simply another pair of steady hands.
Oshigoto was set up to provide calm, practical support where projects don’t quite fit neatly into traditional roles or structures.
Over time, projects tend to accumulate complexity — not because anyone is doing a bad job, but because scope expands, responsibilities blur, and pressure increases. Oshigoto exists to step into those moments and bring clarity, structure, and judgement.
We work across project set‑up, delivery and reset — supporting teams when something needs shaping, steadying, or re‑aligning.
Because it shouldn’t be hard
Oshigoto is deliberately small and senior.
The work is hands‑on, embedded, and proportionate to what’s needed — not formulaic and not overly process‑led.
Engagements may be short and strategic, or longer and more embedded, depending on the challenge. The common thread is focused support that helps teams think clearly and move forward with confidence
Oshigoto is led by Rob Price.
Rob has spent over 35 years working across architectural practice, client‑side and contractor‑side roles, leading and supporting complex projects from early concept through to delivery.
That breadth of experience means Oshigoto brings:
Rob works directly on assignments — there is no hand‑off and no juniorisation of responsibility.
Most projects begin with a conversation.
Sometimes that leads to a short piece of advisory input.
Sometimes it develops into more sustained project or delivery support.
Either way, the aim is the same:
Honest project health checks. Calm, senior diagnosis. Practical fixes.
Coordinated, compliant, contractor‑ready information — so redesign doesn’t happen on site.
We work best with:
This way of working isn’t theoretical.
It’s been tested on complex, high‑risk projects at serious scale.
Large workplaces. Phased refurbishments. Live buildings. Long programmes. Multiple stakeholders.
Our experience includes projects for people like:
Shell
Bloomberg
MAN Group
Hearst
Bayer
Roles varied. Responsibilities shifted. What didn’t change was the need for clear thinking, strong coordination, and decisions that held up on site.
Feasibility, test fits, early diagnostics, and risk‑led thinking that prevents false starts.
Unpicking complexity. Clarifying roles. Re‑establishing momentum without adding noise.
Plug‑in architectural leadership, design management and coordination—focused where it matters.
From early strategy through technical design and delivery, we understand how decisions made on paper play out on site. That perspective shapes everything we do.
A lot of complexity creeps in when the wrong people start driving decisions.
Not because they lack intelligence —
but because they don’t own the consequences.
Projects drift when influence outweighs accountability,
when career priorities quietly override project priorities,
and when decision‑making sits with the wrong skill sets.
Clarity returns once decisions are owned
and the project itself is allowed to come first.
Revit is a powerful authoring tool. BIM is a way of deciding how information is created, shared, and relied upon. Confusing the two often leads to projects carrying more risk than anyone intended.
Authoring in Revit does not automatically mean better coordination, nor does it, by itself, justify higher fees. The more important questions are about scope, responsibility, and what information is actually required to make sound decisions at each stage.
There is often an enthusiasm to make the model work too hard — to model every fixing, junction, or component. In practice, understanding boundaries and strengths is far more valuable. Much of what sits beyond a 1:20 level adds complexity rather than clarity.
Used well, Revit’s real strengths sit elsewhere: scheduling, specification links, coordination checks, and the ability to generate consistent visuals and walkthroughs from the same source of information. When this is understood early, projects avoid duplication, re‑work, and the familiar pattern of parallel models being rebuilt downstream.
When those questions aren’t addressed early, BIM doesn’t become more helpful — it simply becomes louder.