How Developers Can Stop Early Decisions from Becoming Major Overruns: Marian Krotov’s Framework 

As developers worldwide struggle with delays rooted in poor preparation, Russian project director Marian Krotov has successfully applied a cross-functional system that helps prevent early decisions from becoming cost and schedule overruns, cutting one project’s forecast budget by 7–9% without compromising quality. 

Construction delays usually become visible on site, but a 2025 cross-continental analysis suggests that many begin much earlier. After examining 480 public infrastructure projects across Latin America, Africa, and Eurasia, CoST traced 60% of the identified delay drivers to the preparation phase, including poor feasibility studies, unclear scope, and inadequate financial planning. Among projects with usable delay data, about 70% ran late and took 73% longer than originally planned on average.

Marian Krotov, a recognized project director at FSK Severo-Zapad, one of the largest residential developers in Russia, has already found an answer to this problem. He developed an integrated project control methodology that combines financial modeling, engineering review, contractor capability assessment, and cross-functional risk management into a single decision framework. Drawing on more than 18 years in construction and development, he has applied this approach to major residential projects at FSK Severo-Zapad and Pioneer, including a review that reduced one project’s forecast construction budget by 7–9% without compromising quality or the property’s consumer characteristics.

“I try to understand the whole project, from its economics and strategy through construction and operation,” Marian says. “A decision can appear effective within one function and still create costs elsewhere.”

Keeping Design and Economics in the Same System  

A project’s financial model can become outdated long before executives notice a formal budget problem. Original calculations may rely on preliminary quantities, early specifications, assumed approval periods, provisional construction methods, or market prices that no longer reflect the project under development.

Meanwhile, the design continues to evolve. Engineering requirements change, authorities impose new conditions, procurement lead times shift, and contractors refine the scope. Finance may still measure the project against assumptions that the design and construction teams have already left behind.

Marian’s methodology addresses that gap by comparing the financial model with the project as it currently exists. He examines whether quantities, specifications, permits, procurement periods, construction sequencing, contractor capacity, and commercial assumptions still support the expected cost and return.

The review extends beyond checking whether individual budget lines have increased. Marian assesses how each proposed decision affects the entire development.

A less expensive system may require more labor or extend installation. A material substitution may reduce the initial budget while increasing maintenance or warranty exposure. A technical change may raise design costs but create more sellable space. A low contractor price may depend on productivity or scheduling assumptions that the project cannot realistically achieve.

“When we assess an optimization proposal, I ask what it changes across the entire project,” Marian says. “A lower-priced system may need more labor to install. A design change may raise engineering costs and still pay for itself by creating more sellable space. A cheaper material may reduce today’s budget and increase warranty or maintenance costs later. The real measure is the project’s total cost over time.”

His methodology therefore treats the financial model as a live project-control instrument. The model must reflect the current design, while technical decisions must account for their financial, contractual, operational, and commercial consequences.

That connection matters most during design and preconstruction, when the developer still has several workable options. Once the company orders materials, mobilizes contractors, or places activities on the critical path, a correction can affect procurement, sequencing, labor, financing, and delivery at the same time.

The methodology demonstrates an approach that may be applicable to other large residential developments facing rising construction costs and increasingly complex coordination. It shifts project control toward the stage when management still has the ability to change course.

Turning Project Reviews Into Financial Results  

Marian developed the whole-project review process and implemented it at Pioneer. On one residential development, he initiated a reassessment of design and engineering solutions, materials, and construction processes.

The project team did not define optimization as finding the lowest available price. Each proposed saving had to preserve regulatory compliance, construction quality, and the characteristics promised to buyers. The team also considered whether a change would create added costs through installation, schedule disruption, maintenance, or reduced commercial value.

This process required coordination among the project’s technical, financial, construction, and management functions. A proposal that appeared efficient within one department could not proceed until the team understood its consequences for the rest of the development.

The review reduced the forecast construction budget by approximately 400 million rubles, or 7–9%, without lowering quality or the property’s consumer characteristics.

The case illustrates the value of reviewing several connected decisions while the project still has flexibility. The result did not come from one major design cut. Marian and the project team examined how technical solutions, materials, and construction processes worked together, then removed costs that did not contribute to safety, quality, or customer value.

A second residential development presented a different problem. The project had entered a deficit model, meaning its current cost structure no longer supported its target financial indicators.

Marian reviewed the financial model against the current project, identified possible CAPEX reductions, and participated in approving technical changes. Those measures helped return the development to its target financial performance.

This case shows that the methodology was not limited to a single cost-reduction exercise. Marian applied the same whole-project review to a different financial problem, using CAPEX analysis and technical changes to restore the development’s target performance.

The exercise also showed why periodic budget reporting alone cannot protect project economics. Executives need a direct connection between what the design currently requires and what the financial model currently assumes. Without that connection, a project may appear viable on paper after its actual cost structure has already changed. Although Marian developed the framework through individual projects, its structure may also be applied to other large residential developments facing rising construction costs and increasingly complex coordination.

