# Monthly Salesforce Support Decision Worksheet

Use this worksheet to decide what help to buy. This is a planning aid, not a service agreement or a tested result.

## 1. Define the work

<div class="table-scroll">
<table>
<thead>
<tr>
<th>Request or recurring problem</th>
<th>Who is affected?</th>
<th>Business consequence</th>
<th>Deadline</th>
<th>Evidence of the current problem</th>
<th>Acceptance check</th>
</tr>
</thead>
<tbody>
<tr>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>2</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>3</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
</table>
</div>

Which requests are possible defects in previously accepted work? Which are new requirements? Which recur?

## 2. Compare the models

Evaluate an internal administrator, monthly support, a hybrid arrangement, a scoped project and ad hoc help against the SAME workload.

- What skills and usable capacity are required?
- Who understands the business and can approve priorities?
- What internal coordination, testing and decision time is needed?
- What total cost assumptions are supported by actual quotes or internal figures?
- What work is excluded from each option?
- What would cause you to change models?

### If you already have an internal admin or developer

License count is context, not a staffing rule. List the work your internal team covers today and the work that keeps waiting.

<div class="table-scroll">
<table>
<thead>
<tr>
<th>Workstream</th>
<th>Internal owner and available capacity</th>
<th>Missing skills or cover</th>
<th>Proposed external contribution</th>
<th>Scope and acceptance check</th>
</tr>
</thead>
<tbody>
<tr>
<td>Daily user support, cases and sales processes</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Internal service targets and customer commitments</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Integration repairs or development to reduce manual work</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Relevant platform changes and release testing</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Documentation, review and absence cover</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
</table>
</div>

Which tasks recur enough to justify monthly capacity? Which need a separate project? Who owns priorities, connected-system decisions, testing and sign-off?

## 3. Agree the operating rules

Record proposed answers before accepting a monthly arrangement:

- Monthly hours and fee; minimum increments; meetings and administration.
- Investigation, testing, documentation and deployment time.
- Unused hours, expiry or rollover, overages and approval authority.
- Working hours; acknowledgment, assessment and delivery expectations.
- Emergency needs and how they will be covered.
- Delivery owner, internal decision owner and acceptance owner.
- Location of current configuration/code records and usable documentation.
- Who handles connected systems and Salesforce vendor support cases.
- Cover for an unavailable consultant and arrangements for handover.
- Review point, cancellation and any transition work.

## 4. Evaluate results

<div class="table-scroll">
<table>
<thead>
<tr>
<th>Measure</th>
<th>Starting position</th>
<th>Evidence at review</th>
<th>Decision</th>
</tr>
</thead>
<tbody>
<tr>
<td>Important unresolved requests and their age</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Agreed changes accepted</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Repeat problems or reopened work</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Investigation/delivery/test/handover time</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Internal coordination time</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Usable documentation and retained knowledge</td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
</table>
</div>

Separate estimated time released from cash savings. Record unknowns rather than filling them with optimistic numbers.

## 5. Choose the next step

Continue, change the allocation, train an internal owner, commission a bounded assessment, scope a project or stop. Record the reason, owner and next review date.

[Read about Logic Conduit's monthly Salesforce support](https://logicconduit.com/salesforce-managed-services.html) or [discuss your two most pressing problems](https://logicconduit.com/#contact).
