The safest market is so sad...

ERP Is Not a Software Business. It Is a Control Business.

ERP is not glamorous. It is not a blue ocean. It is not the kind of market where people wake up one morning and suddenly decide they need “digital transformation” because a conference speaker said so.

ERP is much more basic than that.

Whatever happens in the economy, companies still need to control what they do. They need to invoice, report, approve, pay, collect, comply, measure, and explain. They need to know where the money is, where it went, what is blocked, what is late, what is taxable, what is profitable, and what is quietly bleeding cash in the background.

That makes ERP a safe industry. Not an easy one. Safe.

The mistake is to treat ERP as software. It is not. ERP is infrastructure for business discipline. It is the nervous system of the company. It is where accounting meets operations, where management meets reality, and where the pleasant stories from sales meetings either survive contact with numbers or die.

The market is crowded, of course. But crowded does not mean closed. It only means that the naive entry points are gone. You do not win here by saying “we also have an ERP.” Nobody cares. You win by choosing your battlefield, your customer, your industry angle, your channel, and your obsession.

And the obsession should not be features.

The obsession should be retention, trust, migration, usability, and business relevance.

The Real Market Is Not New Companies. It Is Other People’s Customers.

One uncomfortable fact must be accepted from the beginning: most ERP sales do not come from newly opened companies. New businesses represent a very small part of the market. The vast majority of the opportunity comes from companies already using something else.

In other words, this is not mainly a creation market. It is a replacement market.

That changes everything.

It means the central question is not “how do we sell ERP?” The central question is: why would a company take the risk of leaving its current system and move to us?

Because migration is scary. It touches accounting history, stock, contracts, workflows, reporting, approvals, employees, habits, fears, and hidden messes that nobody wants to expose. A company may hate its current ERP and still refuse to change it, simply because the pain is familiar.

So the sales strategy must attack the fear directly.

Do not promise “implementation.” Everybody promises implementation. Promise controlled migration. Promise continuity. Promise automatic data import. Not free. Automatic. Make migration a product. Package it, price it, explain it, demonstrate it, document it. Treat it as one of the main weapons, because for many customers it is the main obstacle.

The company that makes migration feel safe wins the first battle.

The company that keeps the customer after migration wins the war.

Retention is not a support function. Retention is strategy. In a market where most business is taken from competitors, losing customers is not leakage. It is strategic failure. Every lost customer becomes somebody else’s case study.

ERP Has Users, But It Also Has Beneficiaries

Another mistake: ERP companies often sell to users and forget the beneficiaries.

The users are usually accountants, operators, warehouse people, payroll staff, clerks, administrators. They matter. They suffer daily if the product is bad. They know the screens, the shortcuts, the frustrations, the ridiculous clicks, the reports that never export properly, the fields that make no sense.

But the beneficiaries are somewhere else.

The beneficiaries are owners, CEOs, CFOs, commercial directors, plant managers, board members. They do not want to “use ERP.” They want decisions. They want visibility. They want to know if the company is healthy or lying to itself.

This is where most ERP products are still strangely weak.

They drown the operational user in forms and reports, but give the decision maker very little that feels alive. A CEO should not have to beg accounting for a report that is already outdated by the time it arrives. A CFO should not need three people and two Excel files to understand exposure, margins, debt, taxes, working capital, overdue invoices, stock rotation, or cash pressure.

The ERP must move upstairs.

It needs executive dashboards. Real-time, clean, sharp, ugly if needed, but useful. Revenue, costs, taxes, growth, new customers, credit exposure, margins, collections, stock, production, approvals, risk. Not decoration. Not Power BI theater. Actual management instruments.

And these instruments should not be generic.

Each industry has its own pulse. Construction does not breathe like retail. Retail does not bleed like manufacturing. Manufacturing does not move like distribution. Distribution does not think like services.

So build industry intelligence. Not just fields and templates. Build best-practice report libraries. Build benchmarks. Build alerts. Build “this is what good looks like” into the product.

