Network comparison diagram
2 APPROACHES EXAMINED
7 COMPARISON DIMENSIONS
JP OPERATIONAL CONTEXT

Two approaches to
urban network advisory

Conventional consulting and structured fixed-scope advisory produce different kinds of outcomes. Here's what those differences look like in practice.

— WHY THIS COMPARISON MATTERS

The question behind the engagement

When a municipal team or transit operator decides to review their network infrastructure, they typically encounter two broad categories of advisory available to them: open-ended consulting arrangements with flexible scope, or structured engagements defined by a clear deliverable and duration.

Neither is wrong in every situation. Open-ended arrangements suit genuinely exploratory work where the shape of the problem isn't yet clear. Fixed-scope advisory suits organisations that have a defined question and want a considered answer returned in a form they can act on.

This page tries to describe both approaches honestly, so that teams considering how to commission network work can understand what they'd be getting into with each.

— SIDE BY SIDE

Approach comparison

SCOPE DEFINITION

CONVENTIONAL

Often agreed after work begins; scope can expand as findings emerge.

PMG APPROACH

Defined before the engagement starts. Deliverable, duration, and fee agreed in writing.

DELIVERABLE FORMAT

CONVENTIONAL

Slide decks, verbal recommendations, summary emails. Long-form documents less common.

PMG APPROACH

Written document — structured, diagrammed, formatted as a reference rather than a sales artefact.

FEE STRUCTURE

CONVENTIONAL

Day-rate or time-and-materials. Final cost confirmed after completion.

PMG APPROACH

Fixed fee. ¥24,500 to ¥43,500 depending on service type. No variable billing.

— DISTINCTIVE ELEMENTS

What makes the methodology different

Written over verbal

Most advisory produces something that lives in a meeting room and fades afterward. Our engagements produce documents. That document is the product — not a summary of conversations that happened to take place.

Options, not directives

We don't tell clients what to build. We document what we observed, set it in context, and present a set of considered options. The decision about which path to take — and when — belongs to the client.

Fixed engagement, clear end

Every engagement has a defined end point. We don't encourage continuation beyond what was agreed, and our deliverables are designed to support independent decision-making rather than dependency on further input from us.

Built for Japanese operating environments

Assessment formats, session structures, and documentation conventions are calibrated for Japanese public sector and transit organisations. We don't require clients to translate our outputs into their internal language.

Diagrams as documentation

Where a network or system relationship is better shown than described, we produce diagrams that can be included in planning documents and internal briefings. These aren't decorative — they carry content.

No preferred vendor position

We don't have commercial relationships with technology vendors or implementation partners. Our assessments reflect what we observed, not what would favour a referral arrangement.

— OUTCOMES

What each approach tends to produce

OPEN-ENDED CONSULTING

  • Broad exploration of the problem space, with findings shaped by what emerges during the engagement
  • Recommendations often tied to the consultant's preferred framework or prior experience
  • Final cost and timeline become clear retrospectively rather than being fixed in advance
  • Useful when the brief cannot yet be stated precisely

STRUCTURED ADVISORY (PMG)

  • A written document covering the defined area or system, with observations and considered options
  • Findings presented neutrally, without a built-in preference for a particular technical path
  • Cost and duration fixed before the engagement begins
  • Suitable when a team has a defined question and wants a considered written answer

— INVESTMENT PERSPECTIVE

Cost, value, and what you're paying for

The three services sit between ¥24,500 and ¥43,500. That's a fixed number — not an estimate that grows. Here's how to think about what that covers.

¥24,500

URBAN NETWORK ASSESSMENT

Two-week site-survey engagement. Written assessment covering coverage, gaps, and considered options across a defined urban area.

¥43,500

COMMUNICATION INTEGRATION

Four working sessions mapping existing tools and identifying integration points. Reference document accompanies each session.

¥31,000

TRANSIT CONNECTIVITY

Three-week engagement examining passenger information and ticketing intersections. Concludes with a formal presentation to the client team.

