Skip to content
ON PLATFORM SINCE 2011 · CASPERLOGIC FOUNDED 2019
+91 8861685544 [email protected]
casperlogic
Book a working session
casperlogic
Services Expertise Insights Company
Book a working session
Home/Services/Managed Services

We run the org so your team can get on with the business.

A named team against your backlog, published SLAs by severity, and a monthly report you can forward upward without editing it.

Most managed-services contracts are sold on response times and judged on something else entirely: whether the org is in better shape in month twelve than it was in month one.

So we report on both. You get the ticket numbers, because you need them. You also get a monthly read on limits, technical debt and the things nobody raised a ticket for — which is usually where the next outage is coming from.

A support contract that only ever closes tickets is a treadmill. The point of a named team is that the number of tickets should go down.

SCOPE

What the engagement includes

A named team, not a queue
The same engineers month to month. They learn your org once and keep that knowledge, instead of you re-explaining it to whoever picks the ticket up.
SLAs published by severity
Response and resolution targets written down before you sign, not negotiated per ticket while something is broken.
A monthly org-health report
Limits, technical debt, failed scheduled jobs and outstanding security items — written so you can forward it upward without editing it first.
Release-window regression testing
Three Salesforce releases a year. We test your critical paths during the preview window, before they reach your users.
A backlog you prioritise
You decide what matters, we estimate and deliver. No change-request theatre for a job that takes two hours.
An exit that is not a hostage situation
Everything we build is documented and in your repo. If you take it in-house we will help you hand it over properly.
PROCESS

How we work

01
Org read
Ninety minutes in your Setup with an architect. We write down what we see, including the parts that are fine.
02
Onboard
Access, runbooks and escalation paths agreed in writing. Your backlog imported and estimated so month one is not spent scoping.
03
Run
Tickets, changes and releases handled against the published SLAs, with the same named engineers throughout.
04
Review
A monthly report and a call. What we fixed, what we found, and what we think you should do next.
FAQ

Questions we get asked

What is the minimum commitment?

Two months, rolling. Long enough that we can learn the org and you can judge whether it is working, short enough that you are not trapped if it is not.

Do we have to move all our support to you?

No, and most teams do not. Plenty keep an in-house admin for day-to-day changes and bring us in for the work that needs an engineer — Apex, integrations, migrations, releases. We would rather share the org with a good admin than replace one.

What is actually in the monthly report?

Org limits and how close you are to them, technical debt we hit that month, failed scheduled jobs, outstanding security review items, release changes that affect you, and burn-down on the backlog. Roughly two pages, written in English.

ALL SERVICES
casperlogic
Not sure you need this much?

Tell us what breaks and how often. If a half-day of fixes would do it, we will say so.

Book a working session
Org-health report — samplePDF · 4 KB
NO SLIDE DECK, NO DISCOVERY INVOICE

Let us open Setup and tell you what we actually see.

Ninety minutes with an architect who has shipped on this platform since 2011. You leave with a written read on your org whether or not you hire us.

Book a working session See what we do