We Run Our Business on Referrals
Fresh Projects is a UK-based software platform designed for architects, engineers, and other built-environment professionals to manage financial aspects of their projects. It helps teams track fees, timesheets, expenses, billing, and overall profitability to keep projects on budget and profitable. The platform also centralises project data, streamlines administrative tasks, and offers mobile app support for easy access and updates.
1a Colinette Road
London
SW15 6QG
© 2026 Fresh Projects
Product
We Run Our Business on Referrals
Fresh Projects is a UK-based software platform designed for architects, engineers, and other built-environment professionals to manage financial aspects of their projects. It helps teams track fees, timesheets, expenses, billing, and overall profitability to keep projects on budget and profitable. The platform also centralises project data, streamlines administrative tasks, and offers mobile app support for easy access and updates.
1a Colinette Road
London
SW15 6QG
© 2026 Fresh Projects
Product
When Teams Stop Speaking The Same Operational Language
When Teams Stop Speaking The Same Operational Language
When Teams Stop Speaking The Same Operational Language
Reading Time:
Reading Time:
6
6
minute(s)
minute(s)
During a recent conversation with a practice leadership team, somebody made an offhand comment that stayed with me afterwards.
“We spend more time discussing the reporting than the projects.”
Nobody laughed because everyone around the table recognised the feeling immediately.
The practice itself was doing well. They had grown steadily over several years, expanded into new sectors and built a strong delivery team. There were systems in place, monthly reporting packs, forecasting structures and regular operational reviews. From the outside, it would have looked like a business with a good grip on performance.
What had become harder was maintaining confidence that everyone across the practice was interpreting operational information in the same way.
Forecasts were being updated at different points in the month depending on project pressure. One office had gradually adapted a reporting template to suit a specific client and that version had started circulating more widely. Project managers carried slightly different assumptions around what constituted a “healthy” fee position. Teams were still producing reports, but people no longer felt entirely certain they were looking at a single operational reality underneath them.
The conversation reminded me of several moments during the recent RIBAJ webinar, Running a Modern Architecture Practice, with Nigel Ostime and Rachael Trott. A large part of the discussion focused on visibility, but not in the way people often frame it.
Most established practices are not operating without systems or reporting. The challenge tends to emerge later, once complexity starts spreading unevenly through the business. Growth introduces more projects, more teams, more delegation and more local decision-making. Over time, operational habits naturally begin evolving in slightly different directions.
That drift is rarely intentional. In many cases it develops because teams are trying to solve sensible local problems quickly. A project lead builds a spreadsheet because they need a clearer way of tracking scope changes on a live job. Another team adjusts forecasting categories to make internal reporting easier. Someone delays updating project information because a client issue takes priority that week. None of these decisions seem particularly important on their own, which is partly why the cumulative effect often goes unnoticed for a long time.
Eventually, however, leadership teams begin feeling the consequences in subtle ways. Meetings become slower because people want additional checks before decisions are made. Finance teams spend more time reconciling reports that technically already exist. Directors start asking for parallel versions of the same information because confidence in the underlying reporting has weakened slightly.
At one point during the webinar, I described it as the moment when:
“Instead of sitting in that meeting making decisions, the debate turns to whether the data can be trusted or not.”
That reaction seemed to resonate with a lot of the audience because operational friction rarely presents itself dramatically inside architecture practices. More often, it appears as hesitation.
One of the audience poll responses during the session illustrated this quite well. Around 68% of attendees described themselves as “mostly confident” in their project and financial reporting. That answer felt revealing because “mostly confident” usually means teams are functioning, but leadership still senses some inconsistency somewhere in the process.
The operational strain often becomes visible long before firms would describe themselves as having a reporting problem.
In another webinar poll, 60% of attendees said time and resource constraints were the biggest barrier to improving visibility. That finding mirrors a broader pattern emerging across professional services firms. Research published this year by McKinsey highlighted how operational complexity increasingly affects decision-making speed inside growing knowledge businesses, particularly where workflows become fragmented between teams, offices or business units.
Architecture practices feel this acutely because project delivery naturally creates decentralised ways of working. Teams adapt quickly to client demands, project stages and commercial pressures. That flexibility is often one of the sector’s strengths. The difficulty comes when operational processes evolve independently for long enough that practices lose consistency around forecasting, utilisation, reporting ownership or project performance tracking.
Nigel Ostime touched on this during the webinar when discussing how practices gradually outgrow structures that previously worked perfectly well at a smaller scale. It was an important point because many operational systems are initially built around proximity and informal communication. Once firms expand, those informal alignments become harder to maintain consistently across the business.
I have seen this happen in practices where reporting itself remained technically accurate, but operational interpretation had diverged enough that leadership teams no longer trusted how confidently they could act on the information in front of them.
Sometimes the signs are surprisingly ordinary. A finance team notices that project managers are updating forecasts at entirely different rhythms. Utilisation assumptions begin varying between studios. Teams continue maintaining their own “safe” spreadsheets alongside the central system because they no longer feel completely comfortable relying on shared reporting alone.
None of this usually points to incompetence. If anything, it often reflects capable people trying to manage operational pressure pragmatically.
Harvard Business Review recently explored a similar dynamic in an article about organisational alignment, arguing that operational inconsistency often emerges when intelligent teams solve local problems in isolation without enough shared visibility across the wider organisation. That observation feels particularly relevant inside architecture practices, where delivery teams constantly balance commercial constraints, client demands and project realities simultaneously.
One of the more interesting aspects of the webinar discussion came from Rachael Trott’s comments around adoption and operational buy-in. Practices sometimes assume that introducing better systems automatically creates better visibility. In reality, operational confidence usually depends far more on shared behaviours than software alone.
Teams need a common understanding of when information should be updated, what “good” forecasting looks like and who owns reporting confidence across the practice. Without that alignment, even sophisticated systems can gradually become fragmented by inconsistent habits around them.
This is partly why live operational visibility has become increasingly important for larger firms. Static month-end reporting often struggles to keep pace with how quickly project conditions shift across delivery teams. By the time leadership reviews a report, the operational reality underneath it may already have moved on.
That does not mean architecture practices are suddenly abandoning spreadsheets. Most still rely heavily on them because they remain flexible and familiar. The challenge is less about spreadsheets themselves and more about disconnected workflows creating multiple operational realities across the business.
It is one of the reasons many firms have started exploring tools like LiveSheets more seriously. The value is not really about creating another dashboard. In practice, the biggest benefit tends to come from helping finance teams, project leads and leadership work from the same live information without forcing people to abandon familiar workflows entirely.
The practices that seem to navigate operational growth most confidently are rarely the ones trying to add more layers of reporting. More often, they focus on reducing friction. Reporting ownership becomes clearer. Forecasting habits become more consistent across teams. Project updates happen closer to real time. Parallel processes gradually reduce.
None of those changes sound especially transformational when written down individually. Together, though, they make a noticeable difference to how confidently a leadership team can operate.
Because operational visibility is not simply about having access to data. It depends on whether teams across the practice are still interpreting, updating and using that information consistently enough for leadership to trust the picture they are seeing.
Once that consistency begins drifting, decision-making slows down far more quickly than most firms expect.
Continue the conversation
Following the webinar, we created a companion resource exploring some of the operational signs teams may no longer be working from the same operational picture.
Are Your Teams Speaking The Same Operational Language?
A practical infographic for growing architecture practices looking to improve operational consistency, reporting confidence and visibility across teams.
You can also watch the full RIBAJ webinar replay featuring Nigel Ostime, Rachael Trott and Simon Berry.
During a recent conversation with a practice leadership team, somebody made an offhand comment that stayed with me afterwards.
“We spend more time discussing the reporting than the projects.”
Nobody laughed because everyone around the table recognised the feeling immediately.
The practice itself was doing well. They had grown steadily over several years, expanded into new sectors and built a strong delivery team. There were systems in place, monthly reporting packs, forecasting structures and regular operational reviews. From the outside, it would have looked like a business with a good grip on performance.
What had become harder was maintaining confidence that everyone across the practice was interpreting operational information in the same way.
Forecasts were being updated at different points in the month depending on project pressure. One office had gradually adapted a reporting template to suit a specific client and that version had started circulating more widely. Project managers carried slightly different assumptions around what constituted a “healthy” fee position. Teams were still producing reports, but people no longer felt entirely certain they were looking at a single operational reality underneath them.
The conversation reminded me of several moments during the recent RIBAJ webinar, Running a Modern Architecture Practice, with Nigel Ostime and Rachael Trott. A large part of the discussion focused on visibility, but not in the way people often frame it.
Most established practices are not operating without systems or reporting. The challenge tends to emerge later, once complexity starts spreading unevenly through the business. Growth introduces more projects, more teams, more delegation and more local decision-making. Over time, operational habits naturally begin evolving in slightly different directions.
That drift is rarely intentional. In many cases it develops because teams are trying to solve sensible local problems quickly. A project lead builds a spreadsheet because they need a clearer way of tracking scope changes on a live job. Another team adjusts forecasting categories to make internal reporting easier. Someone delays updating project information because a client issue takes priority that week. None of these decisions seem particularly important on their own, which is partly why the cumulative effect often goes unnoticed for a long time.
Eventually, however, leadership teams begin feeling the consequences in subtle ways. Meetings become slower because people want additional checks before decisions are made. Finance teams spend more time reconciling reports that technically already exist. Directors start asking for parallel versions of the same information because confidence in the underlying reporting has weakened slightly.
At one point during the webinar, I described it as the moment when:
“Instead of sitting in that meeting making decisions, the debate turns to whether the data can be trusted or not.”
That reaction seemed to resonate with a lot of the audience because operational friction rarely presents itself dramatically inside architecture practices. More often, it appears as hesitation.
One of the audience poll responses during the session illustrated this quite well. Around 68% of attendees described themselves as “mostly confident” in their project and financial reporting. That answer felt revealing because “mostly confident” usually means teams are functioning, but leadership still senses some inconsistency somewhere in the process.
The operational strain often becomes visible long before firms would describe themselves as having a reporting problem.
In another webinar poll, 60% of attendees said time and resource constraints were the biggest barrier to improving visibility. That finding mirrors a broader pattern emerging across professional services firms. Research published this year by McKinsey highlighted how operational complexity increasingly affects decision-making speed inside growing knowledge businesses, particularly where workflows become fragmented between teams, offices or business units.
Architecture practices feel this acutely because project delivery naturally creates decentralised ways of working. Teams adapt quickly to client demands, project stages and commercial pressures. That flexibility is often one of the sector’s strengths. The difficulty comes when operational processes evolve independently for long enough that practices lose consistency around forecasting, utilisation, reporting ownership or project performance tracking.
Nigel Ostime touched on this during the webinar when discussing how practices gradually outgrow structures that previously worked perfectly well at a smaller scale. It was an important point because many operational systems are initially built around proximity and informal communication. Once firms expand, those informal alignments become harder to maintain consistently across the business.
I have seen this happen in practices where reporting itself remained technically accurate, but operational interpretation had diverged enough that leadership teams no longer trusted how confidently they could act on the information in front of them.
Sometimes the signs are surprisingly ordinary. A finance team notices that project managers are updating forecasts at entirely different rhythms. Utilisation assumptions begin varying between studios. Teams continue maintaining their own “safe” spreadsheets alongside the central system because they no longer feel completely comfortable relying on shared reporting alone.
None of this usually points to incompetence. If anything, it often reflects capable people trying to manage operational pressure pragmatically.
Harvard Business Review recently explored a similar dynamic in an article about organisational alignment, arguing that operational inconsistency often emerges when intelligent teams solve local problems in isolation without enough shared visibility across the wider organisation. That observation feels particularly relevant inside architecture practices, where delivery teams constantly balance commercial constraints, client demands and project realities simultaneously.
One of the more interesting aspects of the webinar discussion came from Rachael Trott’s comments around adoption and operational buy-in. Practices sometimes assume that introducing better systems automatically creates better visibility. In reality, operational confidence usually depends far more on shared behaviours than software alone.
Teams need a common understanding of when information should be updated, what “good” forecasting looks like and who owns reporting confidence across the practice. Without that alignment, even sophisticated systems can gradually become fragmented by inconsistent habits around them.
This is partly why live operational visibility has become increasingly important for larger firms. Static month-end reporting often struggles to keep pace with how quickly project conditions shift across delivery teams. By the time leadership reviews a report, the operational reality underneath it may already have moved on.
That does not mean architecture practices are suddenly abandoning spreadsheets. Most still rely heavily on them because they remain flexible and familiar. The challenge is less about spreadsheets themselves and more about disconnected workflows creating multiple operational realities across the business.
It is one of the reasons many firms have started exploring tools like LiveSheets more seriously. The value is not really about creating another dashboard. In practice, the biggest benefit tends to come from helping finance teams, project leads and leadership work from the same live information without forcing people to abandon familiar workflows entirely.
The practices that seem to navigate operational growth most confidently are rarely the ones trying to add more layers of reporting. More often, they focus on reducing friction. Reporting ownership becomes clearer. Forecasting habits become more consistent across teams. Project updates happen closer to real time. Parallel processes gradually reduce.
None of those changes sound especially transformational when written down individually. Together, though, they make a noticeable difference to how confidently a leadership team can operate.
Because operational visibility is not simply about having access to data. It depends on whether teams across the practice are still interpreting, updating and using that information consistently enough for leadership to trust the picture they are seeing.
Once that consistency begins drifting, decision-making slows down far more quickly than most firms expect.
Continue the conversation
Following the webinar, we created a companion resource exploring some of the operational signs teams may no longer be working from the same operational picture.
Are Your Teams Speaking The Same Operational Language?
A practical infographic for growing architecture practices looking to improve operational consistency, reporting confidence and visibility across teams.
You can also watch the full RIBAJ webinar replay featuring Nigel Ostime, Rachael Trott and Simon Berry.
Published:
Published:
When Teams Stop Speaking The Same Operational Language
When Teams Stop Speaking The Same Operational Language
When Teams Stop Speaking The Same Operational Language
Why growing architecture practices often lose reporting confidence gradually, long before anyone formally identifies a systems problem.
Why growing architecture practices often lose reporting confidence gradually, long before anyone formally identifies a systems problem.
What It Really Means When a Client Recommends You
What It Really Means When a Client Recommends You
What It Really Means When a Client Recommends You
Why the built environment has always grown through trust, and what that means for the firms that do it well.
Why the built environment has always grown through trust, and what that means for the firms that do it well.
Why Reporting Leaves Firms Guessing
Why Reporting Leaves Firms Guessing
Why Reporting Leaves Firms Guessing
Inside many built environment firms, meetings meant for decisions quietly turn into debates about the numbers on the page.
Inside many built environment firms, meetings meant for decisions quietly turn into debates about the numbers on the page.
Why Multi-Office Firms Lack Visibility
Why Multi-Office Firms Lack Visibility
Why Multi-Office Firms Lack Visibility
In many built environment consultancies, reporting technically works. The challenge is that clarity often arrives after the moment when it would have influenced action.
In many built environment consultancies, reporting technically works. The challenge is that clarity often arrives after the moment when it would have influenced action.
Why Reporting Slows Firms Down
Why Reporting Slows Firms Down
Why Reporting Slows Firms Down
Even with reporting systems in place, many architecture, engineering and quantity surveying firms find that insight arrives too late to influence decisions during delivery.
Even with reporting systems in place, many architecture, engineering and quantity surveying firms find that insight arrives too late to influence decisions during delivery.
Compare A&E Management Tools
Compare A&E Management Tools
Compare A&E Management Tools
Choosing a practice management system is no longer about feature lists. This guide explains how architecture and engineering firms should compare tools in 2026, focusing on adoption, usability and decision-making rather than complexity.
Choosing a practice management system is no longer about feature lists. This guide explains how architecture and engineering firms should compare tools in 2026, focusing on adoption, usability and decision-making rather than complexity.
Spreadsheets in A&E Firms: What Works
Spreadsheets in A&E Firms: What Works
Spreadsheets in A&E Firms: What Works
A practical guide to using Excel and Sheets well, and knowing when to graduate to purpose-built systems without losing the flexibility you love.
A practical guide to using Excel and Sheets well, and knowing when to graduate to purpose-built systems without losing the flexibility you love.
Women in AEC at Fresh Projects
Women in AEC at Fresh Projects
Women in AEC at Fresh Projects
Why representation, visibility and better systems matter for the future of architecture and engineering
Why representation, visibility and better systems matter for the future of architecture and engineering
Architecture Leadership Challenges
Architecture Leadership Challenges
Architecture Leadership Challenges
How firm leaders can protect margin, prepare successors and modernise delivery without losing what made them successful
How firm leaders can protect margin, prepare successors and modernise delivery without losing what made them successful
5 Ways to Outgrow Spreadsheets Profitably
5 Ways to Outgrow Spreadsheets Profitably
5 Ways to Outgrow Spreadsheets Profitably
How architecture and engineering practices protect margin as teams and project complexity increase
How architecture and engineering practices protect margin as teams and project complexity increase
The Profitability Pyramid Explained
The Profitability Pyramid Explained
The Profitability Pyramid Explained
Understanding the real drivers of financial performance for medium and large practices over the past year
Understanding the real drivers of financial performance for medium and large practices over the past year
3 Lessons to Help You Run a More Profitable Practice
3 Lessons to Help You Run a More Profitable Practice
3 Lessons to Help You Run a More Profitable Practice
Practical insights from A&E leaders on spotting profit risks early, communicating value, and protecting margins
Practical insights from A&E leaders on spotting profit risks early, communicating value, and protecting margins
Embracing Neurodiversity in Architecture
Embracing Neurodiversity in Architecture
Embracing Neurodiversity in Architecture
How inclusive practice design can unlock creativity, innovation and operational clarity
How inclusive practice design can unlock creativity, innovation and operational clarity
Profitable Projects: Winning the Right Projects in AEC
Profitable Projects: Winning the Right Projects in AEC
Profitable Projects: Winning the Right Projects in AEC
How to qualify leads, focus your pipeline and forecast success more confidently
How to qualify leads, focus your pipeline and forecast success more confidently
Profitable Projects: The Art of Cashflow Alchemy in AEC
Profitable Projects: The Art of Cashflow Alchemy in AEC
Profitable Projects: The Art of Cashflow Alchemy in AEC
How architecture and engineering firms can turn unpredictable cash flow into a strategic advantage
How architecture and engineering firms can turn unpredictable cash flow into a strategic advantage
Setting Fees for Profitable Projects
Setting Fees for Profitable Projects
Setting Fees for Profitable Projects
Why bottom-up fee setting, clear scope and real-time cost visibility underpin profitable projects
Why bottom-up fee setting, clear scope and real-time cost visibility underpin profitable projects
Tools That Improve A&E Profitability
Tools That Improve A&E Profitability
Tools That Improve A&E Profitability
Why better visibility across projects, people and finances is now essential for sustainable practice performance
Why better visibility across projects, people and finances is now essential for sustainable practice performance
How to Manage Inflation on Architecture Projects
How to Manage Inflation on Architecture Projects
How to Manage Inflation on Architecture Projects
Practical ways to protect fees and margins when costs change mid-project
Practical ways to protect fees and margins when costs change mid-project
An Architect’s Guide to Project Budgeting
An Architect’s Guide to Project Budgeting
An Architect’s Guide to Project Budgeting
How to build realistic, profitable project budgets that support better pricing and delivery
How to build realistic, profitable project budgets that support better pricing and delivery
Improve Project Profitability: An Architect’s Guide
Improve Project Profitability: An Architect’s Guide
Improve Project Profitability: An Architect’s Guide
Practical ways architecture practices can protect margins and make better commercial decisions
Practical ways architecture practices can protect margins and make better commercial decisions
Calculate Your Cost Rate in 3 Simple Steps
Calculate Your Cost Rate in 3 Simple Steps
Calculate Your Cost Rate in 3 Simple Steps
Why understanding your true cost rate is the foundation of profitable fees, resourcing and decision-making
Why understanding your true cost rate is the foundation of profitable fees, resourcing and decision-making
When to Hire: Key Decisions
When to Hire: Key Decisions
When to Hire: Key Decisions
Why workload visibility and forecasting matter more than instinct in mid-sized architecture practices
Why workload visibility and forecasting matter more than instinct in mid-sized architecture practices
5 Basics to Improve Profitability
5 Basics to Improve Profitability
5 Basics to Improve Profitability
Five practical habits that help architecture practices improve profitability without adding complexity
Five practical habits that help architecture practices improve profitability without adding complexity
3 Questions for Profitable Firms
3 Questions for Profitable Firms
3 Questions for Profitable Firms
How clear insight into projects, clients and utilisation drives better decisions in mid-sized A&E firms
How clear insight into projects, clients and utilisation drives better decisions in mid-sized A&E firms
What Makes Firms More Profitable?
What Makes Firms More Profitable?
What Makes Firms More Profitable?
Why the most profitable firms spend less time on financial management and still make better decisions
Why the most profitable firms spend less time on financial management and still make better decisions
A-Team Approach to Profitability
A-Team Approach to Profitability
A-Team Approach to Profitability
Why reallocating work across roles can dramatically improve utilisation and margins in 50–100 person A&E practices
Why reallocating work across roles can dramatically improve utilisation and margins in 50–100 person A&E practices
I Love Excel. I Hate Excel.
I Love Excel. I Hate Excel.
I Love Excel. I Hate Excel.
Why spreadsheets break down in 50–100 person architecture and engineering practices, and what works better
Why spreadsheets break down in 50–100 person architecture and engineering practices, and what works better
Getting Project Fees Right
Getting Project Fees Right
Getting Project Fees Right
How accurate budgeting and disciplined scope control protect profitability in 50–100 person A&E practices
How accurate budgeting and disciplined scope control protect profitability in 50–100 person A&E practices
Working Capital Risks in A&E Firms
Working Capital Risks in A&E Firms
Working Capital Risks in A&E Firms
The financial blind spot that catches even well-run architecture and engineering practices
The financial blind spot that catches even well-run architecture and engineering practices
We Run Our Business on Referrals
Fresh Projects is a UK-based software platform designed for architects, engineers, and other built-environment professionals to manage financial aspects of their projects. It helps teams track fees, timesheets, expenses, billing, and overall profitability to keep projects on budget and profitable. The platform also centralises project data, streamlines administrative tasks, and offers mobile app support for easy access and updates.
1a Colinette Road
London
SW15 6QG
© 2026 Fresh Projects
Product
