In-House vs Managed Infor Support: How to Decide

In-house Infor support keeps Lawson or CloudSuite knowledge inside your own team. Managed Infor support moves that work — functional help, tax and regulatory updates, year-end, custom reports, integrations, security and upgrades — to an outside provider under defined response times and a predictable fee. Neither model is better on its own. The deciding factors are whether you already have Infor specialists you intend to keep, how much of your support load is routine versus project work, and whether you can staff coverage around payroll and financial close without gaps.

What "in-house" and "managed" actually mean

In-house support means your own employees own the application. They take the tickets, apply the updates, build the reports, test the upgrades, and carry the pager when a payroll run goes sideways. Managed support means an outside team owns that run-and-maintain work under contract, while your team keeps the business decisions.

The distinction that matters is not who logs into Lawson or CloudSuite. It is who owns the queue when something breaks the night before a payroll or close deadline.

What in-house support does well

An internal team has context an outside provider cannot buy. They know which department really owns that general ledger string, why a custom report exists, and which workaround people rely on during month-end. That context is why in-house teams often resolve familiar issues faster than any ticket queue.

In practice, in-house support tends to win on:

• Institutional memory. Years of configuration history, custom reports and one-off workarounds live with the people who built them.
• Proximity. Finance and HR can walk over and ask. Priorities get set in a hallway, not in a change request form.
• Control. Every change, every access grant and every patch decision stays inside your walls.

Where in-house support quietly breaks down

The strain rarely shows up in an audit. It shows up as a deadline that nearly slipped.

• Key-person risk. One or two people hold most of the Lawson or CloudSuite knowledge. When they leave, retire or take two weeks off in January, the queue stops moving.
• Deadline compression. Tax and regulatory updates and year-end work land on a fixed calendar whether or not your team has capacity that month. Everyone else's projects wait.
• Specialist gaps. IPA/ProcessFlow work, ISD/Birst reporting, security reviews and upgrade testing are not everyday tasks for a small team, so they get deferred until something breaks.
• Coverage. Genuine 24/7/365 coverage on an internal team means three shifts or an on-call rotation that burns people out. Most mid-market teams end up with business-hours support and hope.

What managed Infor support actually covers

Be specific about scope before comparing price, because "managed Infor support" means very different things at different providers.

Cendien's Infor practice covers Infor Lawson support and Infor CloudSuite managed services, plus ongoing functional and technical support for Lawson, CloudSuite and CSI/SyteLine. The work includes tax and regulatory updates and year-end, custom reports, integrations, security and upgrades, and support for a move from Lawson to CloudSuite or from Lawson to Workday. On the Lawson side, the covered modules are HR, payroll, benefits, absence and time, and the financials — general ledger, accounts payable, accounts receivable and budgeting — along with IPA/ProcessFlow and ISD/Birst reporting.

Delivery matters as much as the list. Cendien's support is delivered by a dedicated U.S.-based team from Carrollton, Texas, with on-site coverage across Dallas–Fort Worth and remote support nationwide. Cendien's ERP application managed services — which span Infor, Workday, Oracle and PeopleSoft — are stated as a 99.9% uptime SLA, a 15-minute response time, 24/7/365 support and a fixed monthly fee for managed support.

Read those numbers as a scope question, not a sales claim: an SLA is only useful if the work it covers is the work you actually need done.

Managed does not mean "someone else owns Infor"

A managed contract buys execution and coverage. It does not buy direction. Even with a provider handling the queue, someone inside your business still has to own:

• which configuration changes are approved, especially anything touching payroll or the financials;
• how processes should work, rather than how they happen to work today;
• who is allowed to see or export payroll, benefits and financial data;
• the priority order when two urgent issues arrive the same morning.

Teams that skip this step get a provider that is busy but not aligned. Teams that name an internal owner get a provider that behaves like an extension of the department.

The trade-offs, stated plainly

• Cost shape. In-house cost is salary, benefits, training, backup coverage, and the specialist work you still have to buy externally. Managed cost is a fixed monthly fee for a defined scope. Compare the total cost of coverage — including the deadline scramble — not an hourly rate against a monthly fee.
• Flexibility. An internal team can pivot the same afternoon to whatever the CFO raises. A managed contract is bounded by scope, so ask what lands in scope versus what becomes a change request.
• Continuity. In-house accumulates context but loses it when a person leaves. Managed should accumulate it in documentation — but only if the contract requires runbooks and you actually receive them.
• Access to specialists. Managed support gives you IPA/ProcessFlow, Birst/ISD, security and upgrade people without hiring for skills you need a few weeks a year.
• Control and audit. In-house keeps everything inside your environment. Managed means vendor access reviews, segregation of duties and a real exit plan.

When managed support is the wrong answer

Managed support is not automatically the mature choice. Several situations call for something else:

• Your team is staffed and only needs surge help. If the gap is two weeks around year-end, staff augmentation with Lawson consultants is a better fit than replacing the function. You get the hours you are short without renegotiating who owns the application.
• You are pre-go-live or mid-implementation. That is a project, not managed support. Fix the build before you buy the run.
• Your processes change materially every quarter. A fixed-scope contract will keep generating change requests. Stabilize the process, or scope the work as project-based until it settles.
• You need substantial custom development. Development is project work with its own estimate. Bundling it into a support contract hides the cost instead of controlling it.
• Nobody internally can own the queue. A managed provider needs a counterpart who can approve changes and set priorities. Without one, decisions stall and the SLA quietly becomes irrelevant.

