Six-months-with-RamBase-Mitac_s-journey-from-go-live-to-results

Six months with RamBase: Mitac’s journey from go-live to results

Six months ago, answering a customer's order inquiry could take Angelina Persson ten minutes or more, switching between Excel files, internal systems, and production schedules to piece together a complete answer. Today, as Chief Operating Officer at Mitac, she has the same information at her fingertips in seconds.

The difference? RamBase Cloud ERP

"Everything we need is now in one place," says Persson. "Real-time data, complete traceability, instant answers. It's transformed how we operate."

For the 40-person operation, the six months since going live have been about discovering what's possible when information flows freely and everyone works from the same source of truth. This is their honest, unfiltered account of what actually happens in the first six months after flipping the switch.

The reality check: What actually changed?

From guesswork to certainty

Before RamBase, Mitac had no unified business system. Finding information meant hunting through spreadsheets, emails, and local files. The impact touched every department:

Production:

"The difference for me is enormous," says Sanna Virtanen, Production Manager. "Before, I was working with estimates and assumptions. Now I can follow the entire production flow from delivery to delivery and see reality as it actually looks."

This shift from estimation to reality changes everything. Sanna can now enter all necessary information, control exactly who sees what, and track dependencies across the entire production process.

"It's fantastic," she says. "Instead of constantly searching for information in multiple places, you now find it readily available."

The transparency has even changed how Mitac works with customers.

"It forces all of us to become more structured," Sanna adds. "And it forces customers to become more structured too."

Sales & Purchasing:

"I have control over things in a way I never did before," says Adam Bergqvist. "I can follow the flow and clearly see if something needs to be back-ordered from a supplier. Before, it was 'yeah, I think we have it', more guesswork. Now I can see it directly in RamBase instead of logging into several systems or emailing suppliers to ask. We don't need to think we know anymore. Now we know."

This certainty eliminates an entire category of problems: promising delivery dates based on assumptions, scrambling when inventory didn't match expectations, and the downstream effects on customer trust and production schedules.

Time tracking gets real

One of the most tangible improvements came in time registration. Before, operators filled out paper forms without really knowing how long they'd actually spent on each part. Today, it's measurable with RamBase.

"It makes it much easier to follow up and set requirements on how long tasks should take," says Angelina. "No more guessing, just data."

This shift enables accurate job costing, reveals previously invisible bottlenecks, and provides the foundation for continuous improvement. When you know how long things actually take, you can make informed decisions about pricing, capacity, and process optimization.

Complete traceability transforms quality

The system provides end-to-end visibility: when something was purchased, when it arrived, what it's used in, and where it is in production.

"We can trace everything now," explains Angelina. "If there's a quality issue, we can find the source quickly. And we can see patterns that might indicate problems before they become major incidents. That kind of visibility was impossible before."

The cross-departmental transparency means fewer surprises. Production can now clearly see when all components have arrived and when they haven't, eliminating miscommunications that used to be routine.

"Those 'I didn't know that component wasn't coming' situations are increasingly rare," says Sanna.

The implementation philosophy: Confidence before speed

One of the most striking aspects of Mitac's journey is their deliberate pacing.

"The implementation has been a transparent process," says Angelina. "We've trained departments little by little, giving everyone time to participate, learn, and become comfortable. We moved forward slowly and deliberately—it's been a safe and good way for everyone in the organization to adopt the new system."

This phased approach created several advantages:

  • Reduced resistance when people aren't overwhelmed
  • Early wins that built momentum and confidence
  • Organizational learning that allowed discovery of optimal workflows
  • Sustainable change embedded in daily operations

For companies considering similar transitions, Mitac's approach offers a valuable counterpoint to rushed implementations. Speed matters less than sustainability.

What's next: Growing into the system

Six months in, Mitac is candid about being early in the journey. They're working on extracting comprehensive KPIs around specific efficiency gains and error reduction metrics. Those numbers will come.

But the qualitative improvements are already clear:

  • Decisions happen faster because data is immediately accessible
  • Miscommunications have decreased through shared visibility
  • Inventory accuracy has improved from guesswork to certainty
  • Customer service has strengthened through faster, more accurate responses

Perhaps most importantly, Mitac invested in RamBase early in their growth trajectory, before inefficiency became crisis.

"We didn't wait until things were broken," reflects Angelina. "This positions us to scale with confidence as demand increases, rather than playing catch-up with infrastructure."