Compared to open-ended consulting, where a day rate of ¥40,000–¥80,000 is not unusual and engagements routinely run longer than planned, a fixed-fee engagement offers a different kind of value: certainty. You know what you're spending before you commit.

The document you receive at the end can be used in internal planning, presented to stakeholders, and retained as a reference over time. It's not a sunk cost — it's a working asset.

— CLIENT EXPERIENCE

What the process feels like from the inside

CONVENTIONAL ENGAGEMENT

Week one: kickoff meeting, project charter, stakeholder alignment. Several people from your team involved from the start.

Weeks two to four: status updates, steering sessions, feedback rounds on draft materials. Ongoing time commitment from internal staff.

End of engagement: final presentation, recommendations document, transition planning. Conversation often continues with follow-on scope.

Total internal time: significant and distributed throughout. Hard to predict at the outset.

PMG STRUCTURED ENGAGEMENT

Week one: initial scoping call and written brief. We confirm the boundary, the deliverable, and the start date. Minimal internal time required.

During the engagement: site walks, documentation review, and/or working sessions are conducted with focused participation from relevant staff. No steering overhead.

Final week: written document delivered, reviewed together at handover session. Engagement concludes cleanly. No follow-on scope unless separately agreed.

Total internal time: concentrated and predictable. Most teams find the demand manageable alongside ongoing operations.

— LASTING IMPACT

What stays useful after the engagement ends

One of the less-discussed differences between approaches is what remains once the work is done. This matters more than it first appears.

A document you can return to

The written assessment doesn't expire. Teams reference it in later planning discussions, use it to onboard new staff, or present it to oversight bodies as evidence of due diligence.

Decisions that hold

Because recommendations are presented as options with context — rather than directives — the decisions teams make are grounded in their own reasoning. They're easier to defend and less likely to be reversed.

No dependency created

The engagement is designed to leave the client more capable of managing their own network questions — not more reliant on continued advisory input to understand their own infrastructure.

— CLARIFICATIONS

A few things worth clarifying

"Fixed scope means limited findings"

A defined scope doesn't limit the quality of what we find. It defines the geographic or organisational boundary — not a ceiling on how carefully we look within that boundary. Scoped work can be thorough.

"Short engagements produce shallow work"

Duration correlates with ambition of scope, not depth of observation. A two-week assessment of a defined urban area can be more precise than a six-month engagement that keeps expanding its scope.

"Advisory without implementation is incomplete"

Not every organisation needs someone to implement — many already have internal teams or procurement processes. What they need is an informed, independent assessment to inform those decisions. That's what we provide.

"A fixed fee means corners are cut"

Fixed fees work when the scope is defined. Because our engagements begin with a precise brief, we can price accurately. The fee covers the engagement as described. No corners are cut — the work was scoped to fit the fee, not the other way around.

— IN SUMMARY

When this approach is the right one

Structured fixed-scope advisory isn't for every situation. But for organisations in the following positions, it tends to be a good fit.

01

You have a defined question

You know broadly what you want to understand — coverage across a district, integration options for a communication stack, or connectivity gaps in a transit system.

02

You need a written record

The outcome needs to be presentable internally, used in procurement decisions, or retained for audit purposes. A verbal debrief won't serve those needs.

03

You want predictable cost

Budget cycles and procurement approvals are easier when the fee is a single fixed number rather than a range dependent on how the work develops.

04

Your team has limited bandwidth

You can't absorb weeks of steering meetings and feedback rounds. The engagement should deliver something useful without consuming your team's time continuously.

05

You're in Japan

Our work is built for Japanese operational environments. The documentation formats, session structures, and framing of options are calibrated for how decisions get made here.

06

You want independence

You'd prefer findings from someone with no vendor relationship or implementation incentive — just an honest account of what's there and what the options are.

— READY TO PROCEED?

Start with a conversation

If the structured approach sounds like a reasonable fit for what you're working on, get in touch. We'll discuss the brief and let you know whether one of our engagements would be useful — without any pressure to proceed.

Send us a message