Questions to ask before your Infor support renewal

Ask these in writing and compare the answers side by side, whether the renewal is with an internal team you are funding or an outside provider.

1. Which modules and products are in scope? Name them — Lawson HR, payroll, benefits, absence and time, general ledger, AP, AR, budgeting — plus CloudSuite or CSI/SyteLine if you run them. Scope described as "Infor support" is not scope. 2. Are tax and regulatory updates and year-end included? These are the highest-risk weeks of the year. Confirm they are in the base fee, not an annual add-on. 3. Who applies patches and tests them? Apply-and-test is different work from apply-and-hope. Ask what testing happens before a change reaches production. 4. Is IPA/ProcessFlow work covered? Same question for ISD/Birst reporting. These are usually where a generalist provider stalls. 5. What is the response time, and what does it measure? Response time is not resolution time. Cendien's ERP application managed services state a 15-minute response time and 24/7/365 coverage — make sure you know which queue that clock starts on. 6. Is there an uptime commitment, and how is it measured? Cendien's ERP application managed services state a 99.9% uptime SLA. Ask any provider what counts against it and what happens when it is missed. 7. Fixed fee or time and materials? If fixed, what triggers an overage? If hourly, ask for the rate card and the expected monthly range. 8. Who owns the customizations and the documentation? You should leave a renewal — or an exit — with runbooks, interface inventories and report specifications, not a provider's institutional memory. 9. Who is on the team, and where are they? A named team you can meet beats a pooled queue. Ask who covers your platform and your time zone. 10. What does termination look like? Notice period, data handback, parallel-run support and knowledge transfer should be written down before you sign, not negotiated during a divorce. 11. Reference checks in your own platform mix. A strong Workday reference says little about a Lawson payroll year-end.

How to decide in one working session

You do not need a six-month evaluation to settle this. Block an hour with your IT lead, the finance owner and the HR or payroll owner, and work through four questions.

1. Sort last quarter's Infor work into three piles — routine maintenance (updates, access, reports), deadline work (tax, regulatory, year-end), and project work (upgrades, integrations, transitions). The proportions tell you where the pressure actually is. 2. Count your specialists. If IPA/ProcessFlow, Birst/ISD reporting or upgrade testing depend on one person, you have a coverage problem, not a capacity problem. That distinction points to managed support or augmentation rather than another hire. 3. Test your coverage honestly. Ask what happened the last time a payroll issue landed outside business hours. If the answer involves someone's personal cell phone, write down what that costs you in attrition and risk. 4. Decide who owns direction before you decide who owns the queue. The internal owner of Infor priorities, change approval and data access should be named in the same meeting. If nobody will take it, fix that first.

A useful rule of thumb: keep in-house what differentiates your business and buy what is merely necessary. Most mid-market finance and HR teams do not differentiate themselves by applying tax updates at midnight.

How Cendien fits into this decision

Cendien has been an IT consulting, staffing and managed services firm since 1999, based in Carrollton, Texas, and serving Dallas–Fort Worth. The Infor work is not a side practice: it covers Infor Lawson support across HR, payroll, benefits, absence and time and the financials, plus Infor CloudSuite and CSI/SyteLine managed services, along with tax and regulatory updates, year-end, custom reports, integrations, security, upgrades and Lawson-to-CloudSuite or Lawson-to-Workday transitions.

That means three practical options rather than one pitch. If you need the whole run-and-maintain function covered, ERP application managed services set out the scope, the stated SLAs and the fixed monthly fee. If you need specific skills for a fixed period — a year-end crunch, an upgrade, a reporting backlog — staff augmentation with Lawson consultants covers that without changing who owns the application. If the pressure is tied to a specific calendar event, the Lawson year-end W-2 checklist is a reasonable place to see how the work is sequenced.

Where the answer depends on your own environment — module mix, customization depth, how many people currently touch Infor — it is worth a short conversation rather than a guess. You can contact Cendien and describe what you run today.

FAQ

Do we lose our Lawson customizations if we move to managed support?

No. Customizations stay in your environment; a provider takes over maintaining and supporting them. What changes is who understands them, which is why an inventory of custom reports, IPA/ProcessFlow flows and interfaces belongs in the transition scope — and why you should ask for that documentation as a deliverable rather than a favor.

Can managed support start mid-year?

Usually yes. A mid-year start needs a knowledge transfer plan: access, documentation review, a parallel period where the provider shadows your team, and an agreed cutover date for the ticket queue. Ask any provider to describe that sequence before you sign, because a contract that starts on paper without a handover plan just moves the backlog.

What happens to support during a Lawson-to-CloudSuite or Lawson-to-Workday move?

Transition work is project work and should be scoped separately from ongoing support, even when the same team does both. The useful question is continuity: who covers the legacy environment while the new one is being built and tested, and who owns the cutover weekend. Getting that answer in writing prevents the common gap where the old system is unsupported before the new one is stable.

In-house and managed Infor support solve different problems. Matching the model to the problem you actually have — coverage, specialists, deadlines or direction — is the decision worth making carefully.