See how Projects fits into the full picture.
### Why manage your projects inside Wonderly Your sales team already captured the client details, scope, and contract terms in the CRM. When you create a project from a closed deal, that information carries over. Your delivery team picks up exactly where sales left off. Here's what that looks like in practice: **Centralizing all your work.** Every input is connected to the information that makes it actionable: * Tasks show what needs to be done * Milestones show what phase the task belongs to * Blockers show what is preventing a task from starting * Assignee show who is responsible Team members open the project and see what is assigned to them, what is due, and what is blocked. Managers see who is working on what and what is behind. **Building reusable templates.** Your process stays the same from client to client. What changes is the client's goal and scope. Templates let you standardize delivery so every client receives the same level of service. Wonderly lets you build templates at every level: * **Project templates:** the full structure including milestones, tasks, and settings * **Milestone templates:** a single phase of work with its tasks and optional dates * **Roles:** placeholder assignees you map to team members when the project starts **Where do I start?** Template the project you deliver most often. If you run the same type of engagement for most clients, that is your first template. **What if my process isn't perfect yet?** It doesn't need to be. Create the template based on how you deliver today. As you learn what works and what doesn't, update the template. Every future project inherits the improvement. **Can my team use these?** Templates are shared across your team. Everyone follows the same process without rebuilding it each time. #### **Connecting sales to delivery** 1. **CRM to Projects.** When a deal closes, you create a project from the deal record. Client details, scope, and contract terms carry over automatically. Your delivery team starts with the full context from the sales process instead of chasing it down or asking the client to repeat themselves. Pair this with a project template and your team can begin work the same day. 2. **Projects to Client Portal.** You choose which tasks, milestones, and updates your client can see through the Client Portal. Clients check progress on their own time instead of waiting for a status call or email. You can assign tasks directly to clients when you need input, approvals, or assets. Both sides see what is outstanding, so nothing gets held up waiting for unclear expectations. If a milestone is delayed, update the portal with context before the client asks. 3. **Projects to CRM.** Everything from the project stays connected to the client record: notes, files, and outcomes. When new work begins for the same client, the full history is already there. *** ### How to build your basic project components * **Every milestone has a clear outcome.** You can look at the milestone name and know what "Completed" means. * **Every task is specific.** "Website" is not a task. "Build homepage wireframe" is. * **Every task is owned.** Every task has an assignee, deadline, and duration. * **Dates and durations are set.** The deadline tells you when it's due. The duration tells you how long it takes. A task due Friday that takes 8 hours means something very different than one that takes 30 minutes. * **Blockers are defined upfront.** Your team knows what needs to finish before their work can start. * **Assignments are based on capacity.** Before assigning a task, check the Workload view to see who has capacity. Assigning work to someone already full is how deadlines slip. * **Your client sees what they need to.** Be intentional about what you share. Not every task needs to be visible to your client. Show milestones and key deliverables that give them confidence the project is moving. Internal tasks like "review contract template" or "sync with design team" create noise without adding clarity. If a task requires client input, make it visible and assign it to them so both sides know what is outstanding. Now that you know what good looks like, here's how to get started. ### Planning your project **When should you create a project?** Not every piece of work needs a project. A single action with one owner and a deadline is just a task. Create a project when work involves multiple people, spans multiple stages, or delivers something to a client. **Start with a Wonderly doc.** Before building your project, open a doc and outline the high-level plan: what are the milestones, who is involved, what are the key deadlines. Once the plan is clear, create your project and save it as a template for next time. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.wonderly.com/help/work-hub/projects-overview.md?ask=