CRM Implementation Plan Template
Four documents and four sheets that score the design against the tier's published ceilings and make every field name what reads it.
Free download · No account needed
Where the Ceilings Bind
The design, scored against the tier on the order form
Fenmore Instruments, 62 users, Sales Hub Professional. Checked in week two, from a design document.
| Constraint | Design wants | Tier allows | Verdict |
|---|---|---|---|
| Custom objects | 7 | 0, top edition only | FAIL, over by 7 |
| Calculated properties | 51 | 40 per account | FAIL, over by 11 |
| Deal pipelines | 6 | 15 | pass |
| Ticket pipelines | 3 | 15 | pass |
| Currencies | 3 | 30 | pass |
| Properties, largest object | 57 | 1,000 | pass |
Custom objects are not capped here, they are absent
The instinct is that a limit means a number. On this tier it does not: the feature is gated to the top edition, so a design holding seven of them cannot be built at all. Neither failure needed a sandbox, a solutions engineer or a configuration attempt.
The passes matter as much. Six pipelines against a ceiling of fifteen is what made the remodel possible, because a team that believes pipelines are scarce invents custom objects to avoid spending them.
Every CRM implementation plan you can download is the same six phases on a Gantt chart: discovery, configuration, data migration, testing, training, hypercare. Underneath it sits a requirements checklist that only ever grows, because a requirements process has no mechanism for saying no. Ask eleven stakeholders what they need and you get the union of eleven wishlists. So the design is finished when everybody has been heard, which is a different condition from the design being buildable.
Two checks make it buildable and both are arithmetic. Fenmore Instruments proposed eleven objects, seven of them custom, on a tier where custom objects require the Enterprise edition rather than being capped at some number. It proposed 51 calculated properties against a published ceiling of 40. The design was infeasible on the paper it was written on, twice, and both numbers were readable in week two. All seven objects collapsed onto standard ones, and every collapse made the design better rather than smaller.
The second check is the field budget. Every field names a requested report, a routing rule, an automation, or a gate at a stage, or it goes on a cut list with the reason attached, which is stricter than what a field dictionary records after the fact. 268 proposed, 96 cut, 177 final. Then run it backwards: 31 of 34 requested reports computed from the survivors, and the 3 that would not named 5 fields nobody had proposed.
What's in the pack
Object and Field Design
A row per field carrying either a named consumer or a stated cut reason, with calculated fields counted separately against their own ceiling.
Integration Map
One row per connection with the match key, the no-match behaviour, and exactly one named system owning every field a two-way sync can write.
Test Cases
Cases derived from the business workflows with the performing role on each, plus the permission and required-field variants suites usually omit.
Open Decision Log
Every design question with what it blocks, the rejected option, a decider and a date, so an unknown is visible rather than absorbed into the build.
Implementation Design
The document the configuration gets transcribed from: object model, field budget, required fields per stage, and what the design deliberately does not do.
Object Model Note
The argument for each collapse, one object at a time, with what it costs and the reporting it makes possible written next to each other.
Where the Ceilings Bind
The scorecard: what the design wants against what the tier allows, the failures with the amount they fail by, and the passes that stop bad workarounds.
Go-live Criteria
Thresholds with named signers, the decider by name, the exception mechanism, and the written consequence of a no-go so somebody will call one.
How to use it
- 1
Open in River, or take it blank
Open the pack in River and hand it your report list, or download the Word documents and CSV sheets and score the design yourself.
- 2
Send the tier and the report list
The exact tier and edition, plus every report and dashboard the business asked for and who asked for each one.
- 3
Score before anything else
The published ceilings say whether the design can be built at all. A failure here invalidates work on the field list, so it goes first.
- 4
Run the consumer test both ways
Forward produces the cut list with a reason on every row. Backwards produces the fields nobody proposed, which are the valuable ones.
Frequently asked questions
Is this template free?
Yes. The zip is Word documents and CSV sheets, no account and no card. Edit with AI is the optional half: the agent scores your design against the tier and fills the sheets. The rest of the packs are in the template library.
What format are the downloaded files?
Word (.docx) for the four documents and CSV (.csv) for the four sheets, zipped together. Excel, Numbers and Google Sheets open the sheets straight off the download, and the design documents open in Word or Pages. Nothing needs converting.
Does this work for a CRM other than the one in the example?
Yes. Both mechanisms need a published limits table and a report request list, and every major CRM publishes the first. The worked example uses one vendor because its per-tier ceilings are documented plainly enough to cite.
Where does the data migration and testing fit?
It is the next piece of work and a different artifact. This pack ends at the go-live decision. The system migration plan sizes the freeze window, and the field mapping pairs the source columns to the fields this design kept. A dedicated UAT plan scores every workflow before sign-off, and the software rollout plan gets the team using it afterwards.
We have already configured half of it. Is this too late?
No, and the ceiling check is worth running first anyway, because it takes an hour and can invalidate work in progress. Run the consumer test against what exists: a field at 60% blank in month three is the same finding arriving more expensively.
Why does this insist on so few objects?
Because a custom object arrives with no native reporting, no permission model, no association labels, no mobile layout and no third-party support, and all five get rebuilt or done without. Six of the seven here collapsed onto objects that already had them.
What does 'Edit with AI' actually do?
It signs you up, installs this pack as a private workspace, and puts the agent in front of the four sheets with nothing in them. Send the tier, the report list and any draft field list, and the first thing back is the ceiling scorecard.
Find out whether your CRM design can be built
Take the Word documents and CSV sheets blank, or open this exact pack in River and get the ceiling scorecard back first.
Edit with AI