September is often treated as a restart. Teams return, projects regain momentum and priorities are reorganised.

It is also a useful moment to review how the business is actually operating.

Over the summer, some weaknesses tend to become more visible: processes that stop when a specific person is unavailable, manual tasks that consume more time than expected, approvals with unclear ownership, or information that is still spread across different files and systems.

These are not isolated inconveniences. They are usually signs that processes need to be reviewed.

Start with dependencies

A good first question is simple: which processes still depend too much on individual people?

If an approval, report or operational task becomes difficult when someone is away, the process may rely more on personal knowledge than on a defined workflow.

This creates operational risk and makes scaling harder.

The objective should be to make responsibilities, information and next steps clear enough that the process can continue without constant intervention from the same people.

Review recurring manual work

Manual work often survives because each individual task seems relatively small.

Updating spreadsheets, copying information between systems, checking statuses manually or preparing recurring reports may only take a few minutes each time.

Across several people and departments, however, the impact becomes significant.

This is where ERP systems can create real operational value.

With Odoo, information from sales, purchasing, inventory, projects, manufacturing and finance can be connected within the same environment. Data is entered once and can then support the next steps in the process, reducing duplication and unnecessary administrative work.

Clarify who owns decisions

Another frequent source of delay is unclear ownership.

Who approves an exception? Who follows up on a delayed delivery? Who validates an unexpected purchase? Who acts when a margin falls below target?

When this is not defined, decisions move through emails, meetings and informal conversations.

Technology can support approval flows, responsibilities, activities and alerts, but the organisation first needs to define how the process should work.

That is why process design should come before system configuration.

Make sure teams are working from the same information

Different departments naturally have different priorities:

• Sales looks at pipeline and revenue. 
• Operations looks at capacity and delivery. 
• Finance looks at cash flow and margin.

Problems appear when each team is also working from a different version of the data.

An integrated ERP can reduce that gap by connecting the different stages of the business process. A quotation can become an order, trigger operational activities, generate a delivery and ultimately feed invoicing and accounting.

This gives teams a shared operational view and reduces the time spent reconciling information between departments.

Use September as a practical checkpoint

A September reset does not need to become a large transformation programme.

It can start with a few concrete questions:

• Which processes created the most friction during the last months?
• Where are teams still doing repetitive manual work?
• Which activities depend too much on specific individuals?
• Where is information still fragmented?
• Which decisions repeatedly require unnecessary coordination?

These questions often reveal where improvement will have the biggest operational impact.

At Oxalyo, this is also how we approach Odoo projects: we start by understanding the processes, identifying unnecessary complexity and defining how the business should operate.

Only then do we look at how Odoo can support that model.

September is therefore a good moment to review more than the backlog.

It is an opportunity to decide which habits, processes and workarounds should not simply return to business as usual.