Make the ERP teach the company how to see itself.

The Accountant Community Is Not a Side Audience. It Is a Strategic Asset.

If accountants are the main daily audience for many off-the-shelf ERP products, then the professional community around them is not just a marketing opportunity. It is a distribution engine, a feedback engine, a trust engine, and a retention engine.

Bring accountants, auditors, consultants, tax advisers, lawyers, trainers, and implementation specialists into the same orbit.

Not in a boring newsletter. Not in another dead “partner portal” nobody opens.

Build a living professional community around the product.

Create a small online academy. Certification paths. Practical training. A “genius” program for advanced users. Turn strong users into independent freelancers who can support the application across the country. Give them visibility. Suggest a transparent man-day price. Let them negotiate. Let the market breathe.

This creates more than support capacity. It creates belonging.

And belonging is underrated.

ERP is sticky when the product is good. It becomes very sticky when a whole professional ecosystem grows around it.

There is also a deeper opportunity: let customers group around industries and co-finance improvements. If ten companies in the same sector need the same report, workflow, integration, or dashboard, do not force them into ten separate custom projects. Aggregate demand. Finance the change together. Reward contribution. Build points, royalties, credits, recognition.

Make customers feel that the product evolves with them, not despite them.

Add libraries, seminars, vouchers, professional association partnerships, expert directories, certifications, bundles, events, socialization. Even raffles if needed. Yes, raffles. This market is serious, but it is not dead.

And then animate it. Relentlessly.

A community that is not animated becomes a cemetery with login credentials.

Auto-generated content can help. Video can help. Webinars can help. Rankings can help. Public recognition can help. A database of accountants with profiles, locations, scores, specialties, certifications, and availability can help.

Make a damn Facebook of accountants if that is what the market secretly needs.

Not because it sounds fashionable. Because accountants influence software decisions more than most vendors admit.

Sell It Like Infrastructure. Price It Like a Subscription. Scale It Like Lego.

The off-the-shelf ERP model should be simple to understand and easy to expand.

Sell it like antivirus software: yearly subscription, continuous updates, visible protection, compliance readiness, and clear renewal logic. The customer must understand why they pay every year. Not because of licensing tricks, but because the product keeps them alive, compliant, updated, and operational.

Use online demo accounts. Let prospects touch the product. Let partners demonstrate it. Let industries see their own version, not a generic database with fake invoices and dead sample customers.

Build the product in layers.

Core ERP. Industry add-ons. Optional modules. Widgets. Connectors. Dashboards. Mobile approvals. Alerts. Smart reporting. Marketplaces.

Like Lego: scale up, scale down, pay for what you use, and understand the total cost of ownership.

TCO must become a selling weapon. Especially against large, heavy, expensive platforms. If a customer is trapped in a mammoth system where every minor change becomes a budget discussion, attack that. Calmly. Mathematically. Brutally.

Do not say “we are cheaper.”

Say: here is what ownership actually costs over five years. Here is the implementation cost. Here is the support cost. Here is the cost of change. Here is the cost of waiting. Here is the cost of internal frustration. Here is the cost of not seeing your numbers on time.

That is how you sell against giants.

Not by pretending to be bigger. By being sharper.

Cloud Is Not Optional. But Trust Must Be Engineered.

Cloud is no longer a future direction. It is the obvious direction.

Data centers are looking for partners. Co-marketing is possible. Infrastructure players need serious business applications to justify cloud adoption beyond storage, email, and generic hosting.

But ERP data is sensitive. Customers will not move just because the vendor says “cloud.” They must trust the model.

So trust must be engineered.

Use strong authentication. Use OTP tokens. Use encryption. Use clear backup policies. Use physical security arguments where relevant. Explain where the data is, who can access it, how it is protected, how disaster recovery works, and what happens if something goes wrong.

Do not hide security behind vague language.

Customers trust what they understand.

The cloud offer should not feel like “your data is somewhere.” It should feel like “your data is safer, more available, better protected, and easier to control than it is in the improvised server room next to the printer.”