Comments (0)

Leave your comment

No comments here yet, start first!

Leave your comment
Add the comment

You may also read:

From coat to full control – five levels for better financial management

“Find the coat!”, he said and threw a new set of travel expenses on the desk. Some time ago, an acquaintance of mine had an expense claim for a raincoat rejected. He had bought it in connection with a conference when it suddenly started to rain. The company should cover that much, he thought. The company didn’t think so. They asked him to review the travel invoice again. He went back, summed up and assessed, and submitted a new travel expense report with the same final amount, but without a visible coat. If you don’t have a reasonable level of granularity in your bookkeeping, it’s possible to hide the coat. Why detailed accounting is an economist’s dream Every economist’s dream is a specific set of accounts where the information available can enable useful and good analysis. A data basis where you don’t have to make assumptions or guess at allocations. Just as an engineer must consider strength measurements and material properties when constructing a building, finance must build its reporting and accounting data in a detailed and forward-looking way. Block Quote Level 1: Chart of accounts – the foundation of accounting In a traditional set of accounts, you’ll find main accounts showing income, expenses, assets, and liabilities. But for most businesses, these figures only scratch the surface. On their own, they add limited value. Compared to historical figures, they may be slightly more informative, but only slightly. The level below is various general ledger accounts that are part of an accounting group. Here it may be common to create an account for rent, one for cleaning, one for exterior maintenance, all of which will make up the main group “office costs”. You can do the same on the revenue side. Some people have an account for products, one for maintenance and one for service assignments. Then you have broken down total revenue a little more and can look at the change between the different main categories. But to take the analysis a step further, we need to look at where in the organization the revenues and costs actually arise. Level 2: Departments – cost allocation where it happens Most companies are divided into departments, which means that both revenue and costs can be recorded where they occur. It’s often straightforward to set up a departmental structure, but accurately allocating costs to the right departments can be challenging. At the same time, you must avoid the internal invoicing trap, where the focus shifts from optimizing company-wide value to maximizing departmental performance. Read more: ERP for the CFO Level 3: Customer and supplier – the key to financial analysis This one goes without saying: using customer and supplier data in financial analysis is invaluable. How much do your suppliers invoice annually? Who are your most important customers? What is their share of turnover? How has it changed since last year? Customers and suppliers can also be grouped into categories. RamBase offers many options for this, predefined or user-defined fields such as: Industry sector Geography Supplier size Classification (a, b, c supplier) RamBase also has dedicated fields for end customers. This means you can track not only who you invoice but also who actually uses the product. Companies subject to export controls and international trade regulations can benefit especially from this. Read more: Why your CFO’s input is crucial when choosing an ERP system Level 4: Additional dimensions – freedom to customize There are several dimensions that can be linked to individual transactions in the system and used for reporting and analysis. RamBase supports up to 10 dimensions, and here only your imagination sets the limits. These dimensions can be linked to general ledger accounts, sometimes as mandatory fields, to ensure proper classification before approval. Relevant dimensions might include: Geography Purpose Project number Activity dimension However, it’s easy to get overambitious and add too many mandatory dimensions. Be sure you’ll actually use the information. A dimension only adds value if the data quality behind it is solid. Level 5: Products and product groups – detailed product insights By creating separate articles for your products, you can break down the revenue base even further. How many units of product X have you sold? What is the average price? What is the net growth and in which customer group is the change most pronounced? RamBase allows detailed product specification. You can define fixed sales prices, predefine accounting rules, link to suppliers, and more. Products can also be grouped into product groups, enabling reporting independent of general ledger accounts. Read more: Get to know the finance module in RamBase Cloud ERP  Where’s the coat? If my acquaintance’s employer had taken a thoughtful and detailed approach to accounting data, he would have left the payroll department empty-handed. It wouldn’t have been possible to hide a coat among the totals and call it something else. We have to hold two thoughts in our heads at the same time. We can impose all kinds of requirements for details and specifications, but sometimes it’s more efficient to let a few details slip – like the coat – rather than spend significant resources maintaining the quality and granularity of our data.
From-coat-to-full-control-five-levels-for-better-financial-management
RamBase-companies-listing-visiting-card-logo
zweryfikowano

5/5(1 vote)

RamBase


RamBase
Central Europe
300 people
View profile
Industry
Automotive, Dystrybucja, Produkcyjna, Usługi
Description
Intelligent ERP system for manufacturing and wholesale businesses....
expand