At a high-level, I would suggest considering the following:
- Leverage our google forms or type form Recipe Builder Integrations to solicit the critical elements of your client’s desired onboarding.
- The client’s selections will be marked in the associated task notes, and the task will be marked DONE.
- Have a 2nd recipe that parses those client inputs to dynamically build the client milestone/task experience desired!
We’ve found success in creating a master template to which we add secondary templates which contain less frequent tasking. Our Master Onboarding Template contains the lion’s share of tasking which is common amongst all of our customers. Given that each customer is unique in our industry, we have other templates that we can incorporate into our Master Template that help us reduce the reproduction of tasks that arise infrequently. I am very excited to learn more about Recipe Builder and learn how we can incorporate more automation and connectedness between our various templates.
It may not be the industry best practice, but we are nimble. If there is something better we’ll adapt and make it better as soon as those efficiencies become clear.
We have built some templates with a bit of everything we might need for different clients. Once the project is started, and templates are selected, we usually go thru the tasks and remove, hide, or mark N/A to a few tasks to trim down what the client will see… before inviting them.
This gives us ease of use without creating too many customized templates, but customize a bit on the fly - as the project launches.