That is the standard.

UX Is Not Decoration. It Is Adoption

Software is usually made by engineers. That is both the strength and the problem.

Engineers love completeness. They respect complexity. They are proud of functionality. And in ERP, complexity is unavoidable.

But complexity as capability is good. Complexity as a giant pill shoved down the user’s throat is not.

ERP does not need to become Facebook. Nobody is asking for childish screens and fake simplicity. But it must move from simple to complex, not from complex to impossible.

The learning curve must be respected.

Use wizards. Use natural language where possible. Use guided flows. Use better defaults. Use role-based screens. Use clean approval paths. Use mobile where mobile makes sense. Use fewer clicks. Use focus groups. Watch real users work. Sit with accountants. Sit with warehouse operators. Sit with CFOs. Watch where they hesitate, where they curse, where they export to Excel, where they call support, where they invent workarounds.

That is where the product is telling the truth.

UX is not about making ERP pretty. It is about making it usable under pressure.

Because people do not use ERP in ideal conditions. They use it at month-end, during audits, under tax deadlines, during stock reconciliation, during payroll closing, when customers are shouting, when managers are asking for numbers, and when nobody has patience.

Design for that reality.

The Channel Cannot Be Bought. It Must Be Built

A serious partner channel is not a list of companies with logos on a website.

It is a governed ecosystem.

Partners need induction, methodology, sales training, technical enablement, implementation discipline, rules, margins, tools, and a shared language. This sounds basic until you see how often even simple words like “lead” and “opportunity” mean different things to different companies.

That confusion kills predictability.

And predictability is the whole point.

A channel exists so sales objectives can move down the funnel at a steady, controlled, measurable rate. It exists so revenue becomes less accidental. It exists so demand can be captured, distributed, served, and expanded without chaos.

Direct requests should be centralized and distributed fairly to partners based on transparent rules: geography, delivery capacity, specialization, workload, customer preference, performance. Otherwise, the channel becomes political. And once it becomes political, trust begins to rot.

Anti-corruption agreements are not paranoia. They are hygiene.

Sales training is not optional. Induction is not optional. Methodology is not optional.

And no, I would not try to “buy” a channel as if it were a volume acquisition. That usually imports other people’s habits, expectations, informal promises, bad behaviors, and historical baggage.

Choose partners carefully. Grow them. Support them. Measure them. Remove them if necessary.

There are many local companies with captive customers in hardware, infrastructure, support, accounting services, or niche software. Many of them have relationships but no scalable portfolio. That is an opportunity. Give them something serious to sell. Give them margin. Give them method. Give them confidence.

The channel should be built on synergy, rules, predictability, added value, and margin.

Not enthusiasm.

Enthusiasm is nice. Governance pays invoices.

Sales Must Stop Selling Discounts

ERP sales must be disciplined. Not desperate.

Do not sell discounts. Sell certainty, relevance, migration, support, industry knowledge, and financial logic.

For a small company, EUR 25,000 may be a major investment. Treat it as such. Do not throw a EUR 15,000 discount into the first offer and then act surprised when the customer stops respecting the price.

Call. Follow up. Understand the business. Know the competition. Know the real objection. Know who is afraid of change. Know who benefits from the current mess. Know who wants the project and who will silently sabotage it.

Sell to the business side, not only to IT.

In many cases, IT is not the buyer. IT may be a gatekeeper, an influencer, a defender of the current architecture, or a risk evaluator. But the ERP decision belongs to management because ERP changes how the company runs.

So sell the functional result.

Do not sell “ERP.” Sell control over stock. Sell faster closing. Sell cleaner tax reporting. Sell fewer manual reconciliations. Sell real-time margin. Sell approval discipline. Sell predictable cash visibility. Sell a management cockpit. Sell survival without Excel heroics.

Build a serious sales toolkit: objections, documents, proof of concept scripts, TCO models, ROI calculators, migration plans, industry decks, competitive battle cards, demo scenarios, proposal templates, implementation roadmaps, references.

