Professional Services Client Hub Template
Share
Explore
Professional Services Client Hub Template

icon picker
Proposal

Our expert Solution Architects help you build your WorkOS — a work operating system that brings together business operations — within Coda so that your team can collaborate in one unified surface across words, data, and apps.
Together, we create unique ways to run the business, design rituals that help teams work, and transition your current tools and process to increase productivity and quality of work. Learn more about the
Solution Studio
⁠
and previous client solutions we’ve co-created.
⁠
Methodology.png
⁠
⁠
Challenge
Client is currently...
A successful implementation of Coda at
Client Name
⁠
@Client Name
⁠
will [TODO]
Solution
There are key use cases to cover during this project:
Do X
Do Y

⁠
[Template] Client Workflow and Schema - Client Workflow.jpg
⁠
⁠
[Template] Client Workflow & Schema in
Miro
⁠
⁠

Key Areas of Value
User adoption
Lift
Minimizing time
Stakeholders & Onboarding
The core project stakeholder group at
Client Name
⁠
will include:
Search
Person
Title
Role
1
​
​
👑 Product Owner
🚶 Project Lead
2
​
​
🔨 Maker
3
​
​
💡 Key Stakeholder
No results from filter
⁠

Search
User Type
Note
Number of users
1
Program Manager
​
15
2
Executive
​
5
3
Cross functional stakeholders
​
30
4
Team
making updates
100
There are no rows in this table
150
Sum
⁠

Given [TODO: DEFINE PRIMARY BUILDER AT COMPANY] prior experience building Coda docs, they are assumed to be the primary participant in co-creation (primarily in the design and solution direction) of the doc and the focus of training during hand-off of the doc.
Coda leverages a “train the trainer” approach to user education, enabling key champions with self serve material and a deep understanding of Coda’s building blocks so they are best equipped to manage the solution long term. Coda will work with workspace owners and Coda champions during the course of the project to guide Coda implementation, and to educate stakeholders on key choices in the process. Once ready for launch, Coda will assist with the development of self-serve documentation on how to use the doc. This may include:
In-doc FAQs and instructions for new collaborators
Doc schema architecture mocks to show key workflows within and between docs
Access to Coda’s Learn Doc and associated resources.
Timeline
We expect these activities to take place over a
34
⁠
working days if we kickoff
3/1/2022
⁠
⁠
View of Milestones
2
Stage
Milestone
Description
Start (Est)
Dur.
End (Est)
Runs parallel with
Architecting ✍️
Deep dive
We’ll dig into the how things currently operate - what works and what doesn’t in the existing set up. Then we’ll visualize the ideal future together.
3/1
5
3/8
​
Product roadmap — Prioritize features for each version
Once we have a baseline, we’ll go through our feature backlog to determine what we’d like to launch in each iteration.
3/8
1
3/9
​
Integration/ecosystem discovery and roadmap
Map out current/desired integration functionality
3/8
1
3/9
Product roadmap — Prioritize features for each version
Building 🧩
Doc Co-Building - Prototype
Design & Implement user experience to make key workflows (such a creating new _____) straightforward for key audiences and users of the doc.
3/9
6
3/17
​
Feedback
Gather feedback on implementation for improvement in version 2
3/17
2
3/21
​
Doc Co-Building - V1
Design & Implement user experience to make key workflows (such a creating new _____) straightforward for key audiences and users of the doc. (2x doc building sessions).
3/21
7
3/30
​
Prioritize Remaining Requests and Issues
Determine what items from the user testing have to be done in the final days of the project.
3/30
1
3/31
​
User Testing
Gather feedback on implementation for final changes to the doc.
3/31
3
4/5
​
Client Data Import
Client imports relevant data into the doc.
4/5
5
4/12
​
Launch 🚀
Enablement resource creation
Create resources for onboarding new users to the doc, as well as other resources identified by Coda Champions as supporting doc usage
3/31
5
4/7
User Testing
Transition 🔑
Closing Meeting, Final Questions, Documentation
Before the end of the engagement, we will meet to verify the work is satisfactory and answer any final questions. Any documentation will be provided before EOW.
4/12
3
4/15
​
⁠
[
Workflow
⁠
]

Timeline
2
Feb 28 - Apr 18
Architecting ✍️
Deep dive
Product roadmap — Prioritize features for each version
Integration/ecosystem discovery and roadmap
Building 🧩
Doc Co-Building - Prototype
Feedback
Doc Co-Building - V1
Prioritize Remaining Requests and Issues
User Testing
Client Data Import
Launch 🚀
Enablement resource creation
Transition 🔑
Closing Meeting, Final Questions, Documentation
Feb 28
Mar 7
Mar 14
Mar 21
Mar 28
Apr 4
Apr 11
Apr 18
Deep dive
Product roadmap — Prioritize features for each version
Integration/ecosystem discovery and roadmap
Doc Co-Building - Prototype
Feedback
Doc Co-Building - V1
Prioritize Remaining Requests and Issues
User Testing
Client Data Import
Enablement resource creation
Closing Meeting, Final Questions, Documentation
⁠


Price
$X
All project fees are billed as fixed fee, payable in advance.
Assumptions [TODO: VERIFY CONTENT]
Doc Building
Coda Solution Architect will provide recommendations on the ideal architecture of Customer’s use case in Coda, based on information received during initial discovery conversations.
Coda typically engages clients in a “pair programming” approach for the actual doc development, such that Key Champions within the client are deeply familiar with the doc design and best prepared for supporting the doc internally.
Once project has concluded, Customer will be responsible for the long term support and maintenance of the created Coda documents.
Migration
Based on the requirements provided by the client, this proposal has been priced without any import of pre-existing data. Coda can provide best practices for migrating from tools like Google Sheets, but actual manual migration from existing tools will be owned by customer.
Though it is not anticipated to be necessary, Coda can provide basic information on usage of our Packs and API infrastructure for migration needs. Much of this can currently be found at
https://coda.io/developers/apis/v1
⁠
.
Integration
Customer will leverage Coda standard Packs and embed functionality to manage any integration with internal tools. Coda will provide guidance on best Pack or embed for a given use case, but will not develop any custom code or integration.
Comments
Feel free to add comments in the content itself or drop general questions, thoughts, or concerns in the table below 👇
⁠
Add Comment on Proposal
⁠
⁠
Search
Done
Question / Comment
Asker
Answer
Added
1
​
John Scrugham
​
6/15/2022
There are no rows in this table
⁠

Gallery
Share
 
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.