Choosing Business Software That Grows With You

Most companies do not choose business software once. They choose it, outgrow it, and choose again a few years later — usually in the middle of a busy quarter, with several years of records sitting inside a system nobody wants to open anymore. That second decision almost always costs more than the first, because by then you are not buying a tool, you are moving a company.

The question a demo will not answer for you

Before asking what a system can do, ask what happens to your information if you leave it. Can you export a complete, readable copy of your data — employee records, payroll history, journal entries, customer and supplier lists — in a format that opens somewhere else? Can you do that yourself, on demand, without filing a request and waiting a week? A summary report is not an export. If the honest answer is "our team can prepare that for you," you are renting your own records.

Ask where the data is stored, who at the vendor can see it, and what happens to it after the contract ends. Under the Data Privacy Act your company remains the personal information controller for your employees' data even when a vendor processes it for you, so a vendor's incident is still your obligation: NPC Circular No. 16-03 requires the controller to notify the National Privacy Commission within seventy-two hours of knowing, or reasonably believing, that a personal data breach has occurred. A vendor who cannot describe how, and how quickly, they would tell you has answered the question anyway.

Roles are what break first as headcount grows

At five people, everyone sees everything and it works. At twenty-five it stops working, because those same screens now hold salary rates, disciplinary notes, bank details and supplier pricing — and the person encoding attendance has no business reading any of them. Software that offers only "administrator" and "user" pushes you into over-granting access, then papering over the gap with trust.

What you want is permission granularity that matches how you actually delegate: rights assigned per module and per action, so a payroll officer can process a run without opening the general ledger, and a branch supervisor sees only their own team. In ERPat this lives in the Security module, which covers accounts, sessions, roles and granular access control across every module — one place to answer the access question instead of a different answer in each application.

Ask about sessions as well. When someone resigns on a Friday, withdrawing their access should be a single immediate action with a record of it, not a round of emails to whoever administers each system.

Room to add modules without starting over

Most growing companies buy software in the order the pain arrives: payroll first, then something for inventory, then a proper ledger once the auditor insists. Bought separately, each purchase is reasonable. Together they create the real cost — the same employee encoded in three places, month-end reconciliations that exist only because two systems disagree, and a spreadsheet quietly acting as the integration layer between them.

The more useful evaluation question is not "does this handle payroll well" but "when I need the next piece, is it already here, and does it run on the same data?" An integrated platform lets you switch on what you need when you need it, working from one employee list, one customer list, one chart of accounts. Ask what adding a module involves — a configuration change, or another implementation project with its own migration — and what it costs, because that answer describes your third year, the one that usually surprises people.

Plan for the second company before you have one

Growth among Philippine SMEs often arrives as a second entity rather than a bigger one: a separately registered branch, a sister company for the trading side, a spin-off that needs its own books and its own filings. Many systems handle that by making you buy and maintain a second installation, which means two upgrade schedules, two sets of user accounts, and no consolidated view of either.

It is worth asking how a platform handles multiple entities even while you still have only one. ERPat's Tenancy module provides multi-tenant management — several separate tenant instances running from a single ERPat deployment — so a second company becomes a configuration decision rather than a second procurement. Records that must stay apart stay apart, while administration stays in one place.

Even if you never use it, the answer is diagnostic: a vendor who has thought carefully about multiple entities has usually thought carefully about the rest of growth.

The rules will change underneath you

Anything touching payroll or tax is only as current as its last update, and this year made the point well. In January the SSS contribution rate rose to 13% of the monthly salary credit — 8.5% employer, 4.5% employee — with the salary credit range widened to ₱3,000 through ₱25,000, and the new WISP provident fund began taking the portion computed above an MSC of ₱20,000, so one deduction for a higher earner now splits across two funds. PhilHealth announced its scheduled increase at the end of 2020, then reverted within days under a moratorium and collected the previous year's rate for all of 2021.

None of that is exotic; it is what an ordinary year looks like. Every one of those changes had to reach the calculation actually running your December payroll. So ask who maintains the contribution tables and withholding schedules, how an update is delivered, whether it is included in what you already pay, and how fast a mid-year change lands. The fixed points hold — 13th month pay is due not later than December 24, and BIR Form 2316 must be in employees' hands by January 31 — but the arithmetic behind them keeps moving.

Buy for a process you can describe

Software formalises whatever process you hand it. If approvals today happen by walking to someone's desk, a system will not invent the policy for you — it will expose that there isn't one, usually during implementation and usually under time pressure. The most valuable preparation before any demo is writing down, in a page or two, who requests, who approves, who posts, and what the exceptions are.

That page doubles as your evaluation script. Instead of watching a prepared tour, hand the vendor your two most annoying real scenarios — the employee with two rate changes mid-cycle, the invoice settled in two tranches — and ask them to do it in front of you.

A short list of questions is a good sign

None of this appears on a feature comparison, which is exactly why it is worth asking. Features are what a vendor prepares for; data portability, permission granularity, multiple entities and the update process are what you live with. Get honest answers on those four and the feature list mostly takes care of itself — miss them, and no number of features will make the third year comfortable.