Yes. A law firm can start IT support month-to-month while it evaluates a longer relationship, as long as the scope, access rules, escalation path, and exit process are clear from the outset. Use the first 60 to 90 days to see how onboarding and real support requests are handled, then decide whether the arrangement meets the firm's needs.
What needs to be clear before the provider starts?
Begin by identifying the systems that support confidential work: email and identity, workstations, remote access, practice and document management, billing, network equipment, and backups. The provider needs a reliable inventory and named firm contacts so work does not depend on informal assumptions.
For each system, identify who owns it, who administers it, and who can approve changes. Include third-party vendors and subscriptions. If the firm cannot yet answer one of those questions, record it as an open item rather than treating it as settled.
Agree on what the monthly service covers and what needs separate approval or pricing. Clarify how staff request help, how urgent work is escalated, and who can authorize a change that could affect access to client records. A service label alone does not define those responsibilities.
Ask for a practical onboarding checklist. It should show what the provider will review, what the firm must supply, and what will remain unknown until a vendor or firm decision-maker responds.
- Confirm the systems, users, and locations included in the initial scope.
- Record system ownership, administrator access, and firm approval contacts.
- Document how staff request help and how deadline-sensitive issues are escalated.
- List unresolved risks, dependencies, and decisions that need follow-up.
Plan to review the relationship after 60 to 90 days; that is a planning window, not a guaranteed technical or contractual milestone.
A good start leaves the firm with a documented view of systems, responsibilities, and unresolved questions. That gives partners a sound basis for deciding whether to continue.
How can we protect client deadlines during onboarding?
Set the escalation path before staff rely on the new support relationship. Identify how employees report an issue, how they flag a deadline or client impact, and who at the firm can make a time-sensitive decision.
Ask how the provider will communicate when a fix depends on a software vendor, a firm approval, or a change outside its control. Staff should know whether an issue is being worked, what is blocking progress, and what they need to do next.
Walk through realistic situations before they happen: a lawyer cannot reach a matter workspace, a new associate needs access before starting, or a suspicious email arrives with changed payment instructions. These checks help expose handoff gaps. They do not replace the firm's legal or security judgment.
Distinguish responsiveness from a contractual service-level commitment. If a particular response or resolution time matters, confirm that it is stated in the agreement and understand what the clock covers. Do not base deadline planning on an informal assurance.
GDS Technology provides IT help desk, managed IT, cybersecurity, and cloud services. The firm should confirm the specific support hours, escalation responsibilities, and included work in its proposed scope rather than infer them from a service name.
Clear escalation and useful status updates help staff keep work moving when technology gets in the way.
How should we handle confidentiality and access?
A month-to-month agreement does not make provider access temporary or automatically limit it. Decide which accounts the provider may administer, what requires firm approval, and how privileged access will be protected and reviewed.
Pay particular attention to access in document and practice management systems. Identify who approves matter-level permissions, how exceptions are recorded, and who should be contacted when an attorney or staff member cannot reach a workspace.
Include administrator accounts, multifactor authentication, shared mailboxes, remote access, endpoint protection, backup administration, and third-party applications in the transition checklist. Name the firm contact responsible for each approval. A partial inventory should be labeled as partial, not presented as a complete security review.
Employee departures need a coordinated process. The firm decides what happens to the person's mailbox, files, active matters, and records; the provider carries out approved technical steps. Retention, legal holds, and professional obligations depend on the firm's circumstances and are not decisions for an IT provider to make.
Document who owns each subscription and administrator account. This makes it easier to maintain appropriate firm control during the engagement and to hand systems over cleanly if the relationship ends.
Defined access and approval boundaries protect confidential work without making routine support harder than it needs to be.
What should we evaluate before choosing a longer agreement?
Judge the service by what happens after onboarding, not only by the sales conversation. Review whether requests have clear owners, whether updates help staff understand what is happening, and whether recurring problems lead to a practical prevention step.
Include the firm administrator and a few attorneys or paralegals who use the systems daily. Ask them whether they know where to go for help and whether the response helps them continue their work. Their experience can reveal friction that a technical checklist will miss.
A GDS client described follow-through this way: "GDS followed up the next day to make sure the door sensor issue is resolved. That kind of attention shows real customer service." This example concerns a door sensor, not law-firm IT. It illustrates the value of confirming that an issue is actually resolved.
For backups, ask what was tested, what was restored, and what assumptions remain. A status report alone does not show whether a critical workspace can be recovered in the time the firm needs. Ask the provider to explain open risks and dependencies in plain language.
Before extending, review the written scope alongside actual support interactions. Consider ownership, communication, follow-through, and the firm's remaining risks, not just the number of tickets closed.
Base the longer-term decision on demonstrated service and documented responsibilities.
How should we compare month-to-month and longer-term costs?
Nationally, fully managed IT planning ranges are $100 - $250 per user/month. These are market planning ranges, not GDS Technology prices. The actual scope can differ based on security tools, backup, network and server coverage, support hours, compliance needs, and included licensing.
Nationally, co-managed IT planning ranges run $60 - $160 per user/month. These are market planning ranges, not GDS Technology prices. A co-managed arrangement assumes the firm retains some IT responsibilities, so compare who handles each task rather than assuming two proposals offer equivalent coverage.
For either model, ask whether licensing, after-hours support, project work, incident response, and vendor coordination are included or separately scoped. Compare the exclusions and responsibilities as carefully as the monthly figure.
Review onboarding charges, minimum terms, notice requirements, project rates, documentation, credential ownership, and the process for returning records and configurations. A longer commitment may fit once the firm has evidence that the scope works. Month-to-month can provide room to evaluate the relationship, but it still needs clear terms.
Compare equivalent coverage and exit obligations, not contract length by itself.
Looking for local help? We've covered this for Norcross.
More on this from Riser Management: Access Agreement Administration | Riser.Management by GDS.
Frequently Asked Questions
Can a law firm use month-to-month IT support during onboarding?
Yes, if onboarding responsibilities are documented and the firm retains control of approvals, access, and deadline escalation. Agree on the systems in scope, who can authorize changes, and how unresolved risks are reported. A short contract does not remove the need for a deliberate transition plan or clear security ownership.
Is month-to-month IT more expensive for a law firm?
It depends on the provider's proposal and what the firm keeps in-house. Nationally, fully managed IT planning ranges are $100 - $250 per user/month, while co-managed planning ranges run $60 - $160 per user/month. These are market ranges, not GDS prices. Compare coverage, licensing, projects, and exit terms.
What should a law firm test before signing a longer IT agreement?
Test how staff report deadline-sensitive issues, who approves matter access, how new hires and departures are handled, and what evidence supports backup recovery. Review communication and ownership during actual service interactions. Ask for unresolved risks and dependencies in writing so firm leaders can make an informed decision about a longer commitment.
Can we leave a month-to-month IT provider without losing access to our systems?
That depends on account ownership, documentation, credentials, licensing, and the written transition terms. Identify who owns each subscription and retain appropriate firm-controlled administrator access. Before signing, agree on notice, cooperation during handoff, return of records and configurations, and how provider access will be removed.
Follow GDS Technology on Facebook, and subscribe on YouTube for new videos.