Make the documents sensational. Not noisy. Sensational in clarity.

A good ERP sales document should make the customer feel slightly embarrassed about how unclear their current situation is.

That is when the conversation becomes real.

Retention Also Depends on the Sales Force

Customer retention and sales force loyalty are connected.

In a competitive ERP market, relationships matter. A customer may stay because the product is good. But often, the customer stays because someone competent knows their context, answers their calls, anticipates their problems, and translates technical reality into business language.

Losing good salespeople or account managers can expose the customer base.

So the internal sales culture matters. Methodology matters. Incentives matter. Trust matters. Anti-corruption matters again. Customer knowledge must be centralized, not trapped inside the memory of one person.

The company must know the customer better than any individual employee does.

That is how you protect the base.

Development Must Avoid the Customization Trap

The product architecture must be disciplined from the beginning.

The number of maintained project instances should be minimal. Customization must not become a swamp. Every exception that becomes a private branch creates future cost, future bugs, future upgrade pain, and future dependency on specific people.

Start with a strong ERP core. Separate industries through add-ons, not uncontrolled customizations.

Think internationally from the architecture level. Go full IFRS as the conceptual core and treat Romania as a localization, not as the center of the universe. That makes future expansion possible and keeps the system intellectually clean.

Industry solutions should be open-ended. They can become entry points into specific markets, but they should not fracture the core.

And some niche solutions should be designed as certified add-ons for Microsoft Dynamics, SAP, or Oracle. That may sound counterintuitive, but it is not. If a niche module is strong enough, it can sell into ecosystems much larger than the original platform. That creates credibility, revenue, and strategic optionality.

Do not think small just because the first market is local.

Industry 4.0 Is Not a Slogan. It Is the Floor

The future is not “coming.” It is already sitting in the warehouse, on the production line, near the scale, next to the label printer, inside the scanner, and inside every cheap sensor nobody has connected yet.

ERP must go to the floor.

Scan everything. Weigh everything. Label everything. Box everything. Pack everything. Track everything. Connect machines, sensors, devices, approvals, production stages, stock movement, and quality checks.

Real time is not a luxury. In operational businesses, real time is the difference between managing and guessing.

And the technology is no longer exotic. With affordable devices, sensors, Raspberry Pi-level setups, mobile terminals, barcode scanners, industrial scales, and connected equipment, a lot can be done without pretending every project is a NASA mission.

The point is not to decorate the ERP with “Industry 4.0” language.

The point is to make the company measurable.

Once things are measured, they can be controlled. Once they are controlled, they can be improved. Once they are improved, the ERP stops being an administrative cost and becomes operational leverage.

The Strategic Direction

The opportunity is not to build yet another ERP.

The opportunity is to build a business control platform with a strong community, disciplined channel, serious migration capability, industry intelligence, cloud trust, executive dashboards, and an architecture that can scale without collapsing under custom work.

Focus on niches. Focus on industries. Focus on migration. Focus on retention. Focus on usability. Focus on the business buyer. Focus on proof.

Finance software acquisition with local banks. Target companies older than five years in competitor systems, because that is when pain becomes mature. Target heavy production countries. Poland. Turkey. Germany. Look for operational density. Look for industries with complexity and money.

Bring in adjacent solutions. Warehousing. Automation. Approval flows. Mobile. Sensors. Reporting. Compliance. Data migration. Add-ons.

Make the ERP addictive in the right places: reporting, approvals, payroll, HR, stock, cash, compliance, management visibility. Not addictive as entertainment. Addictive because once the company sees clearly, it does not want to go blind again.

That is the real product.

Not software.

Clarity. Control. Continuity. Speed.

And if the market is crowded, good.

Crowded markets prove demand. They only punish weak positioning.

The ERP market does not need another vendor whispering “digital transformation.”

It needs someone willing to say, bluntly:

Your company is already running on a system. The only question is whether that system gives you control - or just records the damage after it happens.