Marian has applied elements of this framework across multiple FSK Severo-Zapad and Pioneer developments whose disclosed construction budgets total more than $536 million. His portfolio includes the six-stage quarter, with a budget exceeding $152 million and more than 2.69 million square feet of building area, and the approximately 271,000-square-foot premium residential building, budgeted at approximately $45.6 million.

Contractor Strategy as Project Control  

Developers often compare tender prices before testing the assumptions that make those prices possible. Marian’s methodology treats scope completeness, contractor capacity, productivity, interfaces, and schedule credibility as part of the commercial decision, not as problems to address after the contract has been awarded.

Marian applies the same system to contractor selection. He does not treat the quoted price as sufficient evidence that a bidder can deliver the work.

A contractor may submit an attractive proposal while relying on unrealistic productivity, omitting temporary works or utility interfaces, or pricing from incomplete drawings. Those gaps can return later as change orders, claims, schedule extensions, or quality problems.

Marian examines whether the contractor has the technical resources, management capacity, financial stability, and reporting discipline required for the project. He also tests whether the proposed schedule is realistic and whether the bid clearly includes the work needed to complete the scope.

His responsibilities at FSK Severo-Zapad include tender procedures, contract strategy, and coordination among more than 30 contractor organizations. This scale makes the allocation of responsibility especially important. When several designers, contractors, and internal departments contribute to the same development, an undefined interface can leave critical work without a clear owner.

Marian uses contract strategy to establish scope, reporting requirements, decision rights, change procedures, and responsibility for design gaps. These provisions give the developer a clearer basis for responding when costs, schedules, or technical requirements change.

A low price can weaken project control when the contract leaves major assumptions unresolved. A stronger proposal may offer greater value if the contractor has accounted for the full scope, provided a credible schedule, and demonstrated that it can manage the interfaces on which delivery depends.

Contractor assessment therefore becomes part of the same whole-project framework. The developer compares the bid with the live design, the financial model, the construction sequence, and the risks that the contract assigns to each party.

The process did not remain confined to one assignment. Project teams continued using elements of his approach on subsequent developments while the methodology became part of the company’s project review process.

Why Early Escalation Depends on People  

Technical and financial controls work only when project participants report accurate information soon enough for management to act.

A contractor may delay disclosing a probable schedule problem. A manager may defend an earlier decision after its assumptions have changed. A department may protect its own budget by transferring cost or operational risk to another part of the development.

In each situation, executives lose visibility before the formal numbers show that the project is in trouble.

Marian’s professional training in business psychology informs how he manages this part of project control. He uses defined escalation routes, structured negotiations, and clearer responsibility for decisions to help teams raise uncertainty before positions harden and the available options narrow.

Project participants need to know where to report a problem, what evidence decision-makers require, who has authority to resolve it, and how quickly the issue needs an answer. Without that structure, a technical question can remain open until it disrupts procurement or construction.

Marian established and implemented a more consistent coordination process at Pioneer, connecting the developer, designers, contractors, and internal departments. According to the project account, the process reduced organizational delays, improved decision transparency, and supported the timely completion of key project stages.

The psychology component does not replace engineering analysis, financial control, or contract management. It makes those systems usable. A financial model cannot remain current when teams withhold information. A contract cannot protect the schedule when participants allow an unresolved interface to remain hidden. A technically sound decision may still fail when departments do not agree on who must implement it.

An overrun may become visible during construction, but its cause may already exist in an outdated financial model, an incomplete design, an unrealistic bid, an unclear allocation of responsibility, or a risk that no one escalated. Construction has traditionally managed design, finance, procurement, and execution as separate disciplines. Marian Krotov’s framework integrates them into one decision process, giving developers an alternative to conventional value engineering focused on isolated cost cuts. As projects become larger and more capital-intensive, sustained performance will increasingly depend on keeping those functions connected while management still has room to change course.

Have you read?
Mustafa Kabak on Building HPO.TECH and Prioritizing Certification.
New York Personnel-File Law Applies to Small Businesses Too.
Daniel Nadler’s OpenEvidence Partners With Johns Hopkins Medicine.
Richard Waryn’s Seven Lessons From Dealmaker to Business Owner.
Ronald Karauri-Backed Definite Assurance Captures Kenya’s PSV Insurance Market.

Follow CEOWORLD Magazine on: Google News, LinkedIn, X (Twitter), and Facebook.

Note: The views expressed are those of the authors and do not necessarily reflect those of CEOWORLD Magazine, its Editorial Board, or management. Content is provided "as is," may contain monetized links, and is not professional advice. See our Ethics & Guidelines for details. Reproduction requires prior written permission.

Contact info@ceoworld.biz for inquiries or media requests.