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
| Request or recurring problem | Who is affected? | Business consequence | Deadline | Evidence of the current problem | Acceptance check |
|---|---|---|---|---|---|
| 1 | |||||
| 2 | |||||
| 3 |
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.
| Workstream | Internal owner and available capacity | Missing skills or cover | Proposed external contribution | Scope and acceptance check |
|---|---|---|---|---|
| Daily user support, cases and sales processes | ||||
| Internal service targets and customer commitments | ||||
| Integration repairs or development to reduce manual work | ||||
| Relevant platform changes and release testing | ||||
| Documentation, review and absence cover |
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
| Measure | Starting position | Evidence at review | Decision |
|---|---|---|---|
| Important unresolved requests and their age | |||
| Agreed changes accepted | |||
| Repeat problems or reopened work | |||
| Investigation/delivery/test/handover time | |||
| Internal coordination time | |||
| Usable documentation and retained knowledge |
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 or discuss your two most pressing problems.